Diablo III launch day!
However, I wasn’t going to stay up until midnight to play. I am too old for that sort of thing. But it sounds like I missed a shared experience. When I checked Twitter this morning, Error 37 seemed to be the topic of the day.
Blizzard’s response is to… well… hang in there and keep trying.
We’re aware that some players are experiencing Error 37 when attempting to log in to Diablo III. This error indicates that the Diablo III server is full and is likely the result of high login traffic. If you receive this error message, please wait and try again.
Error 3005 and 3006
Along with Error 37, we’re also aware of players receiving Error 3005 and Error 3006. If you receive either of these messages while playing, please wait and try again.
We’re still looking into these issues; however, a player workaround is available. If you are experiencing either of these issues and are using Windows, create a new user account with administration powers (http://www.wintuts.com/Manage-User-Accounts). From there, log into Diablo III.
Character Creation Issues
While most of the character creation issues have been resolved, it’s possible that if you attempted to create characters previously and did not log out, you may have actually maxed out your character list. If you are still receiving an error creating new characters, log out and log back in and then check your character list.
Hopefully all this will be cleared up by the time I am able to try logging in tonight.
If nothing else, this sure seems to be a sign of sales success.
I just still wish that they had not ditched offline and LAN play.
And it seems that not everybody is getting error 37.