Update Plugins on Your Rust Server

A plugin written for one Rust build can stop loading on the next, so keeping plugins current is part of running a modded server. Your server's Plugins tab checks uMod for newer versions and swaps them in for you, and anything it can't check you replace by hand. This guide covers both, plus what to do after the monthly Rust update. For the first install, see How to install Oxide/uMod plugins on your Rust server.

Update from the Plugins tab

1. Take a backup from the Backups tab if you don't have a recent one.
2. Open the Plugins tab and switch to Installed.
3. Press Check for updates. The button reads Checking for updates while it looks, then turns into Update all with a count in brackets if anything is newer.
4. To update one plugin, press the Update button on its row. A tooltip on it shows the version you have and the version it will go to, and says the plugin loads in a few seconds with no restart.
5. To update everything that has a newer version, press Update all. It asks you to confirm first. If you don't have a recent backup it warns you and offers Go to Backups.

Each plugin is swapped for its newest version and its settings are kept. The panel says the plugin loads in a few seconds, and the Oxide docs say Oxide reloads a replaced plugin by itself. Watch the Console for it loading again. If you see no reload line, run oxide.reload <Name> on Oxide or c.reload <Name> on Carbon, with the plugin's name in place of <Name>.

The tab only knows about plugins whose file name matches a plugin on uMod. It reads the version from the top of the plugin's .cs file and compares it with the newest on uMod.

Update a plugin by hand

For a plugin that isn't on uMod, or when you want a specific version:

1. Download the new .cs file from the plugin's page. Don't rename it.
2. Open the File Manager and go to oxide/plugins (or carbon/plugins on Carbon).
3. Upload the new file over the old one.

The Oxide docs say that Oxide detects the change and reloads the plugin, so you don't need to stop the server. Check the Console for a message that the plugin loaded again.

To force a reload, or to pick up a change to the plugin's config, run this in the Console, with your plugin's name in place of Kits:

oxide.reload Kits

On Carbon, the same command is c.reload Kits.

After the monthly Rust update

Facepunch's monthly update ships a new Rust build that Oxide needs a matching build for. Once the update is out, run Settings > Reinstall, which re-applies the current framework and leaves your plugins, configs and data alone. Then do the Check for updates pass above: a plugin with a newer release is often the fix for that Rust build. How to set your Rust wipe schedule, map and blueprint wipes lists the update dates in Australian time.

If an update breaks something

1. Look in the Console for a red error that names the plugin.
2. Upload the older .cs file back into oxide/plugins if you have it, or restore your backup from the Backups tab. See How to create and restore backups.
3. Check the plugin's uMod page for a note about the Rust or Oxide version it needs.

Common problems

1. Check for updates says nothing is newer - the plugin may not be on uMod under that file name, or uMod didn't answer. The tab says which source didn't respond. Try again in a minute.
2. A red error appears after an update - the plugin may be out of date for the current Rust build. Run Settings > Reinstall, then check the plugin's uMod page.
3. A plugin needs another plugin updated first - the plugin's page lists its dependencies. Update those first.