Generate a Enshrouded enshrouded_server.json
Enshrouded expects strict JSON. Hand it something invalid and it saves its own defaults over your file, so a syntax mistake masquerades as the server ignoring you.
Visual Settings
enshrouded_server.json
Advertisement
The enshrouded_server.json format
Usual JSON discipline applies — no comments, no comma after the last entry, strings in quotes, numbers and true/false left bare. Ports in particular must be numbers; wrap them in quotes and the file is invalid, not merely odd.
Advertisement
The mistake that wastes an evening
When the JSON will not parse, the server falls back to a full default configuration and saves it — so you restart, open the file, and find your settings swapped for values you never picked. That is what a syntax error looks like here; it is not the server refusing one specific setting.
Passwords live in user groups
Current versions replace the single server password with userGroups, each with its own password and permissions. The default groups are Admin, Friend and Guest. Each one sets canKickBan, canAccessInventories, canEditBase and canExtendBase to true or false, plus reservedSlots, the number of slots kept free for that group; with any reserved, the server looks full to everyone else once the open slots are taken. The groups ship with no passwords, so set them before opening the server.
The old top-level password line is no longer how access works. If the server still finds a password there, it creates a group called default with that password and Friend-level permissions, so an existing setup keeps working.
Difficulty presets
gameSettingsPreset picks a difficulty preset: Default, Relaxed, Survival or Custom. The detailed gameSettings block is only read when the preset is Custom, so editing individual values while a named preset is selected changes nothing.