Video Gamer is reader-supported. When you buy through links on our site, we may earn an affiliate commission. Prices subject to change. Learn more
Blizzard has offered players an explanation and action plan as to why many players have been fighting with server outages in the recent release of Diablo II: Resurrected.
In a lengthy post on the Blizzard forums, the dev team have claimed that the outages aren’t down to one specific issue. Rather, a series of problems over have caused the technical teams plenty of headaches. We’ll spare the technical details here, but you can read the blog post for more.
Interestingly, Blizzard say a major source of the issue has been down to the remaster’s original code. As a remake of the 1999 original Diablo II, certain services were retained. “However,” Blizzard say, “one legacy service in particular is struggling to keep up with modern player behavior.”
“We mention “modern player behavior” because it’s an interesting point to think about. In 2001, there wasn’t nearly as much content on the internet around how to play Diablo II “correctly”. Today, however, a new player can look up any number of amazing content creators who can teach them how to play the game in different ways, many of them including lots of database load in the form of creating, loading, and destroying games in quick succession.”
“Though we did foresee this, with players making fresh characters on fresh servers, working hard to get their magic-finding items–we vastly underestimated the scope we derived from beta testing.”
As they work on improving and fixing things, Blizzard are implementing temporary rate limiting and temporary login queue creation. They also say they’ll be breaking down critical functionality into smaller pieces, so they can work on different aspects without taking down the whole game in the hope of reducing server outages in Diablo II Resurrected.
Diablo II: Resurrected Update:
📶 Servers
👾 Legacy Code
🗒 Notes on ProgressRead here: https://t.co/o8WnR3LwEs
— Diablo (@Diablo) October 14, 2021
