Server Commands Reference

Intermediate40-60 minutesCross-platformUnturned Server

Running an Unturned™ dedicated server without a working knowledge of its console commands leads to the same problems every time: players report bad actors and no admin can remove them fast enough, server state drifts because nobody remembered the save command, and the whitelist never got toggled off after a private event. This reference documents every built-in server console command, its exact syntax, who can execute it, and when to use it. Plugin-framework commands from RocketMod and OpenMod are noted where they extend or replace the built-in equivalents.

The 57 Studios™ server team validated this reference against Unturned™ 3.x (3.24.x branch). Commands are drawn from direct testing and from the Smartly Dressed Games official documentation at https://docs.smartlydressedgames.com/en/stable/. Any command not listed in the official documentation is noted as community-observed.

Prerequisites

A running Unturned™ dedicated server. See Setting Up Your Server Panel.
Access to the server console (direct terminal, RCON client, or in-game admin).
Working familiarity with the server config files. See Server Config Files.

Permission tiers

Unturned™ has three levels of command authority on a dedicated server:

Tier	Who has it	How it is assigned
Owner	The Steam account that launched the server process, or any Steam ID listed in `Commands.dat` with `Owner` before the session starts.	Implicit (process owner) or via `Commands.dat` at startup.
Admin	Players explicitly promoted with the `admin` command.	Run `admin <SteamID64>` in server console or in-game by an Owner.
Player	All connected clients who are not Admin or Owner.	Default.

One-time setup

The admin command itself requires Owner or an existing Admin to execute. On a brand-new server, the first admin grant must be run from the server console directly, not in-game. There is no way to grant yourself Admin from a Player-tier in-game session.

Most in-game commands require the player to have Admin or Owner tier. Console-only commands (marked below) must be executed from the server terminal; they cannot be sent by an in-game player regardless of tier.

Permission tier decision flow

Command categories overview

Player management commands

`admin`

Syntax: admin <SteamID64>

Grants Admin tier to the specified player. The player can then execute any admin-level command from in-game chat.

Detail	Value
Permission required	Owner
Console-only	No
In-game syntax	`/admin <SteamID64>`
Persisted	Yes — written to `Players.dat`.

Example:

admin 76561198012345678

The player with Steam ID 76561198012345678 is now Admin. Their admin status persists across server restarts because the grant is written to Players.dat. See Server Config Files for the Players.dat format.

Admin roster hygiene

Keep the admin roster as small as the server requires. Each Admin account has significant power — kick, ban, give, teleport, and slay. A compromised admin account creates as much disruption as a hostile player with no accountability. The 57 Studios server team reviews the admin roster monthly and removes accounts that are no longer actively moderating.

`unadmin`

Syntax: unadmin <SteamID64>

Revokes Admin tier from the specified player.

Detail	Value
Permission required	Owner
Console-only	No
In-game syntax	`/unadmin <SteamID64>`
Persisted	Yes — removes the entry from `Players.dat`.

Effect timing

unadmin takes effect immediately for the current session. The removed admin loses command access in real time; they do not need to disconnect and reconnect. The Players.dat entry is removed at the same moment so the change persists across restarts.

`kick`

Syntax: kick <SteamID64> [reason]

Disconnects the specified player from the server immediately. The player can reconnect unless subsequently banned.

Detail	Value
Permission required	Admin
Console-only	No
In-game syntax	`/kick <SteamID64> [reason]`
Persisted	No

Example:

kick 76561198012345678 Griefing base structures

The reason string is displayed to the kicked player and written to the server log. Providing a clear reason simplifies later review of moderation history.

`ban`

Syntax: ban <SteamID64> [duration_seconds] [reason]

Bans the specified player. If duration_seconds is omitted, the ban is permanent. The player is also kicked immediately if currently connected.

Detail	Value
Permission required	Admin
Console-only	No
In-game syntax	`/ban <SteamID64> [duration] [reason]`
Persisted	Yes — written to `Players.dat` Banned section.

Examples:

ban 76561198012345678
ban 76561198012345678 86400 Exploiting item duplication
ban 76561198012345678 604800 Repeated griefing after warning

Duration is in seconds. Common values:

86400 — 1 day
604800 — 7 days
2592000 — 30 days
Omit — permanent

The ban record in Players.dat stores the Steam ID, timestamp, duration, and reason. See Server Config Files.

Ban without reason

Omitting the reason string still applies the ban. However, reviewing ban history later is significantly harder without a reason. The 57 Studios team's moderation policy requires a reason string on every ban issued for player-conduct violations. Automated bans (anti-cheat) may omit the reason.

`unban`

Syntax: unban <SteamID64>

Removes the ban for the specified Steam ID. Takes effect immediately.

Detail	Value
Permission required	Admin
Console-only	No
In-game syntax	`/unban <SteamID64>`
Persisted	Yes — removes the ban record from `Players.dat`.

`spy`

Syntax: spy <SteamID64>

Takes a screenshot of the specified player's screen and displays it in the server console or returns it to the requesting admin's console. Used for anti-cheat verification.

Detail	Value
Permission required	Admin
Console-only	No
In-game syntax	`/spy <SteamID64>`
Persisted	No

Privacy and disclosure

The spy command captures a screenshot without player consent. Use it within the scope of your server's published rules. The 57 Studios server team recommends disclosing the use of spy in the server's rules documentation so players are aware that screen capture may occur during moderation reviews.

`slay`

Syntax: slay <SteamID64>

Instantly kills the specified player. Useful for clearing a stuck or rule-violating player without a full kick.

Detail	Value
Permission required	Admin
Console-only	No
In-game syntax	`/slay <SteamID64>`
Persisted	No

Item and world commands

`give`

Syntax: give <SteamID64> <itemID> [amount]

Spawns the specified item in the target player's inventory. If amount is omitted, defaults to 1.

Detail	Value
Permission required	Admin
Console-only	No
In-game syntax	`/give <SteamID64> <itemID> [amount]`
Persisted	No — items exist in player inventory; inventory is saved on next server save.

Examples:

give 76561198012345678 363 1
give 76561198012345678 1023 5

Item IDs are the numeric identifiers from vanilla or mod .dat files. The give command is the primary tool for admin item distribution, event rewards, and debugging mod items. Cross-reference your mod's .dat ID field with the number passed to give.

Mod item testing

When testing a new mod item on a dedicated server, give is faster than placing the item in a chest in-world. Use /give <your_SteamID64> <modItemID> from in-game admin chat. See Workshop Content on Dedicated Servers for loading mod content onto the server first.

`vehicle`

Syntax: vehicle <SteamID64> <vehicleID>

Spawns a vehicle at the specified player's position and seats them in it.

Detail	Value
Permission required	Admin
Console-only	No
In-game syntax	`/vehicle <SteamID64> <vehicleID>`
Persisted	No

Example:

vehicle 76561198012345678 120

Vehicle IDs follow the same numbering scheme as item IDs — drawn from the vehicle's .dat ID field. Vanilla vehicle IDs are documented in the Smartly Dressed Games modding reference at https://docs.smartlydressedgames.com/en/stable/.

`teleport`

Syntax: teleport <SteamID64> <targetSteamID64_or_locationName>

Teleports the first player to the position of the second player or to a named location.

Detail	Value
Permission required	Admin
Console-only	No
In-game syntax	`/teleport <SteamID64> <target>`
Persisted	No

Examples:

teleport 76561198012345678 76561199087654321
teleport 76561198012345678 Liberator

Named locations correspond to map-specific location names. The list of valid names depends on the active map. Typing an invalid location name produces no movement and logs an error to the server console.

`experience`

Syntax: experience <SteamID64> <amount>

Grants the specified amount of experience points to the player. Used for event rewards or skill testing.

Detail	Value
Permission required	Admin
Console-only	No
In-game syntax	`/experience <SteamID64> <amount>`
Persisted	Saved on next server save.

`reputation`

Syntax: reputation <SteamID64> <amount>

Adjusts the player's reputation by the specified amount. Positive values increase reputation; negative values decrease it.

Detail	Value
Permission required	Admin
Console-only	No
In-game syntax	`/reputation <SteamID64> <amount>`
Persisted	Saved on next server save.

`time`

Syntax: time <seconds_since_midnight>

Sets the server time. 0 is midnight; 43200 is noon; 86400 wraps back to midnight.

Detail	Value
Permission required	Admin
Console-only	No
In-game syntax	`/time <seconds>`
Persisted	No — time continues to advance from the set point.

Examples:

time 43200
time 0

`day`

Syntax: day

Shortcut that sets the server time to 43200 (noon). Equivalent to time 43200.

Detail	Value
Permission required	Admin
Console-only	No
In-game syntax	`/day`

`night`

Syntax: night

Shortcut that sets the server time to 0 (midnight).

Detail	Value
Permission required	Admin
Console-only	No
In-game syntax	`/night`

`weather`

Syntax: weather <weatherType>

Forces the server weather to the specified type. Valid types vary by map.

Detail	Value
Permission required	Admin
Console-only	No
In-game syntax	`/weather <type>`

Common weather type values: None, Rain, Snow, Storm. Map-specific weather types may exist for custom maps that define additional weather states.

Server lifecycle commands

`save`

Syntax: save

Immediately forces a save of the server state to disk. This writes player inventories, positions, and world state.

Detail	Value
Permission required	Owner / Console
Console-only	No (but typically run from console)
In-game syntax	`/save`
Persisted	This is the save command.

Before shutdown

Always run save before shutdown unless you intend to discard unsaved state from the current session. The 57 Studios server team runs save as the first step in every shutdown and restart procedure. State that has not been saved since the last save call is permanently lost when the process exits.

`shutdown`

Syntax: shutdown [delay_seconds]

Shuts down the server process. If delay_seconds is provided, the shutdown is delayed and a countdown is broadcast to all players. Without a delay, shutdown is immediate.

Detail	Value
Permission required	Owner / Console
Console-only	No
In-game syntax	`/shutdown [delay]`

Examples:

save
shutdown 60

The delay gives players time to find shelter before the process exits. The 57 Studios team's standard maintenance window sequence is save, then shutdown 120.

`reload`

Syntax: reload

Reloads the server configuration from disk without fully restarting the process. Not all configuration changes apply on reload; changes to the map, mode, or core .dat files require a full restart.

Detail	Value
Permission required	Owner / Console
Console-only	Yes
Persisted	N/A

Reload scope

reload re-reads partial server configuration. It does not apply changes to Commands.dat parameters like Map, Mode, or Port. The 57 Studios team's recommendation is to always restart the server process after changing Commands.dat rather than relying on reload for correctness. Use reload only for plugin and permission changes that explicitly support hot-reload.

`map`

Syntax: map <mapName>

Changes the active map. The change takes effect on the next server restart.

Detail	Value
Permission required	Owner / Console
Console-only	Yes
Persisted	Written to `Commands.dat`.

Example:

map PEI
map Washington
map Russia

`mode`

Syntax: mode <modeType>

Sets the server game mode. Valid values: Easy, Normal, Hard, Gold.

Detail	Value
Permission required	Owner / Console
Console-only	Yes
Persisted	Written to `Commands.dat`.

`cycle`

Syntax: cycle <seconds>

Sets the day/night cycle length in seconds.

Detail	Value
Permission required	Owner / Console
Console-only	Yes
Persisted	Written to `Commands.dat`.

`timeout`

Syntax: timeout <seconds>

Sets the client connection timeout in seconds. Clients who do not respond within this window are disconnected.

Detail	Value
Permission required	Owner / Console
Console-only	Yes
Persisted	Written to `Commands.dat`.

Access control commands

`whitelist`

Syntax: whitelist <on|off>

Enables or disables the server whitelist. When whitelist is on, only Steam IDs listed in Players.dat under the whitelist section can connect.

Detail	Value
Permission required	Owner / Console
Console-only	No
In-game syntax	`/whitelist <on
Persisted	Written to `Commands.dat`.

Examples:

whitelist on
whitelist off

See Server Config Files for the Players.dat whitelist format and how to add Steam IDs to the whitelist.

Whitelist for private events

The whitelist is the most reliable way to restrict server access during a private event. Enable it before opening connections, add participant Steam IDs to Players.dat, and disable it after the event concludes. This prevents uninvited players from joining during the restricted window without requiring a server-wide password change.

`password`

Syntax: password <string>

Sets a server join password. Players must enter the password at the server browser connection screen. Set to an empty string to remove the password.

Detail	Value
Permission required	Owner / Console
Console-only	Yes
Persisted	Written to `Commands.dat`.

Examples:

password myEventPassword2025
password

`port`

Syntax: port <number>

Sets the UDP port the server listens on. Default is 27015. Change takes effect on restart.

Detail	Value
Permission required	Owner / Console
Console-only	Yes
Persisted	Written to `Commands.dat`.

Firewall requirement

After changing the port, update your firewall rules and any port-forward configuration on your router or hosting panel to allow UDP traffic on the new port. An unchanged firewall with a new port results in a server that starts but is unreachable to players. See Setting Up Your Server Panel.

`maxplayers`

Syntax: maxplayers <number>

Sets the maximum number of concurrent connections. The Steam server browser reflects this cap.

Detail	Value
Permission required	Owner / Console
Console-only	Yes
Persisted	Written to `Commands.dat`.

Debug and monitoring commands

`log`

Syntax: log <anticheat_flag> <network_flag> <chat_flag> <join_flag>

Configures which server events are written to the log file. Each flag is Y or N.

Flag position	Controls
1	Anti-cheat events
2	Network events
3	Chat events
4	Player join/leave events

Example:

log Y N Y Y

Enables anti-cheat logging, disables network logging, enables chat logging, enables join/leave logging.

`queue`

Syntax: queue <size>

Sets the join queue size. When the server is full, up to <size> players can wait in queue.

Detail	Value
Permission required	Owner / Console
Console-only	Yes
Persisted	Written to `Commands.dat`.

RCON (Remote Console)

RCON allows a remote client to send server commands over a TCP connection without direct terminal access. The 57 Studios server team uses RCON for panel-based administration.

Enabling RCON

Add the following to Commands.dat before starting the server:

RCON
Port 27015

The RCON password is configured separately in Config.json under the RCON section. See Server Config Files.

RCON authentication and command flow

RCON client options

Client	Platform	Notes
mcrcon	CLI, cross-platform	Simple, scriptable. Community-observed to work with Unturned RCON.
RCON web admin panels	Web browser	Requires a panel integration. See Setting Up Your Server Panel.
Custom scripts	Python, PowerShell	Use the Source RCON protocol; Unturned RCON is Source-compatible.

Firewall exposure

The RCON port must never be exposed to the public internet without a strong password. An exposed RCON port with a weak password allows anyone to run arbitrary server commands, including kicking all players, banning admins, and shutting down the server process. Use a firewall rule to restrict RCON access to a specific admin IP range or VPN subnet.

Plugin framework command extensions

The built-in command set covers server administration. Community plugin frameworks extend the command surface significantly.

RocketMod (legacy)

RocketMod adds a permission system that allows fine-grained command access beyond the Owner/Admin/Player tiers. RocketMod commands are prefixed with / in-game exactly like built-in commands. See RocketMod and OpenMod Plugin Basics.

Commonly-used RocketMod command plugins:

Plugin	Commands added
Essentials	`/heal`, `/tp` (self-teleport), `/home`, `/warp`, `/tpa` (teleport request), `/i` (item give to self)
Jail	`/jail <player>`, `/unjail`, `/jaillist`
VehicleManager	`/refuel`, `/repair`, `/fvehicle` (force-spawn vehicle)

OpenMod (modern)

OpenMod is the successor to RocketMod and runs on the .NET runtime with NuGet package management. OpenMod commands may be namespaced (e.g., openmod:install <plugin>). See RocketMod and OpenMod Plugin Basics.

Server lifecycle state diagram

The following diagram shows the relationship between the server lifecycle commands and the states they drive. Understanding this flow prevents state loss from an unordered shutdown sequence.

Common admin workflow examples

New server — initial setup sequence

# Run from server console before opening to players
admin 76561198012345678
password myServerPassword
maxplayers 24
whitelist off
log Y N Y Y
save

Pre-event lockdown sequence

# Before a private event
whitelist on
# Add whitelisted Steam IDs to Players.dat manually
# Then open the server to whitelisted players only

Maintenance window sequence

# Announce in Discord first, then:
shutdown 120
# After 120 seconds server shuts down automatically
# Server restarts via systemd / LGSM / panel auto-restart

Banning a griefing player mid-session

# Get the offender's Steam ID from the server browser or a plugin
ban 76561198012345678 604800 Griefing team structures during active raid
save

Testing a new mod item

# Join the server as admin, open in-game console with ~ then:
/give 76561198012345678 50001 1
# 50001 is the mod item's ID from its .dat file

Admin workflow decision tree

Command quick-reference table

Command	Syntax	Min tier	Persisted
`admin`	`admin <SteamID64>`	Owner	Yes
`unadmin`	`unadmin <SteamID64>`	Owner	Yes
`kick`	`kick <SteamID64> [reason]`	Admin	No
`ban`	`ban <SteamID64> [seconds] [reason]`	Admin	Yes
`unban`	`unban <SteamID64>`	Admin	Yes
`spy`	`spy <SteamID64>`	Admin	No
`slay`	`slay <SteamID64>`	Admin	No
`give`	`give <SteamID64> <itemID> [amount]`	Admin	On save
`vehicle`	`vehicle <SteamID64> <vehicleID>`	Admin	No
`teleport`	`teleport <SteamID64> <target>`	Admin	No
`experience`	`experience <SteamID64> <amount>`	Admin	On save
`reputation`	`reputation <SteamID64> <amount>`	Admin	On save
`time`	`time <seconds>`	Admin	No
`day`	`day`	Admin	No
`night`	`night`	Admin	No
`weather`	`weather <type>`	Admin	No
`save`	`save`	Owner	—
`shutdown`	`shutdown [delay]`	Owner	—
`reload`	`reload`	Owner	N/A
`map`	`map <mapName>`	Owner	Yes
`mode`	`mode <type>`	Owner	Yes
`cycle`	`cycle <seconds>`	Owner	Yes
`timeout`	`timeout <seconds>`	Owner	Yes
`whitelist`	`whitelist <on	off>`	Owner
`password`	`password <string>`	Owner	Yes
`port`	`port <number>`	Owner	Yes
`maxplayers`	`maxplayers <number>`	Owner	Yes
`log`	`log <Y\|N> <Y\|N> <Y\|N> <Y\|N>`	Owner	Yes
`queue`	`queue <size>`	Owner	Yes

Appendix A: Locating a player's Steam ID 64

Many commands require a Steam ID 64 (a 17-digit number starting with 7656119). Ways to obtain it:

Method	How
Steam profile URL	Navigate to the player's Steam profile. If the URL ends in a number (e.g., `/profiles/76561198012345678`), that is the Steam ID 64.
SteamID.io	Visit https://steamid.io and search by username or profile URL. (Community tool — not an Unturned official resource.)
Server log	Player join events (when `log` has join flag `Y`) print the Steam ID 64 alongside the player name.
Plugin roster	RocketMod and OpenMod plugins expose player lists with Steam IDs via in-game commands such as `/players`.
In-game spy	The `spy` command output includes the Steam ID in the console response.

Steam ID format

A Steam ID 64 always starts with 765611 and is exactly 17 digits long. If the number you have does not match this pattern, it may be a Steam ID 32 or a custom vanity URL — use SteamID.io to convert it to the 64-bit format before passing it to ban, kick, admin, or give.

Appendix B: Command execution contexts

Context	How to open	Notes
Server terminal	Direct access to the server process stdout/stdin.	All commands available. No `/` prefix needed.
In-game admin chat	Press `~` or open chat, prefix command with `/`.	Only non-console-only commands available.
RCON client	Connect via RCON client to the RCON port.	No `/` prefix. Output returned to client.
`Commands.dat`	Startup script — commands run before the server accepts connections.	Only startup-valid commands. No `/` prefix. See Server Config Files.

Appendix C: Logging format and rotation

When log Y N Y Y is active, the server log at <Unturned>/Servers/<servername>/Logs/ writes entries in the following format:

[YYYY-MM-DD HH:MM:SS] [SOURCE] MESSAGE

Example entries:

[2025-05-18 14:32:01] [CHAT] Player (76561198012345678) said: hello
[2025-05-18 14:32:15] [JOIN] Player (76561198012345678) joined the server
[2025-05-18 14:35:02] [ANTICHEAT] Player (76561198012345678) flagged for speed anomaly
[2025-05-18 14:35:10] [JOIN] Player (76561198012345678) left the server

Log files rotate daily. Older logs are not automatically deleted; the 57 Studios team recommends a log rotation policy (compress after 7 days, delete after 90 days) to prevent disk exhaustion on long-running servers. On Linux, this is managed with logrotate. On Windows, a scheduled task with a PowerShell script achieves the same result.

Frequently asked questions

What is the difference between kick and slay?

kick disconnects the player from the server entirely; the player is returned to the server browser and can reconnect. slay kills the player's in-game character without disconnecting them; the player respawns. Use slay for minor behavioral corrections where removal from the session is not warranted. Use kick when the player needs to be removed from the active session.

Can a player admin themselves?

No. The admin command requires a higher-tier caller than the target. A player cannot elevate their own tier. The only exception is the server Owner (the process owner), who starts with the highest tier implicitly.

Does the ban command work for players who are not currently connected?

Yes. ban <SteamID64> writes the ban record to Players.dat regardless of whether the player is currently connected. If the player is connected, they are also kicked. If they are not connected, the ban prevents their next connection attempt.

How do I give items to all players at once?

There is no built-in broadcast-give command. The 57 Studios team uses a RocketMod or OpenMod plugin that iterates over connected players and issues give for each. See RocketMod and OpenMod Plugin Basics.

Does `reload` apply changes to Commands.dat?

Partially. reload re-reads some server configuration fields, but changes to core parameters (map, mode, port) require a full server restart. The 57 Studios recommendation is to always restart after changing Commands.dat rather than relying on reload for correctness.

Can I schedule commands to run automatically?

Not through built-in Unturned functionality. RocketMod and OpenMod both have timer/scheduler plugins that execute commands on an interval (e.g., auto-save every 15 minutes, announce server rules every 30 minutes). See RocketMod and OpenMod Plugin Basics.

How do I find which item ID corresponds to a mod item?

Open the mod's .dat file in Notepad++ and look for the ID field. This is the numeric ID passed to give. For Workshop mods you did not author, browse the mod's Workshop page or look at the mod content folder at <Unturned>/Servers/<servername>/Workshop/Content/304930/<modID>/Bundles/Items/.

What happens if I run shutdown with no delay?

The server process exits immediately. Players are disconnected without warning. Any unsaved state since the last save command is lost. The 57 Studios team policy is to always run save immediately before shutdown and to use a minimum 60-second delay for a live player session.

Are RocketMod and OpenMod commands documented anywhere?

RocketMod commands are documented by each individual plugin's author. OpenMod has a central package registry at https://openmod.github.io/openmod-docs/ (community-maintained). See RocketMod and OpenMod Plugin Basics for the framework overview.

Can I use RCON to run commands from a web panel?

Yes, if the web panel supports Source RCON protocol. Most community Unturned server panels (LGSM-based, Pterodactyl, custom panels) include RCON integration. See Setting Up Your Server Panel.

What is the maximum number of admins I can have?

There is no hard limit on the number of Admin entries in Players.dat. Practically, the 57 Studios recommendation is to keep the admin roster as small as the server requires; each admin has significant power and reducing the admin count reduces the blast radius of a compromised account.

Does the whitelist affect players who are already connected?

No. Enabling the whitelist does not kick players who are already connected. It only prevents new connections from Steam IDs not on the whitelist. To enforce a whitelist retroactively, follow whitelist on with a review of the connected player list and kick any non-whitelisted players manually.

Cross-references

Server Config Files — Commands.dat, Players.dat, Config.json field reference.
Workshop Content on Dedicated Servers — loading mod content that can be used with give.
RocketMod and OpenMod Plugin Basics — extending the command surface with plugins.
Setting Up Your Server Panel — installing and running the server process.
Smartly Dressed Games official documentation — authoritative command reference.
Unturned on Steam — the game's Steam store page.

Document history

Version	Date	Author	Notes
1.0	2025-05-18	57 Studios	Initial publication. Full built-in command reference with permission tiers, workflow examples, RCON, and FAQ.
1.1	2026-05-18	57 Studios	Added permission tier decision flow diagram, admin workflow decision tree, expanded callout coverage, updated prev link.

Server Commands Reference ​

Prerequisites ​

Permission tiers ​

Permission tier decision flow ​

Command categories overview ​

Player management commands ​

admin ​

unadmin ​

kick ​

ban ​

unban ​

spy ​

slay ​

Item and world commands ​

give ​

vehicle ​

teleport ​

experience ​

reputation ​

time ​

day ​

night ​

weather ​

Server lifecycle commands ​

save ​

shutdown ​

reload ​

map ​

mode ​

cycle ​

timeout ​

Access control commands ​

whitelist ​

password ​

port ​

maxplayers ​

Debug and monitoring commands ​

log ​

queue ​

RCON (Remote Console) ​

Enabling RCON ​

RCON authentication and command flow ​

RCON client options ​

Plugin framework command extensions ​

RocketMod (legacy) ​

OpenMod (modern) ​

Server lifecycle state diagram ​

Common admin workflow examples ​

New server — initial setup sequence ​

Pre-event lockdown sequence ​

Maintenance window sequence ​

Banning a griefing player mid-session ​

Testing a new mod item ​

Admin workflow decision tree ​

Command quick-reference table ​

Appendix A: Locating a player's Steam ID 64 ​

Appendix B: Command execution contexts ​

Appendix C: Logging format and rotation ​

Frequently asked questions ​

What is the difference between kick and slay? ​

Can a player admin themselves? ​

Does the ban command work for players who are not currently connected? ​

How do I give items to all players at once? ​

Does reload apply changes to Commands.dat? ​

Can I schedule commands to run automatically? ​

How do I find which item ID corresponds to a mod item? ​

What happens if I run shutdown with no delay? ​

Are RocketMod and OpenMod commands documented anywhere? ​

Can I use RCON to run commands from a web panel? ​

What is the maximum number of admins I can have? ​

Does the whitelist affect players who are already connected? ​

Cross-references ​

Document history ​

Server Commands Reference

Prerequisites

Permission tiers

Permission tier decision flow

Command categories overview

Player management commands

`admin`

`unadmin`

`kick`

`ban`

`unban`

`spy`

`slay`

Item and world commands

`give`

`vehicle`

`teleport`

`experience`

`reputation`

`time`

`day`

`night`

`weather`

Server lifecycle commands

`save`

`shutdown`

`reload`

`map`

`mode`

`cycle`

`timeout`

Access control commands

`whitelist`

`password`

`port`

`maxplayers`

Debug and monitoring commands

`log`

`queue`

RCON (Remote Console)

Enabling RCON

RCON authentication and command flow

RCON client options

Plugin framework command extensions

RocketMod (legacy)

OpenMod (modern)

Server lifecycle state diagram

Common admin workflow examples

New server — initial setup sequence

Pre-event lockdown sequence

Maintenance window sequence

Banning a griefing player mid-session

Testing a new mod item

Admin workflow decision tree

Command quick-reference table

Appendix A: Locating a player's Steam ID 64

Appendix B: Command execution contexts

Appendix C: Logging format and rotation

Frequently asked questions

What is the difference between kick and slay?

Can a player admin themselves?

Does the ban command work for players who are not currently connected?

How do I give items to all players at once?

Does `reload` apply changes to Commands.dat?

Can I schedule commands to run automatically?

How do I find which item ID corresponds to a mod item?

What happens if I run shutdown with no delay?

Are RocketMod and OpenMod commands documented anywhere?

Can I use RCON to run commands from a web panel?

What is the maximum number of admins I can have?

Does the whitelist affect players who are already connected?

Cross-references

Document history