Menu
  Log out
 

Enshrouded Config Changes Not Applying

Enshrouded Guide • Updated Apr 6, 2026

Enshrouded Config Changes Not Applying

This is one of the most common admin traps after major Enshrouded updates. You edit enshrouded_server.json, restart, and nothing changes in-game. In practice there are three usual causes: you are editing preset-controlled settings, the file is carrying forward an outdated structure, or the JSON contains a bad value.

Official clue: Keen's November 10, 2025 server-settings article explicitly says older server.json versions can update incorrectly and may need to be deleted so a fresh file is generated on the next startup.

Fast Triage

Symptom Likely Cause Fix
XP, combat, or day/night edits do nothing gameSettingsPreset is not Custom Set preset to Custom, restart, test again
Server name or chat settings ignore edits after a patch Config file structure carried forward badly Back up the file, regenerate a fresh one, then reapply only needed values
Server refuses to boot after editing Bad JSON or invalid text value Check commas, quotes, and allowed enum values

Fix Order That Saves the Most Time

  1. Set gameSettingsPreset to Custom if you touched anything under gameSettings.
  2. Undo every optional edit except the one you are testing.
  3. Restart the server and verify the change in-game.
  4. If even top-level settings still ignore you, back up enshrouded_server.json, delete it, start the server once, and let Enshrouded generate a fresh file.
  5. Copy your values back in carefully, section by section.

Minimal Known-Good Layout

{
  "name": "Enshrouded Server",
  "saveDirectory": "./savegame",
  "logDirectory": "./logs",
  "ip": "0.0.0.0",
  "queryPort": 15637,
  "slotCount": 16,
  "voiceChatMode": "Proximity",
  "enableVoiceChat": false,
  "enableTextChat": false,
  "gameSettingsPreset": "Default"
}

Values That Commonly Break Boots

  • Typing text options wrong, such as global instead of Global.
  • Using unsupported words for fields like weatherFrequency or randomSpawnerAmount.
  • Leaving a trailing comma in the JSON.
  • Copying snippets from outdated guides that still assume a much older schema.

Community pattern: player-support threads from October 2024 onward repeatedly show admins fixing ignored gameplay edits by switching to Custom first, then regenerating the config if the server still behaves like nothing changed.

Once the file is clean, use Back to the Shroud Gameplay Settings to build a sensible ruleset instead of guessing field names.

Need a cleaner way to test Enshrouded settings without babysitting a local install? Host your Enshrouded server with Supercraft and keep config, backups, and restart flow in one panel.

← Back to Enshrouded Guides
Top