434 - PTR 4.2 recount 4.1.0a
What steps will reproduce the problem?
1. Using Recount, Bugsack and Bugsaq on PTR 4.2
2.
3.
What is the expected output? What do you see instead?
Normally recount will show damage
What version of the product are you using?
Recount-v4.1.0a_release.zip
Do you have an error log of what happened?
1x Recount-v4.1.0a release\Tracker.lua:907 bad argument #1 to "bit_band" (number expected, got string)
<in C code>
Recount-v4.1.0a release\Tracker.lua:907 in function "CheckRetentionFromFlags"
Recount-v4.1.0a release\Tracker.lua:994 in function "?"
Libs\CallbackHandler-1.0\CallbackHandler-1.0-6.lua:147 in function <Libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:147
<string>:"safecall Dispatcher[21]":4: in function <string>:"safecall Dispatcher[21]":4
<in C code>
<string>:"safecall Dispatcher[21]":13: in function "?"
Libs\CallbackHandler-1.0\CallbackHandler-1.0-6.lua:92 in function "Fire"
Recount-v4.1.0a release\Libs\AceEvent-3.0\AceEvent-3.0-3.lua:120 in function <Recount\Libs\AceEvent-3.0\AceEvent-3.0.lua:119
Locals:
nil
Please provide any additional information below.
| User | When | Change |
|---|---|---|
| Requital | Jun 21, 2011 at 14:43 UTC | Create |
- 1 comment
- 1 comment
- Reply
- #1
Requital Jun 21, 2011 at 14:49 UTC - 0 likesedit line 977 of Tracker.lua to:
function Recount:CombatLogEvent(_,timestamp, eventtype, hideCaster, srcGUID, srcName, srcFlags, srcFlags2, dstGUID, dstName, dstFlags, dstFlags2, ...)
Problem is semi fixed with that seems just some new flags.