Guides→Configuration
ConfigurationLaunch-required workflow

Set up your Eco server

Use Eco’s server UI or configuration files for world, users and simulation settings, with backups before world-generation changes or mod work.

Use the server UI for normal administration

Eco exposes a server UI for many configuration tasks, including user/admin management and world/gameplay settings. Save changes made in the UI so they persist after restart.

Advanced settings also exist as .eco configuration files. File-level edits normally require a server restart before they take effect.

Know which changes can affect the world

  1. Create a backup before changing world generation, storage or major simulation settings.
  2. Do not edit template configuration files; use the active configuration files generated for the server.
  3. Treat WorldGenerator changes as destructive because they can require a world wipe to take effect.
  4. Use the correct platform account identifier when granting admin or allow-list access.

Mods and sensitive tokens

Eco server mods belong in the server’s validated Mods workflow and normally require a restart. API authentication tokens used by Eco’s web/admin interfaces are secrets; never paste them into a public ticket or commit them to a repository.

KEEP READING

Related guides

Minecraft server types: Vanilla, Paper, Purpur, Fabric, Forge and NeoForgeOpen guide →Set up your Project Zomboid serverOpen guide →Set up your 7 Days to Die serverOpen guide →Set up your Minecraft Bedrock serverOpen guide →