Saves and cloud sync
Steam Cloud is supported. The exit button was renamed Exit and Save on 4 November, and a bug that loaded saves inside a cave was fixed on 6 November.
Saving is one button and one cloud flag, and both of them were involved in the worst bug of launch week.
Every figure below is checked against Pequi studios announcements or Steam's own endpoints on 2026-11-09.
Saving is one button and one cloud flag, and both were involved in the worst bug of launch week.
Exit and Save
The exit button was renamed from "Exit" to "Exit and Save" on 4 November, and the announcement is explicit about why: to make its function clearer. That tells you two things at once. Exiting saves, and before the rename players were not sure whether it did.
That single rename is the best documentation of the save system available. No manual save slot to manage, no quicksave key documented, no published description of how often the game autosaves.
Steam Cloud
Steam Cloud is listed in the game's category list, which means saves sync between machines when you are signed in. Two computers, one save: progress follows you.
The practical caveat is the usual one: cloud sync is not a backup. If a save is corrupted, the corrupt version syncs too. Which is why the section below exists.
Loading into a cave
On 6 November the studio posted an announcement titled "Save Loading Issue Fixed", and the body is worth quoting in substance because it is an unusually honest one.
Players who loaded a save were being transported into a cave instead of where they had saved. The explanation given in the announcement: while fixing one bug, the studio accidentally introduced another that caused some players to load into the wrong location. The announcement apologises directly and says everything is now fixed.
Somewhere unexpected on load between the preceding patch and 6 November was that bug. Still seeing it means your build predates the fix.
Protecting a run
Steam does not expose a save-management interface for this game, and the developer has not published a save file path. So the safe advice is at the Steam level rather than the file level.
| Method | What it protects against |
|---|---|
| Steam Cloud enabled | Losing progress when switching machines |
| A second local copy of the save folder | Corruption syncing to the cloud |
| Not exiting mid-cutscene | The documented class of problem in the 8 November post |
The third row is not superstition. The 8 November performance post states that cutscenes were where low frame rate interfered with game events executing correctly. Exiting during a cutscene on a pre-8-November build was the kind of state that produced the save bugs people reported.
Locating the save folder means the standard Steam userdata path under your Windows user directory, but because the developer has not documented it, this page will not print a path that might be wrong for your setup. The reliable route is Steam's own "Browse local files" and the userdata folder named after your Steam ID.
Invisible inventory
Related but distinct: the 7 November patch fixed an issue where, if you died while your inventory was open, the inventory could become invisible or appear out of position afterwards. That was a display bug, not a data loss. If it happens on an older build, reopening the inventory or reloading corrects it.
No slots, no path
No manual save slots, no save path, no autosave interval, no cloud conflict resolution behaviour, and no save size. The game is a 500MB install with a simple exit-saves model, and the developer has not gone into more detail than that.
Exit-save, applied
One button saves, and it is the one that closes the game. That has three consequences worth knowing before you lose an evening.
Closing the game any other way is undocumented. There is no autosave interval published, no manual save key, and no confirmation prompt mentioned in any patch note. Certainty about a stored session means exiting through the menu.
Switching machines is safe if Steam Cloud is on, because the category list includes it. Not a backup either. A cloud save mirrors whatever is local, including a bad state, which is why copying the folder somewhere else is still worth the thirty seconds.
A save made on an older build can behave oddly on a newer one. The 6 November cave bug is the documented example: a patch-time change to where the game thinks you are. Nothing in the record says saves are versioned, so the safest habit after a big patch is to load once, check you are where you left off, and only then keep playing.
| Situation | What happens | What to do |
|---|---|---|
| Quit through the menu | Saved, per the 4 November rename | Nothing |
| Quit any other way | Not documented | Avoid it when you care |
| Two PCs, cloud on | Progress syncs | Let it finish before playing |
| Patch day | Old save may load oddly | Load once and check position |
Version first, then the save
Every save problem in the public record is a version problem. The cave bug was introduced by one patch and fixed by the next. The invisible inventory was a display fault in a specific build. The Traditional Chinese recipe gap was a locale bug in a specific build.
That makes the version number the first thing to check whenever a save behaves oddly, and the main menu has displayed it since 6 November. Before that patch there was no way to tell which build you were on from inside the game, which is why so many week-one bug reports are impossible to place now.
| Symptom | Likely cause | Check |
|---|---|---|
| Load puts you somewhere else | The 6 November cave bug | Build predates the fix |
| Inventory invisible after death | The 7 November display bug | Build predates the fix |
| Recipes missing at the sewing table | The 4 November locale bug | Build predates the fix, and language is Traditional Chinese |
| Progress missing after switching PC | Cloud sync had not finished | Let Steam finish before playing |
None of those are save corruption in the sense of a lost file. They are the game reading a save under rules that changed, which is a different problem with a different fix: update, load, check.
Three lines
Exit through the button that says Exit and Save. Leave Steam Cloud on. A build older than 6 November should be updated before loading a save you care about.