It sucks, that the client does not recognize you were trying to reconnect. I had more the win in the league with lethal in hand and three against one warrrior. But the client crashed. Oh well, he does often, way too often. When I reconnect, I pressed yes and while loading the game data, he crashed again. During the third restart I got the disconnect. This is more than annoying. The client should recognize I am active, when I press yes and try to reconnect to the game...
I agree, since i had some instances when the game froze without noticable signs. Once you notice and try to reconnect, you already got a delay. Then the game wouldn't let me past the spinning wheel at times, at least not in time to get back in my ranked game. Half a minute to a minute could have made the difference. A loss due to connection timeout can be very upsetting, especially in guild context. (would be greatly appreciated if the guild blitzes were fixed in that same disconnect context: http://forums.cardhunter.com/threads/suggestion-adjust-guild-blitzes.7924/) So either expand the time like proposed, or implement some immediate way to tell the user that connection or game went off the rails. Best would be of course when the client was more stable and would react better to a reconnect attempt. Often i feel its trying to reconnect me right back into whatever instable constellation threw me out in the first place instead of offering me a clean slate.
