Player problem
Open this when a patch or long break changed how the shared world feels.
Co-op Server Recheck
An update entry for multiplayer and shared-save revalidation after a change.
Database entries answer the first practical question. Once that answer is clear, the linked full page should take over.
Best linked page
Open the co-op after-update page
This is a structured lookup entry from the latest database batch review, not a claim of a separate save-file playtest. Use the linked full guide for the deeper answer.
Player problem
Open this when a patch or long break changed how the shared world feels.
Where to use this
Use this when the co-op world worked before, but now the shared baseline no longer feels stable.
What you need first
A shared world, a recent change, and one clear symptom of drift.
Next click
Database fields
Updates
updates
Updates
Use this when the co-op world worked before, but now the shared baseline no longer feels stable.
Updates
Keeping multiplayer rechecks separate from solo update problems.
Updates
Open the co-op hub
How to use this entry
Retest the multiplayer path before changing gameplay or route pages.
Common mistakes
Visual cue

Map handoff
Use the Core as the return anchor when the next route is still unclear and the save needs one stable base loop again.
Next page after this
Tags
Related entries
Batch reviewed Oct 6, 2026
A co-op entry for checking that every player is on the same version before deeper troubleshooting.
Batch reviewed Oct 6, 2026
A co-op entry for world ownership, backup handoff, and shared-save clarity.
Batch reviewed Oct 6, 2026
An update entry for rechecking the first few pages that old habits usually break first.