ChicagoServers has a plugin installer built into the control panel, with the full umod.org catalog of over 1,400 Rust plugins. You can also upload your own .cs plugin files if you prefer.
Installing plugins from the control panel
- Sign in to the control panel at panel.chicagoservers.co and open your Rust server.
- Open the Plugins tab.
- If your server doesn't have a plugin framework yet, click uMod (Oxide) or Carbon under Change framework, then Switch to uMod (Oxide) or Switch to Carbon. Both run uMod plugins (Carbon runs most of them). The panel installs it and puts it back on after every Rust update, so a wipe-day update never switches your plugins off. See How can I install Oxide/uMod/Carbon onto my Rust server?
- Search for a plugin and click Install. It installs in a few seconds and loads by itself, with no restart.

A plugin's settings appear in oxide/config (or carbon/configs with Carbon) once it has loaded for the first time. Click Config next to the plugin on the Plugins tab to open that folder on the Files tab. After editing, type oxide.reload PluginName (with Carbon: c.reload PluginName) on the Console tab to load the new settings. To take a plugin off, click Remove next to it.
Uploading your own plugin files
To find plugins yourself, search umod.org/plugins. Make sure the plugin is for Rust: umod.org has plugins for other games too. Click the download button on the plugin's page to get its .cs file.
- Install uMod or Carbon on the Plugins tab, as above.
- Open the Files tab and go to the
oxide/pluginsfolder (carbon/pluginswith Carbon). - Click Upload and choose the .cs file you downloaded, or drag it onto the page. You can also upload over SFTP: see How to connect to your server's SFTP.
- The plugin loads by itself within a few seconds. Its config file appears in
oxide/config(carbon/configswith Carbon); after editing it, typeoxide.reload PluginName(orc.reload PluginName) on the Console tab.
Note: plugins are made by their own authors, not by ChicagoServers. We can't guarantee that a plugin works as expected, support how it works, or take responsibility for problems or performance issues a plugin causes.
Need help? Open a support ticket and we'll take a look.