"As we’ve unlocked the Diablo 3 installer early, many people will be ready to log in right when the servers go live at midnight, so we’re going to be closely monitoring the impact on the service," Blizzard states. "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. 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," the company adds. "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."

The guide also points out that fans can purchase the game now via Blizzard. The installer will actually be unlocked at 8:01 a.m. PDT on May 14 so that users can begin to install the game, troubleshoot any issues that may occur, download and install the launch day 1.0.1 patch, and be ready to play as soon as the servers come online.

"We’ll be turning on Global Play when the game has launched in all regions," Blizzard says. "This means that you will not be able to play in a region outside your home region until after the Americas’ midnight launch at 12:01 a.m. PDT on May 15. We’ll provide an update once Global Play is enabled, and you’ll then be able to change the region you connect to through the game’s options."

Characters, items, and friends lists will not transfer across regions, and players who use Global Play to connect outside of their home region will only be able to access the gold-based auction house, Blizzard reports.

The Americas servers -- which include the U.S., Canada, Latin America, Australia, New Zealand, and South East Asia -- open at: 12:01 a.m. PDT, May 15. For the complete Diablo 3 preparation guide, head here.

Wow, way to missinterpret toms... they are not enforcing anything. They say its gonna be busy so they might need to throttle things a bit, however the client is programmed to timeout after 40 seconds, they arent forcing you to wait 40 seconds.