Almost every Enshrouded ticket is one of these.
1. The world is empty after a restart
The server loads whatever folder saveDirectory names in enshrouded_server.json. If that value changed, it made a new world. Nothing was deleted.
- Stop the server.
- Open the Files tab and look for the previous save folder.
- Set
saveDirectoryback to that folder name. - Start the server and check the console.
2. The config resets itself
- Invalid JSON is the cause. If the file cannot be read, the server writes a fresh default one, which is why the name, passwords and slot count all change at once.
- Check every comma and quotation mark after an edit, and never leave a comma after the last entry in a list.
- Always stop the server before editing.
3. Players cannot join
- Check
slotCountand remember that reserved slots for admins count towards it. - Check the password matches the group they should join as.
- Confirm they are using the game port from the panel.
- Restart the server after a game update so it matches the clients.
4. The server uses a lot of memory
Enshrouded keeps a large world in memory and grows as players build. If the console shows the process being killed rather than a game error, it ran out of memory. Lower the slot count or move to a larger plan.
5. Progress was lost after a crash
- The world is written periodically and on a clean shutdown. A hard kill can cost the time since the last write.
- Use Stop rather than Kill and give it time to finish.
- Download a copy of the save folder before any big change.
Open a ticket from Support in the Client Area with the last 50 lines of console output and the save folder name you expect to load.





