A level 80 Paladin tank has soloed Mists of Pandaria raid bosses aimed at players 10 levels above him.

Faruz of Chaos Crusade on Ravencrest EU, has taken advantage of a fairly long-standing bug affecting tanking, which has existed since Blizzard’s latest World of Warcraft expansion, Mists of Pandaria, launched in 2012. The bug basically meant that level 80 characters, such as Aelobin, the soloing DK, could get their Vengeance up so high that, in this case, Faruz was generating between 2 and 2.5 million, yes, you read that right, million, attack power.

This pushed Faruz’ DPS up, again just like Aelobin’s, to over a million, hitting around 1.2 million at times. More than enough for a level 80 paladin tank to solo raid bosses! This attack power level resulted in his Seal of Insight proccing for way beyond his maximum health pool every time it popped. He reports that his biggest heal was 1.5 million from Seal of Insight. He was also absorbing huge, huge amounts from Sacred Shield.

As for a level 80 being able to get into level 90 raids to solo bosses, that’s pretty straightforward. Just have a level 90 go in before you, then follow them. The same applies for level 85 raids, like Aelobin’s attempt on a World of Warcraft Cataclysm boss in the Firelands raid at level 80. There’s no hacking, no cheats, no private servers, no exploits, just a crazy bug to a tanking passive and a big chunk of skill. Faruz also soloed the Stone Guard bosses with his level 80 paladin tank, and had a go at Feng the Accursed. You can check out Faruz’ armory here, for verification!

And, at last, this was the straw that broke the camel’s back for Blizzard. In Mogushan Vaults, Elegon is one of the more famously difficult bosses, so to have a level 80 beat him must have been too much for them to bear. In an MMORPG like World of Warcraft, it’s not good for players to be able to totally ignore the gear grind and mechanics of fights! Thanks to Faruz, and probably Aelobin’s level 80 death knight tank soloing, Vengeance has now been hotfixed to scale to a maximum number matching a player’s health pool. This should fix most of these issues, until the next workaround appears!