Skip to main content

Why did your Rust plugin compile but fail to load?

An Oxide compile message tells you the source file passed the compiler. Keep reading that same startup or reload. A plugin can still fail while it starts, or appear in the plugin list while a particular feature fails.

Read one attempt from beginning to end

Save the console lines from just before you loaded the plugin through the first failure or successful load. Include the plugin name, the version and any later unload on the same attempt. If you started the whole game, keep reading until the server is ready for players. Find the current entry in the framework's loaded-plugin list and compare its version with the file you tried to install.

Oxide documents separate stages for preparing the code, loading settings, initializing and registering a plugin. An error in initialization can stop the new code from taking over even if the compiler was happy.

Follow the first missing result

Compare the status you see at the end with the first error for the plugin you just changed.

Follow the first missing result
You seeWhat to check next
A successful compile followed by a config or initialization errorRead the first error for that plugin, including the name of any settings file or missing integration. Compare that file and the named dependency with the author's requirements on a test copy.
A load message followed by an unload or an older version in the current listCheck the later console lines for the reason, then compare the active file and reported version. An earlier load line can belong to the previous attempt.
The intended version stays loaded, but its command or feature failsTry the documented player action once and watch for a new error at that timestamp. Check whether the plugin expects a permission, optional integration or particular game state for that action.

Keep a useful result even if the fix needs the author

Repeat just the changed test on an isolated server. A clear pass is the intended version staying in the list and an ordinary player getting the intended result. If settings or a dependency are still implicated, send the plugin author the first failure plus a few lines of context, exact versions and the action you tried. Take out passwords and live connection details.

In a disposable Oxide test, a plugin compiled successfully and then threw an initialization error. Oxide went back to the prior version and printed a successful load for that earlier version. The log and the current list tell you which code is running. Try the player action separately.

Sources

Analytics settings

Analytics are off.

Help improve RustSC with page counts and performance measurements. Privacy details