In just a week’s time (FINALLY!) Diablo III is actually being released. When you get home after picking up your copy from one of the many midnight launches (or y’know, just pre-install the thing) and try log in to battle.net, you might end up frustrated and dejected – because there’s a pretty good chance you won’t be able to connect.
The reason for this, as you might expect, is that Blizzard is expecting a megaton of users to all try logging in at pretty much the same time – once those servers go live. to ensure a stable service, Blizzard might implement a 40 second delay in connection retries, so the servers don’t collapse under the weight of millions of people intent on clicking the devil away.
“It’s possible we’ll need to adjust the rate at which we’re logging people in to ensure a stable experience, and if we do you may see a delay when attempting to login,” Blizzard warned. “Please be aware that a delay of up to 40 seconds is possible while the game attempts to connect you. If your connection doesn’t succeed in 40 seconds, you’ll be presented with an Error 37 message and asked to try again.
“If you see this error it does in fact mean that you should try again. We’ll be working around the clock to keep you informed of any issues that are occurring through the in-game breaking news window, as well as the official forums.”
Additionally, Blizzard has suggested you create your Battletags NOW to avoid unnecessary delays or immense disappointment in not being able to register to play during the launch period.
“We expect that on launch night both the game service and website will be under very heavy strain due to the immense number of people excited to be among the first playing Diablo 3. With that in mind, we highly recommend you create your BattleTag now, as it’s required to play Diablo 3.”
Blizzard’s outlined a number of other things you should probably look at doing before launch, in its Launch Day Preparation Guide.
Last Updated: May 8, 2012