Turn rollback ramifications

[llamabeast]

Heh, well a rollback is worth trying in that situation, but I would expect the same thing to happen again! In fact it would be somewhat mysterious if it didn't.

Anyway if you did want to rollback in that situation it would at least be very easy to try, since the admin could rollback and then force hosting without any players getting involved. On the downside, whenever dominions crashes on llamaserver, what is generally actually happening is that hosting takes infinite time rather than crashing outright. I then have to go and kill the process, and in the meantime everyone wonders why the llamaserver has stopped working (it's not allowed to host more than one game at once, so all other games will get stuck waiting for that game to host; also the "Last updated" time will stop updating which is really just an indication that it is unhappy).

[Muse]

Say, would it be possible to make rollbacks completely safe by simply auto-creating a new game iteration for each rollback?
IE-- the turn file is resent, and only turns done for the new file are accepted.
Everyone would have to re-do the turn, but it shouldn't be possible for overlap troubles to occur.

Perhaps a requirement to place the game-name (for the new iteration) in the e-mail subject would be useful.

I am aware that the Llamaserver determines game-identity from the 2h itself, but I am not certain how that is done. Perhaps a hash in the 2h?