@crusader8463: What's the exact error you're getting?

@Rawson: @BrockNRolla: @Bocam: Earlier it was saying that "The game was not out. Please come back later." Now it's saying "This battle.net account does not have a diablo 3 licence attached to it. Error 12"

@crusader8463: PM a GM on the Diablo forums and tell them about the error, they'll fix it for you.

@crusader8463 said:

@Rawson: @BrockNRolla: @Bocam: Earlier it was saying that "The game was not out. Please come back later." Now it's saying "This battle.net account does not have a diablo 3 licence attached to it. Error 12"

That's the authentication error from Asia and EU. I'll check mine to see what I get.

@BrockNRolla said:

@crusader8463 said:

@Rawson: @BrockNRolla: @Bocam: Earlier it was saying that "The game was not out. Please come back later." Now it's saying "This battle.net account does not have a diablo 3 licence attached to it. Error 12"

That's the authentication error from Asia and EU. I'll check mine to see what I get.

I looked again and it appears the game defaulted to EU. I changed it to NA and it changed back to the game is not out yet.

@BrockNRolla said:

@crusader8463 said:

@Rawson: @BrockNRolla: @Bocam: Earlier it was saying that "The game was not out. Please come back later." Now it's saying "This battle.net account does not have a diablo 3 licence attached to it. Error 12"

That's the authentication error from Asia and EU. I'll check mine to see what I get.

@Bocam is right. I don't get that error so you'll definitely want to get in touch with someone at Blizzard.

Can I change my region to EU and hop in just to check it out and switch back to Americas? Don't want to do it and be stuck.

I am starting a campaign to redo the launch of this game, it didn't take any of my choices into consideration.

@crusader8463 said:

@BrockNRolla said:

@crusader8463 said:

@Rawson: @BrockNRolla: @Bocam: Earlier it was saying that "The game was not out. Please come back later." Now it's saying "This battle.net account does not have a diablo 3 licence attached to it. Error 12"

That's the authentication error from Asia and EU. I'll check mine to see what I get.

I looked again and it appears the game defaulted to EU. I changed it to NA and it changed back to the game is not out yet.

Problem solved!

For now...

@wmaustin55: It'll say you don't own the game

Blizzard is gradually easing up the the server capacities to prevent an overload. That's why people are getting the Error 37 message. Just keeping trying to log in.

In the US. Just installed, updated and attempted log in. Took password and authenticator password just fine and fast. So far no problems here.

It has Begun!

Ya - Eurpean Battlenet is still down for maintenance.

Oh well - Guild Wars 2's 7 hours stress test just ended, and I'm tapped out. Let awesome be awesome, and go straight to bed. Hoping I'll get to play tomorrow without issues.

ArenaNet saved the day. My condolences for those who sat there staring at the Diablo 3 login screen.

@BrockNRolla: The problem for me now is that it doesn't come out until 4am here and I gotta be up by 7am and off to work by 8am. Got a couple guys in my training class that were literally going nuts all day today looking at count down pages, so I fear to see them tomorrow knowing they could be home playing it. I'm rather tired today, for some reason, so I will see if I can get to sleep early and see if I can get in a few hours before I go to work tomorrow. Will see how it goes.

@crusader8463: A problem for us all. I hope that it's running well enough for you to get in! Good luck!

I really hope that with all the COD and WOW money activision have that they don't screw up this launch in the US, given that they also run and maintain some of, if not the largest online gaming servers and data centers already; that there should not be issues at 12:01.

Kind of glad I bought a physical copy and won't be playing till tomorrow.