Diablo 3 Stress TestAs a note: please make sure you’ve used the beta client and not the full client for the game. You will be unable to log in with anything but the beta client. If you can’t get in, don’t worry. They’re working on it. Many people think that the beta is broken currently, but they actually have hundreds of thousands of people in and playing right now; they’re just working on expanding that limit.

    Update: Beta is live!

    The #D3 open beta is now LIVE! #gogogo

    Update 2: Tip for those using non-US clients. Change your region to “Americas.”

    If you are connecting from a non-US #D3 client, be sure to change your region to “The Americas” in your game options for the open beta.

    Update 3: From Bashiok on “No License Error.”

    We’re investigating why some people are seeing a ‘no license’ Error 12 for the #D3 open beta. Hang tough.

    Update 4: From Bashiok on capped concurrency and errors.

    We’ve temporarily capped #D3 open beta concurrency until we can address some stability issues. Expect Error 37 and login failure.

    The open beta has begun and we’ve been extremely successful in that we’ve already managed to break a few things. We’ve capped the open beta concurrency until we can resolve some stability and service issues, and until it’s resolved you will likely see an Error 37 when attempting to log in.

    • Error 12 – This is an error we’re still investigating, but should only be appearing for Korean accounts which are not able to participate in the open beta. If you do not have a Korean account, we’re still investigating this issue but suspect it may simply be due to the Battle.net Account services being slammed by the high volume of traffic.
    • Error 3003– Click Options, under Account change your region to The Americas. The open beta is only being held on US hardware.[…] We have a ton of people in-game and playing right now. We’re just working on trying to get a ton more in.

    Many people have been met with “Error 3005” along with “Player Disconnected” messages. According to a recent blue, this error is intended. One poster explains that they were actually able to log in after repeated attempts, but the servers are actually down for maintenance that should conclude in about 13 or so minutes as was posted in a tweet by DiabloWikiBashiok.

    Vasadan said the following:

    Hey guys, sorry for the late response. We are in the process of doing some server updates right before Open Beta begins. If you continue getting this error message, come back in an hour or so 🙂

    A tweet a few minutes ago popped up from Bashiok on the same matter:

    Approximately 24 minutes until #D3 open beta… #crossesfingers

    I’m sure the “crosses fingers” part is in the hopes that nothing goes wrong in the maintenance necessary before the servers are flooded with beta participants. Bashiok posted this about 10 minutes ago, so we should see servers up and running in about 10 to 15 minutes.

    Good luck with the tidal wave that is sure to come! Thanks Ady for reporting this.

    Image credit: vxhelix

    You may also like