Nameplate Threat/aggro highlighting inverted past 1.13.2.6 version (classic)
TobalJackson opened this issue ยท 9 comments
Hello,
Beyond version 1.13.2.6 the aggro status (red border/tick marks around enemy nameplates) has been inverted. Up to this version, the nameplate highlighting (red ticks) indicated when you had aggro, and monsters not targeting you did not have the ticks/red highlighting.
Beyond this version (confirmed in 1.13.2.13 or .16, can't remember which) this highlighting only applies when monsters are NOT aggroed/targeting you, making battles in a party very confusing.
I know .16 had some inaccuracy issues regarding the threat color where it would show the wrong state. But I've not heard nor seen any issues with it being permanently swapped, I would suggest you try a newer version and see if this issue still persists for you.
Will try updated version, waiting to get into queue, I have the same problem that recently started within the last day or so.
I must have updated through Twitch app, that seem's like that's when it went haywire.
edit: problem is persistent with update
It doesn't make sense that it would work in .12 but not in .13. Beyond this it could make sense as I implemented a threat lib and that might be reporting the threat differently for some classes. But I highly doubt that is it.
But just for my sanity, because I can't replicate this, you aren't tanks are you? And your Threat Mode under Threat & Highlighting isn't set to Tank?
Because it being blue while having aggro is intended behavior for tanks if your threat mode is either set to Auto or Tank.
The auto mode counts you as a tank for things like bear form for druids, righteous fury for paladins, and if you are in defensive stance or have a shield for warriors.
Tried newest version, and it still seems bugged as originally described. Seems like latest version that doesn't exhibit bugged behavior is 1.13.2.12-classic
It doesn't make sense that it would work in .12 but not in .13. Beyond this it could make sense as I implemented a threat lib and that might be reporting the threat differently for some classes. But I highly doubt that is it.
But just for my sanity, because I can't replicate this, you aren't tanks are you? And your Threat Mode under Threat & Highlighting isn't set to Tank?
Because it being blue while having aggro is intended behavior for tanks if your threat mode is either set to Auto or Tank.
The auto mode counts you as a tank for things like bear form for druids, righteous fury for paladins, and if you are in defensive stance or have a shield for warriors.
yes, I am a tank, druid tank to be exact.
for a while, if i HAD aggro, it was red, which I am use to and preferred, being blue when I have aggro is throwing me off. How would I switch it back to red = aggro and blue = not aggro?
In your profile settings it's under Threat & Highlighting > Threat Mode, and just set that to DPS/Healer. And it will be red when you have aggro and blue when not.
I've never changed this setting though I believe I've seen it set to Auto. I also play a druid, however when I was testing this with the latest (1.13.2.22) I'm almost certain the behavior persisted while in cat form. However I won't be able to play for another 6 hours so I will test this and this mode setting then.
As an addendum, I didn't know the modes existed, however I think this inversion makes sense for tank form vs DPS form, but I didn't know that it existed. Thanks for the information.