How to Install Oxide Plugins on a Rust Server (uMod Guide)

Install an Oxide/uMod Rust plugin by confirming the framework is running, uploading the plugin’s original .cs file to the active plugins directory, checking the load result, configuring its JSON file, and granting only the permissions it documents. A normal installation watches the directory and compiles the file automatically, so you usually do not need to shut down the server.

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.

This guide covers self-hosted servers, FTP and control-panel hosts, and uMod Agent installations, including updates and the common reasons a plugin fails to load.

#	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.

1. Confirm that Oxide or uMod is installed

A Rust plugin cannot run on a vanilla server. Oxide/uMod supplies the plugin loader, compiler, hooks and permission system that a .cs file needs. The server provider must support Oxide 2.0 or newer; if the framework is missing or incompatible, the file will not load or do anything.

Check a running server

1. Start the Rust server.
2. Open the server console, or use in-game chat with the required administrative access.
3. Run oxide.version.
4. Confirm that the command returns an Oxide/uMod version instead of an unknown-command error.

If oxide.version fails, stop here. Installing a plugin before fixing the framework only creates confusing file and compilation errors. Ask the host whether Oxide/uMod is enabled and supported for the server’s current Rust build, or install the framework before proceeding.

#1 Best Overall

Rust Key Cards, Rust Red Key Card, Cobalt Restricted Access Cards, Rust Gift For Gamers, Blue Key Card, Green Key Card (ALL THREE)

• 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*

$25.00

Buy on Amazon

Install with uMod Agent

When you are setting up a new server through uMod Agent, the documented Rust installation command is:

umod install rust -P

You can specify an installation directory when needed:

umod install rust -P --dir="/path/to/dir"

Keep the Agent installation current with:

umod update -P

Existing Oxide plugins are documented as compatible with uMod, but each plugin still has its own Rust and framework requirements.

2. Download the correct plugin file

Use the official uMod/Oxide plugin listing or a reputable release page maintained by the plugin developer. Download the C# source file, not a web page, screenshot, readme, or an archive that you have not extracted.

Preserve the filename and extension

Keep the original filename and the .cs extension exactly as supplied. Do not add a second extension such as .cs.txt, rename the class file for convenience, or edit its name to match a server nickname. Oxide uses the expected plugin file identity when it loads and generates related configuration and data files.

Read the plugin page before uploading

Compatibility is plugin-specific; there is no single matrix that guarantees every plugin works with every Rust build. Before installation, note:

• Supported Rust, Oxide and uMod versions.
• Required companion or dependency plugins.
• Registered permissions and the commands used to grant them.
• Whether the plugin creates a configuration or data file, and which keys it accepts.
• License terms and any restrictions on redistribution.
• Release notes describing breaking changes or migration steps.

Download dependencies as separate original .cs files and install them in the same way. A dependent plugin may compile only after its required companion is present.

3. Upload the file to the active plugins directory

Standard Oxide path

For a conventional Oxide installation, the default directory is:

oxide/plugins

On a remote host, open that folder with FTP, the provider’s file manager, or its control panel. Upload the unchanged .cs file directly into the folder. If you downloaded a ZIP, extract it first; the server will not compile a source file that remains inside the archive.

uMod Agent path

Some uMod Agent and side-loading workflows use:

umod/plugins

Follow the path shown by that installation rather than creating a second plugins folder. Uploading to an inactive or similarly named directory is a common reason for seeing no load message.

What happens after upload

With Oxide/uMod already running, the framework watches the plugins directory, compiles the source and loads it automatically. A routine install or replacement therefore does not require a full server shutdown. Allow a short interval for compilation, then inspect the console. If your host batches file changes or pauses the server while writing files, wait until the transfer is complete before judging the result.

4. Verify that the plugin loaded

Read the server console

A successful load normally produces a plugin load message. A compiler failure instead identifies an error and usually includes a line number. Save or copy that text before changing files; the first error is often the useful one.

List loaded plugins

Use the plugin-list command documented by uMod:

umod.plugins

Check that the plugin name appears in the returned list. A name in the file manager is not proof of a successful compile.

Exercise the feature

If the plugin adds a chat command, console command or game feature, test it with an administrator account. Use the permission documented on the plugin page; an unprivileged test can look like a loading failure when the plugin is actually working but access is denied.

Inspect logs when the result is unclear

Look in the Oxide logs directory:

oxide/logs

Compare the timestamp with your upload and search for the plugin name, compiler errors, missing dependencies and JSON parsing errors. Do not repeatedly reload a plugin while ignoring the original error; fix the reported cause first.

5. Configure the plugin safely

Configurable plugins commonly create a JSON file in:

Rank #2

Rust Video Game Notebook

$15.00

Buy on Amazon

oxide/config

The filename normally matches the plugin name, for example oxide/config/PluginName.json. The file may not appear until the first successful load. A plugin with no configurable settings may never create one.

Edit valid JSON only

Preserve the filename and use valid JSON syntax. Typical mistakes include a missing comma, an extra trailing comma, unmatched braces, smart quotation marks, or changing a Boolean or number into an unsupported text value. Keep a backup before making edits, especially when the plugin stores nested settings.

Apply changes with a reload

After saving the configuration, reload the matching plugin from the server console:

oxide.reload PluginName

Replace PluginName with the plugin’s documented name, not necessarily the display label shown in a menu. Watch the console for a successful reload or a JSON error. If a configuration was expected but is absent, check the load result and oxide/logs rather than creating a file with a guessed name.

6. Grant permissions deliberately

Oxide or the plugin registers permission strings. The default groups are generally admin and default; who belongs to the administrator group depends on the server owner’s setup. Always copy the exact permission string from the plugin’s documentation, including capitalization and punctuation.

Useful permission commands

Run these in the server console, using a player name or Steam ID where indicated:

oxide.grant user <name-or-steam-id> <permission>
oxide.grant group <group> <permission>
oxide.revoke user <name-or-steam-id> <permission>
oxide.show perms
oxide.show user <name-or-steam-id>

Use a user grant for a one-off exception. For recurring roles, grant the permission to a group and manage membership separately. Avoid broad wildcard grants unless you understand every permission they cover; a wildcard can give a player access to unrelated plugin features.

Diagnose a denied command

1. Copy the permission string from the plugin page instead of typing an approximation.
2. Run oxide.show perms to confirm that the plugin registered it.
3. Grant it to the intended user or group.
4. Run oxide.show user <name-or-steam-id> to inspect that player’s effective permissions.
5. Retry the feature after the grant. Reloading is normally unnecessary for a permission change unless the plugin’s instructions say otherwise.

7. Update, roll back or remove a plugin

Prepare an update

Before replacing a working version, back up:

• The current .cs file.
• The matching file in oxide/config, if one exists.
• Any plugin data files created by the plugin.
• Notes about custom permissions and dependencies.

Read the new release notes and check its Rust/Oxide compatibility. Configuration keys can change between releases, and a new version may require a companion plugin or a migration step.

Replace the file

Overwrite the old source with the new original .cs file in the active plugins directory. Oxide detects the replacement and reloads the plugin automatically. Watch the console and test the feature rather than assuming that a successful file transfer means a successful update.

Recover from a bad update

If behavior changes unexpectedly or compilation fails, restore the backed-up source and matching configuration/data files. Then reload the plugin and consult the release notes and compatibility guidance. Restoring only the source while leaving incompatible new configuration values can reproduce the problem.

Unload or remove

For a temporary stop, use the load, reload and unload operations documented by your Oxide/uMod command set. To remove a plugin permanently, unload it if necessary and delete its .cs file from the active plugins directory. Decide separately whether to archive or delete its configuration and data; keeping backups makes a later reinstall safer.

8. Troubleshoot the common failure modes

9. Choose an installation workflow

The plugin itself is the same source file, but the administration experience differs by hosting method.

Regardless of workflow, compatibility information comes from the plugin page and release notes, while access control comes from the plugin’s registered permissions and your server’s groups. Convenience does not remove the need to read compiler output or preserve rollback files.

10. A repeatable installation checklist

1. Start the server and confirm oxide.version works.
2. Read the plugin’s supported versions, dependencies, permissions, configuration notes and license.
3. Download the original .cs file and preserve its filename and extension.
4. Upload it to the active oxide/plugins directory, or the documented umod/plugins directory for that Agent installation.
5. Wait for automatic compilation and inspect the console.
6. Run umod.plugins and test the feature with an administrator account.
7. Inspect oxide/logs immediately if the plugin is missing or reports an error.
8. Edit the matching JSON file in oxide/config, keep the syntax valid, and run oxide.reload PluginName.
9. Grant only the exact documented permission to the required user or group.
10. For updates, back up source, configuration and data, then recheck dependencies and release notes after replacement.

11. Practical checks that prevent repeat failures

Separate transfer problems from compiler problems

First prove that the server can see the file. Confirm the upload completed, the file is not zero bytes, and the name ends in exactly .cs. Then check the console for compilation. A missing load message usually points to a path or filename problem; a named line number points to source, dependency, or version compatibility. Treat those as different investigations instead of repeatedly uploading the same file.

Keep an installation record

For each plugin, record its source URL, version or release date, required companions, permission strings, configuration changes, and the directory where it was installed. This is especially useful with uMod Agent because side-loaded plugins are outside the Agent lock file. A short record lets you reproduce the setup after a host migration and tells you which files must be restored during rollback.

Make changes in a safe order

1. Back up the current source and configuration/data.
2. Install or update dependencies before the plugin that consumes them.
3. Upload one plugin at a time so the resulting console message is attributable.
4. Wait for automatic compilation and test the feature before changing permissions or settings.
5. Edit JSON, reload the named plugin, and verify the setting in-game.

Changing several plugins and configuration files at once makes a later error difficult to isolate. A full restart is not the normal requirement for installation, but follow your host’s procedure if it pauses or stages file transfers.

Rank #3

Rust Game Props Large Furnace (S)

• Acrylic Painting Pla Plastic

$14.99

Buy on Amazon

Understand what a successful load does not prove

A plugin listed by umod.plugins has compiled and loaded, but that does not prove every player can use it, that its configuration is appropriate, or that its dependencies will remain compatible after a Rust update. Test an administrator-only command, then test the intended regular-player path with the exact permissions you plan to grant. Keep broad permissions off until the feature has been verified.

12. Frequently asked installation questions

Can I install a plugin without restarting the Rust server? Yes. Oxide detects changes in the active plugins directory, compiles the file, and loads or reloads it while the server is running. Wait for the transfer to finish and watch the console. A host that batches writes may delay detection, but a routine install does not require a full shutdown.

Where exactly do I put a .cs file? Use oxide/plugins for a normal Oxide installation. An installation managed by uMod Agent or a side-loading workflow may use umod/plugins. Do not create a second folder based on a guess; identify the directory used by the running framework.

Why does my Rust plugin not load after upload? The usual causes are an unsupported or missing framework, the wrong plugins directory, a ZIP that was not extracted, a changed extension such as .cs.txt, a compiler error, or a missing dependency. Check oxide.version, the console, umod.plugins, and oxide/logs in that order.

How do I reload an Oxide plugin? Use oxide.reload PluginName in the server console after editing its configuration or when the plugin documentation requests a reload. Use the plugin’s actual name, not a shortened menu label, and watch for a successful reload or JSON error.

Why was no JSON configuration created? The plugin may have no configurable options, or its first load may have failed. Confirm the plugin loaded successfully, read its documentation, and inspect oxide/logs. Do not invent a filename; configuration names normally match the plugin name.

Do I need to grant permissions to an administrator? Not necessarily. The server’s group setup may already give an administrator access, but the plugin’s own permission still controls its features. Check the documented string and use oxide.show user to see effective permissions. Grant only what the intended user or group needs.

Are uMod and older Oxide plugins interchangeable? Existing Oxide plugins are documented as compatible with uMod, but compatibility remains plugin-specific. Check the plugin page for supported Rust and framework versions, dependencies, and release notes before installing.

What should I back up before an update? Save the current .cs file, its matching configuration, any data files, and notes about permissions and dependencies. If the new release changes keys or requirements, restoring all related files—not just the source—gives you a reliable rollback.

Frequently Asked Questions

How do I install an Oxide plugin on a Rust server?

Verify oxide.version, download the original .cs file, upload it to the active oxide/plugins (or documented umod/plugins) directory, confirm the load in the console or with umod.plugins, then configure and grant permissions as documented.

Why is my Rust plugin not loading?

Check that Oxide/uMod is installed, the file is in the active directory, the archive is extracted, the filename still ends in .cs, and no compiler or dependency error appears in the console or oxide/logs.

How do I reload an Oxide plugin?

Run oxide.reload PluginName in the server console, replacing the placeholder with the plugin’s actual name.

How do I give a plugin permission?

Copy the exact permission string from the plugin page and run oxide.grant user or oxide.grant group. Use oxide.show user to verify the resulting access.

Where is the plugin configuration file?

Normally it is oxide/config/PluginName.json, created after a successful first load. Some plugins have no configurable file.

Can I use a managed Rust server panel?

Yes. Use its file manager, console, or one-click installer, but verify that it writes to the same Oxide/uMod instance and active plugins directory used by the running server.

What is the safest way to update a plugin?

Back up the source, configuration, data, permissions, and dependencies; read the release notes; replace the source; watch the automatic reload; and restore the complete backup if behavior or compilation breaks.

The Bottom Line

Reliable Rust plugin installation is a verification process: confirm Oxide/uMod first, preserve the developer’s original .cs file, use the active plugin path, read the console and logs, keep JSON valid, and grant only documented permissions. Backing up source, configuration and data turns updates and host migrations into reversible changes instead of emergencies.

Quick Recap

Bestseller No. 1

Rust Key Cards, Rust Red Key Card, Cobalt Restricted Access Cards, Rust Gift For Gamers, Blue Key Card, Green Key Card (ALL THREE)

Wallet-Size Replica – Standard 3.375x2.125 inches, 30 mil thick—fits in any wallet.; NOT a sticker*

$25.00

Bestseller No. 2

Rust Video Game Notebook

$15.00

Bestseller No. 3

Rust Game Props Large Furnace (S)

Acrylic Painting Pla Plastic

$14.99

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.