Hide Admin Commands in the Rust Console

When an admin runs commands on a Rust server, players can end up watching it happen in global chat: an item hand-out, a kick, a ban. Two uMod plugins quiet that. No Give Notices removes the "gave" notices, and Secure Admin lets you turn off the public kick and ban announcements. Checked against No Give Notices 0.3.1 (released July 2026) and Secure Admin 1.1.8 (released August 2018, still listed on uMod), October 2026.

Both plugins need Oxide or Carbon on the server. If the Plugins tab says Your server runs plain Rust, start with How to install Oxide/uMod plugins on your Rust server.

Stop the item "gave" notices

The plugin's own description is "Prevents F1 item giving notices from showing in the chat". It hooks two kinds of message: a server chat line from the sender "SERVER" whose text contains "gave", and a player action broadcast whose text contains "gave". Both are dropped.

1. Open Plugins, stay on Store, search for No Give Notices and press Install.
2. On Oxide, a newly installed plugin stays unloaded until the server restarts: restart, or type oxide.load NoGiveNotices in the Console to load it now. On Carbon it loads by itself, and c.load NoGiveNotices or c.reload NoGiveNotices do it by hand.

That is all. The plugin has no config file, no commands and no permissions, so there is nothing to set up. Use give as an admin and the chat stays quiet.

Quiet kick and ban announcements

Secure Admin's source registers its own ban, kick, say and unban commands, which only work for players holding a permission, and it decides whether a kick or ban is announced to everyone. Secure Admin 1.1.8 compiled and loaded on Carbon on Rust build 2635 when we tested it, but we did not try its commands with players online, so test a kick on a spare account before you rely on it.

1. Install Secure Admin from the Plugins tab the same way, then load it as for No Give Notices, with oxide.load SecureAdmin on Oxide or c.load SecureAdmin on Carbon.
2. Once it is loaded, grant the permissions to yourself, or to a staff group, from the Console. A permission doesn't exist until its plugin is loaded. Replace the number with your SteamID64. These are the Oxide commands:

oxide.grant user 76561198123456789 secureadmin.ban
oxide.grant user 76561198123456789 secureadmin.kick
oxide.grant user 76561198123456789 secureadmin.say
oxide.grant user 76561198123456789 secureadmin.unban

On Carbon, oxide.grant prints nothing and does nothing. Use c.grant with the same arguments:

c.grant user 76561198123456789 secureadmin.ban
c.grant user 76561198123456789 secureadmin.kick
c.grant user 76561198123456789 secureadmin.say
c.grant user 76561198123456789 secureadmin.unban

Anyone without the matching permission is told "You are not allowed to use the 'kick' command" and nothing happens.

3. Open Plugins, switch to Installed, press Config on Secure Admin and set these two to false:
   • Broadcast Bans (true/false)
   • Broadcast Kicks (true/false)
4. Press Save, then Reload plugin.

With a broadcast switched off, the plugin sends the "has been banned" or "has been kicked" line only to the person who ran the command. Both are true by default.

The other Secure Admin settings

The same config holds more switches, all true by default:

Common problems

1. Everyone still sees the "gave" line. The plugin only handles the two message types above. A notice that reaches chat another way, such as from a different plugin, isn't hidden.
2. "You are not allowed to use the 'ban' command". The account running it lacks secureadmin.ban. Grant it as above.
3. The plugin fails to load after a Rust update. The Console shows a red compile error. Secure Admin has not had a release since 2018, so check its uMod page for a newer version, or remove it and rely on the game's own commands from Rust server.cfg and admin commands.