The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Install Carbon by stopping your Rust dedicated server, downloading the matching Carbon.Windows.TARGET.zip (or the Linux package), and extracting it into the server directory that contains RustDedicated.exe. Start the server normally, then run c.version in the console. A production build is the appropriate choice for most public servers; edge and experimental builds are for administrators who accept faster changes and possible incompatibilities.
Godlike.Host offers hosted Rust servers with its own game panel, SFTP access and free DDoS protection, if you would rather not host it yourself.
What Carbon is and what the installation changes
Carbon is a server-side mod loader for Rust rather than a desktop application with an installer wizard. The project describes it as a “self-updating, lightweight, intelligent mod loader for Rust utilizing the latest C# and Harmony, fully compatible with Oxide.” You add its files to an existing Rust dedicated-server installation, and Carbon loads when that server process starts.
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
Rust Key Cards, Rust Red Key Card, Cobalt Restricted Access Cards, Rust Gift For Gamers, Blue Key... | $25.00 | Buy on Amazon |
| 2 |
|
Rust Video Game Notebook | $15.00 | Buy on Amazon |
| 3 |
|
Rust Game Props Large Furnace (S) | $14.99 | Buy on Amazon |
As an Amazon Associate I earn from qualifying purchases.
The practical consequence is that file location matters. Carbon must be extracted into the Rust server root—the directory containing RustDedicated.exe on Windows—not into a general downloads folder, a separate “mods” folder, or a second nested directory. The archive’s internal folders must remain intact.
Choose a Carbon build before downloading
Carbon documentation separates release channels from the archive’s build target. The filename pattern Carbon.Windows.TARGET.zip uses TARGET for a target such as Release or Debug; the project also offers production, edge, and experimental channels. Do not treat “Debug” in a filename as the same thing as the “edge” channel.
#1 Best Overall
- Inspired by the Rust Video Game – These cards replicate the iconic keycards found in Rust (Red, Blue, Green).
- High Quality PVC Plastic – Printed on both sides, durable and water-resistant. Not a sticker.
- Great Rust Gift Idea – Perfect for fans of Rust, whether for cosplay, loot-themed gifts, or collection.
- Wallet-Size Replica – Standard 3.375x2.125 inches, 30 mil thick—fits in any wallet.
- NOT a sticker*
| Choice | Best for | Risk and maintenance profile |
|---|---|---|
| Production | Most public Rust servers and routine administration | Carbon’s most stable channel for the official Rust public release; the sensible default when uptime and plugin compatibility matter. |
| Edge | Administrators who need newer changes before production | Changes arrive faster, so incompatibilities or behavior changes are more likely. Test on a copy before using it on a busy server. |
| Experimental | Testing, development, or deliberate evaluation of unfinished changes | Highest likelihood of breakage. Keep a verified backup and a rollback plan. |
For a normal public server, download the current production release and select the archive matching your operating system. Keep the Rust server files current as well: Carbon’s installation guidance says to verify the server files and update them every time the server boots. This reduces failures caused by a loader or plugin expecting a different Rust build.
Prepare the server safely
Do this preparation before modifying any framework files:
- Schedule downtime. Stop the Rust process cleanly. Never overwrite Carbon files while the server is running.
- Record your launch command. Keep the existing shell script, batch file, startup parameters, ports, identity, and world settings unchanged so you can start the server the same way after installation.
- Back up the server. At minimum, copy the server configuration, identity and save data, existing plugin data, and the current Rust server directory. A full copy makes it possible to remove Carbon without guessing which files changed.
- Check free disk space and permissions. The account that runs the server must be able to read the extracted files and write logs, configuration, and plugin data.
- Verify the Rust installation. Update or validate the dedicated-server files through the distribution or management method you already use before adding Carbon.
Keep the downloaded ZIP until the server has started successfully. It is useful for comparing the expected folder structure and for reinstalling the same version during troubleshooting.
Install Carbon on a self-hosted Windows server
The following procedure applies to a Windows Rust dedicated server where you can access the files directly.
- Stop Rust. Shut down the server from its console or service manager and wait until
RustDedicated.exehas exited. Confirm that no process is still holding the server files open. - Open the correct directory. Browse to the Rust dedicated-server root—the folder that contains
RustDedicated.exe. If you cannot see that executable, you are not at the installation root. - Download the matching archive. From Carbon’s official releases page, obtain the current Windows archive named in the form
Carbon.Windows.TARGET.zip. Use the production release unless you intentionally selected another channel, and choose the target appropriate to that release. - Extract in place. Extract the ZIP directly into the directory containing
RustDedicated.exe. Allow the extractor to merge the archive’s folders with the existing server folders. Do not first extract to a temporary folder and then copy only the files that look important. - Preserve the archive structure. After extraction, Carbon’s directories and files should sit alongside the existing Rust server files. A common mistake is an extra level such as
RustDedicatedServerCarbon.Windows.Release...; if the archive created that extra wrapper folder, move the contents so Carbon’s expected paths are directly under the server root. - Review overwrite prompts. If Windows reports files with the same name, stop and check that you are in the correct Rust root and that the archive matches the intended Carbon release. Do not overwrite unrelated save data or configuration simply to dismiss a prompt.
- Start Rust normally. Use the same batch file, shell command, service definition, or control-panel start action you used before installation. Carbon is loaded by the server process; it does not require a separate desktop shortcut.
- Verify from the server console. Once startup has completed far enough to accept commands, enter
c.version. A Carbon version response confirms that the loader is running. If command behavior differs in a future Carbon release, consult that installed version’s current command documentation.
How to recognize a correct extraction
The strongest check is a combination of location and behavior: the Carbon files are in the same root as RustDedicated.exe, the server reaches its usual ready state, and c.version returns Carbon information. A server that starts but gives an unknown-command response usually indicates that Carbon did not load, rather than proving that the installation succeeded.
Install Carbon on Linux
Carbon advertises quick-start scripts for Windows and Linux, but Windows paths and commands should not be copied to a Linux host. Download the Linux archive or use the current Linux quick-start instructions supplied by the Carbon project. Identify the directory that contains the Linux Rust dedicated-server executable, stop the service, and extract Carbon there while preserving its folder structure.
Rank #2
- Stop the Rust service or screen/tmux session and wait for the process to exit.
- Back up the server directory and note the account that owns the files.
- Use Carbon’s Linux-specific package or quick-start script for the selected channel.
- Extract into the Rust server root, not the parent directory and not a separate application directory.
- Restore or verify ownership and execute permissions if your extraction method changed them.
- Start the server with the existing service or shell command and inspect its console output.
- Run the Carbon version command from the server console when the process is ready; use the installed release’s Linux documentation if the command syntax has changed.
The cited Windows installation workflow does not establish a universal Linux path. Linux distributions, service managers, container layouts, and hosting panels differ, so use the OS-specific Carbon documentation rather than translating drive letters and executable names by guesswork.
Use a managed hosting control panel
Some managed Rust hosts expose Carbon as a panel option instead of requiring file access. One documented workflow uses these controls:
- Stop the server from the panel.
- Enable automatic updates if the provider offers that switch.
- Choose Carbon as the modding framework.
- Set the modding root directory to
carbon. - Save the configuration and start the server.
- Open the provider’s console and perform the Carbon version check described earlier.
These labels and paths are provider-specific, not a universal Carbon requirement. A different host may use another root-directory field, install Carbon automatically, or require support to change the framework. If the panel does not show Carbon, do not upload Windows files into an arbitrary mod folder; ask the provider whether Carbon is supported and which release channel it maintains.
Carbon, Oxide, and plugin compatibility
Carbon is designed to be compatible with Oxide plugins, and Facepunch’s Rust wiki documents Carbon’s carbon.reload hot-reload command. Compatibility is a design goal, not a guarantee that every plugin works without changes. Individual plugins may depend on particular game versions, libraries, permissions, configuration formats, or other plugins.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minuteChoose one framework
Do not install Carbon and Oxide as competing frameworks in the same server process. The documented hosting guidance states that they cannot run simultaneously and instructs owners to choose one. If you are migrating, stop the server, make a backup, remove or disable the previous framework according to its documentation, install Carbon, and test before restoring a large plugin set.
Place plugins using Carbon’s documentation
uMod documentation describes oxide/plugins as the default plugin directory for Oxide installations and says that replacing an updated .cs file loads the new version automatically in that framework. Carbon has its own framework paths and compatibility layer, so do not assume that an Oxide directory layout applies to every Carbon release. Follow the current Carbon plugin documentation or the instructions supplied by the plugin author.
Rank #3
- Acrylic Painting Pla Plastic
Test one plugin at a time
After the loader itself is verified, add a small, known-compatible plugin set and restart or hot-reload as appropriate. Read the server console for compiler errors, missing dependencies, permission failures, and API warnings. Add larger groups only after the first group works; otherwise a single incompatible plugin can make the whole migration appear broken.
Recommended Free Tools
Verify startup and diagnose a failed installation
Use this order so that file-placement problems are separated from plugin problems:
| Symptom | Likely cause | Action |
|---|---|---|
c.version is unknown |
Carbon is not loaded, the command was entered before the server console was ready, or the archive is in the wrong directory. | Stop the server, confirm the archive was extracted beside RustDedicated.exe, remove any extra nested folder, verify the release matches the OS, and start again. |
| Server starts but no Carbon files appear to work | Only selected files were copied, or the archive’s folder structure was flattened. | Restore the backup if necessary and extract the complete archive in place. Do not copy individual DLLs or folders by appearance alone. |
| Startup reports file or assembly errors | Rust and Carbon are out of sync, a partial update occurred, or a plugin targets an incompatible API. | Verify and update Rust files, reinstall the complete matching Carbon archive, then start with plugins disabled or removed from the active Carbon path to isolate the cause. |
| Existing Oxide plugins fail to load | A plugin has an unmet dependency, uses an API Carbon does not expose identically, or was placed in an Oxide-only path. | Read that plugin’s current requirements, move it to the path Carbon documents, install dependencies, and test it alone before reporting a framework-wide failure. |
| Two frameworks report conflicts | Carbon and Oxide are both enabled. | Stop the server and select one framework. Keep a backup of the disabled framework’s data so migration can be reversed cleanly. |
| Panel installation does not provide a Carbon option | The host does not support Carbon or uses a different control-panel workflow. | Check the host’s supported-framework list and ask for its Carbon-specific root path and update policy. Do not assume a generic mod toggle is equivalent. |
| Linux service will not start after extraction | Wrong archive, incorrect ownership, missing execute permission, or a path copied from a Windows guide. | Use the Linux package and instructions, restore ownership and permissions for the service account, and inspect the service log for the first reported error. |
Keep Carbon and Rust updated without breaking the server
Update in a controlled order
- Announce maintenance and stop the server cleanly.
- Back up the complete server state, including saves, configuration, plugin data, and the current Carbon files.
- Verify the Rust server files and apply the Rust update required by your distribution or host.
- Read the Carbon release notes and select the production channel unless you have a specific reason to test edge or experimental code.
- Replace Carbon using the complete matching archive or the provider’s supported updater; preserve the directory structure.
- Start without changing unrelated launch parameters.
- Check the console and confirm the Carbon version before re-enabling or updating plugins.
- Test core gameplay, permissions, scheduled tasks, and the most important plugins before declaring the maintenance complete.
Why automatic updating still needs supervision
Carbon is described as self-updating, and some managed hosts expose automatic updates. Automation reduces manual file work but does not remove the need for backups, release-channel decisions, or plugin testing. A Rust update can change APIs or behavior even when Carbon itself updates successfully. Keep at least one known-good Carbon archive and a dated server backup so you can return to the previous state if a new combination fails.
Self-hosted versus managed Carbon installation
| Decision point | Self-hosted server | Managed hosting |
|---|---|---|
| File and launch control | Direct access to the Rust root, archives, permissions, and startup command. | Depends on the host; file access and launch parameters may be restricted. |
| Carbon selection | You download and extract the chosen release yourself. | The panel may provide a Carbon framework selector or automatic installer. |
| Updates | You control timing and can keep a local rollback archive. | Automatic updates may be available, but the provider controls supported channels and timing. |
| Console verification | Use the server console attached to your service, shell, or batch process. | Use the panel console if the provider exposes one; otherwise request confirmation from support. |
| Operating-system responsibility | You must use the correct Windows or Linux archive and maintain permissions. | The provider normally handles the host OS, but you still need to follow its Carbon-specific path and policy. |
| Backups and restore | You choose the backup tool, schedule, retention, and restore test. | Backup features vary by provider; verify what is included and how to download or restore it. |
| Support | You troubleshoot paths, permissions, Rust updates, and plugin dependencies yourself. | Provider support may handle installation issues, but plugin-specific problems remain your responsibility unless the plan says otherwise. |
Choose self-hosting when you need complete control over files and launch commands and are comfortable maintaining the OS. Choose a managed service when a supported Carbon option, panel console, automatic updates, and provider assistance are more valuable than direct control. The existence of one host’s Carbon workflow does not establish that every host offers the same controls.
Remove Carbon or roll back safely
If a release causes problems, do not delete random DLLs while the server is running. Stop the process, preserve logs, and restore the full pre-installation or pre-update backup. If you intend to return to Oxide, follow that framework’s migration instructions and keep Carbon disabled; never leave both frameworks active while testing. Start the restored server with its original command, verify that the game reaches its normal ready state, and then reintroduce plugins in small groups.
For a less drastic rollback, reinstall the previously known-good Carbon archive that matches the current Rust server version, then test without plugins. If that combination works, add plugins one at a time and record which change reintroduces the failure. This gives you a reproducible rollback path instead of relying on an untracked mixture of old and new files.
Quick Recap
Installation checklist
- Rust server stopped before files were changed.
- Current Rust files verified and updated.
- Production, edge, or experimental channel selected deliberately.
- Archive matches the operating system and intended build target.
- Complete archive extracted into the directory containing
RustDedicated.exeon Windows, or the documented Linux server root. - Archive folder structure preserved with no extra nesting level.
- Original launch command retained.
- Carbon version command returns a response from the server console.
- Only one modding framework is enabled.
- Plugins tested against Carbon’s current paths and each plugin’s own requirements.
- Backups and a known-good rollback archive retained.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
