Fix Enshrouded Steam Cloud Character Sync Problems
Enshrouded dedicated servers do not store character progression. Keen's FAQ is explicit on that point: the world save is on the server, but characters stay on clients. That is why a server can look fine while one player logs back in missing levels, inventory progress, or recent build materials.
What this means: if only one player's progress is wrong, rolling back the dedicated world may make things worse. Start with the client save path and Steam Cloud behavior first.
Where the Different Data Lives
| Data Type | Stored Where | Admin Impact |
|---|---|---|
| World, terrain, base state | Dedicated server saveDirectory |
Server host can back up and roll it back |
| Character progression | Player client save / Steam Cloud | Each player may need their own recovery step |
Recovery Path for the Affected Player
- Turn off Steam Cloud for Enshrouded temporarily.
- Back up both the local save folder under
%USERPROFILE%/Saved Games/enshroudedand the Steam remote folder underSteam/userdata/<SteamID>/1203620/remote. - Compare timestamps. The usual failure mode is an older cloud copy overwriting a newer local one.
- If the local files are newer and correct, copy them into the Steam remote folder while Cloud remains disabled.
- Re-enable Steam Cloud and choose the local/newer data when Steam presents an out-of-sync prompt.
Why this guide exists: community reports going back to February 2024 describe Steam Cloud replacing newer local Enshrouded progress with older cloud state, which feels like a dedicated-server rollback even when the world itself is fine.
Server-Side Checks Before You Blame the Player
- Confirm the world still contains the group's recent structures and quest-state changes.
- Check whether multiple players were affected. If yes, the problem may be the world save instead.
- Look for dirty shutdowns or crashes in the server logs around the time of the loss.
Admin Policy That Prevents Future Damage
| Policy | Why It Helps |
|---|---|
| Tell the group where characters are stored | Prevents wrong assumptions about what a server rollback can restore |
| Avoid force-killing the server process | Reduces the odds of mixed world/client state after disconnect chaos |
| Have affected players back up local saves before major patches | Gives a recovery point if Steam Cloud makes a bad choice |
If the world itself is damaged, switch to Save Game Rollback and Backups. If the server never finishes coming online, use Startup Logs and File Locations.
Want simpler world management while players keep control of their own characters? Host your Enshrouded server with Supercraft and separate server recovery from client-save guesswork.