In the last few days there have been more login and server problems with Diablo 2: Resurrected on PC and consoles – including lost character progress, which, according to Blizzard, was the exception and was limited to a few minutes. The customer service of Blizzard Entertainment provided regular updates on the situation via Twitter and meanwhile the Community Manager has published a very detailed report on the difficulties in the English forum. Problems and bottlenecks in the server architecture are explained and overloads of the central, global database are mentioned. At the same time, it is said that the gaming behavior of current users is very different from the behavior of players 20 years ago and the “old code base” (e.g. when creating online games) is not prepared for this. Thanks to many “content creators”, there would be many more players who undertake “Baal Runs for XP” or other specialized runs (“Pindleskin, Ancient Sewers etc. Runs for magic find”), many of which cause a large database load creating, loading and ending games in quick succession. “Although we anticipated this (…), we underestimated the scope that we derived from the beta tests by far,” it says.
In order to reduce the server rush and possible overloads, the server architecture is to be purged or optimized and further measures taken. This includes a limitation when creating new games (e.g. do not create two games within 20 seconds; example: “Pindleskin Runs”) as a time-limited measure. A queue like in World of WarCraft or New World is also planned to avoid drop-outs at weddings. This login queue has already been implemented in the backend (at the moment it looks like a failed authentication in the client) and is available on the PC as of today. The console update should follow in the next few days. In addition, the server services are to be divided into many small services in the future.