How to configure Enshrouded server settings
Edit Enshrouded difficulty, custom gameplay options, and role passwords in enshrouded_server.json, including the settings Enshrouded 1.0 changed. Use berrybyte Game Settings for managed values, stop before editing files, and verify permissions.
Enshrouded settings live in enshrouded_server.json at the server root.
Use Settings → Game Settings for values managed by berrybyte, such as
the server name. Use Files for difficulty and role permissions.
No server yet? Set up an Enshrouded dedicated server first.
Change a setting
Stop and back up
Stop the server and create a backup. Wait for the process to exit before editing.
Choose the right editor
Change Server Name in Game Settings. For difficulty or roles,
open enshrouded_server.json in Files.
Keep the allocated queryPort and plan-controlled slotCount.
Save and start
Edit only the intended keys. Keep valid JSON, save, then start.
Wait for HostOnline and test with one player.
berrybyte writes managed name, slot, and port values at startup. Manual changes to those fields can be replaced.
Difficulty
Set gameSettingsPreset to Default, Relaxed, Hard,
Survival, or Custom. Custom values belong under gameSettings
and require the Custom preset.
This is an excerpt to merge into your existing file, not a replacement for the whole config:
{
"gameSettingsPreset": "Custom",
"gameSettings": {
"playerHealthFactor": 1,
"shroudTimeFactor": 2
}
}Keep other generated keys. Keen's gameplay reference lists allowed values.
What changed in 1.0
Keen's 1.0 changelog changed two difficulty settings:
- Enemy amount (
randomSpawnerAmount) has a new Automatic option. It scales the enemies in each encounter to the party size, counting only players actively playing nearby. Check Keen's gameplay reference for the exact value before editing the file by hand. - Enemy damage (
enemyDamageFactor) values were reworked to match the damage players actually take. A custom value you set in Early Access may feel different in 1.0, so retest it with your group.
Role passwords
Edit passwords and permissions inside userGroups.
The old top-level password is a legacy field, even if a startup
control still displays it.
| Key | Permission |
|---|---|
canKickBan | Kick and ban players |
canAccessInventories | Use containers |
canEditBase | Change base blocks and props |
canExtendBase | Extend bases |
reservedSlots | Hold slots for that group |
Group names are labels; check their actual flags. Keep Admin's password private and use a different, non-empty password for friends.
In 1.0, user groups and their passwords work as before on dedicated servers. Player-hosted worlds can now promote or demote players in-game, but that isn't possible on a dedicated server. Change a player's role by giving them a different group's password. Keen's role reference explains the generated roles.
Test chest access, building, and moderation with the intended role. If the config no longer loads, restore the saved copy and apply one change at a time.
Frequently asked questions
Where are Enshrouded server settings stored?
The root enshrouded_server.json stores server configuration. On berrybyte, use Game Settings for the managed server name. Difficulty and userGroups are edited through Files while the server is stopped.
What server settings changed in Enshrouded 1.0?
Enemy amount (randomSpawnerAmount) gained an Automatic option that scales encounters to the players nearby, and the enemy damage values were reworked. User groups and passwords work as before, but players can't be promoted or demoted in-game on a dedicated server.
Which password controls Enshrouded admin access?
The password in the Admin entry under userGroups. The legacy top-level password does not manage modern roles. Use different non-empty passwords for ordinary players and admins.