Saves and replays

Save a local match#

A local checkpoint preserves the world and pending admitted orders. Loading it replaces the current local timeline and pauses at the restored point; resume when ready to continue. Orders admitted before saving are not converted into extra immediate actions by loading.

Keep a replay when you want the recorded history. Playback follows the recorded commands and controller changes, including bot actions. It does not ask the bots to invent another match. Seeking back and forward should return to the same recorded world state.

Continue from a replay#

When watching a local recording with one original human ruler, pause at the point you want to continue and choose Continue as that ruler. The game writes a separate manual save, then opens it paused at the recorded tick. Your new orders start a new timeline; the original replay stays unchanged. The button is disabled while seeking, after the result, or if playback failed. Shared recordings with multiple human rulers do not offer this local branch.

Match the build#

Saves and recordings bind their game rules, data and protocol versions. A file from an incompatible development build is refused rather than silently changing its meaning. Keep the matching build with important recordings.

The chronicle records public events. It does not expose another ruler's private orders, resources or negotiation attempts. Local pause/save/load is not available inside a remote match; remote continuity uses the agreed recovery procedure in reconnecting and continuing.