Saves & progression
Know what returns when you replay a location
Replay rules changed across the Demo updates: 1.01 restores destroyed crates, 1.04 adds random items to empty replay chests, and 1.06 says all enemies originally in the location now appear on replays. Older reports of fewer enemies describe the earlier behavior.
On this page
Separate three kinds of container
| Container | Documented purpose | What to expect |
|---|---|---|
| Estate chest | Store your own items | Developer says items are saved; not a random loot-refill rule. |
| Empty chest in a replayed location | Random loot in 1.04 | If not refilled immediately, complete the location and check subsequent runs. |
| Destroyed crate | Respawns on replay in 1.01 | No guaranteed item or quantity is specified. |
Why an old run may have fewer enemies
An October 25 player described a smaller group on repeat visits; the developer confirmed reduced repeat spawns and planned a rework. The November 3 version 1.06 announcement then states that all enemies that were present now appear when replaying. Compare the build you are actually running before treating the old post as a current farming strategy.
Make a useful repeat-run check
- Note your displayed version and which location you are replaying.
- Finish the location if its empty chests have not repopulated, following the 1.04 advice.
- On a later run, compare the same container or encounter. Record what you actually find; random loot does not promise the same item.
- Bring desired loot back to estate storage. Do not leave valuable personal gear in a raid chest as a persistence experiment.
Containers and dismantling are different material routes
Version 1.04 says breakable jars may contain minerals; 1.06 adds destroying barrels with fists. Neither note supplies a guaranteed drop rate, rare-resource route or optimal farm. For unwanted weapons and armor, the Deconstruction Workbench is a separate documented system. Do not assume every breakable object yields the material a recipe needs.
Your replay plan is sound when…
You know the container or encounter type and its versioned rule. A random empty result, an estate-storage problem and an older reduced-enemy run are not interchangeable symptoms.
Sources & version
Source-based explanation; no independent gameplay or file-transfer test. Original source dates retain their scope. Later notes establish the changes they explicitly describe; silence is not proof that every mechanic stayed identical.