When the Anniversary event went live, it broke at least two old raids: Firelands and Uldir.
EDIT: Neither of these raids were broken from the Anniversary event.
1> When a Timewalking Raid is active, the “current” timeline of that Raid is scaled (for better or worse) so you may not be able to solo it, but just for that week. The Anniversary event has/had nothing to do with it.
2> When in Uldir and trying to kill Mythic G’huun, you have to do the Orbs FIRST before you attack G’huun.
I’ll leave the rest of this post here for posterity.
…
In Firelands, you’re lucky to solo any of the trash. When you should be able to 1-shot everything with an auto-attack.
In Uldir, G’huun was just recently allowed to be solo’able, but now you can’t. You can nuke him to about 20% and then he heals so fast, you can’t kill him. I even brought in friends and the same thing happens no matter how many ppl are there: 20%… and then he’s unkillable.
Is there any chance these will be fixed? Or do we have to wait until Anniversary event is over? Which then carries THE VERY REAL possibility that it will still be broken.
Interesting. Is your character getting scaled at all? Are you still level 80 and your IL is measured in hundreds? Firelands is a Timewalking-eligible raid, which is why I ask.
Otherwise, are the mobs’ health pools scaling up to unkillable amounts, or are your abilities just doing no damage to them?
I can check if you like, but since others have noted it’s broken, I have a feeling it’s just broken.
All I know is I ran in, expecting to 1-shot that first group of mobs on the way to the Spider. And … that very first Fire Giant I’m like swinging and swinging and swinging … I’m like … whoa… something’s wrong. lol
I was never in any danger. Your health never goes down. But you can’t kill anything.
This happened when they changed timewalking scaling but the tw raids still use old scaling and for some reason this was applied to walking in the raid versus just queuing for it at the npc. So BT firelands and ulduar are borked.
I’m going to have to check this out. I’ve spent a lot of time in that raid, and I’m genuinely curious. I appreciate the response!
That’s a plausible explanation. It’s weird that we’d have multiple months of the old timewalking scaling if they intended to update it to Chromie Time scaling, but it’s definitely not unprecidented for bugs to take an eternity to squash.
Hmmm, kinda borked that TW would have any affect on a non-TW raid. But this is blizz after all. All they need to do is alter the code on a squirrel in Elwyn Forest for half an expac to fall over.
i’ve reported bugs with legacy content that had been previously reported FOUR YEARS prior. far as blizzard seems to be concerned, play current content or get bent.
which seems like a really stupid decision. with the scale of content in this game, if it WORKED it would be a huge selling point. instead, they neglect what the dont simply remove. and let me tel ya, it feels REAL bad doing an old questline and finding out the next step has been removed.
At some point … I think it was in Legion… the farm broke. And the little adds that would spawn when you’d do various chores would all spawn at max level and kill you! lol
I reported that bug for … must have been 6-7 years before it was fixed.
The issue with the raids that have timewalking available for them (Black Temple, Ulduar, and Firelands) is that the legacy buff is no longer active in there when you’re doing the raids normally. They didn’t directly get any harder, you’re just only dealing and taking normal damage instead of the legacy buff modifying it.
That’s separate to the issues in other raids, which were mostly to do with bosses with ‘raid split’ mechanics being bugged. Like N’Zoth not spawning Psychus inside the portals. Those issues have seemingly been fixed.
Interesting to hear about G’huun though. I’m gonna go try it myself and see if I can experience what you’re talking about since I haven’t been in there since before 11.0.5.
