
Rust Plugins: Installing and Using Oxide
Rust is a great game, but the vanilla server does not give you many tools to manage it. That is where Oxide comes in. This guide walks you through installing Oxide, adding plugins, and keeping everything running smoothly even after Rust's monthly updates.
Install Oxide by dropping its files into your Rust server's root folder and restarting, then add plugins by placing their .cs files into the oxide/plugins folder. Configs generate automatically and can be edited afterward, but expect Oxide and your plugins to break briefly after Rust's monthly forced update until they're patched.
What Oxide (uMod) Is and Why Rust Needs It
Oxide, also called uMod, is a modding framework for Rust servers. On its own, Rust does not let you add custom commands, permissions, or extra features. Oxide changes that. It acts as a bridge between the game server and third party plugins, so admins can add anything from simple chat commands to full economy systems.
If you plan to run any kind of custom server, whether it is PvE, roleplay, or just a friends and family server with extra tools, you will need Oxide.
Installing Oxide
- 1Stop your Rust server before making changes.
- 2Download the latest Oxide release for Rust from the official uMod website.
- 3Extract the files into your server's root folder. This usually means dropping files into the same directory as your RustDedicated server files.
- 4Restart the server.
- 5Check your console log. If Oxide loaded correctly, you will see Oxide version info printed when the server starts.

Most hosting panels also offer a one click Oxide install. If your provider has this option, it saves you from doing it manually.
Where Plugins and Configs Live
Once Oxide is installed, a few new folders appear in your server directory.
oxide/plugins: this is where plugin files (.cs files) go.oxide/config: this holds the config file for each plugin, usually in JSON format.oxide/data: this stores saved data, like player stats or economy balances.oxide/logs: useful for checking plugin errors.
To install a plugin, drop its .cs file into oxide/plugins. The server will usually auto load it. A config file will be generated automatically on first load, which you can then edit.
Plugins Worth Running
There are thousands of plugins available, but a few are considered must haves for most servers.
- Vanish: lets admins go invisible to catch cheaters or handle issues quietly.
- BetterChat: adds more control over chat formatting and filters.
- Economics: adds an in game currency system many other plugins rely on.
- Backpacks: gives players extra inventory space, which is popular on modded servers.
- Zone Manager: lets you create safe zones or restricted areas.
Always check plugin reviews and update history before installing. Abandoned plugins can break your server after a Rust update.
Permissions and Groups
Oxide comes with a built in permission system. This lets you control who can use which commands or plugin features.
Common commands include:
- oxide.grant user "player name" permission.name
- oxide.grant group groupname permission.name
- oxide.group add groupname
Most admins set up groups like admin, moderator, and vip, then assign permissions to each group instead of individual players. This makes managing large staff teams much easier.
Monthly Rust Updates Breaking Plugins, and Recovery
Rust gets a forced wipe and update on the first Thursday of every month. These updates often break Oxide itself, along with many plugins, since the game's underlying code changes.
Here is what usually happens and how to recover.
- 1Rust releases the update.
- 2Oxide developers release a matching update within a few hours to a day.
- 3Update your Oxide files following the same install steps as before.
- 4Check
oxide/logsfor any plugins throwing errors. - 5Wait for plugin developers to patch their plugins if errors persist. Most popular plugins update within a day or two.
It helps to keep a lightweight backup server or test environment, so you are not stuck without a working server while waiting for updates.




