The launch of Blizzard’s long awaited Diablo III has rather predictably resulted in Battle.NET servers struggling to cope with the launch-day load.
Also predictably enough, thousands of angry fans descended on Blizzard’s forums to complain about being unable to connect. Instead of getting to play the game, they were greeted by an Error 37 – the servers are too busy.
Shortly after, the US servers went down for "emergency maintenance", initially for an hour but ultimately for three. At least that’s when some people got to play, other new Diablo III owners had to wait over half a day to get play online.
Blizzard tweeted that the developer was "testing and implementing multiple fixes for the current #D3 service" but then a game bug emerged manifesting as a time out Error 3006. This is apparently easily triggered by players performing common actions and after which, they cannot log in again.
The company tweeted that it was planning a "hotfix" to address the Error 3006.
It’s somewhat embarrassing for the firm to suffer such launch day trip-ups given the lengthy beta program but then few companies face launch day demand on anything like the scale of Blizzard games.
For those interested in giving the online RPG, 12 years in the making, a try out – the less patient may be well advised to give it a few days.
Want to receive up-to-the-minute tech news straight to your inbox? Then click here to sign up for the completely free PCR Daily Digest and Newsflash email services. You can also follow PCR on Twitter and Facebook.