Update Rust Server & Oxide/Carbon Without Losing Plugins

Updated 6 November 2026 · Standard formula, shown below

Updating a Rust server while keeping Oxide (uMod) or Carbon modding frameworks and their plugins intact is a routine but delicate operation. This guide walks you through the process step by step, covering both frameworks, so you can apply official updates without wiping out your plugin configurations, data files, or custom settings.

What You’ll Need

Access to your server’s file system (FTP, SFTP, or a hosting control panel like Pterodactyl or TCAdmin).
Your server’s current modding framework: Oxide (uMod) or Carbon.
A backup tool or the ability to copy folders on your server.
Basic familiarity with stopping and starting your server.

Step-by-Step

Stop the server. Always shut down the Rust server completely before touching any files. This prevents file corruption and ensures all plugin data is written to disk.
Back up your server folder. Copy the entire server directory, or at minimum the server and oxide (or carbon) folders. If you’re using a hosting panel, use its snapshot or backup feature. This is your safety net.
Identify your current framework version. Look for the Oxide.Core.dll in the RustDedicated_Data/Managed folder (for Oxide) or the carbon folder (for Carbon). Note the version you have.
Update the game server. Use your hosting panel’s update button (usually “Update” or “Reinstall”) or run the SteamCMD command to fetch the latest Rust dedicated server files. Example: steamcmd +login anonymous +app_update 258550 +quit. This will overwrite the game files but should not touch your server folder or plugin folders if they are outside the game directory (which is the default on most hosts).
Update the modding framework. Download the latest Oxide (uMod) or Carbon release from the official source (oxidemod.org for Oxide, carbonmod.gg for Carbon). Extract the contents.
For Oxide: Copy the contents of the extracted Oxide folder into your server’s root directory, overwriting existing files when prompted. This updates the core DLLs but leaves your oxide/plugins and oxide/config folders untouched.
For Carbon: Copy the contents of the extracted carbon folder into your server’s root directory, overwriting existing files. Carbon’s plugin and config folders are typically inside carbon/plugins and carbon/config, so they remain intact.
Delete old framework files (optional but recommended). If the update includes a major version change, remove the old framework DLLs that are no longer needed. For Oxide, check for any Oxide.*.dll files that are not in the new release and delete them. For Carbon, follow the same logic for Carbon.*.dll.
Start the server. Launch the server and watch the console output. The framework should load, and you should see messages like “Loaded plugin …” for each of your plugins.
Verify plugin data. Once the server is up, run a command like oxide.plugins (for Oxide) or carbon.plugins (for Carbon) in the console to list all loaded plugins. Check a few plugin configs to ensure they are still intact.

Common Mistakes

Updating while the server is running. This can cause file locks and corruption. Always stop the server first.
Overwriting the entire server folder. Some hosting panels have a “Reinstall” option that wipes everything. Use it only if you have a full backup and are prepared to reinstall plugins.
Forgetting to update the framework. A new Rust game version may require a newer Oxide/Carbon. If you only update the game, plugins may fail to load.
Copying plugin files into the wrong folder. Plugins go in oxide/plugins or carbon/plugins, not the root or Managed folder.
Ignoring version compatibility. Some plugins may not work with a new framework version. Check the plugin’s page for updates.

Tips

Keep a staging server. Test the update on a separate server instance before applying to your live server.
Read the changelogs. Both Oxide and Carbon publish release notes. Check for any breaking changes or migration steps.
Backup before every update. Even if updates usually go smoothly, a backup is your only way to roll back.
Use a scheduled update routine. Set a reminder to check for updates weekly, as Rust updates frequently.
Keep your plugins updated. After a framework update, check if your plugins have new versions. Outdated plugins are a common cause of errors.

Troubleshooting

Plugins not loading after update. First, check the server console for error messages. Often it’s a missing dependency or a plugin that needs a newer version. Update the plugin or remove it temporarily.
Server crashes on startup. This is usually due to an incompatible framework version. Revert to the previous framework backup and wait for a compatible update.
Plugin configs reset. If your configs appear empty, check if the plugin’s config file was overwritten. Restore from your backup. This can happen if the plugin was reinstalled incorrectly.
Oxide/Carbon not detected. Ensure you copied the framework files to the correct directory. For Oxide, the Oxide.Core.dll must be in RustDedicated_Data/Managed. For Carbon, the carbon folder must be in the root.
Data files corrupted. If plugin data (like player data) is corrupted, restore from your backup. Always back up before updating.

Frequently Asked Questions

Will updating reset my plugin configurations?

No, if you only update the game and framework files, your plugin configs in oxide/config or carbon/config remain untouched. However, some plugins may automatically regenerate configs if they detect a version mismatch, so always back up.

Can I update the game without updating Oxide/Carbon?

Technically yes, but the framework may break if it’s not compatible with the new game version. It’s best to update both together.

How do I know which framework version I need?

Check the official Oxide or Carbon website after a Rust update. They usually release a compatible version within hours. You can also look at the release notes.

What if a plugin doesn’t work after the update?

First, check if the plugin has an update. If not, try removing it and re-adding it. If it still fails, it may be abandoned; consider an alternative.

Do I need to recompile plugins after a framework update?

No, plugins are compiled at runtime. You just need the plugin files (.cs for Oxide, .cs or .dll for Carbon) in the correct folder.

Can I use the same backup for both Oxide and Carbon?

No, they are different frameworks. You should back up the entire server folder, which includes the framework-specific folders.

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.