Essential Admin Commands
Admin commands in Eco are powerful governance tools that should be used with transparent policy to preserve trust in economy and law systems.
Enabling Admin
Add your SteamID to the Admins list in the server GUI or `Users.eco` file.
Common Commands
/kick [User] [Reason]- Kick a player./ban [User] [Reason]- Ban a player./fly- Toggle flying mode./give [ItemName] [Amount]- Spawn items./skill [User] [SkillName] [Level]- Modify skills.
World Management
/meteor destroy- Remove the threat./save- Force save the world.
Command Governance Standards
Create a documented list of commands allowed for routine moderation versus emergency intervention. Clear boundaries prevent accusations of arbitrary interference and make admin behavior predictable for citizens and lawmakers.
- Routine scope: Use minimal-impact commands for moderation and technical fixes.
- Emergency scope: Reserve economy or world-altering commands for incident response only.
- Transparency: Publish major command interventions in a public changelog channel.
Operational Checklist
Treat this topic as a repeatable server operation, not a one-time change. Schedule changes during lower traffic, announce maintenance windows, and keep a rollback snapshot before each update. If your server is modded, validate changes on a staging copy first so startup logs, world loading, and player joins are confirmed before production rollout.
Validation Steps
- Capture baseline metrics: Record CPU, RAM, and average player ping before changes.
- Apply one change at a time: Avoid batch edits that make root-cause analysis difficult.
- Review logs after restart: Check for version mismatch and dependency warnings immediately.
- Run a real join test: Confirm fresh clients can connect and complete core gameplay actions.
- Observe for at least 24 hours: Validate behavior under peak load, not only right after reboot.
Performance and Stability Notes
Most hosting incidents come from resource spikes combined with configuration drift. Keep restart cadence predictable, review world/save growth weekly, and cap optional systems that generate extreme entity counts. When performance drops, compare with your last known-good baseline and revert recent high-risk changes quickly to reduce downtime.
Backup and Rollback Policy
Use automated daily backups plus pre-change snapshots for risky operations. Keep at least one off-node copy and test restore procedures routinely. A practical retention strategy is 7 daily, 4 weekly, and 2 monthly restore points. If a change causes instability, roll back first, stabilize service, and then reattempt with a narrower test scope.
Game-Specific Hosting Notes
- Simulation tuning: Law, meteor, and economy settings should be tested together to avoid destabilizing progression.
- Admin policy transparency: Publish governance rules clearly so law changes do not feel arbitrary.
- World lifecycle: Plan season length and wipe criteria before launch to prevent mid-cycle conflict.