Diablo 2: Resurrected’s Server Issues Are Seemingly Being Blamed on Players Who Create Video Game Guides
Diablo 2: Resurrected, since its launch, has consistently been getting complaints regarding its ongoing server issues. Thankfully for those who no longer want to be kept in the dark about what is going on, a rep from Blizzard has decided to give some insight into the nature of the problem. As it turns out, the culprits are two things: a 20-year-old legacy code and modern player behavior.
“This was a new threshold that our servers had not experienced at all—not even at launch,” the devs said. “This was exacerbated by an update we had rolled out the previous day, intended to enhance performance around game creation.” Instead of fixing the bugs, the global database was overloaded, “causing it to time out.”
With that in mind, they decided to roll back the update in the hopes that load would ease up on their servers, as they continue to investigate deeper into what could be causing the major issues in Diablo 2: Resurrected’s servers. Unfortunately, rolling back the patch was not the answer to their problems. There was even a much higher surge in traffic and the game’s servers fell over once again.
According to the devs, a legacy code is at fault. This code is reportedly related to Diablo 2: Resurrected players’ abilities to create and join games, in addition to reading characters from the database. “We did optimize this service in many ways to conform to more modern technology,” they said. “But, as we previously mentioned, a lot of our issues stem from game creation.”
With that said, Diablo 2: Resurrected devs are now seemingly putting blame on what they refer to as “modern player behavior.” “In 2001, there was not nearly as much content on the Internet around how to play Diablo 2 correctly,” they said. “Today, 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.”
Although Blizzard has already predicted that this could happen, they admit that they have “vastly underestimated the scope we derived from beta testing.”