On Kazrogal - first wave did not spawn. Waves 2-7 did, on wave 8 Thrall does his emote and despawns before any trash reached us.
1 Like
This is the 3rd time i’ve heard about this. Sounds pretty gamebreaking.
Just happened to my raid as well. First time starting Kazrogal trash, first wave never spawned, waves 2-7 spawned, on wave 8 everything despawned, no wave 8 trash or boss spawned, no thrall or npcs.
We had this bug the first clear on PTR, on the first clear on live, and the first clear with alts, CAN YOU PLEASE FIX THIS?!?!?!?!
2 Likes
Happened to me last night, luckily we were aware of what will happen so we purposfully wiped.
Worked after that.
Just happened 10 minutes ago on Faerlina. Looks like the mobs in the alliance camp are aggroing the trash pack or something
We had to call it after it happened to us 3x in a row. I had the paly tank ride down to try and engage the first wave, but they just immediately despawn with no zone wide yell. You stand there and then the gargoyles spawn.
Saw this tonight on Azuresong.
Happened yesterday on Faerlina. Raid was standing by the tower closest to the way we enter to line of sight. None of us were on unpathable objects like the boxes or in the tower as far as I could tell. First wave leading up to Kaz’rogal just despawned instantly. Tried waiting for the event/thrall to reset by hiding far up on the hill. Same thing happened again after resetting this way. First wave instantly despawned again.
This is still happening. 2 weeks in a row now, We’ve had Wave 1 not spawn, and wave 7 boss spawns and despawns. wasting 20+ mins, 11 if we let the first waves kill Thrall.
If the first wave doesn’t spawn then you’ll need to reset.
Invite another toon and get everyone to logout, works when it happens to my guild and saves a lot of time. Unless you want to just wipe that works too though takes more time.
This is still happening, 4 weeks in a row now. We’ve either had to do a mass logout and Reset from an alt, or wait on thrall to die and waste 15-20 minutes of raid time.
This happened to me today. EDIT: On retail. So perhaps this bug has been around for a long time, or perhaps some refactoring of classic code has caused it again. Idk.
This happened to me also today, and looks like this post is 2 years old. Wow. It’s pretty pathetic they can’t fix small things like this for years.