Fix Rust Oxide / uMod Plugins Not Loading
Plugin failed to compilenot loadingMissing dependencyAfter 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.
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.
Update Rust first, then update Oxide to match, then start the server. Updating them out of order is the #1 cause of "plugins not loading" after a wipe.
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.
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.
Rust hosting that keeps up
Our Rust hosting handles updates and Oxide on fast CPUs and NVMe, protected by multi-Tbps Anti-DDoS in Frankfurt.
Frequently asked questions
Why do my Rust plugins break after every wipe?
Forced Rust updates often change the API. Oxide and each plugin must be updated to match the new build. Update Oxide first, then refresh outdated plugins.
Where do Rust Oxide plugins go?
As .cs files in the oxide/plugins/ folder. Their config files are created automatically in oxide/config/ on first load.
How do I reload a single plugin?
Run oxide.reload PluginName in the server console — no full restart needed. Oxide also auto-reloads when a plugin file changes.
Related articles
Fix AMX Mod X "Couldn't load library" / Plugin Failed in CS 1.6
AMXX plugin stuck on "bad load", "couldn't load library" or "failed"? The real causes and the exact fix.
Read fix Game ServersFix FiveM "Couldn't load resource" / Failed to Start
A FiveM resource won't start or throws "couldn't load resource"? Here are the real causes and fixes.
Read fix Game ServersHow to Read a Minecraft Server Crash Report (and Fix It)
How to read a Minecraft crash report, find the mod/plugin at fault, and fix the most common crashes.
Read fix
