Ah yes. Hmm. See, it reports all but 1 damage point as overdamage
9/11 16:42:16.653 SPELL_DAMAGE,0x000000000006755D,"Zakones",0x511,0xF1300079A80018D2,"Tattered Training Dummy",0x10a28,49238,"Lightning Bolt",0x8,3895,3894,8,0,0,0,1,nil,nil
3895 is damage
3894 of that is overkill
Unless these dummies have 1 health and die with each hit they should not report overkill.
Currently Recount removes overkill from damage dealt, but so far I was under the impression that overkill fields only ever are set for targets that died to a particular damage deal. One can temporarily disable that by replacing this line in Tracker.lua:
amount = amount - overkill -- Taking out overdamage on killing blows
with this one:
-- amount = amount - overkill -- Taking out overdamage on killing blows
Recount will then not remove overkills on killing blows but work correctly for target dummies. Are these dummies to stay for live? If yes I may have to remove overkill removal to avoid issues until the dummies report damage more normally.
The dummies are effectively immune to all damage, which is to say that you never really see their health fall below 100% (except where Blizzard forgot something). You and fifty battle-crazed friends can hit them all day, and they just sit there. There is also a heroic training dummy with appropriate to-hit attributes.
I assume they will be part of the final release. They sit in the sewers of Dalaran next to an Arena spot. You cannot gain weapons skill by attacking them, you can only test out your dps and combat rotation macros. They are super-handy and very much in context with the game and their location.
Saw them, the heroic one should work fine. The small one has 1 HP and apparently the combat log reports all but that 1 HP as overkill. Either I'll not support overkill, write special handling for this one case, or recommend that people use the boss one for tuning their DPS via recount. Not sure yet which is the most desirable option :P
we started a discussion on my guild's forum about Recount. Would you like to explain me
what "Owner Combat Time" and "Per Combat Time" are in the following formula (You posted it some monhts ago)?
I do not know why this happens. This is stuff that goes to the addon channel and should not be visible to you. If anybody has a clue what can cause addon channel whispers to become visible like this I'd be thrilled to learn about it.
For now you can try "/recount sync" to turn this off.
Hi, my boss segments option has been fairly sketchy for the past month or two, leaving out several boss encounters. How are these boss segments differentiated from non-bosses and how can I edit this list to ensure that recount splits the information correctly?
Off the top of my head the bosses that are not splitting correctly include Brutallus, Kil'jaeden, and Azgalor in enUS localization.
Assuming Recount dips into Babble-Boss or another library for this information, this problem would have started around the same time all the ruRU translations started being done, but with recent updates more bosses seem to be disappearing from the boss segmentation list.
Boss segmentation happens depending if a skull-level mob was part of a fight. It's independent of locale. I found it to work well up to brutallus at least.
Yea, I have no idea what is causing it then. Would it make a difference if I were the person initiating the pull? It's the only thing I can really think of. The bosses that don't seem to work are the ones I've been engaging first or ones with adds who are non-boss that start combat (KJ and Akama).
As long as the skull mob hits or is being hit by anybody in your group it will trigger the segmentation. Who pulled is irrelevant, also when people hit that mob is irrelevant. Akama works fine for me. Haven't had a chance to see KJ so cannot talk about that.