Echoes of Elysium Console Commands and Admin Controls
Search results often present a long list of EoE commands as if it were an official API. The safer answer is build-aware: verify what the current server package exposes, test it on a copy, and never treat a community command as guaranteed.
No universal command list is asserted here. The public game site and server-app observation do not establish a permanent set of console commands, admin keys, or item IDs for every build.
Find the current control surface
- Check the current server panel, package documentation, or in-game help.
- Record app/package, branch, build, and the account used for testing.
- Back up the world before using a command that can alter players, ships, inventory, or time.
- Test a read-only/status action first, if one is exposed.
- Use a second normal account to confirm privilege boundaries.
Safe admin procedure
| Action | Good practice |
|---|---|
| Grant access | Use the current package/panel identity format and remove former operators. |
| Moderate | Record player, time, reason, and action; use the least powerful control. |
| Recover a bug | Use a backup or test copy first; tell the crew when progress is changed. |
| Test a command | Run it on a scratch world and record exact syntax and result. |
Why copied commands fail
- The command belongs to an older build or a different package.
- The control is client-only rather than server-authoritative.
- The operator lacks the required permission.
- The command syntax or item identifier changed.
- The panel intercepts or overwrites the manual configuration.
Protect the crew's progression
Keep god mode, item spawning, repair, teleport, and similar powers for controlled testing or an announced recovery. A long-running airship campaign depends on players trusting that resources and ship progress were earned. See admin permissions and save recovery.
Related guides
Run EoE with managed server controls and live backup options.