Sign in with
Sign up | Sign in

Game Breaking Bug Already Spotted in Diablo 3

By - Source: Kotaku | B 4 comments
Tags :

Diablo 3's launch has been a tale of server outages and player woe...

You’d think that after successfully launching a game that’s been hyped for well over a decade, Blizzard’s Diablo III team would be sitting back to relax. Apparently not. Every Diablo III developer I spoke to at the game’s launch party at the Irvine Spectrum Center in Blizzard’s home city said that they’d be right back at work the next day.

Between all the Error 37s I’ve encountered through the 15th and 16th, I can definitely see why. Blizzard’s got their work cut out for them. Diablo III players know what I’m talking about. For most of the first day of the launch, Diablo III servers were overloaded and under maintenance, much to the sorrow (and sometimes wrath) of gamers who had ditched work or school in order to play the game.

Despite those hoops and ladders to jump through in order to play Diablo III, gamers have other concerns to worry about when playing: game breaking bugs. The trigger for the bug is fairly easy to trigger too. After acquiring the Warrior companion, if Diablo III players decide to equip the NPC party member with a shield, they will be kicked off of the server with an Error 3006.

Blizzard’s already been made aware of the issue and actually has compiled an entire list of game breaking bugs on the community forums. It's currently in the process of addressing each of these bugs.

It’s sad to see a game that’s been so highly anticipated be plagued with such launch issues. Then again, at least it’s not Duke Nukem Forever.

Discuss
Ask a Category Expert

Create a new thread in the UK News comments forum about this subject

Example: Notebook, Android, SSD hard drive

This thread is closed for comments
  • 1 Hide
    MajinCry , 17 May 2012 20:13
    What!? A game company that actually gives a damn about fixing their game's bugs?

    Major kudos to them.
  • 0 Hide
    refraction , 17 May 2012 20:43
    Agree with MajinCry, they spotted it, told people not to equip a shield until theyve killed his mate jolnar or whatever he's called, which isn't long after getting the companion anyway, most people wont know how to do it, its a diffrent key to Diablo 2 for a start.

    blizzard have made a good job of trying to address the issues that have arisen. Im more dissapointed in the people who were supposed to be beta testing the game not finding it in the months theyve been playing, after all, isnt that the point in beta testing?

  • 0 Hide
    mathew7 , 18 May 2012 15:23
    I'm so glad I fought the urge to buy it.....2 reasons kept me:
    1. (the most important) the online requirement....I'm not a "social" gamer....I want to enjoy MY game.
    2. (nail in the coffin) price

    Regarding the online issues, I've watched SWTOR launch news. I remember that was much better, with announced staged logins and it was not even worldwide (my EU country was not on the dec11 list along with 3 more....not to mention non EU/USA/Canada users).
    Not to mention the "it's ok to have bugs" mentality even on console games (long gone are the PS2-impossible-to-update game requirements).
  • Display all 4 comments.
  • 0 Hide
    Anonymous , 4 July 2012 17:11
    Kudos? You are kinding? The game is sold as a premium package at a high cost to gamers and has game breaking bugs after 10 year dev!
    So glad I passed this overhyped overpriced over DRM'd remake of Diablo.
Taylor