It was expected really, one of the most anticipated games of the last decade launched by a company that hosts the most subscribed MMORPG in the world and people are surprised by server issues on the first day?
For those of you who haven’t heard of Diablo 3, it follows on from Diablo 2, which was released back in 2000. Diablo 3 was announced by Blizzard Entertainment (the creators of the hugely popular World of Warcraft) in 2008. I have had my copy of Diablo 3 on pre-order from Amazon since early 2010. Early reports are saying that Diablo 3 is the most pre-ordered PC game ever and the UK launch event which happened at HMV Oxford Street is said to be HMV’s biggest launch event ever. (continues after pic)
All of this, to a game that requires access to Blizzard’s servers, is of course going to encounter problems, not as many as I Blizzard expected probably, but problems none-the-less.
One of the most common error codes received by gamers attempting to log in is Error 37, which means the server is full and users should just keep attempting to log in to Battle.net.
The trending on twitter has already started as users declare that Error 37 is actually a surprise Diablo 3 DLC and that Error 37 is now reserved as an insult for the most disappointing of failures. For more humour, check out the trending on Twitter.
What can users hope for once they do traverse the error codes and log in? Diablo 3 is a hack and slash roleplaying game set in Blizzard’s world of Sanctuary. Five character classes are available for players to choose from and hours of gameplay await.
Keep your eyes on FTN for my follow up article of Diablo 3 First impressions.
For those of you with serious error code issues, Eurogamer has posted a handy list of Error Code descriptions.
Sources – MCV
Pics from the MCV Facebook page.