Player problem
Open this when an old save no longer feels trustworthy after a patch or long break.
Returning Player Review
An update entry for rechecking the first few pages that old habits usually break first.
Database entries answer the first practical question. Once that answer is clear, the linked full page should take over.
Best linked page
Open the returning-player checklist
Player problem
Open this when an old save no longer feels trustworthy after a patch or long break.
Where to use this
Use this as the first re-entry stop after a break instead of rereading every old guide.
What you need first
A save that has been idle long enough to feel stale or a patch that changed the route feel.
Next click
Database fields
Updates
updates
Updates
Use this as the first re-entry stop after a break instead of rereading every old guide.
Updates
Resetting an old save without reopening the whole library.
Updates
Check the modded-save page
How to use this entry
Rebuild the baseline, then move back into the exact route page that now matters.
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
Aug 2026
An update entry for separating patch changes from mod baseline issues.
Aug 2026
An update entry for route trust, landmark changes, and map revalidation.
Aug 2026
A co-op entry for checking that every player is on the same version before deeper troubleshooting.