The admin plugins most Rust servers run
Most modded Rust servers run plugins from the same six categories, and knowing what each category is for is more useful than copying somebody else's plugin list.
6 min read · Updated Oct 21, 2026 · By GuavaHost Team
There is no official list of plugins a Rust server needs. What there is, after years of modded servers, is a set of problems that nearly every owner hits and a category of plugin that solves each one. Start from the problem you have rather than from a list of downloads.
You need a modding framework before any of this works. Installing Rust plugins with Oxide or Carbon covers picking one, switching it on and installing plugins from the Plugins page under Rust tools in your server menu.
Permissions come first
Every other plugin depends on this. Oxide and Carbon both ship with a permission system built in, and most plugins register their own permissions with it rather than inventing their own admin check.
The model is simple: permissions are granted to a group, and players are put in groups. You run it from the Console tab:
oxide.group add vip
oxide.grant group vip kits.vip
oxide.usergroup add 7656119XXXXXXXXXX vip
The commands are carbon. prefixed on Carbon but work the same way. Two habits save you a lot of pain later: grant permissions to groups rather than to individual players, and give your staff only the permissions their job needs. Staff permissions and least privilege explains why that matters more than it sounds.
Note that Rust's own admin levels are separate from plugin permissions. ownerid and moderatorid control the game's built-in F1 commands, and How to become a Rust admin covers those.
Admin tooling
This is the category that makes moderating possible. Between them, these plugins give you:
- an invisibility or spectate mode so you can watch a suspected cheater without them seeing you
- a map or radar overlay showing players, bases and sleepers while you investigate
- teleport commands, so you can get to a report instead of running across the map
- a tidy way to remove a griefed or misplaced structure without exploding it
- player lookup: when they joined, their playtime, their previous names
Widely used examples on uMod include Vanish for invisibility, AdminRadar for the overlay, a teleportation plugin for getting around, and RemoverTool for taking structures down cleanly.
One warning specific to this category: admin overlays are among the most expensive plugins you can run, because they redraw constantly for anyone using them. Turn yours off when you are done investigating.
Anti-cheat support
Rust runs EasyAntiCheat at the client, so plugins do not replace anti-cheat. What they add is evidence and reach.
Useful things in this category: logging combat and damage events so you can read back what happened in a fight, flagging suspicious patterns for an admin to look at, sharing ban lists across a community of servers, and connecting your server to an external ban database so a known cheater is stopped at the door.
Treat anything that claims to detect cheats on its own with scepticism. The honest version of this category gives you better logs and faster bans, not automatic detection. Rust's built-in combatlog command in the F1 console is still your first stop when a player reports something, and the server Console tab holds the rest. How to read server logs and crash reports covers getting around them.
Quality of life
The category that defines what your server feels like, and the one most likely to get out of hand.
Typical pieces: kits so players start with something, stack size and gather rate controls, faster smelting or crafting, a clan or team system, a friends system, a chat formatter that shows group tags, and a sign or furnace helper.
Pick these deliberately. Every gather rate multiplier and instant craft plugin moves your server further from vanilla, and players arriving from the Modded browser tab will judge you on whether the result is coherent. Two or three well-chosen changes read as a theme. Fifteen read as a mess.
Economy
If you want shops, rewards or a currency, this is where it comes from. The usual shape is a core economy plugin that holds balances, plus a shop or reward plugin that spends them, plus whatever earns the currency: playtime, voting, events, selling loot at a vending machine.
Start with the core plugin and one way to earn and one way to spend. Economies with five earning sources and no sink inflate within a week and stop meaning anything.
Events
Scheduled or random server events: convoys, airdrops on a timer, raidable bases, boss NPCs, hackable crate chains. They are what keeps a server interesting in week three of a wipe when the clans have everything.
They are also the heaviest category by a wide margin. An event plugin that spawns a hundred NPCs and a base full of entities is doing exactly the kind of work that makes Rust struggle. Add one at a time, watch your server through a busy evening, and read Tune a Rust server for better performance before you stack several on top of each other.
The plugin sprawl problem
Rust has a wipe cycle, and plugin lists grow across it. A plugin gets added to fix a complaint, another for an event weekend, another because somebody suggested it. Nothing gets removed, because removing things is scary and nobody remembers what the thing in the third row does any more.
Three months later, something breaks after a monthly force wipe and you have forty plugins to work through, half of which you cannot explain.
A routine that keeps this under control:
- Write down why each plugin is installed, in one line, somewhere you will find it again. Your Discord staff channel is fine.
- Remove anything you cannot justify in that one line. The Plugins page keeps the config file when you remove a plugin, so reinstalling later keeps your settings.
- After Facepunch's monthly force wipe, update the framework first, then the plugins that still throw errors in the Console. Fix them one at a time.
- Take a backup before any batch of plugin changes. Back up and restore a Rust server save covers what to keep, and Rust wipes: map wipe vs blueprint wipe covers the wipe itself.
How many plugins is too many? has the general version of this, and Safe plugin and mod sources is worth reading before you install a .cs file from somewhere you have not used before.
Common questions
Do I need plugins to run a Rust server?
No. A vanilla server works perfectly and appears on the Community browser tab, which is exactly what plenty of players are looking for. Installing a framework moves you to the Modded tab, so only do it if you actually want to change how the server plays.
Which plugins should I install first?
Set up permissions and basic admin tooling before anything else, because that is what lets you moderate the server at all. Add quality of life and events later, once you know what your players are asking for.
Will plugins break after a Rust update?
Often, yes. Facepunch's monthly force wipe changes the game enough that frameworks and plugins need updating, so expect to update Oxide or Carbon first and then any plugin still erroring in the Console. Giving yourself an hour after the monthly update rather than opening to players immediately saves a lot of stress.
Can I use paid Rust plugins on my server?
Yes. Paid plugins are single .cs files like free ones, so you upload them to oxide/plugins or carbon/plugins on the Files tab instead of installing them from the Plugins page. Buy from the established marketplaces rather than a random link, since a plugin is code running with full access to your server.
Still stuck? Jump into our Discord at discord.gg/GuavaHost and the team will help you out.
- rust
- plugins
- oxide
- carbon
- admin
Host a Rust server From $15.99/mo, with instant setup and DDoS protection.
Still need help? Our team is online 24/7 to answer questions.