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

This happened yesterday for sure.. not sure how common the bug is, as I don't remember particularly high numbers of deaths to charges, but we lost at least 1 paladin due to a charge/auto.

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.

No, they hotfixed the damage that Al'ar's Charge itself does, but that's just the base damage and it makes it somewhat more likely that someone might live through a single autoattack following a charge. It's not a fix to the underlying problem.

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.

No, the charge itself killed people. That was changed.

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.

The free auto attack after charge was supposed to be fixed on all charging mobs I thought.
A charge of "X" damage is ok, a charge plus a melee auto attack from any raid mob will often kill most classes outright.

It does seem reduced in 2.1 but it's definitely not 'fixed'. It still occurs.

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.

I think it's just a very broad mob targetting issue.

I bet it's the same issue that causes Karathress to sometimes drop a Spitfire Totem at the feet of his RSTS shadowbolt target if the abilities sync up, or that makes Copernian randomly fireball her random conflag target.

I know it vexes me on the Sporebats leading to Hydross. Not a pull goes by without at least one clothy getting killed by it. Obviously there's ways of preventing it, but they're also mobs on which having everyone standing in melee range will hurt a fair bit due to that AoE DoT they do.

Our tauren resto druid got charged by supremus and swung at and killed (twice), yet our scrawny undeads didnt - could this be a "cow range" thing (hitboxes)?

I doubt it; the same thing happens frequently in Heroic Shattered Halls on the bladefisted fellows after the first hall, and on Kargath himself. I've seen him take swings at anything from Draenei to Gnomes.

Yeah, I don't think we have ever made it through one of those packs without having a mage or priest die from a charge.

That would be me. I was the add DPS healer sporting 14k armor and well over 10k hp. The charge did negligible damage, the auto attack crit for 13.8k. No way around that and if the stated design suggests that they did not intend for the charge to one-shot people that were topped off, I hope they fix it in the near future.

Maybe they could reset the auto attack timer when he charges, disable his melee until he returns his selection to the primary target or implement the ability for a boss to have a "focus" target for RSTS type attacks and add the ability for the UI to access the focus target of your target (possible PvP implications there though). The latter would be a cool addition, in my opinion.

The same thing would occasionally happen on the Twin Emperors, when Vek'nilash would Uppercut a random target in melee range he'd occasionally auto-attack and splatter them. Rogue avoidance is high enough that this was less noticeable, but it was pretty common to lose at least one melee DPS during the fight to this.

Thinking about it more, I'd say it's more likely that the target-switch broke the 110% melee threat buffer, so if the target was sitting in that buffer he'd just become the primary target. Seems like if it behaved like Alar's charge it would be even more common than it was.

The bug is very annoying in many of the places it presents itself. On fights that aren't too demanding on 100% survival, like Al'ar, it makes the first kill a bit more difficult but can be worked around. We're working on Kael'thas now where losing anyone is a severe problem, and we've had trouble with Copernian killing people with fireballs when she switches targets to conflag. Again, it can be worked through, but it's just stupid to have difficulty caused by a widely known and documented bug.

Why is everyone talking about this charge-melee thing like it's new? I remember getting one-shotted by Attumen, trash in Heroic SH, Lair Brutes, and many other things.

I wear Molten Armor whenever I'm around charging mobs, just to avoid the crit and one-shot.

It seems reasonable that this would be difficult to fix. If a mob's auto-attack timer is up, and he has a target, he's going to swing at them. Even on fights when the designer clearly wants the mob to not make white attacks in some situation, they seem to have a heck of a time using scripting or whatever tools they have to prevent that fundamental behavior (Netherspite breath phase, Aran punching people, Emperor Vek'lor). Any fix will probably require heavily redoing the mob AI.