Installing Rust Plugins – uMod/Oxide Guide

Last checked: September 27, 2026. You install Rust plugins via uMod/Oxide by enabling the framework, downloading a suitable .cs file from the official uMod plugin page and uploading it to /oxide/plugins/. Afterwards, you check the configuration, permissions and console. A controlled process is important, because faulty plugins can affect gameplay, permissions or server stability.

Requirements

You need a Rust server with file access, console access and an enableable uMod/Oxide framework. With game-serverhosting, the typical order is: enable the framework in the panel, let the server start, upload plugin files and then set the configuration and permissions. Don't plan changes during peak player activity; if possible, test them first with a few players or on a separate setup.

The official uMod site is the primary source for Rust plugins and documentation. Use the existing plugin overview at umod.org/plugins?game=rust for downloads. For how uMod works, the official documentation at umod.org/documentation is also authoritative. Always check there whether a plugin is actively maintained and which permissions or dependencies are listed.

If you're still working on the basic setup of your Rust server, the internal guide Rent and Set Up a Rust Server will help. For RAM, settings and plugin planning, you'll also find the guide Renting a Rust Server: RAM, Settings & Plugins.

Installing uMod/Oxide

uMod is a plugin framework for Rust. It adds a plugin layer to the server through which C# plugins can be loaded, configured and given permissions.

1. In the startup variables, set Modding Framework (FRAMEWORK) to oxide
2. Save the change and restart the Rust server
3. Use oxide.version in the server console to check whether Oxide is loaded

After the change, wait until the server has fully started and check oxide.version. Only then should you upload files to /oxide/plugins/. If folders such as /oxide/config/, /oxide/data/ or /oxide/logs/ are still missing, uMod may not have been fully initialized yet, or the server needs to be started cleanly once.

Installing a Plugin

1. Visit umod.org/plugins?game=rust
2. Download the plugin (.cs file)
3. Upload it to /oxide/plugins/
4. The plugin is usually loaded automatically; a full restart is often not necessary, but can make sense for larger changes

Always upload the original .cs file of the plugin and don't change the file name unnecessarily. After the upload, you should watch the server console. uMod normally reports there whether the plugin compiled and loaded, or whether syntax errors, missing dependencies or version problems occur.

Choosing Rust Plugins

There are different uMod plugins for teleportation, chat, kits, gather rates or inventory. Search the official Rust plugin list, open the respective project page and check the version, dependencies, commands and permissions there. Blanket download counts go out of date quickly and say nothing about compatibility with your Rust version.

Install plugins one at a time. After each upload, check the console and the functionality with a test account. Plugins for economy, teleportation or inventory in particular can change existing gameplay.

Plugin Configuration and Stored Data

Configurable plugins usually create a JSON file under /oxide/config/ after loading successfully. Plugins without configurable options don't need to have a file there. Only open it after the plugin has loaded once, and make sure the JSON stays syntactically valid.

{
  "Default Multiplier": 3.0,
  "Quarry Multiplier": 3.0,
  "Pumpjack Multiplier": 3.0
}

This is only an example of the JSON format, not a guaranteed schema of a current GatherManager version. Use the keys and values generated by the plugin itself; // comments are invalid in JSON.

Only change values whose meaning you know. After a change, reload the plugin in the server console with oxide.reload <PluginName> or restart the server in a controlled way. The uMod configuration documentation describes this process. If the console reports JSON errors after saving, first check commas, quotation marks and brackets.

Plugin Permissions

Many Rust plugins are installed but unusable for players without correctly set permissions. uMod works with permissions for users and groups. The plugin page often states which permission needs to be granted.

oxide.grant user <steamid> <permission>
oxide.grant group default <permission>
oxide.revoke user <steamid> <permission>

user is suitable for individual administrators or testers. group default generally affects normal players and should be used carefully. Grant permissions only as broadly as necessary, especially for admin, teleport, kit, remove or economy functions.

Verifying the Result

After installation, you should check three things: First, the plugin must load in the console without compile errors. Second, oxide.plugins should show the plugin in the list of loaded plugins. Third, the relevant in-game command or effect must work with a test account.

For configurable plugins, check the file under /oxide/config/ and read load errors in the log. For economy, kit or inventory plugins, also back up the associated data under /oxide/data/; the .cs file and config alone don't necessarily contain player progress. If several plugins were changed at once, test them individually. That way you can find out more quickly whether a problem comes from the plugin itself, a permission, a faulty config or a conflict.

Troubleshooting

• Plugin doesn't load: Check the Oxide version, the Rust server version and the notes on the plugin page.
• Errors in the console: Read the specific error message and check whether the plugin is up to date. For plugin errors, the respective umod.org page is the right starting point.
• Performance: oxide.plugins also shows failed plugins and the reason for the failure. Use status and hook times as a hint, test the specific demanding gameplay situation and unload recently changed plugins one by one with oxide.unload <PluginName>. The Oxide command reference explains plugin status, hook times and targeted unloading.
• Conflicts: Test plugins individually, especially if several plugins change chat, teleport, kits, zones or inventory.
• Config gets overwritten: Back up the config and associated files under oxide/data separately. Stop the server or unload the plugin, edit the config only afterwards and load it again. A saved value is only applied if the JSON is valid and the key matches the plugin version.
• Players can't use commands: Check the permission names on the plugin page and grant them correctly with oxide.grant.

FAQ

Do I have to restart the Rust server after every plugin?

Not always. Many uMod plugins are loaded automatically after being uploaded to /oxide/plugins/. For larger changes, dependencies or unexplained errors, a controlled restart still makes sense.

Where do I find the config files?

Configurable uMod plugins store their JSON files under /oxide/config/ by default. A plugin without configurable options doesn't create a file there.

Why doesn't a plugin command work in the game?

Usually a permission is missing or the command is named differently than expected. Check the plugin page, set the permissions with oxide.grant and then check the console.

Can I install several Rust plugins at the same time?

Technically yes, but in practice you should proceed step by step. Install one plugin, check the console and functionality, and only then move on to the next.

What do I do about performance problems after an installation?

Disable the most recently installed plugins one by one, watch the server console and check oxide.plugins. That way you narrow down whether a specific plugin or a combination is the cause.