‘Legacy code’ in Diablo 2: Resurrected is causing widespread connection headaches

DMCA / Correction Notice
- Advertisement -


The first few weeks of Diablo 2: Resurrection haven’t gone particularly smoothly. At launch, players reported problems with missing or locked-out characters, and some were unable to start the game.

- Advertisement -

Three weeks down the road, some players are still struggling to connect to the game’s servers: Diablo 2: Investigations, and several reports of Resolve: Resurrection login problems have surfaced. Blizzard CS Twitter Account From October 9th, most recently just a few hours ago.

See more

There are apparently serious problems with the game, and there is growing concern by fans about Blizzard’s apparent inability to fix them, community manager PezRadar posted a lengthy post. platform update Explaining what went wrong, what is being done about it, and why it can take some time for things to fully recover.

advertisement

“On Saturday morning Pacific time, we experienced a global outage due to a sudden, significant increase in traffic,” explained PezRadar. “This was a new limitation that our servers didn’t experience at all, not even at launch. This was exacerbated by an update we made the previous day aimed at boosting performance around game creation. was rolled out – these two factors combined have overloaded our global database, causing it to time out.”

To help ease the load, Blizzard rolled back Friday’s update, but the measure proved inadequate—an even bigger increase in traffic on Sunday led to another outage. Things went sideways again on Monday when Blizzard reformatted Diablo 2’s backup global database and then attempted to switch it. After being switched on, the database continues to run its backup processes instead of serving requests from remote servers.

- Advertisement -

That issue was fixed on Tuesday, but another high concurrent player count on the same day resulted in a “degradation in database performance,” which database engineers are still working to fix. The situation is so dire that the Diablo 2: Revived team has enlisted engineers from other parts of Blizzard to help fix minor problems, focusing on “core server issues.”

“We also reached out to our third-party partners for assistance,” PezRadar said.

Ironically, it seems that Blizzard’s desire to maintain an authentic Diablo 2 experience in the remaster is the main cause of all these headaches. A “legacy service” typically handles critical tasks including “game creation/joining, updating/reading/filtering game lists, verifying game server health, and reading characters from a database”. It was upgraded and optimized for Diablo 2: Revived but still rooted in 20-year-old technology, and is having a hard time keeping up with “modern player behavior”.

“In 2001, there wasn’t nearly as much material on the internet about how to ‘correctly’ play Diablo 2 (child runs for XP, magic quests for Pindleskin/Ancient Sewer/etc),” PezRadar he said. “Today, however, a new player can look to any number of wonderful content creators who can teach them how to play the game in different ways, many of them creating, loading and destroying games in the form of lots of database loads. Includes. Quick succession. Although we foresaw this—with players creating new characters on new servers, working hard to obtain their magic-quest items—we greatly underestimated the scope we gained from beta testing “

Another major issue is the frequency of global database saves, which are happening too often for no good reason. Blizzard has made some changes to help smooth things out for now and is also working on a more permanent fix, but that will take some time to come as it’s an architecture redesign that needs to be built, tested, then It will take some time to implement.”

See more

For now, Blizzard is taking three steps to help make Diablo 2: Resurrected more reliably accessible: rate limiting, which will put a cap on how quickly and often players can create games and include: may include; creation of an MMO-style login queue to help ensure that servers are not suddenly crushed by a large number of simultaneous logins; And dividing important tasks into smaller services.

But those measures may isolate a part of Diablo 2: the revived player base all on its own. For example, players running into the rate limit will get an error message saying that there is a problem communicating with the game server, which isn’t much different from what they’re actually playing (but hopefully this will happen). will happen less frequently and for fewer people) ), while login queues mean players may have to wait longer before they are allowed into the game. Both are better than the current situation, but will not do much to address the widespread call to eliminate these troubles altogether.

Blizzard says it is committed to coming up with better long-term solutions.

PezRadar said, “We have incredibly hard-working people to manage incidents, diagnose issues and implement improvements in real time – not just on the D2R team, but at Blizzard.” “This game means a lot to all of us. Many of us on the team are lifelong D2 players—we played during its initial launch in 2001, some are part of the modding community, and so on. We assure you We can keep working as long as the game experience feels good to us not only as developers, but as players and members of the community.”



- Advertisement -

Stay on top - Get the daily news in your inbox

Recent Articles

Related Stories