A Rust forced wipe happens on the first Thursday of the month, and your modded server can stay empty if the framework is still waiting for an update. The real choice is between Oxide's very large catalog and Carbon's availability, often ready the same day. Changing framework removes neither your world nor your players, and the plugins stay stored in separate folders.
Choosing between Oxide and Carbon for Rust
The first criterion is not the performance promise. It is your margin on the evening of the forced wipe. Rust updates its client and server on the first Thursday of the month, often around 8 p.m. in France. If your players arrive in the first 30 minutes, one hour of waiting already clogs the queue. If your peak starts on Friday evening, the delay matters much less.
The second criterion is the catalog. Oxide, also called uMod Rust, has years of history behind it and brings together thousands of Rust server plugins. Permissions, kits, economy, community anti-cheat, zones, loot, the building blocks are already there. Carbon starts with a shorter list. In return, it aims for lighter execution and output closer to Rust updates.
The third criterion is your dependence on plugins. Under 15 plugins, both frameworks hold up. Between 30 and 60 plugins, compatibility becomes the real issue. Beyond 80 plugins, hooks called in a loop, such as OnTick, OnEntityTakeDamage or OnPlayerInput, matter more than the logo shown at startup.
The fourth criterion is migration risk. It stays low if you keep the folders clean. Oxide stores its extensions in oxide/plugins. Carbon keeps its in carbon/plugins. The 28015 game port, the 28016 RCON port and the server.cfg file do not change because you replace the framework.
Compare Oxide and Carbon in a table
Oxide and Carbon do not fix the same problem. Oxide wins when you want a plugin that has already been proven on 500 servers. Carbon wins when the server needs to come back up quickly after a Rust update, with less leeway left to the loader. The wrong choice is to copy another server's stack without looking at your number of plugins, your wipe day and the real time of your peak.
| Criterion | Oxide, uMod Rust | Carbon Rust | Threshold that changes the decision |
|---|---|---|---|
| Availability after forced wipe | Widely used, but waiting possible after a Rust update | Often available on the forced wipe day | Beyond 1 h of waiting, a wipe-day server loses its queue |
| Plugin catalog | Thousands of plugins, lots of public feedback | Shorter catalog, variable compatibility with Oxide plugins | Starting at 30 plugins, test every dependency |
| Performance | Good if the plugins are clean | Faster loader, less overhead in several cases | Above 120 ms per server tick, measure before adding RAM |
| Community support | Forums, error histories, old snippets | Smaller community, answers often more technical | A plugin with no update for 12 months becomes a gamble |
| Migration | Separate Oxide folder | Separate Carbon folder | No map loss if you do not touch the save folder |
The reading is straightforward. Oxide reduces functional risk. Carbon reduces delay risk and can reduce CPU load. Neither one saves a badly written plugin that scans 200 000 entities every 5 seconds.
Using Oxide, uMod Rust, without getting trapped
Oxide remains the safest choice for a classic modded server. If you are looking for oxide or carbon because a kits plugin no longer starts, Oxide has a concrete advantage: someone has often already run into the same error, on the same Rust version, with the same C# plugin. Messages like Error while compiling: BetterChat.cs or Failed to call hook OnPlayerConnected come up in old discussions. They are still useful.
Its strength is the ecosystem. A PvE server with 40 plugins quickly finds its base: StackSizeController, Vanish, ZoneManager, NTeleportation, Economics, Kits. The oxide.reload PluginName command avoids a full restart when you fix a configuration. Keep it handy when 25 players are already connected and the tick is still at 20 TPS.
Oxide's limit shows up during major Rust updates. The forced wipe sometimes changes hooks, Unity classes or internal signatures. Oxide follows. Not always in the first minutes. For a monthly server that wipes at 9 p.m. with 80 players waiting, that delay becomes the number one problem.
Do not confuse catalog with quality. A uMod plugin downloaded 50,000 times can still break the tick if its configuration in oxide/config triggers backups too often or announcements every 10 seconds. If your server drops below 18 TPS with 50 players, remove first the plugins that listen to damage, loot, and movement. Adding 4 GB of RAM does not fix a saturated server thread.
Install Carbon Rust when the wipe cannot wait
Carbon is for administrators who want a fast restart after an update. On forced wipe evening, its advantage is immediate. When Oxide asks you to wait for a compatible build, Carbon is often ready the same day. On a public server with a monthly wipe, a queue, and Discord announcements at 20 h, this difference takes priority over a cosmetic plugin.
Carbon also works on execution cost. The gain does not turn a weak processor into a tournament machine, but it shows up on servers heavy with hooks. If your server tick regularly goes above 100 to 150 ms with 60 players, test Carbon in A/B on a copy. Keep the same map, the same plugins, and the same number of sleepers. Otherwise, your measurement is worthless.
The limits are still clear. The Carbon catalog is shorter. Some Oxide plugins work, others need adaptation, especially those that affect permissions, timers, or internal calls. Put Carbon plugins in carbon/plugins and keep their settings in carbon/configs. Do not mix the folders to save 5 minutes. That is how you waste an evening trying to find out why a plugin is reading an old configuration.
Carbon fits less well on the RP server that depends on 70 old uMod extensions and a private plugin compiled in 2022. It fits very well on the server that accepts a short selection, administration, permissions, stack, gather, kits, teleportation, logs. Fewer parts. Fewer surprises.
Move from Oxide to Carbon without losing the map
Changing framework does not destroy anything by itself. The Rust map, blueprints, sleeping bags, and inventories stay in the server identity backup folder. Oxide and Carbon plugins stay separate. What breaks a migration is deleting the wrong folder manually, or running two plugin systems at the same time.
- Stop the players cleanly. Send a console save before shutdown.saveWait for the save to return in the console, then stop the server. A shutdown while the world is being written can produce a partial file.
- Copy the backup folder for your server identity, the server configuration file, then the existing Oxide or Carbon folder. A useful backup often weighs between 200 MB and 3 GB depending on map size, number of entities, and abandoned bases.
- Disable the old framework before enabling the new one. Do not keep two loaders. If the console shows two framework banners at startup, you are testing a bad setup.
- Start with zero plugins, then add at most three plugins, permissions, administration, then a gameplay plugin. Restart or reload between each batch. When an error appears, you know which batch caused it.
- Recreate permissions methodically. The admin, moderator, VIP, and player groups do not always use the same format from one framework to another. A server with 200 VIPs does not migrate by guesswork.
On the Starmine panel, the Oxide/Carbon selector avoids manual upload of the framework, changing the startup target, and sorting the plugin folders for this specific case.
Choosing Oxide or Carbon for your Rust server
Choose Oxide for a stable community server, with 10 to 60 players and a long list of plugins. Keep it if your gameplay relies on well known uMod extensions, if your moderators already use Oxide commands, or if your wipe does not need to open within 15 minutes after the Steam update. For a PvE server, light RP, or modded semi vanilla, Oxide mainly avoids stupid incompatibilities.
Choose Carbon for a server that lives around wipe launch. If your Discord announcement says opening at 20 h 05 and 80 players are waiting, Carbon Rust gives you a better chance of keeping the schedule on the first Thursday of the month. Choose it also if your plugin selection fits in 15 to 35 well known extensions and if every update is first tested on a copy.
| Profile | Choice | Reason |
|---|---|---|
| Vanilla server with 5 admin plugins | Carbon | Few dependencies, fast start after wipe |
| PvE server with economy, kits, zones, and teleportation | Oxide | Larger and better documented uMod Rust catalog |
| Competitive wipe-day server, 50 to 150 players | Carbon | Availability and CPU load matter more than historical comfort |
| RP server with 70 plugins and private scripts | Oxide | Fewer surprises with old Rust server plugins |
If your server drops below 18 TPS with fewer than 40 players, do not switch frameworks at random. First, disable the plugins that log every shot, every loot, or every movement. If the tick rate goes back up, the framework was not the first culprit.
Guides
Do players need to install anything for Oxide or Carbon?
No. Oxide and Carbon run server-side. Players join with the standard Rust client, on the same game port, often 28015.
Do all my Oxide plugins work on Carbon?
No, not all of them. Many simple plugins work as is or need only minor adjustments, but those that touch permissions, advanced hooks, or internal calls need to be tested one by one.
Does changing framework delete my map or inventories?
No, the framework does not contain the map. World, player, and inventory data stay in the server identity backup, as long as you do not delete that folder.
Why does my modded server lag with 32 GB of RAM?
Rust often saturates the server thread before it runs out of memory. A plugin that processes too many events can drop TPS even with plenty of free RAM.