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). We mention “modern player behavior” because it’s an interesting point to think about. We did optimize this service in many ways to conform to more modern technology, but as we previously mentioned, a lot of our issues stem from game creation. Importantly, this service is a singleton, which means we can only run one instance of it in order to ensure all players are seeing the most up-to-date and correct game list at all times.
This service, with some upgrades from the original, handles critical pieces of game functionality, namely game creation/joining, updating/reading/filtering game lists, verifying game server health, and reading characters from the database to ensure your character can participate in whatever it is you’re filtering for. However, one legacy service in particular is struggling to keep up with modern player behavior. In staying true to the original game, we kept a lot of legacy code. In a statement issued by Blizzard’s Community Manager, the team details the reasoning behind Diablo 2 server issues, stating that some of the “legacy code” from the original 2000 release of Diablo 2 isn’t able to keep up with today’s modern online. While Blizzard has published a number of updates in hopes of resolving the issues, it would appear that some coding that was brought over from the original game may, in fact, be the culprit as Blizzard explains the reasoning behind Diablo 2 server issues, all while outlining their plans to fix it. If you’ve been playing (or trying to) Diablo 2 Resurrected these past few weeks, you’re probably well aware of all the server related issues going on.
0 kommentar(er)
