To help with this the D2R Items, we've got people working in a queue to log into the game, similar to what you encountered the queue in World of Warcraft. This will keep the game's population at the appropriate level which we currently have, so we can monitor areas where the system is strained and take action before it causes the game to go to an end.
When we correct a problem, we'll in a position to increase the population caps. This queue for logins has been partially implemented in the backend (right now, it's looking as if there's a failure to authenticate the client) and is expected to be fully deployed in the coming days on PC and console following.
Players will also be rate restricted, but only in cases where games are constructed, closed and then reconstructed within short time periods, which is mostly instances in which players are farming regions like Shenk Eldritch or Pindleskin.
"When this occurs, the error message will indicate that there is an issue communicating with game servers. It isn't an indication that the game servers may be down for this specific instance. It's simply a sign that the rate limit has been set to ease the load on the database in order to keep the game running." Blizzard advised.
It's like an absolute nightmare, to be honest, and I am so sorry for the engineers who have what appear like months of retroactive fixes in front of them. There's an internet school of theory that says, Blizzard should have seen this coming and prepared for it.
However, that's also a fundamental one of the risks you take with remasters. These games were developed in an era when information and multiplayer services didn't enjoy the same amount of popularity and accessibility is available today. Moreover, it's impossible to say for certain if some of the older infrastructure will scale the way we imagine it could.
Sometimes it is all the way to the point where it all falls apart in a burning heap.Diablo 2: Resurrected's servers are crashing in the wake of "modern players' behaviour"Diablo II: Resurrected was released to wide-ranging and persistent server issues. Today the Blizzard community manager offered some insights into the cause of the issue. The cause is partly some 20-year-old code and also some contemporary player behavior.
Resurrected's server issues during the last few weeks have seemed to get more severe. This culminated in several instances of server downtimes in the last week, in which a global outage could be attributed to, Blizzard say, by an increase in traffic. "This was a first-of-its-kind event which our servers had never experienced at all, not even when they were launched," reads the post on the Buy D2R items Switch.
