The issue was further aggravated by an update we had deployed earlier in order to D2R Ladder Items improve the performance of game creation. Both of these factors caused our database to become overloaded, causing it to time out. We were able to reverse the Friday update that was previously released hoping to ease the load on the servers through Sunday while providing us with the time to dig deeper into the root cause."

As it turned out, rolling back the patch was not enough. Sunday saw a further growth in traffic and servers fell over again. On Monday, they were again down. This post is long , but extremely thorough in its breakdown of why this happening.

However, specifically Blizzard place the blame on the old code used in making and joining games and also reading characters from the database. "We have optimized this service in multiple ways to make it more compatible with technologically advanced technologies, but as we previously mentioned, a lot of our problems stem from the creation of games," says the post.

Which is why we are moving into the realm of player behavior.

"We have mentioned'modern behavior of players" as it's an interesting idea to contemplate. As of 2001 there weren't as much information on the internet about what it takes to play Diablo II 'correctly' (Baal plays for XP as well as Pindleskin/Ancient Swers for magic find, etc).

Today, however an aspiring player can browse the internet for any number of fantastic content creators who will teach them how to take part in different methods, many with a lot of database load by creating.

loading, and completely destroying games in quick succession. Although we knew this was possible-with players creating fresh characters on fresh servers trying their best to find their magic-finding items-we vastly underestimated the potential we discovered from the beta testing. "Basically you're too experienced, and videogame guides can be blamed Buy D2R Ladder Items. (You are able to read the most comprehensive Diablo 2 builds guide here.)