Diablo II: Resurrected released weeks ago, and it didn’t exactly go as planned. Server issues and locked characters were common in the days following the launch, but server outages and authentication issues have persisted since then. In a new post on the official forums, Blizzard explains what exactly is going on with Diablo II: Resurrected’s recurring server issues, and what the team is doing to fix it–including login queues and a limit on rapidly creating and joining games.
Most of it boils down to server load. As highlighted last weekend, large spikes in player numbers, and the amount of in-game lobbies they were creating, caused a global server outage. Blizzard says the spike in traffic on October 9 was bigger than that of the game’s launch, and that when combined with an update rolled out for the game just a day before, caused Diablo II: Resurrected’s global database to time out. Server traffic increased the following day, causing another outage. A switch between global databases caused yet another server outage on October 11, followed by another spike in player traffic on October 12 that caused more issues.
As for why Blizzard’s servers seem completely unable to meet player-demand, that has to do with legacy code used in the original Diablo II which is still present in Diablo II: Resurrected, and the fact that modern players are very rapidly creating game lobbies, then abandoning them, and then creating new ones.
Continue Reading at GameSpot
Source: Game Spot Mashup