Title says it all. There is no reason the fight should be this bugged for this long. It’s no secret that the encounter has been broken since it launched.
The fight has been bugged for so long it amounts to nothing other than negligence and unprofessional operations by the decision makers at Blizzard.
They need to fix the game they are literally paid to steward.
What’s bugged.
kt keeps attacking while in the RP phase of the fight and wipes the whole raid because he just fireballs random people to death and theres nothing you can do but wait for the rp phase to end. its kind of rare for it happen but when it does its very rage inducing its been in the game since tk first released. it was never common enough at the time to get noticed and fixed because so few people even went past t4 in the og release
Thats nuts.
Yeah I doubt they will fix it. Especially hearing how they kept all the bugs in MoP and haven’t done anything about it.
We are a subscription farm.
Don’t worry right after they fix the AQ event, they’ll get onto this one.
We had A’lar dive bomb the add tank and land on one of the flag poles in the room and reset to 100% hp. Lol.
But how does them fixing this benefit their bottom line today?!
Yes Blizzard will get right on fixing a boss that was broken in the original version of the game with their grand total crew of 3 people working on Anniversary..
The only “bug” I’ve seen is Capernian will sometimes start running around, which I don’t know is a bug or if that’s some weird interaction with player distance + whoever has threat
hero when he first comes out and burn him down so he doesnt have shield up and doesnt bug out.
thats how we solved it.
you shouldnt need hero for last phase anyways.
They’ll fix it just like they fixed durumu and lei shen in ToT..
Oh wait.
Classic + will be a freaking Mess, No clue why you guys believe in these guys any longer
#nochanges am I right. Gotta have TBC era with no changes.
You will have a better chance on getting this fixed by Superchatting one of Blizzard lapdog Streamers and bringing it to their attention and asking them if they can pass it on to one of their personal GM’s.
This is one of those odd bugs where it only happens if you’re in a bad raid lol
its totally random when it happens. I have had it happen once this release in my raid on the release day clear but the rest of the clears it did not do it. its one of those bugs that was rare enough and so few players actually did t5 during the first release that it never really got reported enough to get attention from blizzard during the time they actually cared about the game. its some of that good old 2007 spaghetti code. none of the devs that originally made tk work for blizzard anymore so its a total crap shoot if they can even figure out the code to fix it these days.
whats happening is when he has the shield you have to break to interrupt his case still on him , he bugs and starts going down the threat list till it wears off.
you should hero right as he comes out and burn him down before that and it will go ez for you.
thats what weve done the past 2 or 3 weeks now and it works every time.
He attacks during RP, sometimes he also shields himself and pyroblasts while in RP so you can’t do anything about it.
Quick someone bring this to Esfands attention with a SuperChat! LOL
Pretty sure once he gets in contact with one of his Blizzard handlers it will be fixed within days…
If you have bad dps just lust p4 shrug skip and phase him before the shield. Or you can just wait out the shield if your dps is low and then push into p5 after. Not that complicated