Rust admin commands: how to become an admin and what you can do
Running a Rust server means being able to deal with problems as they happen: a cheater, a stuck player, a griefer, a bug. For that you need admin power in the game. Rust handles it with a short list of commands and a file that remembers who has authority.
Roles in Rust
There are two levels:
- Owner: full control, including managing other admins and server settings.
- Moderator: can kick, mute and ban, and use a limited set of tools, but not the full range.
Both are tied to a player's SteamID64, the long number that uniquely identifies a Steam account. It looks like 76561198000000000. Look yours up from your Steam profile URL, or from a lookup site, rather than guessing.
Make yourself an owner
You do this from the server console, not from the game, because you cannot give yourself admin from inside the game before you have any:
ownerid 76561198000000000 "YourName" "Server owner"
server.writecfg
The first line grants owner status. The second saves the change to a file called users.cfg, so it stays after a restart. Without server.writecfg, the change disappears when the server stops. Moderators work the same way with moderatorid.
To remove one, use removeowner or removemoderator followed by the SteamID64, then server.writecfg again.
Use the server console in your panel for this, and keep the list short. Everyone listed has the power to change your server.
Using admin commands in game
Once you are an owner, press F1 in the game to open the console. A selection of useful commands:
| Command | What it does |
|---|---|
kick "name" "reason" | Remove a player from the server |
ban "name" "reason" | Ban a player |
unban steamid | Remove a ban |
say "message" | Broadcast a message to everyone |
teleport "name" | Move to a player |
noclip | Fly through objects to inspect a situation |
god true | Take no damage, handy for investigating without risk |
inventory.give "item" amount | Give yourself items for testing |
Command names change between game versions, so if one does not work, type part of it in the console and look at the suggestions it offers.
Using admin power responsibly
Having the keys does not mean you should use them freely. Habits that keep a server healthy:
- Do not play on your admin account. Use a second normal account for playing. An admin who is seen to use
noclipor items, even for testing, destroys trust. - Log what you do. Keep a note of bans and reasons, so you can answer appeals fairly.
- Be consistent. The same rule applies to a friend and to a stranger.
- Limit how many admins there are. The fewer, the less can go wrong.
Handling cheaters and rule breakers
When someone is accused:
- Gather evidence, such as clips or screenshots, rather than acting on rumour.
- Watch with
noclipandgodif it is happening now, but keep out of sight. - Ban with a clear reason once you are sure.
- Record it, and share the outcome with your team.
Anti-cheat tools and plugins help. A plugin can log suspicious activity for you to review, as described in How to install Oxide or Carbon plugins on your Rust server.
Remote administration
Many owners manage the server from a phone or a web tool using RCON, which needs the password from your server settings. It is convenient, and it is also an attractive target. Set a long password, keep it private, and read What RCON is and how to use it safely. Also see How to configure your Rust server for where RCON is set.
If you lose admin access
If you cannot get into the game as an owner, use the panel console to run ownerid again with your SteamID64, then server.writecfg. You only need access to your hosting account for this, which is another reason to protect it with strong login habits. Keep your NGP Cloud account secure covers it.
Still stuck? Open a ticket on Discord - run /ticket in any channel, pick a department, and include your Server ID or Invoice ID so we can jump straight in.