Damage from Fire Elemental Totem not shown
Bigmike4470 opened this issue · 8 comments
Game and Details! version
WD 10335 RELEASE 3.4.0
Describe the bug
- Steps to Reproduce (what did you do to make the bug happen):
When Fire Elemental Totem is used, damage from the guardian is inconsistently reported by the addon. - Result (what happens when you follow the steps above):
Some fights when the totem is cast damage from the Elemental is shown under pets, sometimes it is not. On fights where details does not show damage from the elemental it does show in warcraftlogs. - Expected (what you think the expected behavior would be when following the steps):
Damage from the Fire Ele should be reported as pet damage. - When the bug started (a date, wow path release, details update, etc)?
Started noticing about a week ago. - Additional information:
Lua Error
Post here lua errors, if you aren't getting any, use /console scriptErrors 1
Screenshots
Post images of the bug if necessary.
Here is a screenshot of expected behavior
Here is a screenshot of a fight where Fire Ele Totem was cast but no damage from the Elemental is shown
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.
Other Information
If necessary, add more info here.
Anecdotal but every shaman I know has been complaining about this, not an isolated incident.
Ver 3.4.0 10337 (core 148)
Issue persists. It worked for me on a few fights, but not on all. I suspect it happens when there are multiple Shamans with Fire Elemental up at the same time.
I believe a fix should be implemented in the most recent alpha. Would you mind testing?
Oh sorry for not clarifying, this is an issue on Wrath Classic, not Dragonflight. In Wrath, Fire Elemental Totem is the name of the spell in the spellbook.
I believe a fix should be implemented in the most recent alpha. Would you mind testing?
Thank you, was able to find it on curseforge. After some limited testing it does seem like this issue is resolved on the latest alpha. Will try and do more testing with larger sample size to confirm.