Recount

382 - Link to combat on forums

This link directs to comment about change to the combat log

http://blue.mmo-champion.com/topic/171721/41-combat_log_event_unfilter-changed

User When Change
XylanTrueheart Apr 27, 2011 at 01:22 UTC Create

You must login to post a comment. Don't have an account? Register to get one!

  • 2 comments
  • Avatar of Zidomo Zidomo Apr 28, 2011 at 17:08 UTC - 0 likes

    Update: the problem was the RecountDamageReduction plugin (from Curse) not updated for 4.1, as per the error message. Stop loading that (or "fix" it by adding hideCaster on the appropriate line), no further errors.

    RecountDeathTrack & RecountThreat - - which also have no new code for the patch - - haven't caused any bugs...yet. Still testing.

  • Avatar of Zidomo Zidomo Apr 27, 2011 at 05:27 UTC - 0 likes

    As a followup, the bit_band & nflags drycodes in the latest r1151/v4.0.1a release have failed to stop the error spew. After a few seconds of idle time after logging on in WoW 4.1 live with that version:

    		["message"] = "Recount-1151\\Tracker.lua:907: bad argument #1 to 'bit_band' (number expected, got string)\nRecount-1151\\Tracker.lua:907: in function `CheckRetentionFromFlags'\nRecountDamageReduction-v4.0.1 stable\\DamageReduction_Mode.lua:144: in function `?'\nCallbackHandler-1.0-6:147: in function <...onLoader\\CallbackHandler-1.0\\CallbackHandler-1.0.lua:147>\n<string>:\"safecall Dispatcher[14]\":4: in function <[string \"safecall Dispatcher[14]\"]:4>\n<in C code>: ?\n<string>:\"safecall Dispatcher[14]\":13: in function `?'\nCallbackHandler-1.0-6:92: in function `Fire'\nAceEvent-3.0-3 (Ace3):120: in function `OnEvent'\nStopAddonMessage-1.6.2beta\\core.lua:282: in function <Interface\\AddOns\\StopAddonMessage\\core.lua:211>\n(tail call): ?:\n",
    			["type"] = "error",
    			["time"] = "2011/04/27 01:03:42",
    			["session"] = 2441,
    			["counter"] = 5,
    		}, -- [997]
    		{
    			["message"] = "Recount-1151\\Tracker.lua:907: bad argument #1 to 'bit_band' (number expected, got string)\nRecount-1151\\Tracker.lua:907: in function `CheckRetentionFromFlags'\nRecountDamageReduction-v4.0.1 stable\\DamageReduction_Mode.lua:144: in function `?'\nCallbackHandler-1.0-6:147: in function <...onLoader\\CallbackHandler-1.0\\CallbackHandler-1.0.lua:147>\n<string>:\"safecall Dispatcher[13]\":4: in function <[string \"safecall Dispatcher[13]\"]:4>\n<in C code>: ?\n<string>:\"safecall Dispatcher[13]\":13: in function `?'\nCallbackHandler-1.0-6:92: in function `Fire'\nAceEvent-3.0-3 (Ace3):120: in function `OnEvent'\nStopAddonMessage-1.6.2beta\\core.lua:282: in function <Interface\\AddOns\\StopAddonMessage\\core.lua:211>\n(tail call): ?:\n",
    			["type"] = "error",
    			["time"] = "2011/04/27 01:03:42",
    			["session"] = 2441,
    			["counter"] = 26,
    		}, -- [998]
    

    They look the same but were recorded separately...heh. Probably another trigger a thousandth of a second later.

    Last edited Apr 28, 2011 by Zidomo
  • 2 comments

Facts

Last updated
Mar 30, 2012
Reported
Apr 27, 2011
Status
New - Issue has not had initial review yet.
Type
Other - Some other kind of issue
Priority
Medium - Normal priority.
Votes
1

Reported by

Possible assignees