…”goddammit I’m still not in!”
…”goddammit, now it’s not letting me make a character!”
Even more clickclickclickclickclickclickclickclick…
…”and now it’s not letting me log in…oh, wait, nevermind, there it goes”.
A TORRENT of clickclickclickclickclickclickclickclickclickclick…
…”wait, WHAT time is it? GAD!”
Diablo 3 is, from what I can see, a gameplay experience that’s polished to a fine sheen. I’m not sure yet if I like it more than I do Torchlight, since Torchlight has a sort of earnest eagerness to please and indie charm that you just aren’t going to get from the Blizzard monolith. I do like it, though. Diablo’s just as compelling as it ever was. Getting rid of the skill trees was a stroke of brilliance, too, that takes away the stress of worrying about your “build” and lets you get to the part you actually want to play.
That said, there’s one bit that ISN’T polished, and it’s the servers. Folks, having to log into a single-player game is bad enough. Having said single-player game not let you log in because the servers are too busy is just downright perverse. I think I saw the entire Internet start screaming “YOU GOTTA BE KIDDING ME” in unison a few hours ago, and they had every right.
Sure, rocky launches for online-only games are normal enough, but this never needed to be an online-only game. The only reason it is is due to Blizzard’s terror at the idea that the game would be reverse-engineered by people looking to game their real-money auction house. It will be reverse-engineered anyway, of course; but in the meantime, you’ve got people who own a single-player game that they can’t play because the servers are overloaded.
The worst part is that tomorrow’s going to be worse. This was just the die-hards who were willing to stay up all night. In about 14 hours or so, those servers are going to get hammered like a fratboy on St. Patrick’s Day. Unless they take action soon, it’ll be a debacle, and the stench of it will hang over the entire game for a good long time.