How to Install and Manage Plugins on Your Rust Server

 

    Once you've installed a modding framework — Oxide (uMod) or Carbon — plugins are how you actually add features: kits, teleport/homes, gather-rate control, PvE protection, shops, and thousands more. This guide covers the whole loop: get a plugin, install it, configure it, and manage permissions, all on gamever.

 

Step 1 — Get the plugin

 

    Download the plugin's .cs file from a reputable source (uMod/Codefling and similar plugin sites). Each plugin page lists which framework and Rust version it supports — check that before downloading.

 

Step 2 — Upload it

 

    Put the .cs file in your framework's plugins folder, inside your server's identity folder (next to cfg/):

 

• Oxide → oxide/plugins
• Carbon → carbon/plugins

 

    Use the File Manager for one or two files, or FTP for a batch (connect with the credentials from Settings → FTP server settings). The framework auto-loads the plugin within a few seconds — no restart needed for most plugins.

 

Step 3 — Configure it

 

    The first time a plugin loads it writes a default config:

 

• Oxide → oxide/config/<Plugin>.json
• Carbon → carbon/configs/<Plugin>.json

 

    Edit that JSON in the File Manager, then reload the plugin so it picks up the change:

 

oxide.reload <PluginName>     # Oxide
c.reload <PluginName>         # Carbon

 

Step 4 — Permissions

 

    Most plugins gate features behind permissions you grant to players or groups. From the Console (or RCON):

 

Oxide	Carbon	What it does
oxide.grant group default kits.use	c.grant group default kits.use	Give the whole server a permission.
oxide.grant user <steamid> <perm>	c.grant user <steamid> <perm>	Give one player a permission.
oxide.revoke …	c.revoke …	Remove a permission.
oxide.show perms	c.show perms	List known permissions.
oxide.usergroup add <steamid> vip	c.usergroup add <steamid> vip	Put a player in a group (e.g. VIP).

 

    A common pattern: create a vip group, grant it the perks, and add paying/role players to it.

 

Managing and troubleshooting

 

• A plugin won't load? Check the Console for the error — usually a Rust-version mismatch or a missing dependency plugin.
• Edited a config and nothing changed? You forgot to reload the plugin.
• Removing a plugin: delete its .cs from the plugins folder (and optionally its config/data files).
• After a Facepunch update, some plugins need their own update before they work again.

 

Additional Tips

 

• Match the plugin to your framework and Rust build — that's the #1 reason a plugin fails to load.
• Reload after every config edit — the server won't re-read the JSON on its own.
• Use groups for perks (vip/default) instead of granting each player one by one.
• Keep a short list of your plugins so you can re-check them after each update.
• Back up your oxide/carbon folder before big changes — the Backups tab or an FTP copy.

 

Conclusion

 

    The plugin loop on gamever is simple once your framework is on: drop the .cs in oxide/plugins (or carbon/plugins), edit the JSON config, reload, and grant permissions from the console. That's everything you need to shape your Rust server exactly how your community wants it.

 

    Rent your Rust server at gamever.io — one-click Oxide/Carbon, full file and FTP access for plugins, and a built-in console. Free trial, promo code WELCOME.