Details sporadically fails to detect damage
Travestii opened this issue ยท 4 comments
Before Start!
Make sure the bug also happen when Details! is the only addon enabled.
Checked.
Game and Details! version
Use /details to grab these two.
VCT 12819 RELEASE 4.4.0
Describe the bug
-
Steps to Reproduce (what did you do to make the bug happen):
The problem occurs consistently when I join dungeon groups using the random dungeon finder while playing my secondary spec (affliction warlock). -
Result (what happens when you follow the steps above):
Details occasionally fails to detect my damage. Sometimes entire combat segments are blank, in which case I don't appear on the meter at all. Sometimes only partial segments are undetected, in which case I appear on the meter but with inaccurately low damage. I have also seen instances where Details detects my abilities, but marks them all with 0 damage. In this case I appear on the meter with 0 damage done.
Damage of other party members appears to be correctly detected. Other players also report seeing me on their own meter with what appears to be correct damage numbers.
/combatlog detects (at least some of) the damage not detected by Details.
-
Expected (what you think the expected behavior would be when following the steps):
Consistent detection and display of damage. -
When the bug started (a date, wow path release, details update, etc)?
On 24 July I tried the affliction spec in the guild main raid. Since I wasn't pleased with my performance I started running some RDF for practice. I noticed the problem during these RDF runs. -
Additional information:
I have not noticed the problem while in my primary spec (demonology warlock). I don't yet have any data to know if the problem occurs in regular groups (guild raids etc.)
I have talked to a fellow guild member who also describes similar issues when using secondary spec in RDF. This is a hunter.
Lua Error
Post here lua errors, if you aren't getting any, use /console scriptErrors 1
Screenshots
Combat Log
Include a link to a combatlog file if the error is about not detecting a skill, usable item or item proc.
The log can be as simple as hitting a mob with white damage and using the item/skill.
WoWCombatLog-073024_101536.txt
Other Information
The attached screenshot is from the first trash pack after Helix Gearbreaker in Deadmines. Relevant timestamps:
7/30 10:18:35.135 UNIT_DIED,0000000000000000,nil,0x80000000,0x80000000,Creature-0-4458-36-22496-47296-000028A03D,"Helix Gearbreaker",0x10a48,0x0,0
7/30 10:19:10.772 SPELL_DAMAGE,Player-4476-038DD7F8,"Travesti-Gehennas",0x511,0x0,Creature-0-4458-36-22496-48420-000028A03E,"Defias Digger",0xa48,0x0,87385,"Seed of Corruption",0x20,Creature-0-4458-36-22496-48420-000028A03E,0000000000000000,31810,116235,0,0,0,-1,0,0,0,-290.69,-559.79,291,1.5708,85,4693,4692,-1,32,0,0,0,nil,nil,nil
Hey, update to version 12822. Make sure you're on this version using: "/details version".
When you see the bug happening, use the command: "/details pstate", it'll show a message on your chat, post here which message was.
You may also use: "/details debug" and tick the first checkbox, messages of entering and leaving combat should appear if things are correct.
When you see the bug happening, use the command: "/details pstate", it'll show a message on your chat, post here which message was.
STATE_REGULAR
You may also use: "/details debug" and tick the first checkbox, messages of entering and leaving combat should appear if things are correct.
I saw the messages while playing solo. Didn't notice them in RDF group though. (Maybe I was just too busy looking at everything else / maybe we didn't leave combat very often.) Nevermind, it's there.
I've seen exact same issue.
Version
VCT 12824 RELEASE 1.15.3
state is REGUAR as well
combat starts/ends fine
I'm playin on SoD classic, also Warlock as OP
EDIT:
On some testing - looks like it only happens when pet is attacking (and maybe attacks first?)
EDIT2:
When this happens details doesn't pick up my damage
And when I attack first I get this debug and details pick up damage
