How to Install and Manage Oxide Plugins on Rust

If you've picked Oxide as your framework, here's exactly how to get plugins installed and keep them running smoothly.

Where Plugins Go

Oxide plugins are single .cs files that live in the oxide/plugins/ folder — accessible from your server's File Manager.

Installing a Plugin

1. Download the plugin's .cs file from a trusted source (uMod's official plugin directory is the standard place — avoid random third-party file shares for anything that touches your server).
2. Upload it directly into oxide/plugins/ via the File Manager.
3. Oxide auto-detects and loads new plugins dropped into that folder — no restart required for most plugins, though a restart is a safe fallback if a plugin isn't picking up.
4. Check the console — a successful load logs a confirmation message; an error there tells you immediately if something's wrong (a missing dependency, a version mismatch).

Configuring a Plugin

Most plugins generate their own config file (and sometimes a data file) automatically on first load, in oxide/config/ and oxide/data/ respectively. Edit the config, then use the plugin's reload command (often oxide.reload PluginName typed into the console) to apply changes without a full server restart.

Updating Plugins

Plugin authors update their .cs files as Rust itself updates (a Rust patch can break plugin compatibility until the author pushes a fix) — check the plugin's source page periodically, especially right after a major Rust update, and re-upload the new version over the old file the same way you installed it originally.

Managing Dependencies

Some plugins require other plugins to function (a common pattern: a core "framework" plugin that several add-on plugins hook into). Install dependencies first, in the order the plugin's documentation specifies — installing an add-on before its required dependency usually just fails to load with a clear error in the console.

Common Issues

• Plugin won't load: check the console for the exact error — usually a missing dependency or a Rust-version incompatibility after a recent update.
• Plugin loaded but not working as expected: check its config file — most unexpected behavior traces back to a config value, not a bug in the plugin itself.
• Server performance dropped after adding several plugins: some plugins are genuinely resource-heavy; if you've added a lot at once, disable them one at a time to isolate which one is the actual cause before assuming it's your plan's specs.

Removing a Plugin

Delete its .cs file from oxide/plugins/ and restart — this stops it from loading on next boot. Its config/data files aren't deleted automatically, so clean those up too if you want a completely fresh removal.