Up to LvL 6, then it was over
Warning! There was an error. (Code 316719). This is the real life santuary we live in.
Error 37 all over again boys. LOL
1 Like
Getting the exact same error and then I get thrown into a 100+ minute queue. So, thanks, Blizzard. 
got to level 4 now sitting and staring at my amazing character hoping to get back in past this code lol
I closed it out now a 35 min que. I tryed making a new character but it did not work
Yay fellow error 316719 peoples! I made it to level 5, at least its something ya? Happy beta day, nothing like staring at a error code and pondering if waiting in an hour queue (for the 3rd time) is worth it. Decisions Decisionsā¦
1 Like
Well, I went from level 3 to 7 before erroring out again.
Also, just started submitting bug reports whenever the game kicks me to the character select screen and does not allow me back in.
This is a jokeā¦now its a 110 minute que time. Well, the like 30 minutes of gameplay I got was fun I guess. (not including the cut scenes and what not)
Guess I will just try again tomorrow morning, not going to wait for a third time today.
I just got this error after putting an item into stash, what this error looks like to me is classic de-syncing from the servers due to severe server lag and the server isnāt releasing your character from the game, so its stuck until the server releases your character either by a server restart or the serving crashing, this happened on D3 release and on D2R release AND the Blizz staff knew this has been an issue.
Now stuck in 2 hour queue to get back into the game and if this is indeed similar to Error 37 then the error will persist until the server is reset because the game āthinksā you have an active character in-game, so creating a new character or playing an existing character will result in the error, and honestly? Could even further mess up your account, this error needs to be 100% addressed before launch if this is the case.
What I did after getting the error further confirms my suspicion that this is the problem because I created another character, same error - so Iām 100% sure this is classic Diablo de-sync issue.
Simple fix would be to add in an auto-kick feature for inactive or AFK characters, that would release the character from the server and should fix this error, but what do I know?
1 Like
Received 316719, took me to character screen. Canāt start a game, but I donāt want to quit and enter a 90+ minute queue. Has anybody had success just waiting and clicking Start Game until it cleared? Or does the only recourse seem to be restart client?
But if you cant play, I dont think staying in game will ever resolve that. Re-queueing, while painful, is the only option.
This is my 4th time today already, Iām finding is that if and when you get in the game DO NOT go back to the screen to select another or new character or you will get a code 316719 error and will not let you back in. Once I was in I could play just fine.
So they reusing the old faulty netcode?
lol
So far only recourse seems to be restarting client. Messing with settings or waiting or making a new character or changing your tier difficulty - none of those seem to make any type of difference.
3 Likes
Heck, if I remember correctly from original D2 launch this also happened at early launch too!
Was just going to ask if I need to restart or whatā¦ been trying for about 10 minutes to re-enter a game but keep hitting 316719 each time.
Watching my hubs play while I twiddle my thumbs in the bloody queā¦
Got the error & then client crashed so here we are.
Read my post, Iām pretty certain I know whats wrong.
1 Like
Why go back to the character screen? Also, it seems like if you get any type of error message that results you getting booted back to the screen results in then getting the 316719 error code. This last time I got booted was just a āconnection lostā error, sent me to the character screen. Tried to pick my person and get back in, hit me with the 316719 error (RIP)
1 Like