Co-op & Server
Backup handoff
Use this when save ownership changes hands and the backup path needs to be clear again.
Shared worlds get fragile when no one knows who is keeping the clean backup. This page makes the handoff visible before the next patch or session resets the assumptions again.
Watch the main world owner, the backup copy, and the next update check so the shared save does not drift silently.
What to check
Keep the retest short and tied to one real failure.
Why this hub exists
The hub works best when it explains the maintenance reason before it starts routing you onward.
What this hub is for
Shared worlds get fragile when no one knows who is keeping the clean backup. This page makes the handoff visible before the next patch or session resets the assumptions again.
Current watch
Watch the main world owner, the backup copy, and the next update check so the shared save does not drift silently.
When to leave
Once the current failure is clear, move to Shared save ownership instead of staying on the hub.
Best next pages
Open the next page that owns the current failure.
FAQ
Short answers before you open another tab.
Why does the backup matter?
Because co-op saves drift faster when no one knows which copy is authoritative.
What comes next?
Usually the shared base flow or a version check.