Come chat with us and we will get back to you as soon as possible!
Contact SupportHolyHosting
Holy Team

Rust admin commands let you manage players, adjust server behavior, and respond quickly when something goes wrong. For a new server owner, the command list can feel a little like opening a toolbox and finding twelve different hammers. Some commands affect individual players, while others change the world, entities, or global settings.
Used carefully, these commands help keep your Rust server fair, stable, and easier to run. Used carelessly, they can cause confusion fast, so make sure only trusted admins have access.
Rust includes many administrative commands, but most fall into a few practical groups:
Before using protected commands in-game, your SteamID64 must be added as an owner or moderator. The most common server console command for owner access is:
`ownerid steamID64`
After assigning access, run `writecfg` so the permission is saved.
The in-game console is usually the fastest way to run Rust admin commands while actively playing.

If the command works, Rust may show a response in the console, or the result may appear directly in-game. For example, a teleport command moves a player, while a save command may only print a short confirmation.
The server console is useful when you are not connected in-game or when you need to run setup commands such as assigning admin permissions.


A successful command will usually return a message in the console or cause a visible change on the server.
If a command does not work, check the command syntax first. Rust commands often require exact arguments, including player names, SteamID64 values, numbers, or true/false settings. A single missing value can make the command fail without much ceremony.
If the syntax is correct but protected commands still fail in-game, confirm that your account has admin access. Run `ownerid steamID64` from the server console, replacing `steamID64` with your own ID, then run `writecfg`. Rejoin the server if needed and test the command again.
If command changes are not saving, run these from the server console:
`save`
`writecfg`
The `save` command writes current world progress, while `writecfg` stores configuration and permission changes. For permanent gameplay features beyond normal Rust commands, server plugins may be the better long-term option.
Come chat with us and we will get back to you as soon as possible!
Contact SupportPush rotating chat announcements on your Rust server using the Advert Messages plugin. Covers installation through the HolyHosting panel, config tweaks, message ideas, colored text, and quick fixes when nothing fires.
Add custom prefixes, username colors, and ranks to your Rust server using the Better Chat plugin. Step-by-step install, group commands, and config file tips.
Run guarded loot events on your Rust server with the Dangerous Treasures uMod plugin. Step by step setup, configuration tips and common pitfalls explained.