rafter109, on 15 May 2012 - 07:53, said:
Battle.net servers went live at 12:01 PDT, which is 3:01AM my time. I have been in touch with a multitude of users who from the very first moment have encountered the dreaded "Error 37" explaining that the servers were busy. While I understand that there are probably hundreds of thousands of users trying to log on, this only shows a complete failure on Blizzard's behalf on several fronts:
1. Being one of the most anticipated game launches in years, Blizzard knew what to expect in load and should have planned accordingly, even if it required leasing additional servers for launch.
2. Blizzard insists on requiring all users to authenticate with their servers each time a user wants to play. Single Player anyone? Not if Blizzard has anything to do with it.
3. Blizzard caused massive unnecessary network traffic by not staggering launch times based on locale
4. Blizzard also caused massive unnecessary network traffic by forcing all game data to go through their servers.
5. Blizzard removed LAN play option that was present in Diablo 2 forcing users who want to play with friends to use Battle.net servers, yet again, causing massive unnecessary network traffic.
This is not the first time Blizzard has caused something to be totally fubar. Starcraft II launch was also plagued with these problems.
Message to Blizzard: Stop screwing your customer base!!! Listen to what they want and give it to them. You are in the entertainment industry and as such the customer truly is always right.
uh the game had a staggered launch, i was playing for hours before my american mates got on, and while i was ****ed off at the lauch - after 45 minutes i could freely login and out without issue - i have logged in this morning without issue and the game is running and working fine.
as to the always online thing, they do the same thing with starcraft, and I'm always connected so i don't particularly care