Welcome to Elderfield Save Location, Steam Cloud, and Recovery

FIRST CHECK

Back up the complete save folder first, then choose the correct branch for transfer, missing load-list entries, or an incompatible old save.

Before changing anything, copy the complete save folder to a separate dated location. Do not delete, rename, or overwrite your only copy. The correct repair depends on whether the files are missing, the load list is empty, or an old save appears but will not load.

Current save root

SteamDB's current Steam Cloud configuration points to:

<SteamLibrary>/steamapps/common/Welcome to Elderfield - Full Game/save/

The technical record includes global.rmmzsave and numbered slot files such as file0. Exact drive and Steam-library prefixes vary by installation.

Choose the right recovery branch

1. 01Copy the complete save folderKeep a dated external copy before every repair.
2. 02files existLoad list is emptyCheck numbered slots and the global index recovery branch.
3. 03slot visibleSlot appears but will not loadVery old pre-May-2025 saves may be incompatible.
4. 04transferMoving from the DemoBack up both folders and decide whether to replay revised opening content.

Copy the complete save folder→files existLoad list is emptyCopy the complete save folder→slot visibleSlot appears but will not loadCopy the complete save folder→transferMoving from the Demo

Read the route as text

1. Copy the complete save folderKeep a dated external copy before every repair.
2. Load list is emptyCheck numbered slots and the global index recovery branch.
3. Slot appears but will not loadVery old pre-May-2025 saves may be incompatible.
4. Moving from the DemoBack up both folders and decide whether to replay revised opening content.

Branch A: everything works; you only need a backup

1. Save in-game and return to the title screen.
2. Exit normally and wait for Steam to show the game as closed.
3. Open the current save folder.
4. Copy the entire folder—not one guessed slot—to a separate dated location.
5. Leave that backup untouched while testing any transfer or repair.

Branch B: saves are on disk, but the load list is empty

The developer support thread identifies a damaged global.rmmzsave index as one cause. That file describes the load list; the numbered files contain slot data.

1. Make the external full-folder backup above.
2. Confirm numbered files such as file0 exist and have plausible sizes and dates.
3. Follow the developer's current rebuild sequence: recreate clean slots, close the game, then work from copied—not original—slot files.
4. Test one slot at a time.
5. Stop if the replacement causes a new error or the file dates no longer match your intended progress.

The developer thread contains the exact current sequence. This page does not compress it into “delete global.rmmzsave,” because deletion without a backup can turn a recoverable index problem into permanent loss.

Branch C: the save appears, but selecting it does nothing

The developer says very old saves from before May 2025 may be incompatible with the current full game. That is not the same failure as an empty load list. Rebuilding the global index cannot make an incompatible save format compatible.

Keep the original files, record the build period, and ask support whether a conversion path exists. Do not repeatedly overwrite new slots with the same incompatible file.

Branch D: moving from the Demo

The current developer discussion says Demo progress can transfer, but a transfer can skip early full-game content depending on where the Demo save ended. Back up the Demo and full-game folders first. If you want to experience revised opening material, start a separate new-game slot before deciding which progress to keep.

Steam Cloud is not your only backup

The store lists Steam Cloud support, and SteamDB mirrors the synchronized file pattern. Cloud can propagate a damaged index or an unwanted overwrite as readily as a good save. Keep the dated external folder until the destination install opens the correct slot and you have made a new clean save.

Stop conditions

Stop modifying files when:

• you have no external copy of the complete original folder;
• the current symptom does not match the developer's branch;
• only an old pre-May-2025 save is available;
• Steam is still running the game or actively synchronizing;
• a copied slot produces a new error.

If the game itself will not launch on Steam Deck or Proton, use the Deck troubleshooting page before touching saves.

Sources & evidenceOpen the references used for this page

• SteamDB Cloud and UFS configuration
• Developer support: broken saves and load-list recovery
• Developer discussion: Demo save transfer
• Official Steam listing — Steam Cloud