Demo progress does not enter the full release
The no-transfer step is developer-confirmed.
- ◫DemoOld demo save
- ×No transferIncompatible with full release
- ▶Start newCreate a retail save
- ▣Back upUse Save Location
Before you buy: four confirmed Demo answers
The official gameplay trailer below shows the published repair and shop loop; it is not proof that the retired Demo is downloadable or that its save can transfer.
| Question | Current answer |
|---|---|
| Can I play the Demo now? | No Demo download appears on the current official Steam page. |
| Why was it removed? | A developer said the old Demo no longer represented the completed game. |
| Will it return? | No return date or commitment has been announced. |
| Does its save transfer? | No. Start a new save in the full release. |
Official store media shows the published game context, not demo availability. The current Steam listing and developer answers determine the status above.
Can I force an old demo save into the full game?
No reliable or developer-supported migration method is documented. Do not replace retail SaveData or BackupSaveData with demo files; incompatible data could damage or hide the destination save.
What to do next
Install the current retail build, start a new game and create a named backup after the first successful save. Use the Beginner Guide for the first shift and Save Location for platform paths.
What the missing Demo button proves
The lack of a Demo button on the current official Steam page proves only that the previous public demo is not being offered through the normal store listing now. It does not prove that a revised demo will return, that an unofficial archive is safe, or that private testing branches are public. The developer's explanation is narrower: the old build was removed because it no longer represented the completed game. Check the current app page itself rather than an old search snippet, archived announcement, or third-party download catalog. A community request for another demo is not a release commitment.
Keep Demo files separate from the full release
If the old Demo is installed, close the game and Steam and copy its folder to a dated archive. Do not overwrite retail SaveData or BackupSaveData, rename Demo files to force an import, or mix files from different dates. Start a new retail slot, wait for its first normal save, close the game, then back up the matching retail folders together.
If Demo files were already copied into retail, stop creating saves, preserve the current folder for diagnosis, move disputed files out of the active folder, verify the retail installation, and compare Steam Cloud timestamps before accepting a conflict. A clean matching backup is safer than combining individual files.
- Archive the Demo separately
- Start a new retail save
- Back up SaveData and BackupSaveData together
- Do not force an import by renaming files
- Preserve a copied problem state before recovery
How to recognize an outdated demo guide
An old guide may still explain the broad inspection, teardown, and reassembly loop, but it should not be applied automatically to the full release. Look for a publication date, build number, the word Demo, and interface elements that no longer exist. Compare device names, tool unlocks, prices, menu locations, and quest order with the current build. One successful video proves that a result was possible on that route; it does not prove every recorded step was required. For a bug, start with current developer notes and Current Problems, and preserve a separate checkpoint before following old advice.
How to verify future Demo answers
First reopen the official Steam page and check whether a Demo button is present. Then revisit the original developer answer and record its author, date, and exact boundary about transfer. Keep the current store fact, the developer's explanation, and your own backup recommendation separate. Do not publish a return date, file compatibility claim, or complete difference list unless one is actually announced. If availability changes, update the short answer and research date while preserving the earlier state as history. Readers can then see what is confirmed now and what applied only to an older build.
Demo or full release: choose the right answer
A new player should use the current retail build and begin a new retail save. An existing demo save belongs in a separate archive, not in an unfinished retail slot. For a mechanics question, repeat the action in the current build because an old button location, price, or quest order does not prove present behavior. For a story question, do not transfer a demo result into the release without replaying it. For a technical fault, record the platform, build, last successful save, and exact error. This classification adds no invented differences, but it prevents two incompatible game states from being mixed.
| Situation | Safe action | Do not assume |
|---|---|---|
| New player | Start a retail save | A demo will return |
| Old demo save | Archive separately | Renaming makes it compatible |
| Old demo guide | Retest in retail | Steps are unchanged |
| Save error | Protect both folders | Cloud has the right copy |
Evidence to include in a support request
A useful report helps another person separate an old demo issue from a retail bug. Include the operating system, store, current build, language, whether the slot was new or copied, and where every file came from. Describe the last action before the failure and what happened after a restart. A screenshot of the message or file list can help, but remove usernames and other personal data. Do not upload a save publicly when it may contain a profile identifier; first use an official channel or ask which file is required. Also state whether cloud synchronization is enabled and whether an untouched backup exists.
