It is interesting to note that Blizzard's wish to preserve the authentic D2R Items 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 upgraded and optimized for Diablo 2: Resurrected but it's still rooted in 20-year-old technology, and is having a difficulties keeping up with "modern player behavior."
"In 2001 there wasn't nearly as much content on the web about how to play Diablo 2 'correctly' (Baal plays for XP pindleskin/Ancient Sewers/etc magic items, etc.)," PezRadar said. "Today however, a beginner can find numerous amazing content creators who can instruct ways to use the game using a variety of ways.
A lot of them involve a lot of database load in the form of creating loading, destroying, and creating games at a rapid rate. Although we could have predicted this with players making new characters on fresh servers, working hard to discover their magical-finding objects, we greatly underestimated the extent of what we got from the beta testing."
Another major issue is the frequentity of global database saves, that are occurring way frequently without any good reason. Blizzard has made some adjustments to help smooth things out for now and is also working on a longer-lasting solution, but it's some time away because it's "an design overhaul that requires time to develop the system, test it, and finally implement."
For now, Blizzard is taking three steps to help create Diablo 2: Resurrected more reliable and accessible. Rate limiting this will place a cap on how quickly and often players are able to create and join games; the creation of an MMO-style login queue to ensure servers aren't smashed due to a huge number of concurrent logins. the division of critical functions into smaller services.
But , these strategies may end up alienating a part from the Diablo 2: Resurrected player base entirely by themselves. If players reach the limits on rate, for example you'll receive an error message stating that there's an issue communicating with game servers.
That's really not much more than what they're running into today (but it's likely to happen in less frequent intervals and to fewer people) in the case of login queues, which can mean that players will have long waits before being admitted to the game. Both are better over the current scenario, but won't do much to tackle the widespread complaints for a complete elimination of these annoying issues.
"We have employees working incredibly hard to address incidents at a rapid pace, identifying issues, and then implementing solutions--not only on the D2R team, but all across Blizzard," PezRadar said. "This game is so important for all of us.
A lot of us who make up the team are lifelong (no comments found)
Your Comment:
Note: Off-topic, blatantly inflammatory, or otherwise inappropriate comments may be removed. Remember that your username will be attached to your comment and you will not be able to edit or delete your comments once submitted.
| |