Fix Rust Oxide / uMod Plugins Not Loading

After a Rust wipe or a forced update, Oxide (uMod) plugins often stop loading. The reasons are predictable — an outdated Oxide build, a broken plugin, or a missing dependency. Here's the fix.

"Plugins not loading" after a wipe or update nearly always comes down to four things. Match the console message to the cause and go straight to the fix — the first one clears most post-update breakage:

Cause 1: Oxide is out of date

Rust force-updates regularly, and Oxide/uMod must match the current Rust build. If Oxide is behind, plugins won't compile. Update Oxide to the latest build for your branch and restart the server. This single step fixes most post-update breakage.

Cause 2: the plugin itself is outdated

A plugin written for an older API can fail to compile after an update. Check the plugin's uMod page for a newer version, replace the .cs file in oxide/plugins/, and it will hot-reload automatically.

Cause 3: a missing dependency

Some plugins need a library plugin or an extension. If the console says "missing dependency", install the required plugin/extension and reload. Common ones include image/economics libraries the plugin lists on its page.

Cause 4: wrong folder

Plugins go in oxide/plugins/ as .cs files. Configs land in oxide/config/. A plugin dropped anywhere else simply won't be seen. Verify the path.

Reload without a full restart

Oxide watches the plugins folder and hot-reloads. You can also reload manually from the console:

oxide.reload MyPlugin
# or reload everything
oxide.reload *

After any Rust update: update Oxide to match, then update your plugins. That order solves nearly every "not loading" report.

Cause 5: "Plugin failed to compile" from a syntax or API error

This exact console message means the C# code itself won't build — either the plugin author shipped a bug, or a Rust/Oxide API change removed or renamed something the plugin relies on. The compile error in the console names the file and line; if you didn't edit the plugin yourself, the fix is almost always to grab the latest version from uMod rather than trying to patch the code.

How to prevent Rust plugins not loading after every wipe

• Update Oxide before you update your plugins — never the other way round.
• Subscribe to update notifications on each plugin's uMod page so you know before a wipe, not after.
• Keep a test/staging server on the same branch to check plugin compatibility before a live wipe.
• Remove plugins you've abandoned — an unmaintained plugin is the one most likely to break on the next Rust update.
• Check oxide.plugins in console after every restart to confirm everything actually loaded.

Related Rust errors

If plugins load fine but players get kicked by anti-cheat, see Rust "Disconnected: EAC". If the server itself isn't appearing to players, check Rust server not showing in browser. For plugin ideas once things are stable, see our best Rust server plugins list and best Rust server settings.

Rust is a trademark of Facepunch Studios. Oxide/uMod and listed plugins are the property of their respective authors. ESAGAMES is an independent hosting provider, not affiliated with or endorsed by Facepunch or the uMod project.