The core save rule
The official FAQ identifies the host as the owner of the group save and says the game autosaves. That is the practical answer to who keeps progress. It means the host is not just a temporary room opener; the host is the person whose world the group will return to when it continues.
What the next session needs
When the group wants to resume the same journey, the original host should start the world again. Friends can then join through the platform friend route or a fresh Join Code. Agreeing on a regular host before the first long session prevents the group from accidentally creating separate worlds and wondering why the route looks different.
Autosave is not a manual checklist
The official wording supports automatic saving, but the collected material does not provide a complete list of every moment that triggers a save or how a disconnect is recovered. Do not publish an exact autosave interval or a guaranteed rollback rule without a field test. Those details remain待实测.
Cloud saves are a separate layer
Nintendo’s platform listing mentions Save Data Cloud support, but that platform service should not be confused with Big Walk’s host-owned world save. The same caution applies to Steam Cloud or other account storage assumptions. A cloud service may protect a device save without making a different player the owner of the shared world.
Crossplay and progress
Crossplay allows listed platforms to join the same type of world, but the official sources do not say that every platform can independently resume the host’s progress. Keep the host stable and treat cross-platform continuation as a session-ownership question. If a different device or host needs to carry the world, label the result待确认 until directly tested.
A group routine that works
Choose the host, name the world or session in your group chat, and use a fresh Join Code when friends cannot see it automatically. At the end of a session, tell everyone whether the host will be available for the next run. This simple habit is more reliable than trying to infer ownership from the player who solved the last puzzle.
What this page does not promise
There is no evidence here for shared progression, host transfer, manual save slots or a universal recovery method after a crash. Those may be useful future research topics, but they are not facts in the current source set. The safe answer remains host-owned autosave and original-host continuation.
Field test noteDo not turn platform cloud-save support into a promise of cross-platform host-save transfer.