Preparing the interactive tool. Please wait; the guide and worked examples remain available below.
Compare the old world with the documented change
This is a preservation workflow, not a rollback instruction. The official note says older saves may still load but may behave unexpectedly; it does not name a universal broken-save threshold or promise a backward-compatible branch. A successful load is not proof that future writes remain safe.
- Record the displayed game version and the save's approximate creation version if known.
- If the world predates v0.8.02, pause before opening it on the only copy after an update.
- Read the developer announcement and current Steam branch options. Do not assume an old-version branch exists unless Steam currently lists one.
- Use the current platform-supported save backup method; copy rather than move the original and confirm which profile/world the copy belongs to.
- Test the duplicate on the intended build. Check the map, base structures, inventory, and one recent objective before deciding whether to continue.
- If expected content is absent or behaves oddly, stop without overwriting the original and ask with build and save-origin details; never attach credentials or private files publicly.
| Situation | Safer next step | What the source does not guarantee |
|---|---|---|
| World predates v0.8.02 | Preserve the original; test a duplicate on the intended build | No exact save-version cutoff or conversion promise |
| Save origin is unknown | Record current build and test only a copy | No blanket compatibility statement |
| You want the overhaul's intended experience | Start a separate new world | Does not prove every older world is unusable |
| Old world loaded once | Check map, structures, inventory and objective before more writes | One load is not a rollback or long-term safety test |
References: Sunkenland developer: Main Branch Update v0.8.02 · Sunkenland Steam Community Discussions
Version-aware question worksheet
Keep an observed load result separate from a compatibility claim. A useful report says exactly which branch opened which duplicate and what you checked.
- Fill in platform, displayed version, and approximate save origin in the local worksheet.
- Compare the report against the developer's v0.8.02 warning and state clearly if the save was not available for inspection.
- Use Steam Discussions for peer reports only after confirming they describe a similar build.
References: Sunkenland Steam Community Discussions
Before you play
- I recorded the installed build and save origin where known.
- I have preserved an untouched original or do not yet have a backup method.
- I will test only a duplicate before saving over the source.
- I did not assume an old-version branch exists.
- I am not treating the v0.8.02 warning as proof every old save is broken.
Frequently asked questions
Should I restart every Sunkenland world?
The developer recommends a new world for the overhaul as intended, while noting older saves may still load but can have issues. That is a recommendation, not proof every old world fails.
Can the worksheet verify my Sunkenland save?
No. It stores only fields typed into this browser tab and cannot read game files, Steam branches, or world contents.
Sources & revision notes
Editorial revision: November 7, 2026; not a gameplay test date. The reference notes identify source limits and version differences.
- Sunkenland developer: Main Branch Update v0.8.02 (Official)
Developer update notes checked November 7, 2026. They recommend starting a new world to experience the overhaul as intended and warn that extensive changes may cause compatibility issues, missing content, or unexpected behavior in older saves. This is a version-specific warning, not a claim that every old save is broken today.
- Sunkenland on Steam (Official)
Official product listing for platform and co-op scope. Store text is not a complete mechanics manual.
- Sunkenland Steam Community Discussions (Community)
External player posts are user-generated and unverified by GamerWin; distinguish main/test/olderversion branches and include exact build when asking.
November 7, 2026: first publication. Scoped save advice precisely to the developer's v0.8.02 recommendation and compatibility warning; no save was tested.
How we research and correct guidesNo affiliate links or paid placement. Commercial disclosure.