World of Warcraft: Midnight beta testers expected bugs but probably not 30-second delays to loot a wolf. Since the beta launched on November 11, players have been wading through sluggish performance, with the worst lag hitting busy zones. Blizzard pointed the finger at an unexpected suspect: fish. Yes, really.
Fish NPCs blamed for lag in World of Warcraft Midnight beta

The issues began almost immediately. Crowded areas like quest hubs turned into click-and-wait simulators. Players flooded the forums asking why even basic tasks like accepting quests or casting spells felt like trudging through molasses. Lead Producer Zorbrix eventually chimed in with the first wave of answers and oddly enough, they swam straight to the coastline.
He explained that a new layer of reactive NPC behavior had been introduced, especially for wildlife. Fish were now programmed to behave more naturally, responding to players and the environment. But with Midnight’s massive coastal areas, that meant a lot of fish. Once enough players came near them, the fish AI started firing at scale and the servers choked.
Turns out the fish weren’t the only issue
Still, even Blizzard had doubts. Zorbrix followed up days later, walking back the theory. After rebooting servers, things briefly improved, but lag crept back fast. “The fish might have been a red herring,” he wrote. It turns out the real issue was a broader pile-up of server stress and memory problems.
Blizzard is testing new code fixes, but the results haven’t turned the tide. Lag remains a frequent complaint, especially during peak hours.
Players frustrated over $90 beta access
Some fans are laughing off the fish saga, but others aren’t amused. With Blizzard tying beta access to the $90 premium edition, plenty of players feel burned. For them, waiting 20 seconds to open a quest box doesn’t feel like early access it feels like paying to be a QA tester.
What’s breaking World of Warcraft Midnight?
Here’s a quick breakdown of what’s likely behind the beta lag so far:
- Advanced NPC scripting triggering too often
- High instance and memory load in busy zones
- Server performance bottlenecks beyond just fish
- Incomplete optimization for large player counts
- Patch deployment delays and backend strain
Server stress was always part of the plan, but not like this
Beta tests are meant to shake loose bugs before launch. But when a game’s selling premium access as a feature, the bar is higher. The fish were funny at first. Now, it’s clear that Blizzard’s still swimming upstream on performance. Midnight launches next June, but the beta clock is ticking fast.

