wow N'Zoth Bug Sees Entire Region's Bosses Despawn, 25% for Limit

[Starym 3,600]

 

Well, we certainly can't say N'Zoth is a boring boss. After discovering the secret Mythic phase Complexity Limit kept pushing and it was unclear what exactly they were supposed to do, as nothing really happened in the phase to make the bosses crazy high HP any more doable. Then came the fateful pull.

Limit were going about their regular progress, trying to get the boss down to 60% before entering the gate to the Chamber of Heart, and when the gate spawned they decided to keep DPSing the boss. On this particular pull the boss was  just doing some relatively weak Eternal Torment AoE damage which was easily healable, didn't have his Psychic Shell and they proceeded to just damage the boss down to 25% at which point he activated his Psychic Shell. They then went to the chamber, finished that encounter as normal and then...

The next-level crazy thing is that when Limit's N'Zoth despawned, EVERY N'Zoth on US servers despawned, regardless of difficulty. After the despawn, the next pull that they arrived at the same point, N'Zoth was doing massive damage to the raid with the same AoE as before if they don't go into the gate when it spawns. Whether this is the intended mechanic or just some protection while Blizzard fix whatever the issue with the boss is is unclear.

On behalf of @LimitGuild I'd like to apologise to everyone on NA servers who was having a good pull on N'Zoth just now. Our bad! ?

— Preheat (@Preheat1337) February 3, 2020

Raise your hand if you’ve ever been the cause of a boss being despawned for an entire region ??‍♂️#RWF #LimitRaids #WeAreCOL pic.twitter.com/ELSj8JSrW0

— COMPLEXITY-LIMIT (@LimitGuild) February 3, 2020

Now, obviously the bug happened somewhere in that first part of the fight, before 60%, and the boss simply wasn't doing what he was supposed to when the gate spawned. The likely thing is that Blizzard actually despawned him after Limit returned from the gate, so they didn't have to deal with a bugged out easy World First and potentially having to revive N'Zoth afterwards. The fact that they also despawned him for everyone else in the region is just additional hilarity. In any case, Limit's best try is still around 60% and not really the 25% one, and they keep pushing the fight.

Here's a replay of the pull with more details and analysis from the commentator team, as well as the same pull with the guild's comms throughout:

 

Complexity Limit continue to try the boss, are now at 109 pulls overall and still not quite sure what's happening with the fight - whether the boss is still bugged with not triggering some change after they clear the Chamber of Heart, or if it's just hugely overtuned etc, as the regular way the fight is going now seems completely impossible to do. They still have things to try out and at the very least get better at the first three phases, so they're definitely not out of ideas yet, so head on over to their stream to follow their progress.

 

World First race related articles

• N'Zoth Secret Mythic Phase Videos and Explanation

• Mythic Ny'alotha Raid Progress Race Hub

• N'Zoth Loot Drama - Re-kills Possible on Same Reset

• The Raid History World First Timeline

• Method Down Queen Azshara Mythic World First + Video, Raid Comp

• Ragnaros Classic Down World First by APES

• Limit Faction Transfer to Alliance for Ilevel 400 Gear (Bfa, Dazar'alor)

• Method to Livestream Uldir Mythic Progress for First Time in History

• Guild Banned Over Star Augur Exploit: Video Added (Legion, Nighthold)

• Three Top Guilds Suspended For Helya Exploit (Legion, Trial of Valor)

• Banned Guilds Talk about Their Helya Exploit and HC Raiding (Legion, Trial of Valor

• Old Dev Blog on Encounter Tuning and Exploits

[Migol 407]

It seems Highly unlikely to me that Limit's attempts magically affected everyone's like that.

I'd say it's far more likely Blizzard was quietly watching their progress and tried to hotfix change something, and then something went snap.

[Starym 3,600]

2 hours ago, Migol said:

It seems Highly unlikely to me that Limit's attempts magically affected everyone's like that.

I'd say it's far more likely Blizzard was quietly watching their progress and tried to hotfix change something, and then something went snap.

Yep. I mean Blizz definitely pulled the despawn plug on N'Zoth, the question is why it bugged out in the first place, and your theory is most likely.

[Koxsos 38]

Nothing like live alfa testing.
Next up: early access ShadowLands!

[Alastor7783 11]

Even the Devs are rooting for Method. ?

[Prophet001 404]

I was watching this and watching his HP go down and them eat the AOE and it was absolutely hilarious.

I don't think they were exploiting though as there's really no "guide" on how to do the fight.

[Prophet001 404]

8 hours ago, Migol said:

It seems Highly unlikely to me that Limit's attempts magically affected everyone's like that.

I'd say it's far more likely Blizzard was quietly watching their progress and tried to hotfix change something, and then something went snap.

They definitely despawned him b/c of limit hitting 25% and not going down but still being able to eat the AOE.

[Laragon 269]

47 minutes ago, Prophet001 said:

I was watching this and watching his HP go down and them eat the AOE and it was absolutely hilarious.

I don't think they were exploiting though as there's really no "guide" on how to do the fight.

I wouldn't call it exploiting, because they didn't do anything except keep hitting him. The mechanic clearly bugged though and I wouldn't have called it a "worthy" world first if they got it that way.

[breck 29]

This issue caused one wasted pull, maybe two of they tried it again.  At the very least it has already caused the number of attempts on this boss to be inflated. I would have been fine if this was the first kill, bugs happen, its part of the games lore and guilds get lucky from time to time.

[Starym 3,600]

1 hour ago, breck said:

This issue caused one wasted pull, maybe two of they tried it again.  At the very least it has already caused the number of attempts on this boss to be inflated. I would have been fine if this was the first kill, bugs happen, its part of the games lore and guilds get lucky from time to time.

Nah but Limit would be pissed. Their kill would be completely discredited, and unless Blizz revived the boss and removed loot, they couldnt even re-kill it. Not to even mention the infinite drama around it (as if we dont already get enough of the annoying cringy Method vs Limit fanboy action).

[Starym 3,600]

1 hour ago, Laragon said:

I wouldn't call it exploiting, because they didn't do anything except keep hitting him. The mechanic clearly bugged though and I wouldn't have called it a "worthy" world first if they got it that way.

Yea I honestly didn't even think people would think this is an exploit, since it's so obviously not, but there's a LOT of them saying exactly that. Whether they're all Method fans I don't know but it's worrying. There is something to the fact that they did progress for 45% on a clearly bugged boss, but I honestly can't fault them on that, as the first x% they legitimately had no clue what was going on and if this was just a hotfix or something similar.

[breck 29]

I do not think they would be upset at all. They would have not tried the strategy that they did if that was the case.  It would just be an oddity that occurred.