Before updating Episode 2, record its build number, keep the original download and identify the save location from developer instructions. Episode 2-to-3 save compatibility is not confirmed in the announcements reviewed here.
Episode 2 now documents F5/F6 save/load, but the reviewed notes do not establish a save-folder path, Episode 2-to-3 save compatibility, or Steam Cloud support. This remains a preparation checklist, not a tested migration or recovery procedure.
1. Separate the game, the save, and the notes
The game download contains the playable build; the save holds your progress; release notes explain changes and controls. Episode 2 supports F5/F6 save/load, but its public release post does not specify the save-folder path.
Likewise, a folder named “backup” is only useful if you know what it contains. Give a backup folder a meaningful label outside the game’s active data directory, such as FamilyTime-before-update-2026-10-01, and place a short text note beside the copied files. Record the original location, build label, and date. Keep the files inside unchanged unless the developer explicitly instructs otherwise.
The save path is not supplied in the reviewed Episode 2 post. Ask the developer to confirm the location before copying or replacing files; this guide cannot provide a verified path.
2. Back up before updating
For an Episode 2-to-3 update, the announcements reviewed here do not specify a save-migration procedure. Keep the existing installation and save until the developer confirms compatibility. Find the release posts in our development index.
- Identify both versions. Record the version you have and the one you are getting. Keep the source post or download instructions with your notes.
- Read compatibility guidance. Look for a required new game, changed save format, or special installation order. If the notes say to start fresh, preserve the old files rather than forcing them into the new version.
- Close the game normally. For Episode 2, use the documented F5/F6 save/load controls. Finish saving and exit the game before copying save files.
- Copy the confirmed save data. Follow the developer’s file-location guidance and copy the complete documented set to a separate folder. Do not move or delete the originals. Check that the copy contains the expected filenames and non-empty files where applicable.
- Keep a recoverable reference. Keep the original Episode 2 ZIP and its release notes. Record whether it is DX11 or DX12 and the build number; these details identify the version used by your save.
- Test before a long session. Follow the new build’s instructions and check that the intended progress is present. Preserve the untouched backup until you have confidence in the result.
If you cannot identify the save files, leave the working installation intact and request the location from the developer. Copying the download ZIP alone does not back up progress.
3. Treat cloud synchronisation as a separate feature
Valve’s documentation explains that developers must configure which files Steam Cloud manages. It also describes explicit configuration for sharing cloud storage between separate applications, such as a demo and a full release. A Steam listing alone therefore does not establish cloud saving or demo-to-release progress transfer.
The reviewed Steam page does not list Steam Cloud, and the Episode 2 post does not document cloud saves. There is no confirmed automatic backup or synchronisation between these releases.
If a future supported version presents a cloud conflict, stop before selecting a file to overwrite. Record both candidates’ timestamps and the device on which you last played. Seek the relevant support instructions if you cannot identify the intended progress. A newer timestamp is a clue; it is not proof that the file contains the colony you want.
4. Report the smallest repeatable problem
A developer can act on a short sequence more easily than on a general complaint. Describe what you expected, what appeared instead, and the minimum actions that reproduce it. Separate an issue that happened once from one you have reproduced consistently.
A report template to fill in
- Build and source: version label and official download post.
- System: operating system; GPU and memory if the issue concerns graphics or performance.
- Starting state: new game or existing save; previous build if recently updated.
- Steps: a numbered sequence, using the control names shown by this version.
- Expected / observed: one concrete sentence for each.
- Frequency: how many attempts reproduced it; write “once” when that is all you know.
- Evidence: exact error text or a short recording of the relevant action.
Use the support route specified by the developer. Check screenshots and logs for personal paths, account details, or unrelated desktop content before sharing them. Supply a save file only when requested through an appropriate channel, and send a copy rather than your only working version.
5. If an old save will not load
Preserve the original save and the error message before trying further changes. Repeatedly editing, renaming, or resaving the same files can make it harder to identify the original failure. Avoid applying recovery instructions written for a different game simply because the engine or folder name looks similar.
If the current build offers a separate new-game slot, and using it will not overwrite existing progress, a fresh session can help narrow the problem: does the build launch at all, or does the failure appear only when loading the older data? Report that distinction without concluding that it proves corruption.
Keep the original save, the last working build number and the load error. Ask the developer whether that save format is supported before replacing or converting files. We have no tested Episode 2-to-3 recovery procedure.