The alternative, where you write down just the, which is a snapshot of turn 1, and the which is all the orders and rng roles in order made by players, doesn't do this. But it may also contribute dramatically to snapshot size. This guarantees that future versions of wesnoth will have at least a chance to open saves from past versions, even if they are really crazy custom scenarios, and that crazy custom scenarios can be reloaded from a save. And this is repeated for every instance of that unit. That means, all its max hp, resistances, all its attacks, all the strings which correspond to the images corresponding to those attacks, all the wml for its animations and strings for this images, the entire help file description string, etc. One explanation for how this might happen is that, in a game state (snapshot), every unit is written down with ALL its details. I'm just guessing here, but what I am taking away from gfgtfd's comments is that even though the game history determines the game state, it still may take more bits to write down the game state than to write down the game history. Pentarctagon wrote:I know it needs the gamestate, but why does it need the game history as well? You can enable log for network data which prtints all sended/recieved game data in the stderr file. That is why I was speculating that Wesnoth is transmitting a massive amount of data during gameplay. If there were already information available on troubleshooting the problem, then I would have pursued that angle. I have researched this problem extensively on Google and read many forum messages and blog posts and change-logs written by the developers. I am not sure of the reason why, and the documentation does not offer any insight. It is only natural that other players may conclude someone stepped away from the keyboard, when in reality the problem is a technical, network issue. Of course, the other players had to wait as well in those cases. Sometimes I waited for half an hour for the lag to resolve. But I have come to a conclusion recently after comparing my multiplayer experience between one location and another. In the beginning, I was not aware that the problem was local, and thought it might be the server or another player.

Rapidclick github