Resurrected's server troubles over the past few weeks have seemed to get worse

D2R Items Resurrected's server troubles over the past few weeks have seemed to get worse. This culminated in several instances of server downtimes in the last week, when the global outage was caused, Blizzard say, by an increase in traffic. "This was a new threshold that our servers have never previously experienced, since the beginning of our service," reads the post on the Blizzard forums.

The issue was further exacerbated by an update we deployed earlier intended to enhance performance around game development. Both factors led to a massive overload on our database which caused it to slow out. We decided to roll back that Friday update we'd previously deployed in hopes of lessening the load on the servers going into Sunday and giving us the opportunity to explore the root of the issue."

It was clear that the patch's rollback wasn't enough. Sunday brought a bigger increase in traffic, and servers failed again. This time on Monday. The above linked post is long and admirably specific in the explanation of the reasons for this.

But in particular Blizzard place the blame on some old software that was used for making and joining games as well as reading characters from the database. "We tried to improve this service in a variety of ways to conform to more contemporary technology, but as we've already mentioned, a lot of our issues stem from games being created," says the post.

This is the point where we can move into player behaviour.

"We mention 'modern player behavior' because it's an interesting aspect to consider. The year 2001 was the last time there was as much material on the internet about ways to play Diablo II 'correctly' (Baal plays for XP and Pindleskin/Ancient Sewers for magical finds, etc.).

Today, however, a new player can discover a myriad of fantastic content creators who are able to teach players how to participate in various ways, many of them including lots of database load as a result of creating.

We did anticipate this, with players creating new characters on fresh servers struggling to locate their hands on their magical objects-we greatly underestimated the scope we derived from beta testing. "Basically you're too knowledgeable, and videogame guides are to blame. (You can read on best Diablo 2 builds guide here.)

The post concludes by discussing what Blizzard are doing to fix the issues, which includes a variety of less than perfect fixes. This includes rate limits, which will prevent players from creating too many games in quick sequence, and log-in queues.

Therefore, players won't overload servers rather, they queue-up as if joining an MMO. The limitation of rate is taking place today and is considered "mitigation" instead of an in-term solution, however queues will be deployed "in the coming moments on PC."

In addition, Blizzard say they've drafted employees from across the organization, "not just on the D2R team", to help work on the issues. Hopefully, eventually they'll be able to get it working without boundaries.

Legacy code's found in Diablo 2: Resurrected is creating widespread issues with connection two weeks of Diablo 2: Resurrected have not been particularly smooth. As the game was launched, players had reported issues with locked-out or disappearing characters, while some were unable even to launch the game at all.

Three weeks after the launch, some players are still struggling to connect to servers of the game. Multiple reports of investigations into, and resolutions to, Diablo 2: Resurrected login issues have surfaced on buy d2r items.