Blizzard has peeled back the curtain on the technical side of Diablo 2: Resurrected's server issues, which have plagued the new PC game since launch. Community manager Adam Fletcher has posted a lengthy explainer on Diablo 2's blog sharing what's happened, why it's happened, and what the team is doing to tackle these issues going forward.

Alongside surges of popularity overwhelming the servers, Fletcher says that part of the issue comes down to legacy code. In staying "true to the original game", the team kept a lot of the old code, with one legacy service in particular "struggling to keep up with modern player behaviour".

"We mention 'modern player behaviour' because it's an interesting point to think about," Fletcher says. "In 2001, there wasn't nearly as much content on the internet around how to play Diablo II 'correctly' (Baal runs for XP, Pindleskin/Ancient Sewers/etc for magic find, etc). Today, however, a new player can look up any number of amazing content creators who can teach them how to play the game in different ways, many of them including lots of database load in the form of creating, loading, and destroying games in quick succession. Though we did foresee this - with players making fresh characters on fresh servers, working hard to get their magic-finding items - we vastly underestimated the scope we derived from beta testing."

RELATED LINKS: Diablo 2: Resurrected review, The best RPG games, The best Diablo 2 Resurrected classes