Enshrouded Loads Wrong World from a Relative Save Directory

Freeze both the intended and accidental save sets

Every additional save can rotate numbered generations. Disable automatic restart, stop the process through the product's validated graceful path, and copy the source directory and the newly created empty-world directory before changing either.

Keen's FAQ says files save periodically, while save management documents ten rotating generations and a copy on shutdown. Preserve all of them; do not assume the newest timestamp belongs to the established world.

1. 1Record the active JSON, executable path, service account and working directory.
2. 2Copy each candidate save root to a separate dated recovery folder.
3. 3Retain the current logs because they can reveal which path the process used.

Resolve ./savegame instead of guessing

The default saveDirectory is ./savegame. A relative path depends on runtime context; launching beside the executable interactively and starting through a Windows service can resolve it differently if the working directory changes.

Read the active enshrouded_server.json and resolve its path under the actual service command. If stability matters, use an explicit protected path and verify write permissions before moving the world.

• Confirm which JSON the running executable reads.
• Resolve saveDirectory and logDirectory separately.
• Check the service identity can read, create, rename and write files in the destination.

Restore the complete hex-named world family

Keen uses static hexadecimal-style world names such as 3ad85aea, companion _info metadata and ten numbered recovery copies selected by an index. The human-readable server name does not become the save filename.

Move the family as one unit. Renaming the obvious base file or omitting the index can select the wrong generation or leave recovery metadata inconsistent.

1. 1Identify the desired world using the copied source metadata and known timestamps.
2. 2Copy the base world, _info file, all numbered generations and index data.
3. 3Do not edit the 0–9 latest index unless intentionally performing Keen's documented rollback procedure on a safety copy.

Validate the world, roles and client characters separately

Start privately and wait for HostOnline. Join a known base, inspect representative world progress and test a clean restart. Also verify userGroups permissions because the JSON is separate from world generation files.

Keen stores player characters on clients, not the dedicated server. A familiar character entering the restored world proves the client's character still exists; it does not prove the server importer copied that character. Record world and character checks separately.

• World check: bases, terrain/progression and world-specific objects.
• Configuration check: roles, passwords, slots and gameplay preset.
• Client check: each player retains the local character on the source client device.