This issue was addressed on Tuesday, however another increased concurrent player count on the occurred on the same day caused "degraded performance of D2R Ladder Items the database," which the database engineers are still trying to correct. This is a serious issue that the Diablo 2: Resurrected team has brought in engineers from other areas of Blizzard to help fix smaller issues, while focusing on "core Server issues."

"We reached out to our third-party partners for assistance in the same way," PezRadar said.

The irony is that Blizzard's wish to preserve an authentic Diablo 2 experience in the remake is the main cause of all these problems. One "legacy service" in particular handles critical functions including "game creation/joining, updating/reading/filtering game lists, verifying game server health, and reading characters from the database."

It was updated and optimized for Diablo 2: Resurrected but it's still built on 20-year-old technology and has a difficult time being up-to date "modern game play."

"In 2001 it was not as lots of information available on the internet concerning the game of Diablo 2 'correctly' (Baal runs for XP, Pindleskin/Ancient Sewers/etc for the magic find, etc)," PezRadar said. "Today it is, however, that a new player can seek out the most amazing content creators that can teach them ways to use the game various ways.

A lot of them involve a lot of database load due to creating load, then destroying games at a rapid rate. While we anticipated this -- with players creating fresh characters on new servers, working hard to get their items to be magical, we largely underestimated the scope we derived from the beta testing."

Another problem is the regularity of database saves across the world, that are occurring way frequently without any good reason. Blizzard has implemented some changes to make things more streamlined for now and is also working on a more permanent solution, but it's long in D2R Items for sale coming as it's "an architecture overhaul that will require time to develop and test, before implementing."