The issue was further aggravated by
D2R Items an update we released earlier in the day designed to improve performance during game creation. These two elements increased the load on our database globally and caused it to take a long time out. We were able to reverse the Friday update that we had previously released in the hope of easing the burden on our servers as we approached Sunday, while providing us with the time to look into the root of the issue."
It turned out that it wasn't enough. Sunday saw a further increase in traffic, and the servers froze again. Then again on Monday. The linked article is lengthy and extremely thorough in its explanation of the reasons for this.
However, specifically Blizzard put the blame on certain outdated code that is involved in making and joining games and also reading characters from databases. "We have optimized this service in a variety of ways to be more advanced technology,
However, as we've previously stated that a large portion of our problems stem from the creation of games," says the post. This is the point where we can move to player behavior.
"We refer to'modern player behavior as it's an interesting aspect to consider. The year 2001 was the last time there was nearly as much information on the web about the best way to play Diablo II 'correctly' (Baal is available for XP and Pindleskin/Ancient Sewers for
buy D2R Ladder Items the magic find, etc.).
