Reconnecting and continuing a match

Return to the current match#

A temporary disconnect does not make the missing ruler's state public. The session can restore a verified checkpoint and recorded turns, then return the original seat through its normal reclaim process. A caretaker can act for an absent human using lawful observations.

Do not treat a stalled connection as a new match. The current session determines which commands and controller changes belong to its history. Old packets cannot be mixed into another continuation.

When the original host is lost#

Continuing under another host is an explicit agreement to a verified earlier point. Before confirming, compare the proposed host, source turn, participating humans, absent caretakers, any bot-memory reset and the progress that will be discarded. Only confirmed original human participants can join that continuation.

The new match history begins from the chosen state. Resources, paid jobs and armies are not rebuilt from a fresh opening. Progress after that state is lost; separate continuations are not automatically merged.

The development build includes Friends-lobby entry, rejoining after an app restart, caretaker/reclaim controls and explicit new-host continuation. These flows have automated native-provider and browser coverage; physical two-machine Steam play remains unverified. Local save/load is described in saves and replays.