Saves & progression
Before moving your Demo character to the full game
The developer said on October 19 that Demo saves could be transferred, but warned that some achievements would not trigger. The statement predates the planned November 6 full release. We have not verified a successful transfer into that release, so this page explains the choice and risks rather than giving a guaranteed file-copy procedure.
On this page
What was actually said
In reply to “Post Demo Transfer?”, the developer said the Demo is updated alongside the full game and named the Save folder in the game’s root directory as the transfer source. That identifies the developer’s intended route; it does not establish the final installation paths, overwrite prompts, Steam Cloud conflict behavior or release-build compatibility.
Choose your priority before replacing anything
| Your priority | Implication of the statement |
|---|---|
| Keep the time invested in a Demo character | Preserve a separate backup and seek a release-specific success report before replacing files. |
| Earn every achievement from a clean start | The developer warns that transferring progress can miss some triggers. A new run is the route they suggest for earning those achievements. |
| Keep both options open | Keep the old run intact. A backup is a separate file-safety measure, not an in-game manual save slot. |
Why the backup warning matters
The reply describes backing up, starting a fresh run for achievements and later returning to the older saves. We have not tested that cycle. Do not overwrite your only progress on the strength of this pre-release statement, and do not assume Steam Cloud is a versioned backup archive. Before attempting any replacement, obtain reliable instructions for the exact released edition and keep the original files recoverable.
The 1.06 cutscene advice is a different operation
Update 1.06 discusses old saves, the new opening sequence and a fresh game starting outside the fortress. Its Save-folder removal/restoration discussion concerns watching that sequence. It is not evidence of Demo-to-release migration success and must not be treated as a required migration step.
What is still needed for a practical tutorial
A reliable release-specific report must show the source and destination editions/builds, the actual file locations, replacement and Cloud-conflict handling, and a successful load with the intended character. Achievement behavior must remain a separate check. Until that exists, there is no verified full-game transfer walkthrough on this site.
You can make the decision now
Choose whether continuity or achievement triggers matter more, preserve the existing run and treat the release procedure as unverified. You do not need to delete or replace anything to make that choice.
Sources & version
Source-based explanation; no independent gameplay or file-transfer test. Original source dates retain their scope. Later notes establish the changes they explicitly describe; silence is not proof that every mechanic stayed identical.