Skip to main content
Plugins are what turn a vanilla Rust server into a 2x server with kits, teleports, and admin tools. To run plugins you first need a modding framework — Oxide (distributed via uMod) or Carbon — and then you simply drop plugin files into a folder. This guide covers the full workflow on your Wasabi Hosting server.
Installing a modding framework moves your server from the Community tab to the Modded tab of the in-game server browser, even if you don’t change any gameplay values.

​
Oxide vs. Carbon

Oxide (uMod)Carbon
MaturityThe long-standing standard, huge plugin ecosystemNewer, actively developed
Plugin sourceumod.orgOxide-compatible — runs most uMod plugins
PerformanceSolidOptimized, lower overhead on busy servers
Plugin folderoxide/pluginscarbon/plugins
If you’re unsure, start with Oxide — nearly every guide and plugin assumes it. The rest of this page uses Oxide paths; Carbon works the same way with carbon/ folders.

​
Installing Oxide

1

Check for a built-in installer

In the Game Panel, check your server’s settings/Startup for a modding framework option (Vanilla / Oxide / Carbon switcher). If available, select Oxide and restart — that’s the whole installation.
2

Manual install (if needed)

Stop your server, then download the latest Oxide.Rust build for Linux from the official OxideMod GitHub releases. Upload the archive’s contents to your server’s root directory via the File Manager or SFTP (see file management), overwriting existing files when prompted.
3

Start and verify

Start the server. In the panel Console, run:
oxide.version
If it prints a version number, Oxide is installed. The oxide/ folder structure is created automatically on first boot.
Oxide must be updated after every Rust update. Server updates overwrite Oxide’s patched files, so after each update (including the monthly forced wipe) reinstall/update Oxide before starting the server — otherwise it boots as vanilla and your plugins won’t load.

​
Installing Plugins

1

Download the plugin

Get the plugin’s .cs file from umod.org or another trusted source. Only install plugins from sources you trust — plugins run with full server access.
2

Upload to oxide/plugins

Using the File Manager or SFTP, upload the .cs file to:
/oxide/plugins/
3

Let it load

Oxide hot-loads plugins — no restart needed. Watch the panel Console for a load confirmation or compile errors.
4

Configure it

On first load, the plugin generates a JSON config at /oxide/config/PluginName.json. Edit it, save, then reload the plugin:
oxide.reload PluginName

​
Managing Permissions

Most plugins gate features behind Oxide permissions. Run these in the panel Console: 
oxide.grant user "PlayerNameOrSteamID" kits.use
oxide.grant group default kits.use
oxide.revoke user "PlayerNameOrSteamID" kits.use
oxide.group add vip
oxide.usergroup add "PlayerNameOrSteamID" vip
oxide.show perms
Each plugin’s uMod page documents its permission names. Granting to the default group applies to all players; the admin group applies to server admins.
PluginWhat it does
Gather ManagerMultiply gather rates (2x, 5x, etc.)
KitsStarter/VIP item kits with cooldowns
VanishInvisibility for admins
Admin RadarESP-style overlay for catching cheaters
BackpacksExtra portable inventory space
Better LootCustomize loot tables and container contents

​
Keeping Plugins Updated

  • After the monthly forced wipe, Rust’s internals often change and plugins can break. Update Oxide first, then update any plugins that error in the console.
  • Remove or update broken plugins promptly — a failing plugin spams errors and can degrade server performance.
  • Back up your oxide/ folder (configs, data, permissions) before major changes — see backups.
Related reading: admin commands for vanilla admin setup, and server wipes for what survives a wipe (plugin data does, unless you delete it).

Build your modded Rust server

Plugins love fast single-core performance. Wasabi Rust hosting starts at €9.99/month on Ryzen X3D CPUs with NVMe storage.