Multiplayer / host and progress

Hosting and Saves

Big Walk uses a host-owned world rather than a transferable shared save. Pick the host deliberately: that player keeps the world progress, and the same host is required when the group returns to it.

The verified save model

Save owner
The host
Saving
Automatic
When the host stops
Other players disconnect
Continue later
The original host resumes the world

Choose the world version before launch

The host selects a world version for two players, three players, or four-or-more players. Match that choice to the group expected for the session rather than treating it as a graphics or difficulty preset.

  • Confirm the expected headcount before the host creates the world.
  • Choose a host whose device and connection can stay available for the whole session.
  • Keep the host role with the same person on later play dates if the group wants to resume this world.

What autosave does and does not imply

The official FAQ confirms that the host's system automatically saves and holds the group's progress. It does not say that each guest receives an independent copy of the world.

  • Allow the original host to reopen the saved world for the next session.
  • Do not promise that a guest can reconstruct or inherit a missing host save.
  • For a suspected save failure, record the host platform, game version, last known progress point, and interruption time before contacting support.

If the host leaves or disconnects

When the host stops hosting, everyone else is disconnected. This is documented session behavior, not evidence that the guests' installations or accounts are broken.

  • Stop new interactions and agree on a regroup landmark before retrying.
  • Have the original host reopen the world, then share the Join Code generated for that session.
  • If the host also had severe frame-rate or connection trouble, resolve that first because the FAQ notes that poor host performance can affect the network session.

Join Codes are session-specific

A short Join Code is generated whenever the host begins a session. After play starts, the host can find it under Session Details. Friends should use the code for the currently running session, not one saved from an earlier night.

Practical host checklist

  • Name the long-term host and verify the selected world size.
  • Update every copy of the game before creating the session.
  • Share only the current Join Code through a trusted group channel.
  • Test voice or text while everyone is together.
  • End at a recognizable place and note what the group completed; this is a coordination record, not a substitute for the host save.

Sources and evidence boundary

  • Official Big Walk FAQHost ownership, automatic saving, disconnect behavior, world-size choices, and Join Codes.

Last verified: 2026-08-06

阅读简体中文