Connect with us

APPs & Games

The Launch of Diablo 2 Resurrected Provides Some Valuable Lessons



In a lengthy update on the Diablo II: Resurrection server issues, Blizzard has provided a lot of information. The update is extremely detailed and, in the name of transparency, breaks down cheap Diablo 2 resurrected ladder items in great detail all of the different issues that have been bumping up against each other since launch, resulting in outages and the inability to log in.

Diablo II: Resurrected Server Issues

Players have expressed dissatisfaction, and while the team is working to resolve issues as they arise, they are also looking into ways to prevent these outages in the future. An update made recently should limit any potentially lost progress to only a couple of minutes at most, and we are working to make that a permanent fix as soon as possible. The other server issues are related to the high volume of traffic. Demand was even higher last weekend than it had been at the time of launch. Blizzard stores final records in a global database and divides individual data across regional databases that write to the global database on a regular basis but are designed to handle the load.

As a result of the overwhelming demand, which at times reached hundreds of thousands of people, the system became overloaded, resulting in timeouts. The work they did included rolling back the Friday update from the previous week in the hopes that Saturday’s problems would not recur on Sunday, but there was a tremendous amount of demand for the service. Following Sunday’s problems, it became clear that the database would not have enough time to catch up due to the large number of connection attempts.

One of the most intriguing revelations about Diablo II: Resurrection is that the game is based on the original source code. That legacy code is mentioned in the blog update as one of the sources of performance degradation. The development process included updating the code to be compatible with modern technology, but once again, many of the issues are the result of the older code. Compared to 2001, there was not nearly as much potential concurrent demand as there is now in 2021. So, what exactly are they up to now? They’re putting rate limits in place to keep up with Diablo 2 Resurrected Items Xbox S demand, and they’re also putting in place a login queue to keep the servers from being overloaded. This is in addition to modifying data save so that it makes use of regional servers more frequently and writes to the global database-less frequently.

As previously announced late last week, Blizzard has been working on implementing server queues for Diablo II: Resurrected, and they have now implemented them on PC and have begun rolling them out to consoles over the weekend.

The patch notes go into great detail about how the new system is intended to function, and it’s a pretty standard queue system. When there is a lot of demand, everyone will get to the queue screen after the title screen, where they will be assigned a number that indicates their position in the virtual line. You’ll be given the option to leave the queue and play offline if you so desire, or you can simply wait for an opportunity to log in.

While login queues are an imperfect solution that does not appear to be winning over some dissatisfied players, they are only one step in a multi-step approach to assisting those who purchased the game in getting in and playing without losing progress or being kicked out. Because the login issues that have plagued the game since launch day are the result of a variety of factors, including the fact that the game is based on the original code, queues aren’t ideal, but they should help monitor demand and provide some breathing room while the rest of the fixes are being implemented.

However, the launch of Diablo II: Resurrected may provide some valuable lessons in the use of older code and in the planning of cross-platform and cross-progression releases in the future, but the community should receive some assistance in getting into the game for the foreseeable future. Of course, wait times are not limited to older ARPGs like this one, and they can occur during periods of high demand. It is still unclear how their other planned changes will play out. Even so, maintaining server demand levels is at least something that is actively being worked on for the time being in the hopes of keeping things more stable in the long run.

Take, for example, the PTR version number — Patch 2.4 seems like an odd place to start, doesn’t it? Until you consider that the versions of Diablo 2 classic that were released stopped at the 1.14 major version number; Lord of Destruction installed patch 1.7, and subsequent updates brought different changes to D2 classic versus LOD (completely unlike D3’s numbering system, which changed to 2. x for Reaper of Souls). From the perspective of versioning, D2R is a continuation of D2, and patch 2.4 emphasizes this by introducing changes to the way classes are balanced.

Click to comment

Leave a Reply

Your email address will not be published.