Kael'thas bugged, hotfix not incoming
Daelo is saying over on the forums that the Kael'thas event is bugged. After a player reported that the shield (one of the magical weapons that you first have to defeat and then can fight Kael'thas with) has tons more health than expected, Daelo confirmed that if Kael'thas resurrects his advisors while weapons are "alive" their health will be increased, making the fight much harder and throwing most guilds off of their pacing.So if you're headed to Kael'thas this week, beware. Unfortunately, Blizzard says they can't hotfix the issue, which means it'll have to be fixed in a content patch. Fortunately, however, 2.2.2 is due this week, so if Blizzard can sneak it in yet on that one, raiders will be able to take Kael on as of Tuesday. If 2.2.2 is already too far along in the process for the code to be added, however, Blizzard will either have to create a patch just for this fix (2.2.3), or wait until 2.3 releases (which could be a matter of weeks, severly hampering guild progression past Kael).
We'll have to wait and see what they do. This is a confirmed bug, so hopefully we'll see a fix for it with 2.2.2, hopefully on Tuesday.
Filed under: Patches, Analysis / Opinion, Bugs, Blizzard, Raiding
Reader Comments (Page 1 of 1)
TotalBiscuit Sep 30th 2007 7:57PM
Since we just downed Kael'thas for the first time tonight, I can safely say that this bug does not stop guilds from killing him, not in the slightest.
Dryssa Sep 30th 2007 8:14PM
@1:
True, but having to burn through 200k extra HP of shield while trying to get the advisors down in time can be a real hamper on progression. Still, it's not THAT big an issue as the several other bugs in the fight, such as the Pyroblast glitch at 50%.
btw, good to see you're doing well on your "dead" server TB :P
Elarius Sep 30th 2007 8:53PM
Just wanted to add, in our case tonight, we got the bug on every try and is really slowing us down atm, us and another guild are at him atm and its very dissapointing to have to deal with an issue like this one, especially since we got him to 59% a few days ago when we last tried him, i hope its fixed soon.
Changing from phase 2 to 3 is absolutely the most vital point of the fight and making it harder will require way more effort than what we need to atm, on the other hand, great to see ur guild downing him TB, will hopefully gives us some encouragement to kill him even as it stands now.
Also good to hear that you found a guild, remember listening to ur show few weeks back been annoyed to hell not been able to transfer.
Just to sum up, fix this asap as you can blizz, we will probably down him soon but for guilds that just got to the point of sorting phase 2 it will be incredibly hard for them to kill him.
TotalBiscuit Sep 30th 2007 9:43PM
@2 Haha, needless to say, I managed to get off it :>
TB.
Tridus Sep 30th 2007 9:48PM
One really has to ask how these kind of bugs keep appearing in patches, especially when the health of a mob should be a simple field in a database somewhere.
This sort of thing happens FAR too often in patches.
Ugkul Sep 30th 2007 10:09PM
2.3 a matter of weeks?? We just saw the release of 2.2 and TBC was released in mid-Jan. 2.3 would take another 3 months at this rate.
Seraya Sep 30th 2007 10:35PM
Yes, 2.3 will be coming out very soon since they're hoping to get it on the PTR this week or next week.
DJTyrant Oct 1st 2007 2:39AM
@ Total Bisquit
Same thing with the guild I'm in, we downed him tonight without too much trouble. Just have to have the DPS to get through most (if not all) the weapons during Phase 2/3 (not really that hard).
This isn't a game breaking bug, just annoying for guilds that either don't have the extra DPS to overcome it, or are just learning the encounter.
arb Oct 1st 2007 3:10AM
I know this is a pain for those Raiding, but considering the hash Blizzard made of 2.2, please don't encourage them to try to rush code into another release too soon - we'll all regret it. Battlegrounds are still bugged (in my Battlegroup at least) and there are myriad little defects in the interface. Blizzard = great gamecrafters = amateur software engineers.