Should already be in.

Mobs that melee do not hold aggro through BoP unless there is a taunt involved. Period. This leads me to believe that nightbane is completely whacked. (and it may also be the reason that some rumors say you can tank nightbane without a fearward/warrior tank/shaman)

Yup. I completely agree. Something truly bizarre was happening.

Edit: It's possible that Nightbane has a hidden Fixate ability of some sort to allow for tanking him without fear ward/tremor/warrior, and if there's a bug that results in him casting it on a non-tank (like, say, a rogue), then that could explain it (and the other Nightbane errors that have been reported).

Wish I could give you more details, but it seemed on Bloodboil, the first attempt of the night it was fine, but after that it was off by a lot. Hopefully I can try and figure out what is wrong sunday when we go back.

Please do; any info you can provide would be welcome.

Ha, exactly what I have encountered, and seeing that you pulled aggro while under 110% makes me feel a bit better about it, because I could have sworn that I didn't reach it either.

I don't think so. Nightbane just had landed, and I didn't touch him at that moment. I'm also not present on the Omen list and I have set 'always show self' to on, therefore I should have been visible if I did only 1 damage. I was just standing there, waiting for the tank to generate enough threat for me not to pull aggro.

Another related issue. When a tank dies and I have his threat bar pulled out, I get some really high % numbers:


Note that this might be not the correct display for the bug just described. This screenshot was taken while I had that bug where the tank didn't show up on Omen anymore, although being still alive.
It looks pretty similar of course, so it might just be the same.

I'm afraid I don't. Yesterday there was a shadow priest with a similar high amount of threat on VR, but unfortunately didn't check on him either.

Wednesday evening, me and a feral druid were tanking Gruul, both happily generating threat and making sure that I was always on top of the list. Everything was fine until the druid pulled aggro even though his threat level was about 20% lower than mine in Omen. Are there known issues regarding warrior or druid threat values or maybe even the Gruul fight ? How can I help ?

We both updated Omen around 9pm gmt+1 which would indicate that Omen was most likely using Threat-1.0 r44102.

The thing is, Lightning Bolt has traveltime, at max range, that approaches to 2 seconds or more, I can actually have 2 bolts in the row "in air" in some cases, and this makes both cleacast and Capacitor procs unreliable.

Nightbane's fear does not switch aggro, even if you're in range to get feared and resist and the tank does not resist, Nightbane will stick to the tank. Maybe he has a fixate-like ability that he uses on top threat?

Today during Al'ar (using Threat r44250) I Soulshattered at the beginning of Phase 2. It was resisted, but my threat was still halved on Omen. This shouldn't be!

I think I remember people other than the tank having aggro during a fear, when he forgot / was too late for berserker rage.

I still fight Nightbane regularly. He definately does not fixate. I tanked him on the phone last week and missed a fear at 18%, he gibbed the hunter then came back to me.

I also had a DPS warrior 2 nights ago who was #3 on threat behind a rogue suddenly have NB turn to him and stick to him until he was dead. Was just a bit short of the third flight and a good 40k threat behind me. But that's the only time I've had NB do something that didn't follow normal rules.

If a mob sticks to you and continues attacking you while you have BoP, while other players are not immune/feared/etc., something very unusual is happening. That is not normal aggro.

The only behavior I am aware of that will cause this to occur is a taunt. Either the player taunting the mob, or the mob forcing a taunt onto the player via Fixate. There's a good discussion of this mechanic in the Reliquary of Souls thread (last couple of pages of it) in the main forum.

I don't know of Nightbane doing anything like that either, but if he really was attacking you despite your immunity, that's not a threatmeter issue.

I would almost wonder if there's not a larger kink in the aggro system, rather than something fight specific. Twice last week I pulled aggro, swapped in a shield, and stopped attacking. Each time, the mob just kept beating on me until it got to 20% at which point I did what every good warrior does.
I'd been attributing it to getting a few sizable upgrades and having to relearn my threat generation, but perhaps not. Each time I checked the combat log and it would be a MH crit (both times, actually, and on some trash) or something, which shouldn't pull aggro from our tank.


EDIT: as an update, since going back I haven't seen problems, so chalk this one up to 1) me sucking and 2) gremlins

That would indicate you're over-reporting, or he's under-reporting. Have either of you noticed any oddities outside of Gruul?

I'm pretty sure it does, at least with a warrior tank. Our warrior uses macros to stance dance, forgot to set them up one day, missed the rage, and he beelined for a mage on the first fear.

My pulling aggro wasn't related to a fear or anything - just happily DPSing away in the 75-50% HP range and he decided to eat me. I was seriously shocked that he kept on beating on me through BoP.

Next patch Nightbane agros more.


He's starting to turn into the TBC Onyxia.

I've had a similar experience on gruul where I would be the feral offtank and a warrior would MT and I would pull aggro FAR before 110% (something in the region of 80-90%) I decided to keep my threat below 75% at all times for future gruul kills and I haven't pulled aggro since, still not sure as to what the issue is though. We'll be killing gruul today if there's some sort of debug mode or behind-the-scenes data collection that can happen, I'd be happy to get the info and give it to you.

I know I've mentioned this earlier -- I think that sometimes when mobs use secondary-target abilities, it can cause a real, temporary shift in who the "tank" is for aggro/stickiness purposes. So if Gruul goes to HS you, and the MT isn't 110% ahead of you, Gruul might stick. I know I've seen ranged classes on VR who clearly were below the tanks have VR target them for Arcane Orb, shoot an Orb, and then lock onto them for real aggro and run out after them. Almost every ranged aggro pull I've ever seen on VR has been preceded by an Orb on that target. I don't think that's coincidence.

Absolutely, and which is why I've been an advocate for removing the 110/130 Aggro Gain. We simply don't have our DPS push above the MT, which is rarely an issue to begin with against our MT's TPS. So few bosses don't have RSTS abilities where the mechanic doesn't break for us. "Playing safe" is more likely to produce kills for us than wading through unexpected player deaths, which lead to wipes.

Meh, I guess it's a sticky situation when considering the laymen. Layman can pass their MT by some degree of displayed threat without pulling aggro, or layman pulls aggro because of RSTS and MT pulses, while layman is below Aggro Gain. Both are bound to receive the "My displayed threat is wrong! Stupid addon!" There's no right solution I guess.

Mind if I ask when this happened?

Latest reports on Nightbane (one month old, at most) indicate that his fear no longer deaggros the tank. Also, tanked him as a druid this week, without fearward/tremor and had no issues. I fail to see why Nightbane would behave differently based on the class of the player tanking him.

The best explanation I've seen anyone come up with for these occurrances on Nightbane are that instead of reworking the fear mechanic on his Bellowing Roar to not switch away from the tank, Blizzard decided to add a Fixate-like debuff to Nightbane's list of abilities.

What is his ground AoE debuff called? The name eludes me now, but it uses RSTS. I would bet on targetting F'up on Blizzard's end due to Fixate(?) and this AoE effect coming up at the same time.


The Aggro Gain bars are fine in my opinion, they are there to report the expected threat value where you would absolutely rip aggro from the tank. However, it *should* be every player's responsability to understand that riding between the Aggro Gain bar and your MT's is threading on dangerous territory, which can cause undesired and unexpected events.

Last Tuesday, actually.

The RSTS is Charred Earth. I'd tend to agree that it's some weirdness with a Fixate, but I don't think he cast an RSTS around the time that I pulled and held aggro, either.