There was an error. (Code 316719)

Shroud, Kripp, Mathil and Quin are currently in 60+ min queue due to this error.

Been getting this error. Stuck at Character select. Dont really want to quit. Any update on if this error will resolve itself on the server side?

It won’t. Just bite the bullet and restart.

5 hrs later and still happening. Been kicked 3 times in dungeons. Get knocked back to Character Select Screen after a “Network Disconnect”, click on Character and Start Game - Error 316719. Can’t do anything. Quit game, Launch game, get in 100min queue.
If you can’t fix the network disconnect error right now, then at least fix the error preventing us from getting back into the game from the Character Select screen.

That is definitely not how “Betas go”

I expect bugs and minor issues for a Beta. But not that such a big company provides worse and less servers than Indie Companies.

As if there would be millions of players lul…

1 Like

been stuck trying to get my first toon in, not gotten a single second of gameplay yet, and blizzard have gone rather silent

And how do you expect the open beta to handle the servers?

Same. What a great way to waste money on early open beta.

Queues and counting always getting this error at the end.
The first time i tried i was able to play for around 10 minutes before getting disconected.
On the bright side, as people give up on the game the queues decrease and atm it’s below 10 minutes! :slight_smile:

I am staying inside the char screen with faith :smiley:

I waited 30 minutes in that screen clicking play. It didn’t work. I ended up quitting and restarting the game because I might as well queue for another hour than wait and not be able to get in at all.

Level 20 is a pipe dream at this rate. GG Blizz.

Same error (Code 316719), waited 2 hours at character select screen, same error, created new character, same error, finally logged out, now in 85 Min Queue.
I don’t think they are telling us what to do because they honestly don’t know. And yes, its extremely frustrating wanting to get a taste of something new from Diablo franchise, so this kind of launch is extremely disappointing and yet, very expected. SSDD.

Just got this error aswell, I was fighting a Boss in the dungeon near where we start, doing a Sorceress related quest. The one you have 2 mechanical cubes to place to free a necromancer

Not surprising at all. This is just a preview of launch day. Error 316719 = the new Error 37. Ready for another disastrous launch? What kills me is the fact that they had a pretty darn good approximation of the number of players to anticipate for this early access beta since they are obviously tracking preorder numbers. I miss when games used to work.

1 Like

GOOD NEWS!!!

All the streams are still playing fine, go watch them.

1 Like

THIS!!! I want to know if this is true or not. I know I sat there for like 30 minutes and wasn’t able to. I got in queue because I didn’t know if its a registration thing.

1 Like

Like I said earlier. Every time you get error code, you need to restart client and wait in the queue otherwise you will just be stuck there banging your head.

Same for me. Disconnected in a dungeon and I couldn’t log back in or create a new character. Closed the game, 90 minute queue. Waited… got another error while in queue that closed the game on me. Now, I just started a fresh 80 minute queue again. Lame.

same for me, and no i won’t wait 100 mins again only to be able to play 30 minutes tonight

Sat through queue after getting this error to be met with a “No Servers to ping” error when the queue finished, game closed, back in Queue.