At least Blizzard gave us a warning this time. The Diablo IV studio issued a heads-up prior to this weekend’s open beta that players would absolutely, without doubt, experience login queues and have to wait in order to play the game. There is an “extraordinary volume” of players trying to get in now that the floodgates have opened, and the game’s servers are struggling to keep up. This is basically deja vu after last weekend’s myriad problems.
What this means is that many players are seeing half-hour or longer queues, which doesn’t sound that bad. Unfortunately, in practice this can often take much longer. Players are reporting their queue times increasing after the clock has gone down to zero or near-zero. Others are logging in only to crash out immediately and have to rejoin the queue from the top. You might also find yourself at the end of the queue only to get a “login token expired” message. Pretty frustrating!
Blizzard did say that this would likely be the case, and also pointed out that a beta like this is designed to ferret out bugs, server problems and so forth in time for launch. In other words, while it may not work great right now, all this testing will help the developers prepare for launch and that, in turn, should lead to a better, more stable launch experience.
If you’re having issues logging in, you can try again later or simply plan on being in a queue for a while. Get some laundry folded. Do the dishes. Just be sure to keep checking that you’re making progress and that you haven’t already been logged in. You don’t want to get kicked, either.
Another tip: Try logging out / closing Battle.net entirely and then logging back in before playing. Some players are reporting that this helps.
Further Diablo IV reading:
Are you having trouble getting into the game? Let me know on Twitter or Facebook.
Source: https://www.forbes.com/sites/erikkain/2023/03/24/diablo-4-queued-for-login-message-game-crashes-other-issues-plague-open-beta-launch/