Same host, next session
Friday: Alex hosts and the group finishes the Red and Green routes. Sunday: Alex hosts again, and everyone continues that same journey where it stopped.
Big Walk Hosting & Saves
The host owns the save and automatically keeps the group’s progress. To continue the same journey later, the same host needs to start it again.
Choose your host carefully before your group gets far into the game.
Save and host rules checked Sep 2026. Autosave, ownership and the disconnect on session end follow the current official FAQ.
Saves, join methods and world settings all hang off one hosted session, and they are collected in the Co-op overview.
Pressing “Host Game” decides something bigger than who has the better connection. Pick with the whole journey in mind.
Once a group has real progress, someone else pressing “Host Game” is not the same as moving that journey across.
Nothing about the save is manual. The journey is kept for as long as the host plays.
1. The host starts the journey
Open the existing save or begin a new one, then load into the world.
2. Everyone plays together
The group joins the live session the host is running.
3. The host saves as you go
Completed progress is written to the host’s save while the session runs, with no save button to press.
4. The same host opens it again
The next session continues from that save. The world comes back as the group left it.
No. Group progress is saved automatically through the host.
There is no separate player-side save step, and no player has to leave the session to keep what the group has done.
Yes, to continue the same saved journey.
The save belongs to the original host instead of to the party as a shared cloud world. Whatever the group built sits on that player’s save.
Friday: Alex hosts and the group finishes the Red and Green routes. Sunday: Alex hosts again, and everyone continues that same journey where it stopped.
Sunday: Jamie hosts instead. That starts Jamie’s own save, and Alex’s Red and Green progress is not waiting inside it.
Players use these two words for the same thing, and they behave differently.
The journey itself — the progress one player keeps and reopens.
The live game running right now, which friends join with a code.
Same save + a new session = a new Join Code.
There is no normal in-game way to move your journey to a different host.
A player who starts their own session is hosting their own save. It is a brand-new journey with none of your group’s progress in it, however many of the same friends join.
Officially, the original host has to host again to continue that saved progress. Treat hosting as the one job only that player can do for the journey.
Ending a session ends it for the whole group at the same moment.
1. The host ends the session
Closing the game or stopping the session counts as ending it.
2. Everyone else is disconnected
The live game disappears for the other players together, not one at a time.
3. Nothing hands over
No other player is promoted into hosting that journey.
To carry on, the original host starts the saved journey again and the group joins the fresh session.
Multiplayer Troubleshooter →No.
A Join Code identifies the live session. When the host reopens the same save, that session simply gets a fresh code and the progress underneath it is unchanged.
How Join Codes WorkYes. The save follows the host, not a fixed list of players.
The group that started the journey does not have to be the group that continues it. Anyone the host invites into the next session arrives in the same save, with everything so far intact.
How many of those players usually show up is a world-setting question, not a save question.
Check 2 / 3 / 4+ Settings →Held or worn items return through Lost & Found at the start of the next session.
An empty-looking character after a session is not lost progress — check Lost & Found first.
Full Lost & Found GuideThat is a save error on the device rather than normal save ownership. Free up storage and try the same save again.
Fix the Save Error →The questions players ask before a first long session, and after the host goes offline.
Yes. The host saves the group’s progress automatically while the session runs, so nobody stops to save by hand.
How saving works →The host. The save game and everything the group has completed stay with the player who runs the session.
Why the same host matters →Yes, if the group wants to continue the same journey. The original host opens that save again and everyone joins the fresh session.
Continuing a journey →Not on the normal hosting model. Another player starting a session is playing their own save, so the group waits for the original host.
Hosting without the original host →Big Walk does not publish an in-game way to hand a saved journey to another player. Officially, continuing that progress means the original host hosting again.
Hosting without the original host →No. The code changes with each session while the save stays with the host.
How Join Codes work →Everyone else is disconnected at once and nothing hands the session over, so there is no new host to keep playing under.
Host ended session error →Yes. The save follows the host rather than a fixed list of players, so whoever the host invites into the next session arrives in the same journey.
Changing the group →Held or worn items come back through Lost & Found at the start of the next session.
Lost & Found guide →That is a save error on the device, not how save ownership works. Free up space and retry the save.
Fix the save error →House House’s own FAQ states the autosave, the host-owned save and the disconnect on session end.
Read the Official FAQ