This morning at 12:01 AM…. Blizzard proved how to successfully kill a single player game.
For some reason, Blizzard has decided that in order to play Diablo 3 single player.. you have to sign in to battle.net, and you have to STAY signed in.. there is no offline mode. The problem with this logic..is that Blizzard then turned around and ignored everything they should know about launching popular games. They failed to have adequate battle.net servers, which meant huge chunks of people saw this when trying to play:
The failure rate was so high… #Error37 was trending WORLDWIDE last night… #Diablo3..wasn’t trending anywhere. How bad do you have to screw up, to have your error message trending more than your game?
As if the failure to have enough battle.net servers wasn’t enough… to add insult to injury, Blizzard Customer Service.. was telling people error 37 was a problem on their end, and they needed to reboot their cable modems, or re-install the game.. because, you know.. that will suddenly create more battle.net servers to sign into.
While attempting to log in and play last night, I reached out to @Bashiok, @Diablo, @BlizzardCS, and @mikemorhaime to try and find out how to play a single player game, with out having to log into obviously over-capacity battle.net servers.. none of them responded to me.
I suppose I’ll try to play again today..but at this point, the little desire I had to play the game, is pretty much gone based on the horrid launch experience.