This guide covers how to install the Oxide/uMod or Carbon modding framework on your Rust server, add community plugins, and manage them via the console. For general server configuration and startup variables, see the Rust Server Configuration Guide.
Installing Oxide/uMod or Carbon
Oxide (now maintained as uMod) and Carbon are modding frameworks for Rust that allow you to install community-built plugins. These frameworks add features such as economy systems, custom kits, vote rewards, PvE protection zones, and much more.
You do not need to upload any files manually. The modding framework is installed automatically by setting a single startup variable:
- Stop your server from the GPanel Console tab.
- Log in to GPanel and go to the Startup tab.
- Find the
FRAMEWORKvariable and set it to:oxide— for Oxide/uMod (the most widely used framework, with the largest plugin library)carbon— for the Carbon framework (an alternative with its own plugin ecosystem)vanilla— to run without any modding framework
- Start the server. The framework files are downloaded and applied automatically. On first start with Oxide, the
oxide/directory structure is generated. - Check the console log for a line such as
Loaded plugin Oxide.Coreto confirm Oxide is active.
FRAMEWORK variable and start the server, the framework is downloaded and installed automatically. You do not need to upload Oxide or Carbon files via SFTP.
Installing Plugins
Plugins are distributed as .cs (C# source) files. Oxide compiles them on the server at runtime — no pre-compilation is required.
- Download the plugin
.csfile from umod.org or another trusted source. - Upload the
.csfile to theoxide/plugins/directory on your server using SFTP or the GPanel file manager. For help with SFTP, see How to Upload Files via SFTP. - If the server is running, the plugin will be detected and compiled automatically within a few seconds. You will see output in the console confirming it loaded, e.g.
Loaded plugin MyPlugin v1.2.3 by Author. - If the server is not running, the plugin will load on next startup.
Oxide Directory Structure
oxide/
plugins/
MyPlugin.cs <- place plugin files here
AnotherPlugin.cs
config/ <- auto-generated plugin config files
data/ <- plugin data files
logs/ <- plugin log files
oxide/plugins/. Files placed in subdirectories or with incorrect extensions will be ignored. Each plugin must have the .cs extension.
Configuring Plugins
Most plugins generate a JSON configuration file in oxide/config/ the first time they load. To customise a plugin:
- Let the plugin load at least once so it generates its default config file.
- Stop your server (or note that some plugins support live config reload).
- Open the plugin's config file in
oxide/config/PluginName.jsonusing the GPanel file manager or SFTP. - Edit the settings and save the file.
- Reload the plugin with
oxide.reload PluginNameor restart the server.
Managing Plugins via Console
These commands can be run from the GPanel console or via an RCON client. For RCON setup, see Rust RCON Access and Admin Commands.
| Command | Description |
|---|---|
oxide.plugins |
List all currently loaded plugins and their versions. |
oxide.load PluginName |
Load a plugin that is present in oxide/plugins/ but not yet loaded. |
oxide.unload PluginName |
Unload a plugin without removing the file. |
oxide.reload PluginName |
Reload a plugin after updating its .cs file. Use this to apply plugin updates without a full server restart. |
oxide.reload * |
Reload all loaded plugins at once. |
Updating Plugins
To update a plugin to a newer version:
- Download the updated
.csfile from the plugin's page on umod.org. - Upload the new file to
oxide/plugins/, overwriting the existing file. - If the server is running, Oxide detects the file change and automatically recompiles and reloads the plugin. Alternatively, run
oxide.reload PluginName. - Check the console for any errors. Some plugin updates may require changes to the config file in
oxide/config/.
Removing Plugins
To remove a plugin entirely:
- Run
oxide.unload PluginNameto unload the plugin while the server is running. - Delete the
.csfile fromoxide/plugins/. - Optionally delete the plugin's config file from
oxide/config/and data files fromoxide/data/if you no longer need them.
Popular Plugins
| Plugin | Category | Description |
|---|---|---|
| Kits | Gameplay | Allow players to redeem pre-configured item kits. Useful for starter kits or VIP rewards. |
| Economics | Economy | Adds a server currency system. Used as a dependency by many shop and reward plugins. |
| ServerRewards | Economy | Point-based reward system, often combined with Economics for an in-game shop. |
| VoteDay | Utility | Lets players vote to skip to daytime. Reduces complaints about long nights. |
| Clans | Social | Adds a clan/team system with clan tags and shared access to tool cupboards. |
| TruePVE | PvE | Prevents player-vs-player damage. Essential for PvE server configurations. |
| Teleportation | Utility | Adds player-to-player and home teleport commands with configurable cooldowns. |
| DiscordCore / DiscordMessages | Integration | Sends server events (connects, chat, deaths) to a Discord webhook channel. |
Troubleshooting Plugin Issues
If your plugins are not loading, check the following:
- Confirm Oxide is installed and active. In GPanel's Startup tab, the
FRAMEWORKvariable must be set tooxide. The console log should showLoaded plugin Oxide.Coreduring startup. - Plugin files must be placed directly in
oxide/plugins/with the exact.csextension. Files in subdirectories or with wrong extensions are ignored. - Check the console and
oxide/logs/for compilation errors. A plugin with a syntax error will fail to load and the error message will describe the issue. - Some plugins have dependencies on other plugins (e.g. many shop plugins require Economics). Install all required dependencies first.
For other common server issues, see Rust Server Troubleshooting.
Need Help?
If you run into an issue not covered in this guide, our support team is available to help. Submit a support ticket and include your server ID, a description of the issue, and any relevant console output.