Enshrouded

Server name, password and slots, plus what to expect from a game still in development.

Everything in Your panel applies to Enshrouded. These are the parts specific to it.

Startup parameters

Three values, all in Startup parameters:

• Server Name — what appears in the browser
• Server Password — required to join
• Max Players

Change them, save, restart. That is the whole setup.

Game rules

Difficulty presets and the individual game rules — enemy strength, resource yields, stamina, durability — live in the server's configuration file, which you edit in the file manager. Restart to apply.

Enshrouded exposes a fairly detailed rule set, so it is worth a look if the default difficulty does not suit your group.

Memory

Plans start at 8 GB and that is a real requirement rather than a suggestion. Enshrouded keeps a large, voxel-based world in memory, and the amount grows as your group explores and builds.

Two things push it up quickly: a wide-ranging group that opens a lot of the map, and heavy terrain editing, since altered voxels cannot be regenerated from the seed and must be stored.

If the server slows down after several weeks of play, world growth is the usual cause.

Moving an existing world

Upload the save folder through the file manager or SFTP with the server stopped, then start it. Back up whatever is already on the server first.

Still in development

Enshrouded is in early access, and updates land regularly. Two habits worth having:

Back up before an update. Save format changes are possible between versions, and a backup is the only way back.

Expect the occasional breaking change. If the server misbehaves right after a game update, check the developers' notes before assuming your configuration is at fault.

Restarts

A nightly scheduled restart keeps memory use steady on a long-running world. Pair it with a warning message a few minutes ahead so nobody is thrown out mid-build.