Enshrouded Server Settings Explained — Config Reference

Once your dedicated server is installed, everything is controlled through one JSON config file — enshrouded_server.json in the server directory, generated on first launch. This reference covers the settings that matter and how to use them safely.

Where is the config file and how do you edit it?

Stop the server, open enshrouded_server.json in any text editor, save your changes, then start the server again. Most changes require a restart; players should log off first to avoid save corruption.

What are the essential settings?

Setting	What it does	Recommendation
serverName	Public name in the server browser	Short and unique — include your community name
password	Join password; empty = open server	Set one unless you genuinely want a public server
maxPlayers	Player cap	16 is the hard maximum; lower it if your hardware struggles
saveDirectory / logDirectory	Where saves and logs live	Defaults (./savegame, ./logs) are fine
userGroups	Admin/member permissions	See below — this is how you make yourself admin

How do user groups and admin rights work?

The server config defines groups, each with permission flags. The two flags that matter most:

• canKickBan — whether the group may kick or ban players (admin-level; grant to your trusted group only)
• reservedSlots — slots held open for group members when the server is full

The practical setup: one admin group (you and trusted friends, with canKickBan and reserved slots) and a default everyone-else group without those flags. Add players to groups by their Keen Games ID.

How many settings are there overall?

Roughly 55 configurable settings, of which about 37 tune difficulty and world rules — enemy damage multipliers, resource yield, stamina costs, Shroud behavior and similar knobs. If your group finds the base game too easy after gearing up, these multipliers are the sandbox to play in; change them gradually (10–20% steps), because small numbers compound across a whole server economy.

What about crossplay settings?

With 1.0, the server config controls whether PS5 players can join your server. Keep crossplay enabled if your community mixes PC and console players — remember that console players cannot join modded setups, so crossplay servers should run vanilla. Full context in our crossplay guide.

How do difficulty presets interact with custom values?

The config lets you pick a difficulty preset as a starting point, then override individual values. The safe workflow: choose the closest preset, restart, test with your group, then adjust one cluster of values at a time (combat, economy, exploration) so you know what changed what.

What changes need extra care?

• Anything touching saves (save directory, world seed): back up savegame/ first
• Player caps above your hardware: a crowded server with high view distances is the top cause of rubber-banding — lower slots or view distance before blaming the network
• Open servers without passwords: expect strangers; have at least one admin with canKickBan online or reserved slots for your group

Frequently asked questions

Do settings apply retroactively? World-rule multipliers apply going forward; existing items and builds are untouched. Difficulty changes affect new fights immediately.

How do I back up my world? Copy the savegame/ folder while the server is stopped. Do this before every settings experiment — and before migrating hosts, as covered in our hosting comparison.

Where can I see who joined and what happened? ./logs — the server writes connection and admin events there.

---

Sources: dedicated-server reference data (setting counts, group flags), official server tooling behavior, community hosting documentation. Exact key names can shift between patches — last verified 2026-10-18 for v1.0.