Rust Plugin Updates After Wipe Guide 2026

Published on | Updated

How to get Oxide plugins running again after Rust's monthly forced wipe: the update order, matching the Oxide build, finding broken plugins, and which plugin data to reset for the new map.

Rust server plugins

Your plugins survive a wipe. The .cs files in oxide/plugins, their configs and their data stay where they are when you delete a map. What breaks them is the game update that comes with the monthly forced wipe: Facepunch changes the server build, Oxide has to ship a build for it, and a plugin that uses game code Facepunch changed stops compiling until its author fixes it.

So wipe night is two jobs. First get Oxide and your plugins running on the new build, then decide which plugin data to reset for the new map. This guide covers both for Oxide (uMod), checked against the Oxide docs, Facepunch's wiki and Oxide's release notes on 25 October 2026. Carbon notes are near the end.

Update night and wipe day are not the same thing

What happensNew Rust build?New Oxide build?Plugin data to reset?
Monthly update with the forced wipeYesYesYour choice, per plugin
Your own wipe between updatesNoNoYour choice, per plugin
Hotfix or event updateYesCheck Oxide's release listNo, the map stays

The monthly update lands on the first Thursday of the month at 19:00 London time, which is 19:00 UTC in winter and 18:00 UTC in summer. Facepunch's wipe timer page gives that as the default and says it "aligns with force wipes". The next one is expected on Thursday 5 November 2026; our Halloween update checklist has that date with the time in eight zones.

If you wipe weekly or every two weeks on your own schedule, the wipes between monthly updates do not change the build. Oxide and your plugins keep working; only the data questions further down apply. Hotfixes are the other way around: a new build, no new map. In October 2026 Oxide shipped builds for Rust hotfixes on the 2nd, 8th, 9th, 12th and 13th, so check its release list whenever your panel shows a game update.

Why Oxide has to match the Rust build

Oxide is not a plugin that sits on top of the game. Its download contains its own copies of Rust server files: the Linux archive of build 2.0.7839 puts Assembly-CSharp.dll and other Facepunch DLLs into RustDedicated_Data/Managed, next to Oxide's own files. The patch releases name the Rust build they were made for in their notes, for example 2.0.7783: "Patch for October 1st Rust update (2634.289.1)".

Oxide's install guide puts it plainly: "For every server update by Facepunch, there is an Oxide update. Don't mismatch version of Oxide and version of servers." Updating the game puts the vanilla files back, which is why Facepunch's server guide warns: "If you run SteamCMD in your startup script, your files will be reverted back to vanilla."

Plugins are C# source files that the server compiles itself; Oxide's plugin guide says "The server will automatically compile these files when they're placed in the correct directory." When Facepunch renames or changes something a plugin calls, that compile fails, and only a plugin update fixes it.

Before update night

  1. Write down what you run. oxide.plugins lists every plugin "including ones that failed to load" with name, version, author, hook time and file name (plugin commands). Paste the output into a text file. After the update you compare against it.
  2. Back up. Copy the oxide folder (plugins, config, data, lang) together with the server's identity folder. Our backup and restore guide lists the files and how to take a clean copy.
  3. Test plugin updates early. If a plugin author has already released a new version, try it on a test server during the month rather than on wipe night. Our staging branch post covers test servers and what the staging branch can and cannot do for an Oxide server.
  4. Check how your server updates. If your start script runs SteamCMD on every boot, every restart puts the vanilla files back over Oxide. Update by hand or from the panel instead.
  5. Decide on plugin data now. Which data you keep and which you reset is a server rule, so settle it before the night and announce it with the wipe. The section below helps.

Update night, step by step

  1. Save and stop. Run server.save, then stop the server from the panel or with quit.
  2. Back up the identity and oxide folders, even if you did so this morning.
  3. Update Rust from your panel or with SteamCMD, app 258550. Oxide's docs ask for the -beta public switch and advise against the release branch, which they say is not always in sync with public.
  4. Install the Oxide build for the new Rust build. On the releases page, take the newest release that is not marked as a pre-release and check that its notes name today's update. Download Oxide.Rust-linux.zip for Linux or Oxide.Rust.zip for Windows. The archive already contains the RustDedicated_Data/Managed folders, so extract it in the server's root folder (where RustDedicated_Data sits) and let it overwrite what is there. For the 2026 monthly updates Oxide published between 12 and 38 minutes before 19:00 London time. For the Halloween update on 22 October it came about an hour after the announced 17:00 UTC release (2.0.7839 at 18:02 UTC). If the build is not there yet, wait. Do not put the previous Oxide build back on top.
  5. Start and confirm the version. oxide.version "Displays the Oxide version and branch" (miscellaneous commands).
  6. Find what failed. Run oxide.plugins again and compare it with your list. Plugins that failed show the reason; the details are in oxide/logs.
  7. Update the broken plugins. Download the new .cs file and upload it over the old one in oxide/plugins. "Oxide will automatically detect the change and reload the plugin," say the Oxide docs, so no restart is needed. No fix yet? Unload optional plugins with oxide.unload PluginName. That lasts until the next restart, because Oxide loads every plugin it finds in oxide/plugins, so move the .cs file out of the folder if it has to stay off. If the plugin enforces your rules, such as team limits, permissions or the economy, keep the server closed until it works.
  8. Check configs. A new plugin version can add settings. Oxide's config guide warns that some plugins save their config when they unload, so an edit followed by oxide.reload can be overwritten. The safe order is oxide.unload PluginName, edit the file, oxide.load PluginName.
  9. Join and test with an updated game client: the plugins your rules depend on first, then everything players use on day one. Then open and announce it.

Plugin data after a wipe

Plugin data lives in oxide/data. Oxide's data files guide says "Data files do not follow any standard naming convention", so look for files or subfolders named after the plugin. The same guide lists "Group and permission data" among the important files there, and Oxide's permissions guide says it keeps permissions in the oxide.users and oxide.groups files. That is why you never empty oxide/data as a whole on wipe day: your groups, VIP ranks and permissions would go with it.

How plugins notice a wipe

Oxide has a hook called OnNewSave. The game code it sits in builds the save file name for the current map and calls the hook when that file does not exist, which is what happens on the first start after a wipe. A plugin can use it to clear its own data. Whether yours does is up to its author, so check the plugin's page or look for a wipe option in its config before you delete anything by hand.

What to keep and what to reset

Kind of dataExamplesUsual choice
Positions on the mapHomes, warps, zones, custom spawn pointsReset after a new seed or map, because the coordinates belong to the old map. Keep them only if the map file stays the same
Per-wipe progressKit cooldowns and usage, wipe stats, leaderboardsReset if your rules are per wipe
Money and pointsEconomy balances, shop points, rewardsYour server's rule. Announce it before the wipe
Permissions and groupsoxide.users, oxide.groups, VIP groupsKeep

To reset one plugin: run oxide.unload PluginName, move its data file or folder out of oxide/data into your backup folder, and run oxide.load PluginName so it starts without the old data. Move rather than delete, so you can put it back if the plugin misbehaves.

Two more points from the Oxide docs. If a data file is corrupted, restore it from a backup or, as a last resort, delete it so the plugin regenerates it, which loses that data. And "Sometimes when a plugin updates, its data file format may change. In rare cases, this might require converting or resetting the data file." Read a plugin's update notes before you put a new version on the live server on wipe night.

For the map side of the wipe, deleting the map and save files and the blueprint question, see our wipe day checklist.

When it goes wrong

  • No Oxide messages in the console at all. The game update put the vanilla files back. Install the Oxide build made for the new Rust build.
  • Oxide is gone again after every restart. Something runs SteamCMD on boot. Update from the panel or by hand, then reinstall Oxide.
  • Updated players cannot join after you installed Oxide. Check that you installed the build for the new Rust version, not the previous one. An old Oxide build carries server files from the old Rust build.
  • One plugin fails to compile. That plugin uses game code that changed. Wait for its author, then upload the new version, or unload it until then.
  • A plugin loads but behaves strangely. Compare its config and data with your backup. New settings with default values, or a changed data format, are the usual causes.

Carbon

Our Rust plans are set up for Oxide. Carbon support on them is not confirmed, so if you want to run Carbon, ask in live chat first.

For reference, Carbon works differently on wipe night. It patches the game at startup instead of shipping patched DLLs: "With Carbon, your RustDedicated_Data/Managed folder will always be untouched from Facepunch's shipped configuration," says its porting guide. Its update docs say the production build for the wipe update comes out "1 hour before the actual Rust server update drops", and that with self updating on, Carbon "only self updates if you update to the latest Rust version". Its commands are c.version, c.plugins, c.reload and c.unload (command list). Carbon keeps the Oxide folder layout under carbon/, except that plugin configs live in configs instead of config, according to the same guide. Its optional AutoWipe module, off by default, can delete data files such as carbon/data/myfile.json after a wipe. Our Carbon vs Oxide comparison covers the rest.

Plugins on our Rust servers

Our Rust server hosting plans are set up for Oxide. You upload .cs files into oxide/plugins with the panel's file manager or over SFTP, and edit configs the same way. Every plan has backup slots in the panel, 2 on STONE and METAL and 3 on SULFUR and up, so make one before update night. STONE starts at €10.20 a month with 8 GB RAM.

Support is online from 08:00 to 20:00 UTC every day, by live chat, Discord and email. The monthly update at 19:00 London time falls inside those hours all year.

FAQ

Do I need to reinstall Rust plugins after a wipe? No. A wipe removes the map and save files; the .cs files in oxide/plugins and their configs stay. What you need after the monthly forced wipe is the Oxide build for the new Rust build, plus updates for any plugin that fails to compile on it.

Why did all my plugins stop after the Rust update? Almost always because Oxide is missing or does not match. The game update restores Facepunch's own files, so install the Oxide release whose notes name the new Rust update.

Should I delete the oxide/data folder on wipe day? No. It also holds Oxide's permission data (oxide.users and oxide.groups). Reset plugins one at a time by moving their own data files out.

How long after a Rust update does Oxide release a build? There is no fixed time. In 2026 Oxide's builds for the monthly updates came 12 to 38 minutes before the 19:00 London time release, and the build for the Halloween update on 22 October came about an hour after it.