Couldn't the game state get loaded to the client in this case? 

I don't know for sure, but my guess is that this behavior wasn’t implemented to allow players the chance to reconnect. In the past, the game may have had more stability issues, and it probably didn’t seem fair to punish players for something that could have been caused by the game itself rather than by them. Yeah, this seems like the most appropriate behavior, since it also allows the disconnected player to rejoin the game. Many times that’s exactly what happens: the player reconnects. Also, since it’s very common to play against people you know, it’s useful to be able to pause the game and wait for the client to reconnect before resuming. On the other hand, if the host disconnects, it’s reasonable to count it as a resignation, since one could argue that the host is responsible for ensuring that their connection is stable. Just brainstorming: Maybe it would be good to have a short grace period before a disconnection counts as a loss. For example, during the first two minutes of the game, if someone disconnects, it wouldn’t count as a loss, since it’s unlikely that the player left because they were losing. Another idea that comes to mind is some kind of “offline timer.” Each player could have, for example, up to five minutes to reconnect to the game. This would give them a fair chance to resume, while also avoiding situations where the remaining player is forced to finish the match alone just to secure the win. The offline timer could continue running even while the game is paused.

Ey, @AlexHerbert and @sarcoma ! I'm yet to port this mod for R28. I'll work on this during this week and I will upload the new version 

Not that I know of.

@Stan`, thank you!   But it looks too complicated... Is there something more user-friendly ? Something like in civilization description in the game GUI?