Eco Server Admin Commands and How to Use Them (Eco 14.x Guide)

Eco server administration is handled mainly with in-game slash commands, RCON, the Server UI, and configuration files. The commands let an administrator moderate players, control shared time and weather, schedule maintenance, set the spawn point, and perform world-management operations. The exact command set can vary by server build or mod, so run /help or /? on your own server before using syntax copied from an older guide.

This guide uses the documented command syntax associated with the 0.14.2.1 reference while accounting for the Eco 14.x wiki update. It also explains which actions are temporary, which require a save, and which can permanently alter a world.

What are Eco server admin commands?

Eco admin commands are privileged commands that operate on players or the shared simulation. They are entered in the game chat with a leading slash, or sent through RCON without that slash. The command table separates ordinary User commands from Admin commands; an account must have the required access level for an admin command to run.

There are four practical administration paths:

• In-game chat: use slash commands while connected to the server.
• RCON: send the same command remotely, omitting the initial /.
• Server UI: use graphical controls for operations such as saving the server after changing the spawn.
• Server files: edit persistent settings such as the administrator list in Users.eco.

The important distinction is scope. A command may affect only your client, one player, every player, the shared world, or a persistent file. Check that scope before running it.

How do I discover the commands available on my Eco server?

Use the running server as the authority for command names, aliases, permissions, and argument types.

1. Open chat while connected as a player with the appropriate access.
2. Enter /help or its alias /?. You can add a filter string to narrow the results.
3. Enter /helpful when you need the full help output, including subcommands.
4. Read the displayed access label before trying an operation. An entry marked Admin will not run for an ordinary User account.
5. Test syntax on a copy or a non-production server when the command changes the world.

The English wiki command table is tied to a 0.14.2.1 reference and notes that its Eco 14.x material is being updated. Treat the examples in this article as documented syntax, not a guarantee that every server build exposes the same alias or argument. Mods can add, remove, or change commands.

How do I make someone an admin in Eco?

Add the player’s SLGID and/or Steam64ID to the administrator list in Users.eco. The official server-management guidance states: “To make a player an admin on the server, you have to add the player’s SLGID and/or Steam64ID to the Users.eco file’s admin list.”

Find the player’s identifiers

1. Have the player connect to the server.
2. Run /whoami to identify the account IDs associated with your own connection.
3. For another connected user, run /whois username, replacing username with the player’s name.
4. Record the SLGID and/or Steam64ID exactly as displayed. These identifiers are also used for whitelist and blacklist configuration.

Add the identifier to the file

1. Stop or otherwise place the server in the safe maintenance state recommended by your hosting setup before editing its files.
2. Open the server’s Users.eco file.
3. Add the chosen SLGID and/or Steam64ID to the file’s admin list, preserving the existing format and punctuation.
4. Save the file and start or reload the server according to your server build’s normal procedure.
5. Connect with the account and use /manage listadmins to confirm that the account appears in the administrator list.

If the player still receives an access error, run /whoami again and compare the identifier in the file character-for-character. A display name is not a substitute for the account ID.

Which Eco commands kick, ban, mute, or unban players?

The moderation commands have both a /manage form and a short alias. They are Admin-level operations in the documented command table.

Purpose	Command forms	Target and duration
Kick	/manage kick or /kick	Specify the target user and, optionally, a reason. A kick ends the current session but is not a ban.
Ban	/manage ban or /ban	Accepts an account ID, Steam ID, SLGID, or username. An empty time means permanent. Documented duration forms include 1m, 1h, 1d, and 1w.
Unban	/manage unban or /unban	Use the account ID, Steam ID, SLGID, or username associated with the ban.
Mute	/manage mute or /mute	Mutes the selected user. An empty time means permanent; the same documented duration style is used.
List administrators	/manage listadmins	Displays the accounts currently recognized as administrators.

Choosing a target

Use an identifier rather than a name when a moderation action must be unambiguous. Names can change or contain characters that make chat parsing difficult; account IDs remain tied to the account. If you use a username, copy the spelling shown by /whois.

Choosing a duration

Include the unit immediately after the number: 1m for one minute, 1h for one hour, 1d for one day, or 1w for one week. Leaving the time argument empty creates an indefinite ban or mute according to the documented behavior. Use a temporary action when you expect to review the case later, and record the reason in your moderation log.

How do I change the shared time and weather?

Use the shared-world commands when you want every player to see the same simulation state. The /mytime and /myweather command families affect only the issuing player’s view and do not change the world for anyone else.

Set or resume the shared sun

• /time set <hour> moves the shared sun to the specified hour.
• /time midnight sets the shared world to midnight.
• /time resume restarts normal time movement after a forced setting.

Replace <hour> with the hour value accepted by the help output on your build. Run /time resume when an event or test is over; otherwise the world can remain at the forced time.

Set or inspect shared weather

• /weather clear
• /weather rain
• /weather heavyrain
• /weather cloudy
• /weather status

These commands change or report shared weather. For a private visual change that other players should not see, use the corresponding /myweather commands shown by /help.

How do I schedule an Eco server restart, update, or shutdown?

Use the maintenance command with local server time and comma-separated arguments:

/manage maintenance <time>, <message>, <reason>

<time> uses the server’s local clock in hh:mm format. The documented reasons are Shutdown, Restart, and Update. Commas are required, so retain all separators even when your message contains only a few words.

Safe maintenance sequence

1. Warn players in chat or through your community’s normal announcement channel.
2. Run /manage save before scheduling the operation.
3. Enter the maintenance command with the local hh:mm time, announcement message, and one valid reason.
4. Confirm the scheduled operation in the server’s output or help response.
5. For RCON, send the same command without the leading slash: manage maintenance <time>, <message>, <reason>.

The maintenance guidance specifically warns that slash-command and RCON shutdown do not report a save. Saving first removes the ambiguity about whether recent world changes were written before the process stops.

How do I change the server spawn point?

Stand at the desired location and run /setspawn. The command updates the runtime spawn point, but the change is not persistent until you save through the Server UI.

1. Travel to the exact location you want new players to use.
2. Enter /setspawn.
3. Open the Server UI.
4. Choose File -> Save.
5. Wait for the save to complete before shutting down or restarting the server.

If you omit the UI save, the server can revert to the previous spawn after a restart.

Which admin commands can damage or permanently alter a world?

Some Admin entries go well beyond moderation. The command table includes settlement clearing, world cleanup, pollution changes, object removal, mass plant spawning, and forced time or weather operations. Their effects differ in target and scope, and the cited documentation does not claim that every operation is reversible.

Use a risk check before execution

• Target: identify the settlement, object, area, or player affected.
• Scope: determine whether the command changes one entity or the entire world.
• Persistence: find out whether a save is automatic or required.
• Reversibility: assume a destructive edit cannot be undone unless your tested backup proves otherwise.
• Access: confirm you are on the intended server and using the intended administrator account.

Protect the world first

Keep a current backup before testing world-editing commands, and test on a copy whenever possible. The advanced setup guidance documents backup configuration, but it does not promise rollback for each individual command. A backup is therefore an operational safeguard, not proof that a command is reversible.

Can I delete a player profile to solve an account problem?

No. Do not treat profile deletion as routine administration. The Server Management guidance says that safely deleting a player profile is no longer possible as of v0.8.0.0 because the operation could corrupt the world. Resolve access or moderation issues with the account identifiers and management commands instead.

Why did my Eco command not work?

Most failures come from using an outdated alias, missing privilege, incorrect target, or syntax that differs from the server build. Work through these checks in order.

1. Verify the command exists

Run /help, /?, or /helpful. If the command is absent, the server version, a mod, or the command namespace may differ from the guide you used.

2. Check access level

Read the access label in the help output. If an Admin command returns a permission error, confirm the account appears in /manage listadmins and that the correct SLGID or Steam64ID is in Users.eco.

3. Check punctuation and argument order

Maintenance requires commas and local hh:mm time. Duration values need their units, such as 1h. In RCON, remove only the leading slash; keep the command name, spaces, commas, and arguments.

4. Check the target identity

Use /whoami or /whois username to obtain the account identifier. For bans and unbans, try the account ID, Steam ID, SLGID, or exact username accepted by your server’s help text.

5. Check persistence separately from execution

A command can succeed in memory yet fail to survive a restart. The spawn point requires Server UI File -> Save; maintenance should be preceded by /manage save. Confirm the relevant save step before closing the server.

6. Check the execution channel

In-game commands begin with /. RCON commands use the same syntax without that slash. Sending the wrong form can make a valid command appear unknown.

What is the difference between in-game commands, RCON, the Server UI, and file editing?

Choose the interface based on where you are, how broad the change is, and whether it must persist.

Interface	Best use	Persistence and risk
In-game slash command	Immediate moderation, time, weather, maintenance, or spawn actions while connected.	Usually affects the running server immediately; some changes still require a save.
RCON	Remote administration from outside the game client.	Uses command syntax without /; save explicitly before shutdown-related work.
Server UI	Saving runtime changes and operating graphical server controls.	Required to persist a newly set spawn point.
Users.eco editing	Adding SLGID or Steam64ID entries to the admin list.	Persistent configuration; edit carefully and verify with /manage listadmins.
Direct server process controls	Starting, stopping, or maintaining the host process when commands are unavailable.	Follow the server build’s documented procedure and preserve backups before world changes.

What should I configure around a persistent Eco server?

Administration commands work best when the underlying server is maintained safely. The advanced setup guidance covers public or private visibility, backups, firewall and router configuration, and server folders. It also documents default game and web ports of 3000 and 3001 for its version context.

Do not assume those port numbers are current defaults for every Eco build or host. Verify the network settings in the server’s own configuration and help output before opening firewall rules or forwarding ports. Apply the narrowest firewall rules that allow the intended players and management connection, and keep the server files and backups protected from unauthorized access.

Operational checklist

• Confirm the build and mod list before relying on a command from an older guide.
• Keep at least one recent backup before destructive administration.
• Test maintenance scheduling and RCON access on a non-production instance when possible.
• Save explicitly before shutdowns and after runtime changes that must persist.
• Record moderation reasons, durations, and the identifier used for each action.
• Use /help after updates to detect renamed or removed commands.

Eco admin command quick reference

Command	Use	Important qualification
/help, /?	Show available commands; optional filter text narrows results.	Use the live server output as the final syntax reference.
/helpful	Show full help, including subcommands.	Useful when a short help listing hides an argument.
/whoami	Show your player identifiers.	Use the values for admin, whitelist, or blacklist configuration.
/whois username	Look up another player’s identifiers.	Replace username with the exact in-game name.
/manage kick, /kick	Remove a player from the current session.	Optional reason; this is not a ban.
/manage ban, /ban	Prevent a player from joining.	Empty time is permanent; durations include 1m, 1h, 1d, and 1w.
/manage unban, /unban	Remove a ban.	Use an accepted account identifier or username.
/manage mute, /mute	Mute a player.	Empty time is permanent; duration syntax matches bans.
/manage listadmins	Display administrators.	Use it to verify Users.eco changes.
/time set <hour>	Set shared sun position.	Resume normal movement with /time resume.
/time midnight	Set shared time to midnight.	Affects the shared world.
/time resume	Restart normal shared time movement.	Run after a forced time setting.
/weather clear, rain, heavyrain, cloudy	Set shared weather.	Use the full command form, such as /weather rain.
/weather status	Report shared weather.	Does not change weather.
/manage save	Save before maintenance.	Especially important before slash-command or RCON shutdown.
/manage maintenance ...	Schedule shutdown, restart, or update.	Use local hh:mm and comma-separated message and reason.
/setspawn	Set the runtime spawn location.	Use Server UI File -> Save to persist it.

Frequently Asked Questions

Can ordinary players use Eco admin commands?

Only commands exposed to the account’s access level will run. A player can inspect the help output available to that account, but Admin entries require administrator authorization configured on the server.

Why does a command work in chat but fail through RCON?

RCON uses the command text without the leading slash. For example, send manage save, not /manage save, while keeping the rest of the arguments unchanged.

Do personal time and weather commands change what everyone sees?

No. The /mytime and /myweather families are client-side controls for the issuing player; shared-world changes require the corresponding /time or /weather command.

What is the safest way to test a destructive command?

Make a current backup, clone the world or use a separate test server, and verify the command’s target and scope with live help first. Do not assume that a command can be undone merely because it completed without an error.