The Isle Evrima Save Backup and Player Data Recovery Guide
Evrima progression is server-side. A reinstall that preserves the binaries but loses the server's Saved tree can look like a fresh world or erase the practical history of a community. Back up the whole tree before changing branches, maps, or config.
What to back up
| Path | Why it matters |
|---|---|
TheIsle/Saved/PlayerData/ | Per-player progression files, including SteamID-based data on current layouts. |
TheIsle/Saved/Config/ | Game.ini, Engine.ini and the server's operating assumptions. |
TheIsle/Saved/ as a whole | Preserves build-specific state and files that a later patch may require. |
TheIsle/Saved/Logs/ | Useful evidence when a restore appears incomplete or the server will not start. |
A full timestamped copy of Saved is safer than guessing which database or player file is important. Keep at least one copy away from the live server.
Safe backup sequence
- Stop the server cleanly and wait for the process to exit.
- Copy
TheIsle/Saved/to a dated backup location. - Record the Evrima branch/build and the configured
MapName. - Start the server and confirm one known player's progression before announcing the backup as good.
Restore after a reinstall or bad update
- Install the same Evrima branch first; do not restore Legacy data into an Evrima test.
- Stop the fresh server before copying anything.
- Replace the new
Saveddirectory with the backup, preserving ownership and permissions. - Start with the matching map and read
TheIsle.log. - Test with the affected Steam account before allowing the full community back in.
Do not delete saves as a first troubleshooting step. A missing server in the browser is usually a branch, version, EOS or port problem. Preserve
Saved until those causes are ruled out.Supercraft takes managed backups before updates and exposes the server's file access without requiring a manual reinstall. See The Isle hosting plans.