{"id":919,"date":"2021-09-19T12:59:57","date_gmt":"2021-09-19T12:59:57","guid":{"rendered":"https:\/\/xgamingserver.com\/blog\/?p=919"},"modified":"2026-06-15T19:22:30","modified_gmt":"2026-06-15T19:22:30","slug":"top-10-admin-plugins-for-your-rust-server","status":"publish","type":"post","link":"https:\/\/xgamingserver.com\/blog\/top-10-admin-plugins-for-your-rust-server\/","title":{"rendered":"Top 10 admin plugins for your Rust server"},"content":{"rendered":"\n

If you run a modded Rust server, plugins are the difference between fighting fires in chat all night and actually administering your community. Vanilla Rust gives you a solid command surface through RCON and the F1 console, but it stops at the basics. Want invisible spectating, a points economy, controllable gather rates, or a one-window admin menu? Every one of those lives in a plugin. This guide breaks down the ten admin and management plugins that matter most in 2026, where each one installs, and how to wire up permissions so the right people can actually use them.<\/p>\n\n\n\n

Before we get to the list, you need to understand the two frameworks those plugins run on, because that decision shapes everything else about how you manage your server.<\/p>\n\n\n\n

Oxide (uMod) vs Carbon: which framework runs your plugins<\/h2>\n\n\n\n

Rust plugins are written in C# and loaded by a modding framework. There are two in serious use, and almost every plugin you will ever install runs on one or both of them.<\/p>\n\n\n\n

Oxide \/ uMod<\/strong> is the long-established framework with the largest plugin library on the planet: well over 1,400 plugins on uMod alone. It uses a traditional chat-command workflow, and it is what most documentation and tutorials assume. If a plugin exists, it almost certainly runs on Oxide.<\/p>\n\n\n\n

Carbon<\/strong> (carbonmod.gg) is the modern alternative. The official Rust wiki describes it as “a modern modding framework for the game Rust responsible for handling background operations and running custom plugins and extensions with maximum performance.” Crucially, the wiki notes Carbon offers “seamless migration from Oxide with identical folder structure and automatic data migration tools” and “uses Harmony and does not require any additional patches to run existing Oxide plugins.” In practice the community reports roughly 99% compatibility with Oxide plugins, plus dynamic hook loading (only the hooks a plugin actually calls get loaded, which is reported to reduce RAM and speed boot times by around 30-40%). Those performance figures are community-sourced rather than Facepunch-official, so treat them as reported rather than guaranteed.<\/p>\n\n\n\n

The practical takeaway: you can run nearly the same plugin list on either framework. Carbon is typically patched fastest on force-wipe day, which matters when you want to be online for the first-player rush. Whichever you choose, remember that a Facepunch game update overwrites your framework files<\/strong> \u2014 after every wipe or update you must reinstall Oxide or Carbon before any plugin will load again.<\/p>\n\n\n\n

Where plugins and configs install<\/h2>\n\n\n\n

This trips up new admins constantly, so commit it to memory. On Oxide, your folder layout looks like this:<\/p>\n\n\n\n

Folder<\/th>What goes here<\/th>File type<\/th><\/tr><\/thead>
oxide\/plugins\/<\/code><\/td>The plugins themselves<\/td>.cs<\/code><\/td><\/tr>
oxide\/config\/<\/code><\/td>Per-plugin settings<\/td>.json<\/code><\/td><\/tr>
oxide\/data\/<\/code><\/td>Persistent plugin data<\/td>.json<\/code><\/td><\/tr>
oxide\/logs\/<\/code><\/td>Plugin logs<\/td>.txt<\/code><\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Drop the .cs<\/code> file into oxide\/plugins\/<\/code> and the framework compiles and loads it automatically. On first load it generates a default config in oxide\/config\/<\/code> that you then edit and reload. Carbon mirrors this exactly \u2014 the wiki states it uses an “identical folder structure” to Oxide, so the equivalent paths are carbon\/plugins\/<\/code> and carbon\/configs\/<\/code>. (Carbon’s exact paths are not enumerated verbatim in the wiki; it only confirms the structure matches Oxide, so verify against current Carbon docs if you are scripting deployments.) For step-by-step install and permission walkthroughs, our Rust server documentation<\/a> covers the full setup flow.<\/p>\n\n\n\n

The 10 admin and management plugins worth installing<\/h2>\n\n\n\n

1. AdminMenu \u2014 your control center<\/h3>\n\n\n\n

AdminMenu gives you a centralized in-game GUI that integrates with other plugins for one-window server management. Instead of remembering dozens of chat commands, you open a single menu and click through to spawn items, toggle other tools, manage players, and more. It is designed to hook into popular companions like ServerRewards, Vanish, and Godmode, so it becomes the front door to your whole admin toolkit. For anyone managing a busy server, this is the plugin that turns chaos into a clickable interface.<\/p>\n\n\n\n

2. Vanish \u2014 invisible moderation<\/h3>\n\n\n\n

Vanish makes an admin completely invisible to players and AI, letting you observe suspected cheaters discreetly. This is the single most important moderation plugin you can run: catching a cheater in the act is far stronger evidence than reacting to a report after the fact. Pair it with the in-game console (F1<\/code>) and you can watch a player’s behavior in real time without tipping them off that an admin is present.<\/p>\n\n\n\n

3. RemoverTool \u2014 fewer “I misplaced a wall” tickets<\/h3>\n\n\n\n

RemoverTool (maintained at github.com\/MONaH-Rasta\/RemoverTool) lets players hammer-remove their own building blocks within a configurable grace period. It supports the building tiers \u2014 Twig, Wood, Stone, Metal, and Top Tier \u2014 though note it targets building blocks rather than deployables. Giving players a self-service way to fix a misplaced wall or doorway quietly eliminates one of the most common support requests an admin ever gets. Less ticket triage, happier players.<\/p>\n\n\n\n

4. ServerRewards \u2014 a points economy and store<\/h3>\n\n\n\n

ServerRewards is a points-based economy. Players earn points through kills, farming, and playtime (with optional VIP multipliers) and spend them in an in-server store on items, kits, and commands. It sits on top of the Economics plugin, which provides the underlying currency layer. This is the backbone of player retention on most modded servers: a reason to keep logging in, and a fair, non-pay-to-win way to reward engagement.<\/p>\n\n\n\n

5. GatherManager \u2014 the only way to change gather rates<\/h3>\n\n\n\n

This is the most important plugin on the list for one simple reason: vanilla Rust has no built-in gather-rate convar<\/strong>. There is no server.gatherrate<\/code> or anything like it. The only way to make trees give more wood or nodes give more ore is to install a plugin, and GatherManager (by Calytic) is the canonical, best-documented choice. We cover it in depth in its own guide on how to modify the gather rate on your Rust server<\/a>, but here is the short version.<\/p>\n\n\n\n

The config lives at oxide\/config\/GatherManager.json<\/code>, and it splits gathering into four types: dispenser<\/code> (hitting trees, ore, and corpses), pickup<\/code> (collecting ground items like hemp), quarry<\/code> (Mining Quarry output), and survey<\/code> (survey charge results). You set multipliers with the gather.rate<\/code> command:<\/p>\n\n\n\n

gather.rate dispenser Wood 10\ngather.rate pickup Stones 10\ngather.rate quarry Stones 20\ndispenser.scale tree 2<\/code><\/pre>\n\n\n\n
The first line gives 10x wood from trees, the second 10x picked-up stone, the third 20x quarry stone, and dispenser.scale<\/code> adjusts how much resource a dispenser holds, separate from the per-hit rate. Whether the quarry<\/code> type also governs the giant Excavator (versus only the placeable Mining Quarry) is unconfirmed, so treat the quarry setting as targeting mining quarries and verify Excavator behavior against your current plugin version.<\/p>\n\n\n\n
6. Economics \u2014 the currency foundation<\/h3>\n\n\n\n
Economics is rarely the headline plugin, but it is the foundation under ServerRewards and dozens of shop, gambling, and reward plugins. It manages a single currency balance per player that other plugins read and write. Install it early; a huge slice of the economy ecosystem expects it to be present, and adding it later means reconfiguring everything that depends on it.<\/p>\n\n\n\n
7. Godmode \u2014 survive while you administer<\/h3>\n\n\n\n
Godmode makes an admin invulnerable, which sounds trivial until you are trying to investigate a base raid or build an event arena while players (or AI) are actively trying to kill you. It integrates cleanly with AdminMenu so you can toggle it from the same interface as Vanish. Use it for event hosting, building inspections, and safe spectating \u2014 and turn it off before you join legitimate combat, for obvious fairness reasons.<\/p>\n\n\n\n
8. A teleport\/home plugin \u2014 quality of life that retains players<\/h3>\n\n\n\n
Teleport and home-management plugins let players set a home, teleport to teammates, and request teleports to each other. On PvE and modded-PvP servers this is one of the most requested features. From an admin standpoint it also gives you fast travel to investigate reports across the map. Configure cooldowns and combat-block rules carefully so teleporting can’t be abused to escape fights on a PvP server.<\/p>\n\n\n\n
9. A kits plugin \u2014 onboarding and VIP perks<\/h3>\n\n\n\n
Kits plugins let you define bundles of items players can claim, gated by permission, cooldown, or VIP group. A starter kit smooths the first-five-minutes experience after a wipe, and VIP kits give you a clean, permission-driven way to reward supporters. Because kits are permission-gated, they pair directly with the permission system we cover below \u2014 you grant a group access to a kit and the plugin handles the rest.<\/p>\n\n\n\n
10. A discord\/RCON relay \u2014 administer from anywhere<\/h3>\n\n\n\n
Relay plugins push chat, kills, and join\/leave events to Discord and let trusted staff run commands without being in-game. They lean on the same RCON surface Rust already exposes, so they complement rather than replace the official tooling. If you want the underlying mechanics, our Rust RCON and server console commands guide<\/a> explains how the WebRCON connection actually works under the hood.<\/p>\n\n\n\n
Granting access: the permission system<\/h2>\n\n\n\n
Installing a plugin is half the job; the other half is deciding who can use it. Oxide and Carbon share a permission system built around two auto-created groups \u2014 admin<\/code> and default<\/code>. Admins land in admin<\/code> automatically; everyone else sits in default<\/code>. Permissions use a pluginname.permission<\/code> node format, for example vanish.allow<\/code> or coolplugin.use<\/code>.<\/p>\n\n\n\n
Here are the core commands. You can target a user by player name or SteamID64, and the SteamID64 is the 17-digit ID shown in the status<\/code> command’s ID column:<\/p>\n\n\n\n
# Grant \/ revoke to a user (name or SteamID64)\noxide.grant  user 76561197854018763 vanish.allow\noxide.revoke user 76561197854018763 vanish.allow\n\n# Grant \/ revoke to a group\noxide.grant  group admin coolplugin.use\noxide.revoke group admin coolplugin.use\n\n# Create a group, set a title + rank, and inherit from a parent\noxide.group add supporters\noxide.group set supporters \"[Server Supporters]\" 1\noxide.group parent tier_2 tier_1\n\n# Add a user to a group\noxide.usergroup add 76561197854018763 supporters\n\n# Inspect\noxide.show groups\noxide.show group admin\noxide.show perms supporters<\/code><\/pre>\n\n\n\n
Carbon uses the same command surface \u2014 it accepts the full oxide.*<\/code> set and adds the short o.<\/code> alias (so o.grant<\/code>, o.group<\/code>, o.reload<\/code> all work; the o.<\/code> alias works on Oxide too). Carbon’s native reload is carbon.reload<\/code>. Wildcard nodes like *<\/code> or pluginname.*<\/code> are commonly used in practice, but their exact behavior wasn’t in our verified sources, so test them per-plugin rather than assuming they grant everything. For a deeper walkthrough see our guide on how to set plugin permissions on your Rust server<\/a>.<\/p>\n\n\n\n
Plugins, performance, and the single-threaded reality<\/h2>\n\n\n\n
Every plugin you add costs something. Rust runs on Unity and the server is mostly single-threaded, so performance is dominated by single-core CPU clock speed rather than core count. Load comes from entity count, worldsize, player count, AI, and \u2014 relevant here \u2014 plugins. This is one reason Carbon’s dynamic hook loading is attractive: it only loads the hooks a plugin actually uses, which reportedly trims overhead compared to Oxide.<\/p>\n\n\n\n
A few performance convars are worth knowing as you stack plugins. fps.limit<\/code> caps server FPS to prevent wasted cycles (Facepunch has said a server can run capped at 30 FPS with no noticeable difference to players; 30-60 is a common range). server.tickrate<\/code> is read at startup with an ideal of 30-60. And nothing beats the oldest lever in the book: wiping reduces entity count<\/strong>, which is the single biggest fix for a bloated, laggy long-running server. We go further in our guide on how to improve Rust server performance<\/a>. The bottom line for plugin admins: audit your plugin list periodically and remove anything you aren’t actually using.<\/p>\n\n\n\n
A note on the Built Different update and reinstalling frameworks<\/h2>\n\n\n\n
The June 2026 “Built Different” force wipe (June 4, 2026, 2 PM EDT) is a useful reminder of a recurring trap. Every Facepunch update overwrites Oxide and Carbon files, so after the wipe you must reinstall your framework before plugins load. Carbon is usually patched within hours on wipe day, which is a real advantage if you want to capture the first-online rush. If you administer through a big update, read our breakdown of what the Built Different update means for server admins<\/a> before you flip the switch. When you are ready to run a modded server without wrestling the underlying box, our managed Rust hosting<\/a> ships with Oxide\/Carbon support so plugins are a one-click affair.<\/p>\n\n\n\n
Frequently asked questions<\/h2>\n\n\n\n
What are the best Rust admin plugins for a new server?<\/h3>\n\n\n\n
Start with a small, high-impact core: AdminMenu for a clickable control center, Vanish for catching cheaters discreetly, GatherManager to set your gather rates (vanilla Rust has no gather convar, so this is mandatory if you want anything above 1x), and Economics plus ServerRewards if you want a points economy. Add RemoverTool early to cut “I misplaced a wall” support tickets. That five-or-six plugin stack covers moderation, economy, and quality of life without bloating your server.<\/p>\n\n\n\n
Where do Rust plugins and their config files go?<\/h3>\n\n\n\n
On Oxide, plugin .cs<\/code> files go in oxide\/plugins\/<\/code> and their generated .json<\/code> settings go in oxide\/config\/<\/code>, with persistent data in oxide\/data\/<\/code> and logs in oxide\/logs\/<\/code>. Carbon uses an identical folder structure, so the equivalents are carbon\/plugins\/<\/code> and carbon\/configs\/<\/code>. Drop the plugin in, let the framework compile it and generate a default config, then edit the config and reload the plugin.<\/p>\n\n\n\n
Is Carbon or Oxide better for running admin plugins?<\/h3>\n\n\n\n
Both run essentially the same plugins \u2014 the community reports around 99% compatibility, and Carbon uses Harmony so it doesn’t need extra patches to run existing Oxide plugins. Oxide has the larger, more documented library (1,400+ plugins on uMod). Carbon is the modern option with dynamic hook loading that reportedly improves performance and faster patching on force-wipe day. If you want maximum compatibility and tutorial coverage, pick Oxide; if you want performance and quick wipe-day turnaround, pick Carbon. You can migrate between them thanks to Carbon’s identical folder structure and data-migration tools.<\/p>\n\n\n\n
How do I give a moderator permission to use a plugin?<\/h3>\n\n\n\n
Use the permission system. Grant a permission node directly to a player with oxide.grant user  pluginname.permission<\/code>, or grant it to a whole group with oxide.grant group  pluginname.permission<\/code> and then add the player to that group via oxide.usergroup add  <\/code>. The two default groups are admin<\/code> and default<\/code>. Carbon accepts these same commands plus the o.<\/code> short alias.<\/p>\n\n\n\n
Do plugins survive a wipe or a Rust update?<\/h3>\n\n\n\n
Your plugin files and configs in the oxide or carbon folders persist, but a Facepunch game update overwrites the framework itself \u2014 so after every wipe or update you must reinstall Oxide or Carbon before plugins will load again. Carbon is typically patched within hours on force-wipe day. Plan your wipe-day routine around reinstalling the framework first, then confirming plugins loaded, then opening to players.<\/p>\n\n\n\n
Can I change gather rates without a plugin?<\/h3>\n\n\n\n
No. This is the most common misconception in Rust administration: vanilla Rust has no built-in gather-rate convar of any kind. To run anything above 1x you must install a plugin, and GatherManager is the standard choice. Its config sits at oxide\/config\/GatherManager.json<\/code> and it splits rates into four types \u2014 dispenser<\/code>, pickup<\/code>, quarry<\/code>, and survey<\/code> \u2014 which you adjust with the gather.rate<\/code> command.<\/p>\n\n\n\n\n
\n
Free Rust Tools<\/h3>\n
Speed up your server with our free Rust tools:<\/p>\n