Burglin' Gnomes Save File and Progress Guide
Save file location and progress rules for Burglin' Gnomes: Steam Cloud path, backup checks, failed-run resets, and recovery cautions.
By: Frontline Pathfinder | Lead Content Tester, GameguideHub
Tested on Version: Current public build | Status: FIELD TESTED / PATCH SENSITIVE. Save behavior is high-impact and can change after patches, especially around failed days, host exits, and Steam Cloud sync.
Fast answer: on Windows, check %USERPROFILE%\AppData\LocalLow\GamesByFobri\Gnomium\SaveGames for *.bgsave files. Burglin' Gnomes can preserve normal progress through clean saves, but a failed day or missed task minimum can reset the run. Back up the folder only after a stable clear or clean host exit, never while Steam Cloud is actively syncing.
Where Burglin' Gnomes saves progress
Save file location
The practical Windows save path is:
| Platform | Folder | File Pattern |
|---|---|---|
| Windows | %USERPROFILE%\AppData\LocalLow\GamesByFobri\Gnomium\SaveGames | *.bgsave |
| macOS | ~/Library/Application Support/unity.GamesByFobri.Gnomium.SaveGames | Patch-sensitive Steam Cloud override |
| Linux | ~/.config/unity3d/GamesByFobri/Gnomium/SaveGames | Patch-sensitive Steam Cloud override |
If you are searching with German wording such as "Burglin' Gnomes speicherort", this is the same intent: the save location / Speicherort. On Windows, paste the path into File Explorer after replacing %USERPROFILE% with your user folder, or press Win + R and open %USERPROFILE%\AppData\LocalLow\GamesByFobri\Gnomium\SaveGames.
Save folder variants
Burglin' Gnomes is a Unity game, so the LocalLow path is the first folder to verify. Do not confuse it with the Steam installation folder, screenshots folder, or generic Steam userdata folder unless your build stops using the current cloud path.
- Exit the lobby cleanly. Let the host leave through menu flow before copying the save.
- Close the game. Do not copy while the file is being written.
- Pause Steam Cloud risk. Wait for Steam to finish syncing before replacing files.
- Copy the entire SaveGames folder. Keep a timestamped backup outside LocalLow.
- Test restore on a duplicate first. Do not overwrite your only working file.
INFERRED: if your save folder is empty, either the run has not produced a stable save yet, Steam Cloud is still syncing, the host owns the lobby save, or a failed-day state has already deleted the active save.
Progress after failed runs
Keep lobby progress after fail
Do not plan around keeping lobby progress after a failed day. Current failure behavior is brutal: if the team misses the required task count and reaches the game-over state, progress can collapse back to Day 1. That includes the parts players care about most: house upgrades, stored materials, crafted route gear, and day momentum.
| State | Progress Risk | Correct Call |
|---|---|---|
| Clean host exit after stable progress | Lower | Use menu exit, then verify the save exists. |
| Three-task minimum complete | Lower if extraction is clean | Extract instead of farming risky optional loot. |
| Timer low with fewer than three tasks | High | Drop loot and finish the fastest remaining task. |
| Game Over / failed day | Severe | Expect reset; restore only from a known backup. |
| Client disconnect | Variable | Host checks the Haven floor and save state before relaunch. |
This overlaps with the Lobby Progress After Fail Guide, but this page is stricter: it focuses on the physical save folder and backup-safe recovery. For route prevention, use the All Task Guide.
Backup and recovery cautions
Backups are for recovery testing, not for hiding bad route decisions. Make one only after a clean state. If you restore over a cloud-synced folder at the wrong time, Steam can overwrite the file you were trying to protect.
- Back up after a completed day, not during panic. A backup made during a bad state preserves the bad state.
- Do not use random save downloads. They can contain mismatched progression, unsafe files, or stale patch data.
- Keep one untouched backup. Test restores on a copy before replacing the active folder.
- Tell co-op teammates who owns the save. Host-side state matters more than client assumptions.
If you are already near failure, the best save protection is still gameplay discipline: finish three tasks, extract, and leave through a clean host flow.
FAQ
Where is the Burglin' Gnomes save file?
On Windows, check %USERPROFILE%\AppData\LocalLow\GamesByFobri\Gnomium\SaveGames. Current save files use the *.bgsave pattern.
Do you keep lobby progress after failing?
Do not count on it. A failed day or Game Over can reset progress back to Day 1. Clean exits and successful clears are safer than trying to save after failure.
Can I back up my save?
Yes, but only after closing the game and letting Steam Cloud finish. Copy the whole SaveGames folder, keep the backup outside LocalLow, and restore only from a known clean state.
Related Guides and Data Pages
- Lobby Progress After Fail Guide - route decisions before the fail state.
- Complete Beginner Survival Guide - daily task minimum, host saves, and first-week survival.
- All Task Guide - safest three-task routing before optional loot.
- Co-op Guide - host discipline and team routing.