Echoes of Elysium Server Configuration
There is no value in a long-looking configuration table if the current EoE package does not read those keys. Start from the panel, generated files, or package documentation you actually have, and keep each change reversible.
Configuration audit
- Record app/package, branch, build, OS, and instance directory.
- Identify which file or panel field changes after a known safe edit.
- Back up the save and config while the server is stopped.
- Change one supported value.
- Restart, inspect the log, and prove the effect with one client.
Settings to establish before launch
| Area | What to record | Proof |
|---|---|---|
| Identity | Server name, password, visibility, and access list as exposed by the package. | A second account can or cannot join as intended. |
| Endpoint | External address, port, region, and any provider mapping. | Browser listing and real join both work. |
| World | World/save name and active data location. | Expected airship/world loads after restart. |
| Maintenance | Restart window, backup retention, and update source. | Restore test works on a copy. |
What not to assume
- A universal
Game.ini,ServerSettings.ini, orEngine.inischema. - ARK, Rust, or generic Unreal launch flags.
- That a command found in a community post exists in the current build.
- That client-side airship/graphics settings belong on the server.
- That the panel will preserve a manual file edit.
If a setting is ignored
Check the active instance, file authority, section/name, branch, permissions, and restart sequence. Compare timestamps before and after a panel save. If the value disappears, restore the dated copy and use the admin-controls guide rather than adding more guessed keys.
Version discipline
Read the current official Steam announcement stream and record the package build. EoE is evolving; a planned feature or a community workaround is not a supported configuration API.
Related guides
Use managed Echoes of Elysium hosting for panel-backed server operations.