Diablo III Gets “Emergency” Update, Already Beaten By Korean Gamers
Diablo III is now available for consumption, and although it’s less than 24 hours old, the game has already been updated in order to address “error 37,” which is the subject of much discussion on Twitter. Apparently, however, error 37 didn’t stop a few Korean gamers from enjoying the game.
So much so, in fact, they’ve already beaten the game. More on that in a moment, however. The “emergency” update was released by Blizzard in order to address the already-famous error 37, which, according to the Diablo III forums over at Battle.net, was caused by the servers being at full capacity. The game’s developers addressed the issue over at the same forum (who needs Twitter or Facebook?), by saying:
11:30 a.m. PDT- We are in the process of performing an emergency maintenance for Diablo III servers in the Americas to resolve several issues that are currently impacting the game. This maintenance may cause some interruption in communication, ability to log in, use of in-game features, and disconnections. We anticipate all servers will be available for play at approximately 1:30 p.m. PDT. We will provide further updates as necessary. Thank you for your patience.
As indicated, Twitter was quick to react to the error 37 news:
If I were someone who enjoyed using Twitter-speak in my articles, this is the point where I’d be using the “SMH” abbreviation. With that in mind, worry not, Diablo III fans. You ain’t got no problem, folks. Blizzard is on it. Go back in there, chill them players out and wait for the fix, which is coming directly.
(Hat-tip to Quentin Tarantino for the inspiration for that previous stanza)
As for the game itself, some Korean gamers were so eager to get their hands on it, they’ve already beaten it. It only took them five hours to do so, no less. Apparently, the gamers in question completed the single player mode under the normal difficulty setting, which gives all you even harder-core players a new goal to shoot for: beating Diablo III in an expeditious manner, but on a harder difficulty setting, something I’m sure thousands of gamers are working on as I type.
To document their achievement, the gamers in question took a screenshot of the final boss. We’ve included a blurred version of the image in question. If you’d like to spoil yourselves, click the blurred image to reveal the unretouched version:
Click for the full-sized spoiler version… or don’t if you don’t want to be spoiled
Are they any other bugs you’ve noticed that Blizzard needs to address? If so, let us know what they are.