The D2R Items players' rate will also be restricted, but only in situations where games are constructed, closed and then reconstructed within short periods of time This is usually the case in which players are farming regions like Shenk & Eldritch or Pindleskin.

"When this occurs then the error message will say there is an issue communicating with the game servers. This isn't an indication that game servers will be unavailable in this particular instance, it's just a sign that you are being rated limited to help reduce the load temporarily on the database, to ensure that the game running," Blizzard advised.

It's an absolute nightmare to be honest. I feel for the engineers who have what seems like several months of retroactive solutions in their inboxes. There's a school of internet thinking that says, well, Blizzard should have seen this coming and planned for it.

However, that's also a fundamental part of the risk which you're taking when you remaster. These games were written back in an age where information and multiplayer didn't have the popularity and accessibility is available today. Moreover, it's impossible to say for certain if some of the older infrastructure will be able to scale as we believe it will.

Sometimes , it works at times -- up to the point that everything goes down in a fiery heap.Diablo 2 Resurrected's servers have been falling over because of "modern behaviour of the player behaviour"Diablo II: Resurrected launched to widespread and ongoing server problems. Today, a Blizzard community manager provided insight into the source of the issue. The cause is partially a 20-year-old program that's causing the issue, as well as modern player behaviour.

Resurrected's server troubles over the last few months have seemed to become more severe. The result was a series of instances of server downtimes in the past week, where the global outage was caused, Blizzard say, by a surge in traffic. "This was a brand new level that our servers had not ever experienced before, not even at launch," reads the post on the Blizzard forums.

The issue was further exacerbated due to an update that we launched earlier that day intended to enhance performance around game development. Both factors led to a massive overload on our database and caused it time out. We decided to roll back that Friday update we'd already deployed hoping to reduce the burden on our servers leading into Sunday while giving us more time to investigate deeper into the diablo II resurrected items.