"In 2001, there wasn't nearly as much information on the internet about learning how to play D2R Items 'correctly' (Baal runs for XP, Pindleskin/Ancient Sewers/etc for magic finds, etc.)," PezRadar said. "Today it is, however, that a beginner can find the most amazing content creators who can instruct what to do in various ways.
A lot of them involve a lot of database load due to creating load, then destroying games with a rapid pace. We did anticipate this, with players making new characters on fresh servers, working hard to find their magical items, we vastly underestimated the scope we gained from the beta testing."
Another big issue is the frequentity of global database saves that happen way too often for no good reason. Blizzard has implemented some changes in order to reduce the frequency of saves for the moment and is working on a longer-lasting solution, but it's some time away because it's "an architecture redesign which requires time to create, test, then implement."
At present, Blizzard is taking three steps to help create Diablo 2: Resurrected more reliable and accessible. Rate limiting this will place the limit on how rapidly and often players can create and join games; the establishment of an MMO-style login queue to ensure that servers aren't smashed by a large number of concurrent logins; and disaggregating important functions into smaller parts.
However, these measures may end up alienating a section in the Diablo 2: Resurrected player base completely on their own. Players who reach their limit on their rate, for instance are likely to receive an error message that says there's a problem connecting to game servers.
This isn't that different from what they're running into now (but it's likely to D2R items for sale PS4 and affect lesser people) Login queues could mean players face lengthy waits before they're allowed into the game. Both are far better than what's currently happening, but won't do much to address widespread calls for a complete elimination of these annoying issues.
A lot of them involve a lot of database load due to creating load, then destroying games with a rapid pace. We did anticipate this, with players making new characters on fresh servers, working hard to find their magical items, we vastly underestimated the scope we gained from the beta testing."
Another big issue is the frequentity of global database saves that happen way too often for no good reason. Blizzard has implemented some changes in order to reduce the frequency of saves for the moment and is working on a longer-lasting solution, but it's some time away because it's "an architecture redesign which requires time to create, test, then implement."
At present, Blizzard is taking three steps to help create Diablo 2: Resurrected more reliable and accessible. Rate limiting this will place the limit on how rapidly and often players can create and join games; the establishment of an MMO-style login queue to ensure that servers aren't smashed by a large number of concurrent logins; and disaggregating important functions into smaller parts.
However, these measures may end up alienating a section in the Diablo 2: Resurrected player base completely on their own. Players who reach their limit on their rate, for instance are likely to receive an error message that says there's a problem connecting to game servers.
This isn't that different from what they're running into now (but it's likely to D2R items for sale PS4 and affect lesser people) Login queues could mean players face lengthy waits before they're allowed into the game. Both are far better than what's currently happening, but won't do much to address widespread calls for a complete elimination of these annoying issues.
Comments (0)