Diablo 3 may not be playable at launch.

Various internet forums are reporting that users who purchased Diablo 3 during tonight’s midnight launch are unable to play the game due to servers being overloaded. Gamers who purchased the game are stating that upon attempting to play the game provides an ‘error 37’ code as being unable to connect to servers. At this time it is unclear how many users are affected. This appears to affect both single player users as well as those who are playing multiplayer due to the game’s ‘always-on’ DRM that requires a connection to the server to play the game in single-player mode. Updates will be posted if and when more information becomes available.

The error message users are seeing when attempting to access the server; collected via the internet 05/15/2012.

UPDATE: Both Eurogamer and AtomicMPC are reporting on the issue as well. A statement from Blizzard reported via the AtomicMPC site refers to a ‘high volume of traffic’ that could ’cause character creation to be slower than normal’. This is in direct contrast to user reports online which indicate that the game cannot be accessed at all.

UPDATE 05/16/2012: Bloody-Disgusting is reporting that some users still cannot access the game.

~ by Redgoateerob on May 15, 2012.

One Response to “Diablo 3 may not be playable at launch.”

  1. […] Diablo 3 was marred by the game’s always-online requirement, even in single player mode, when the servers were immediately overloaded and the game was unplayable at launch for a number of custom…. If Blizzard, a company with vast amounts of experience in the MMO field, was suceptable to these […]

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: