Advertisement

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

json Format
Identity

Server name in the browser.

Game port, UDP.

Query port, immediately above the game port. Forward both or the server stays invisible.

World

Where the world is stored, relative to the server executable.

Players & Access

Join password.

Slot limit. 16 is the supported maximum. Note these values must be unquoted numbers — quoting a port is a real JSON error here.

Network

Interface to bind to. 0.0.0.0 listens on all of them, which is almost always what you want.

RCON & Query

Where log files are written.

enshrouded_server.json

{
  "name": "My Enshrouded",
  "password": "",
  "saveDirectory": "./savegame",
  "logDirectory": "./logs",
  "ip": "0.0.0.0",
  "gamePort": 15636,
  "queryPort": 15637,
  "slotCount": 16
}

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.

Rather not run the server yourself?

These tools are free and funded by the two hosting services we run. If you want a server that is already set up, here they are.

Advertisement