It doesn’t work out of the box. Troubleshooting required.
And this was a huge surprise to me. Given the past quality of Blizzard’s games, and the extremely long wait fans had for Diablo 3, you’d expect it to be extremely polished and launched without a hitch.
After all, they run the world’s most massive and profitable MMORPG World of Warcraft, so you would think they know a thing or two about server loads and whatnot.
That didn’t happen on May 15th, which was the worldwide launch of Diablo 3. Three days later, gamers are still plagued with problems. I can attest to that, being one of Blizzard’s fanboys who pre-ordered the game and played the beta.
Had to install the darn thing twice as the updater patch didn’t work the first time.
Then kept getting error 3007 and booted out of the game. Was incredibly irate and about to throw a shoe at the screen after three hours of debugging error 3007.
I decided that it was probably not my computer’s problems even though Blizzard’s forum claimed it was a client side issue because:
— all of my other online games seem to play fine
— if thousands of folks around the world are having problems, I can’t be the only one
I had originally wanted to write up my first impressions of Diablo 3 this weekend, but I couldn’t even get the game running.
Al least Blizzard has issued a formal apology to all its fans, but this didn’t stop it from getting caustic reviews on metacritic, many who thrashed it for forcing online persistence for a single-player game.
After all, with the advent of crowdfunded games — Wasteland 2 and Double Fine Advertures are two great examples — traditional games publishing might give way to more hybrid, flexible game publishing models.
Oh well, I’ll probably try Diablo 3 a few hours later or tomorrow. The network issues will probably be solved by then. Hopefully.