.jpg?width=1200&height=630&fit=crop&enable=upscale&auto=webp)
The “legacy code” in “Diablo 2: Resurrection” is causing widespread connection problems
Diablo 2: The first few weeks of the resurrection were not particularly smooth. At the time of release, players reported issues with characters disappearing or locked, and some people were unable to start the game at all.
Three weeks later, some players are still trying to connect to the game’s server: multiple reports of investigations and solutions for “Diablo 2: Resurrected Login Issue” appeared in Blizzard CS Twitter Account Since October 9th, mainly the last few hours ago.
[#D2R] We are aware of an issue affecting our authentication server, which may cause slow or failed login attempts. We are currently investigating the reason and will provide an update when it becomes available.October 14, 2021
There are obviously serious problems with the game, and as fans become more and more upset about Blizzard’s apparent inability to fix these problems, the community manager PezRadar posted a lengthy post Forum update Explain what went wrong, what measures are being taken, and why it may take some time to completely resolve the problem.
PezRadar explained: “On Saturday morning Pacific time, we suffered a global outage due to a sudden and significant increase in traffic.” “This is a new threshold that our servers have not experienced at all, not even at launch. We launched the day before. Updates designed to improve game creation performance exacerbated this situation-these two factors combined to overload our global database and cause timeouts.”
To help reduce the load, Blizzard rolled back Friday’s update, but the measure proved to be inadequate-a larger surge in traffic caused another outage on Sunday. On Monday, when Blizzard repaired Diablo 2’s backup global database and then tried to switch to it, things changed again. After switching, the database continues to run its backup process instead of servicing requests from remote servers.
The problem was fixed on Tuesday, but another high number of concurrent players on the same day caused “a further drop in database performance.” Database engineers are still working hard to fix this problem. The situation is so terrible that the Diablo 2: Resurrection team has received help from engineers from other departments of Blizzard to help solve smaller problems while focusing on the “core server problem.”
“We also seek help from our third-party partners,” PezRadar said.
Ironically, Blizzard seems to want to maintain a real Diablo 2 experience in the remake is the main reason for all these headaches. A “traditional service” specifically handles key functions, including “game creation/joining, updating/reading/filtering game lists, verifying the health of the game server, and reading characters from the database”. It has been upgraded and optimized for Diablo 2: Resurrection, but it is still rooted in technology 20 years ago, and it is difficult to keep up with “modern player behavior.”
“In 2001, there was almost not so much content on the Internet about how to play Diablo 2’correctly’ (Bal running XP, Pindleskin/Ancient Sewers/Magic Discovery etc.),” PezRadar said. “However, today, a new player can find any amazing number of content creators who can teach them how to play games in different ways, many of which include loading large databases in the form of creating, loading and destroying games. Quick successors. Although we did foresee this-players will make new characters on new servers and try to obtain their magic items-but we greatly underestimated the range that we derived from the Beta test.”
Another major issue is how often the global database is saved, which happens too often for no reason. Blizzard has made some changes to help things go smoothly now, and is still working on more permanent fixes, but it will continue for a while, because it is “an architectural redesign that takes some time to build, test, and implement “
[#D2R] As part of the ongoing investigation of the issue in the past few days, our team will actively monitor and respond to the situation during peak game periods, and there may be periods of limited login or game creation.October 13, 2021
Currently, Blizzard is taking three steps to help “Diablo 2: Resurrection” more reliable access: rate limiting, which will limit the speed and frequency of players to create and join the game; create an MMO-style login queue to help ensure The server will not suddenly be overwhelmed by a large number of simultaneous logins; and the key functions will be divided into smaller services.
But these measures may eventually alienate Diablo 2: Resurrecting part of the player. For example, a player who encounters a rate limit will receive an error message stating that there is a communication problem with the game server, which is not much different from what they are currently experiencing (but hopefully it will happen more frequently and with fewer people). The login queue means that players may have to wait a long time before being allowed to enter the game. Both are better than the current situation, but will not play a big role in addressing widespread calls for the complete eradication of these irritants.
Blizzard said it is committed to proposing better long-term solutions.
“Our staff work very hard to manage incidents, diagnose issues, and implement fixes in real time—not only on the D2R team, but throughout Blizzard,” PezRadar said. “This game means a lot to all of us. Many of our team are lifelong players of D2-we played it when we first released it in 2001, some were part of the mod community, etc. We I can assure you that we will continue to work hard until the game experience makes us feel good, not only as developers, but also as players and community members.”