I've noticed plenty of bosses in Ulduar that don't "resist" FD, but it simply doesn't work. Razorscale definitely doesn't like our FD. Does anyone know which ones it does work on, consistently? Also, I've had it not work on quite a few trash mobs as well. And yeah, I generally wait for my DoTs to fade, don't FD directly after an Explosive Shot, and I try to stay down at least a few seconds.

The reason Razorscale is immune to FD is not an actual bug i think; it's part of the encounter. In phase 2, he puts a stacking debuff on the tank which, if stacked high enough, means he won't be able to build any more threat (or use taunts). Razorscale can be taunted, and should be taunted by another tank when the first tank has too many debuffs. This is the way Blizz designed this encounter, but since so many guilds can kill Razorscale 50-0% within a minute, we hardly notice these mechanics. Since the boss can be taunted, the only way Blizz could make threat an issue (even though it is a non-issue at the moment) is by making FD not work on Razorscale.

Is this confirmed by any blue posts or such? Seems like a flawed move, since mages Invis. work afaik.

Blizzard is generally pretty open about bosses with an "interesting" mechanics like this. If it were such that threat dumps didn't work on the boss, we would probably know about it by now, and it would be part of strategies. But I've seen locks and mages dump threat on Razorscale, so I'm fairly confident that FD not working is a bug. However, waiting for a blue post is probably the best option.

I haven't noticed FD not working on any boss but Razorscale, but my guild hasn't gotten to Vezax or Yogg'Saron yet, so I can't speak for those two.

Confirming this, the same kept happening to me yesterday night when we were learning the encounter, first time there on 10men normal mode.
Together with this, I noticed strange issues with Misdirect. I was in the team heading for the tunnel section (two minibosses) and I always kept MD ready to charge up our warrior tank when nuking Acolytes.
What was happening is that I was using MD on the tank, then shot e.g. one Acolyte (Aimed - Auto - Steady), and 100% of threat went -always- to me. Together with Feign Death not resetting threat that gave me some work to do, basically much nukenukenuke->Disengage->nukenukenuke action. Thank god for Aimed.

Anyone else confirming this?

I was just in the gauntlet on Thorim last night, and Misdirection and Feign were both working just fine. In particular I remember misdirecting some loose adds to the tank, and feigning off some aggro when I pulled.

Small chance these things could have happened just when the tank was taunting, but on the several attempts we did, I didn't notice anything funny at all.

Was it the Arena or the Tunnel section?
Also, I wonder if it was my warrior tank's Vigilance messing things up.

The gauntlet in the corridor, not the arena.


EDIT: I just went to look through our WWS, and it looks like significant portions of the gauntlet's logs are absent, so I can't determine whether or not what I saw was merely well-timed taunts. On our fourth run we switched tanks and the gauntlet tank was the one doing the WWS, but I did not directly observe Misdirection or Feign making a difference on that attempt. Feel free to take a look at that though and see if you notice anything:

Wow Web Stats


One thing I noticed which is of a completely different topic is how Misdirection seemed to be applying. Here:

Wow Web Stats

On both Misdirections, the buff did not fade from the tank until three actual damaging abilities had gone off; although debuffs were also applied, Aimed Shot and Explosive Shot. In fact, it faded from the tank the very moment the third damaging ability hit. However, it fades from me shortly before the third damaging ability landed. This leads me to believe that the Explosive Shot debuff does not actually consume a Misdirection charge; Misdirection simply fades from the hunter as soon as the shot is fired, before it lands.

Interestingly enough, observing the time between Misdirection fading from the hunter and the shot landing actually gives us a way to determine exact flight times for shots; or maybe not, considering that the Explosive Shot debuff seems to apply fractionally beforehand.

I would like to retest this, however, considering that both times in the linked report, the third shot fired was Explosive Shot. Observing that another shot has the same result of Misdirection fading from the hunter, travel time elapsing, and then Misdirection fading from the tank the moment the shot lands, or otherwise, would provide a final answer.

It seems that abilities that aren't on the bar will randomly get turned on or off whenever your pet is summoned. For me, it usually only happens at the start of the raid, and once I correct it, it's not a problem for the rest of the night. Just check your pet's spellbook before your first pull of the night and it should be fine.

I have also seen this issue recently but only after I respec'd pets due to primary/secondary spec changes on my part and growl & cower fell off the pet bar. Once I put them back, I have had no further problems with auto turn-on/off. I guess Blizzard haven't fixed that bug they way the 3.1 patch notes claimed.

I can report that it is an awfully nice fact that Feign Death does not work on Constrictors during Yogg while Ice Block, Pally bubble, Vanish, etc all work. And, unlike those others, Feign Death will not prevent targetting of Mind Control, Corruptor spells, or that Shadow Volley.

Feign will break the cast, yes. But it doesn't prevent further spells being cast on you. Can't explain why but on a wipe, you can just drop and lay there and you'll still get nailed. You might want to double check, as will I, on Vanish and Constrictors because it is standard operating procedure for our rogues, along with the rogues of our competing guilds, to blow it should they get constricted on the way to portals.

I'll add the normal addendum that I reserve the right to be grosely wrong

Vanish provides a (very) brief immunity due to auto attacks otherwise breaking it near instantly in many cases.

The way bosses target their abilities appears to be based solely on the target player being alive and not 'immune'. I believe vanished rogues can be targeted just as feigned hunters can.

I realize this is not much to go on, but has anyone noticed any kind of weirdness with Auriaya? Last night I was simply unable to use arcane shot for some reason, for a period of time. Would not let me use the ability, would not invoke the CD/GCD. It was as if I was not facing her, except that I was able to cast every other ability. I ended up firing an arcane shot at a defender, then was able to use it on Auriaya when it came back up.

This parse seems to suggest I had a problem with auto shot a couple weeks ago too. My GCD usage seems to match the other hunters, but auto shot is way lower. Again, if directional facing was an issue I don't know how I would have been able to get special shots off.

Maybe I'm just missing something obvious to everyone but me, but with these two examples I don't feel like I can write it off as simply a UI issue or a logging issue yet.

Yeah, I had that problem as well, we determined it was just some freaky lag....other classes were also having single abilities locked out, it was indeed weird.

I had the same Arcane Shot "lockout" happen on Onyxia a week ago, so you are not alone with this problem.

I experienced a similar issue volleying trash after razorscale had returned to the air. Until I targeted an add & fired a shot at them I could not cast volley under any conditions. My theory at the time was some sort of range bug - I still have razorscale targeted but she was out of range and so I was assuming that was causing the shot to "lock" somehow - but perhaps blizzard has managed to find some new, wierd way of breaking things

I've seen the same issue on Volley. It does a range check if you have something targeted even though it shouldn't matter. Target something in range or target nothing and it works fine.

I noticed a simular ranged problem last night on Xt when the heart spawned I was around 15 yards away but i had to move a further 10 yards to be able to shoot it atall. Same positioning as ive always been in and never had this problem before!

Heart of the Deconstructor has a very strange hitbox, even melee can have a hard time attacking it at times.
Thus, if there's a bug with skills locking out that's linked to range checks, Heart of the Deconstructor is not a good test case, due to it behaving abnormally.

I just had an issue with XT last night, although it wasn't during a heart phase. I couldn't use any of my shots other than auto and steady, it kept telling me "Invalid Target".

After a profuse amount of cursing, relogging fixed it. As an added note it was 10 man Ulduar.

Are you using macros for your shots, and if so do they somehow differ for Steady Shot and the shots you have locking issues with? E.g. [harm] [target=something], etc.
Has anyone experienced these problems while running with default Blizzard UI?