Empyrion dedicated.yaml Settings Guide
dedicated.yaml is the launch contract for an Empyrion world. It tells the server which save to load, which scenario to use, and how players should discover and enter it. Change it while the server is stopped, then read the next boot log before changing anything else.
Settings worth checking first
| Setting family | What it controls | Common mistake |
|---|---|---|
GameName | The persistent save identity. | Renaming it and assuming the old galaxy disappeared. |
| Server name and password | What players see and who may join. | Editing a scenario file instead of the active server YAML. |
| Player limit | The advertised and enforced slot ceiling. | Choosing more slots than the hardware can simulate. |
CustomScenario | Which scenario folder supplies the world rules and content. | Changing the scenario name on an existing save. |
Safe editing order
- Stop the server through its normal shutdown action so the save is flushed.
- Copy the current YAML before editing it.
- Change one setting group at a time and keep indentation valid.
- Start the server and inspect the log for the resolved game name and scenario.
- Join with one admin account before announcing the restart.
A scenario update and a YAML edit are different operations. The YAML can point at a scenario, but it cannot make an incompatible scenario version safe for an existing save.
Why a setting appears to do nothing
Empyrion can generate or copy configuration into the save area. If a change is ignored, compare the file the launcher actually reports with the file you edited. Also check for a duplicate server instance loading the same port or a different GameName.
On a managed plan, edit the supported values in the panel and use Empyrion server hosting for the deployment path. For scenario-specific rules, see Reforged Eden 2 on a dedicated server.