Anyone else see the return of this bug? We have people getting one-shot by his auto-attack again.

I've seen it both on A'lar last week and Supremus this week. Fairly annoying to just be standing there minding your own business and then be randomly oneshot.

"Return of"? This bug has never gone away. Any mob with a charge like that, if its autoattack timer happens to be up when it charges, will take a swipe at its charge target.

I seem to remember the patch notes saying something about this being fixed.... though I don't have the particular note on hand.

We experienced this bug again last night as well. It's annoying to say the least.

Edit: Quoting Daelo's hotfix note from the official forums:

http://forums.worldofwarcraft.com/th...08411172&sid=1

Seems that the charge damage is what was fixed. I misunderstood the original fix as well.

They only fixed the damage on the charge, not the auto attack.

- During Phase 2 of the Al'ar encounter in Tempest Keep, Al'ar occasionally charges at a random player. The damage dealt by the Charge was severe enough to immediately kill a lightly armored target even if the player was at full health. We've reduced the damage done by this Charge ability.

edit: I'm slow :P

There was a hotfix with her charge that reduced the damage of it. That isn't to say the charge and swing timer can't sync up, it still can and always has. It is INCREDIBLY annoying, we had literally 7 phase 2 deaths from this last night and had a 5% bserk timer because we'd lost all our dps to something we simply could not prevent.

There is also no min/max range on it either, she's charge and killed a rogue in melee range and charged nearly accross the whole room to a caster and killed them, which is even more annoying because then she proceeds to cast flame buffet while there's nothing to can do to get back to her in time to stop it!

So to recap, this never was fixed, they simply reduced the damage on her charge ability in hopes that her melee wouldn't 1 shot you, which is absurd given how hard she hits.

Thanks for the responses. I guess I misunderstood the patch notes (or selective retention convinced me that it was supposed to stop the auto-attack). Either way, it's horribly annoying to lose people to such a random occurance.

I know exactly what you mean. For us the charge itself never did much more than 200 damage but players would sometimes get one-shot by a regular melee attack right after the charge. For the last 2 resets though (after the hotfix) that hasn't happened once. Maybe we were just getting lucky and assumed it was related to the hotfix, I kind of doubt it though.

I think you thought about what was in the comments in that thread, first one by Bloodshot in DnT, about auto-attacking. Maybe that's where some misunderstanding was.

http://forums.worldofwarcraft.com/th...08411172&sid=1

The "fix" never made sense to us. Charge damage has always been trivial, and it most definitely was never a threat to a full health player. The auto-attack hit is not fixed, but Al'ar now does a 150 damage Charge, instead of 200!

Unfortunately, the problem is much deeper than Al'ar, as there are roughly a dozen raid NPCs with the ability to auto-attack RSTS targets. In some respects, 110/130% threat caps are probably broken in the same sub-system.