I come back from a trip and can’t wait to get to my computer to play a bit of Diablo 3 all through Sunday night!
First, I get my favorite error 37 (server busy) and then I get Blizzard’s message that they are working hard on the servers, fixing GOD KNOWS WHAT. It’s definitely not a scheduled maintenance as no one in their right mind schedules server maintenance for Sunday evening.
So why the unplanned server maintenance and more importantly, why the silence? Tell us what’s wrong and WHEN (in your estimate) it is going to be fixed. That’s like an auto mechanic saying, “thanks for leaving your car with us, we might have found something, drive a bike for the next month but might fix it tonight. it’s just one of these things, you know, you can never tell which one it’s going to be – a month or an hour.”
I get it when people said about the open beta – relax, Blizzard is tuning their servers and that’s why you get errors, you are not even supposed to play. But once I’m a buying customer I do have certain rights – as in when I’m going to have access to something I already paid.
Not to mention I only play singleplayer and if it was Diablo II, I wouldn’t have had this problem in the first place. And yes, I got killed twice on Friday because the servers lost my connection (I definitely had Internet connection). So Blizzard’s DRM is killing both hardcode mode and my schedule with all these server issues!
End of rant!
Update: OK, we have now moved to error 3003 – so the battle.net servers are totally unconnectable (if this was really a word). A lot of people complaining about the errors as for the majority this is a SINGLEPLAYER game.
Update 2: I managed to log on to THE AMERICAS! Go, go, go! OK, EU is back up, now I get error 37!