Create a game too fast = timeout
Invalid game name = timeout
Trying to join a game that does not exist = timeout
Game is full = timeout
Crash = to the back of the que you go
Say you are doing baalruns in a public game. You have to analyze the gameplay of the host to figure out how quick he is with reactions etc, so you can somewhat gauge what his energy levels and/or cognitive status is so when it is time for them to create new game, you can adjust your typing/joining speed according to your read on how fast this person is about to type in the create game screen. If you fail at this calculation, you will be timed out for joining too fast and if you wait too long the game will be full. Gamble simulator 69420
Say you are doing solo mf runs, you better not want to do just meph because that is punishable behaviour. You need to time your runs because hey, if you make two under 1 minute runs in a row, it is time for timeout.
Crashes? unpredictable right? For me, I have noticed that If I run the game in order from a5 to a1, I will always crash when I go to the Countess. So adjust accordingly, right? Time to never do countess runs because a crash will net you a timeout in the form of a 2h queue
AND SOMETIMES YOU TRY TO JOIN A GAME THE YOU KNOW 100% EXISTS AND YOU GET TIMED OUT ANYWAY. AAAAAAAAH
So anyway, is this how things are going to be from here on out? I for one feel like that these little annoyances just start to add up and if this keeps happening consistently then it just sucks the fun out of the game.