Guide · Wipe day
How to update Oxide & Carbon plugins after a Rust force wipe
Rust's monthly force wipe lands on the first Thursday and usually breaks a few plugins. Here's the fastest way to scan your Oxide (uMod) or Carbon plugins, find what's outdated, update from uMod, Codefling, and Lone.Design, and reload over RCON — without juggling WinSCP tabs.
TL;DR
Connect over SFTP/FTPS → scan oxide/plugins or carbon/plugins → review outdated plugins vs marketplace latest → one-click update → reload with oxide.reload / carbon.reload. Rust Server Admin does all of it in one desktop app or the web console.
Step-by-step: update your plugins after the wipe
- 1
Connect to your Rust server over SFTP or FTPS
Add your server's SFTP/FTPS host, port, username, and password. This works with any host that exposes SFTP and RCON — Pterodactyl, TCAdmin, a managed game host, or a self-hosted box on Docker, LGSM, or bare metal.
- 2
Scan the oxide/plugins or carbon/plugins folder
Point the scan at your plugins directory — oxide/plugins for Oxide (uMod) servers or carbon/plugins for Carbon. Rust Server Admin reads every .cs plugin and records its title, author, and installed version.
- 3
See which plugins are outdated
The scan compares each installed version against the latest release on uMod, Codefling, and Lone.Design, so you get a clear list of outdated plugins that broke or fell behind during the Rust update.
- 4
Apply one-click updates
For each outdated plugin, download the newest version from its marketplace and upload it to the server over SFTP/FTPS in one step — no manual WinSCP or FileZilla transfers.
- 5
Reload plugins over RCON
Reload the updated plugins live with oxide.reload <PluginName> or carbon.reload <PluginName> from the built-in WebRCON console, so changes take effect without a full server restart.
- 6
Verify in the console
Run oxide.plugins (or the Carbon equivalent) in RCON to confirm every plugin loaded on its new version and watch the console for any compile errors before players join.
Oxide vs Carbon plugin paths
The workflow is identical for both modding frameworks — only the folder differs. Oxide (uMod) servers load plugins from oxide/plugins; Carbon servers use carbon/plugins. On a managed host the full path is often /home/container/oxide/plugins or /home/container/carbon/plugins. Reloads use oxide.reload on Oxide and carbon.reload on Carbon.
Wipe-day checklist
- Update Oxide/uMod or Carbon to the build that matches the new Rust version.
- Scan the server and note every plugin flagged as outdated.
- Update paid plugins from Codefling and Lone.Design, and free ones from uMod.
- Reload each updated plugin over RCON and watch for compile errors.
- Confirm player-facing systems (kits, shop, stats) work before you announce the server is up.
FAQ
- Why do Oxide and Carbon plugins break after a Rust force wipe?
- Facepunch ships a forced update on the first Thursday of each month. That update often changes the game's API, so Oxide/Carbon and any plugins built against the old API can fail to compile until their authors publish new versions. Updating your modding framework and plugins right after the wipe is what gets the server healthy again.
- Where is the Rust plugins folder?
- On Oxide (uMod) servers, plugins live in oxide/plugins. On Carbon servers, they live in carbon/plugins. On many managed hosts the full path looks like /home/container/oxide/plugins or /home/container/carbon/plugins.
- Do I have to update every plugin after a wipe?
- Only the ones that changed. Scanning shows installed version versus marketplace latest, so you can update just the outdated plugins instead of re-uploading everything.
Do the whole thing in one tool
Rust Server Admin scans your Oxide and Carbon plugins over SFTP, checks uMod, Codefling, and Lone.Design for updates, and gives you a live RCON console — on desktop and the web.