Diablo 2 Resurrected on Consoles Won't Let You Play After 30 Days Offline
People playing Diablo 2: Resurrected on consoles have a problem. It turns out that after 30 days of offline play you have to log in again.
One of the arguments console gamers used against their PC brethren, claiming the superiority of their platforms, was the lack of need for an Internet connection in order to play offline. Used - because, as it turns out, Blizzard Entertainment broke that rule. Internet users noticed that after 30 days of not playing or being offline, you have to log back into Diablo II: Resurrected.
This "discovery" has greatly disgusted the community gathered on Reddit around the remaster of Blizzard's iconic hack'n'slash, now developed by Vicarious Visions. Its members ironically wonder if they've accidentally ended up on the subreddit for the PC version, and those who haven't bought it yet assure that they never will. Some ominously predict that this isn't the last DRM protection on consoles, while others don't seem to understand what's going on and think that someone has completely lost access to the game.
This, of course, is not the case - to get back to playing, you just need to log in again. What is more, it has been like this since the release. This solution is supposed to be a kind of protection, but we have to admit that it can be a nuisance, for example, for people who spend a long time in a place without access to the network. For PC fans of the Diablo series, however, this is nothing new - the third installment required a constant connection to the Internet, and some players report that the offline mode in Resurrected causes them such problems that they have to be online all the time anyway (although it should work the same way as on consoles, as Blizzard reported on its website some time ago).
Below are some sample comments - including the ones I've quoted above.
