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.
I actually got to play this morning, but I did have to deal with the error for around 30 minutes.
I tried sporadically for the most part, then about 30 minutes after my first attempt, I decided to spam the logon screen and got in on my second try.
The game is awesome, so there is that.
@Darraxus – There was a good response to that last tweet I posted. It said, basically, that once you are in the game, you don’t have the desire to leave just to use Twitter.
I will get to try tonight.
I’m struck by the good-natured sense of humor present here. I’m probably missing all the rage given the nature of the post, but good to see some people took the opportunity to have a laugh over it.
Per Ars Technica, this may not be the only major bug you’re missing out on: http://arstechnica.com/gaming/2012/05/diablo-3-give-a-knight-a-shield-and-he-kicks-you-from-the-game/
@ Aufero: I did not have an issue with giving the Templar a shield, but then again, I didnt give him anything until after you hire him.
I’m fully convinced that this is intentionally. Rather than spending more money to handle the massive, and one-time spike of player activity, companies just set a limit and let everyone bash their heads against it for a few hours/days.
Quick! Reinforce the D3 node!
Ohwait, wrong company. ;-)
@HWL – Well, even a reinforce requests takes advance notice and a downtime cycle before it can be implemented. I’ll see how they responded in a few hours.
Pingback: The Internet Strike Back [Diablo 3] | Diminishing Returns