Make sure people having an Asterisk ( * ) ending their name delete their KTM and get latest Omen.

Nobody in the raid was using ktm, everybody had omen.

I had our tank do the full reinstall method using WAU, still no avail, had funky threat last night on Hydross, same behavior, generated threat as per normal, then about 20 seconds in, he falls off the meter. I've been running this guy through the ringer getting this straightened out, any other thoughts or information I can provide to get a fix.

On that note, has anybody noticed that people that aren't using KTM will get an asterick by their name occasionally? I'll try to screenshot it next time it happens but I've seen it happen on a handful of occasions now.

KTM handles Insignificance just fine unlike Threat/Omen, so that's not an issue

I guess it is a same thing that happens with threat freezes/resets - Omen fails to handle it's own version checks due to bugs in channel communications and starts thinking it is a KTM data.
Probably that could happen when someone relogs into combat.

Except if you don't have a master target set KTMs threat will be ALL sorts of messed up.

zapateria: I believe Nightbane has some serious bugs or unknown threat mechanic. See this thread for more info:

WoW Forums -> Nightbane Aggro Issues

It may not be relevant to Omen but there have been other reports of aggro issues after a Vanish and not just at Nightbane.

This thread: Aggro and Threat Management in End-game - Unofficial World of Warcraft Forums claims that Vanish at Magtheridon didn't appear to work, in fact it actually seemed to get the Rogue in question killed.
I dismissed this as being something else wrong but seeing an increasing number of reports like these could mean something serious is wrong.

Edit: the evidence for a problem relating to Vanish and getting aggro afterwards is, I admit, very scant. I myself have not experienced any problems of this nature yet I have to add.

Exactly, problems have been reported at Nightbane (encountered myself) and Magtheridon.
I haven't heard of other complaints except on these two bosses.

I've experienced the "Vanish and get eaten 10 seconds later" thing, too. Something is definitely borked.

Speculation: if a mob resisted the de-aggro aura portion of vanish only, would the behavior have been, as you remember it, accurate?

Happens when you do damage to certain bosses just as you vanish. Mag is a big one on this. Typically if you stop auto attack and let dots tick off then vanish it doesn't happen.

It's NOT intended, and is a known bug :P

Everything I've read on the matter leads to him having some sort of full/partial aggro dump at some point while he's in the air, but no one is sure as to when. It's the Ony deep breath of TBC in my opinion :P

Nightbane clears threat between phases. This is known, and handled. He exhibits behavior similar to a Fixate (mob sticking on a player regardless of threat levels), however, and I think it sometimes gets cast on a DPS, resulting in that DPS's death.

Have you got a reference to this from a reliable source? (Edit: sorry, that made it sound as if you are unreliable. I was looking for references for further confirmation of this problem)

The Vanish part can fail and you remain in combat but your Threat is always wiped. This is at least what the Blues have been telling us and what I have always seen in practice.
I have had Vanish fail as I have grabbed aggro but still had the mob turn back to the tank.
This has never worked otherwise, at least not until now.

The behaviour being reported is of Rogues Vanishing as a precaution to wipe threat prior to nuking with AR and BF. Well that is at least my take on the more coherent and complete replies in some of the Threads I have read. It is -after- this precautionary Vanish that the Rogue is getting aggro and being killed. It is almost as if Vanish is causing a threat spike (doubling aggro instead of removing it) for those bosses.

On Nightbane I was killed despite using Vanish.
Aggro -> Vanish -> Dodged -> Hit -> Dead

Normally the mob can land one attack on you when you vanished, but the health won't be substracted from your pool (happened multiple times, last example was Morogrim), but on this occasion Nightbane just kept beating on me and did NOT turn to another player.


// Edit
Here was the thread:
Random Magtheridon Issues [Merged]

I don't know if this is an already known issue, but I've also experienced non-threat-clearing-behaviour of Vanish. When I or any rogue I know happen to pull aggro on the Leotheras-fight ( while in demon-form ) and perform Vanish, Leo doesn't seem to be very impressed ( read: he keeps throwing fireballs at the rogue ) and he will continue to dislike the rogue until the tank manages to re-gain the aggro via his normal mechanics. This behaviour is reproducible, as it happens nearly everytime you "try" it ( at least 2 weeks ago, haven't been able to test it since then )

Ah yes, had that happen as well on our last wipe.

Tell your rogues to just Cloak and get clear of others, and soak a fireball or two till your warlock gets their act together.

Or better yet, just stop attacking before the demon transition.

I get that; I was asking because if you pulled aggro at an unexpected time (assuming vanish didn't remove your threat) it may have helped point toward some possible bug/mechanic. Alas, it continues to perplex.

There is a big difference between getting aggro, then Vanishing and then getting killed and Vanishing preemptively and getting aggro.
There are timing issues here which Blizzard acknowledge as being a problem which will not easy to solve. Vanish is not always reliable as a way of "giving" the mobs back to the tank in this situation, we all know that.

The problem I have been seeing reported is that a preemptive Vanish results in the Rogue getting aggro. This is an entirely different thing altogether.

Is it possible to show the aggro and self arrows on the left side as in former times?

Hm, no. That was the first time for me that Vanish didn't clear my aggro and the mob continued to beat on me (ever). The second time was Leotheras bombing me.

Maybe there were some reports of this behavior, but for me it hasn't happened before.