This guide covers Oxide plugins. Vanilla Rust cannot load them. For Carbon, use its documentation and the plugin author’s compatibility notes.
Check Oxide is installed
In Console, enter oxide.version. Check the startup log if the command is unavailable. Rust Autowipe has a Modding Framework field in Startup with vanilla, oxide and carbon options. Rust Staging does not have that field. Contact Konnect support if you need help enabling Oxide.
Upload the plugin
- Check the plugin’s supported versions, dependencies and permissions. Back up first if it changes saved progress or data.
- Download its .cs file from the official plugin page. Keep the filename and extension.
- Upload the file to oxide/plugins. Oxide loads it while the server is running.
- Check Console for the loaded message or compile errors.
oxide/
├── plugins/ — plugin .cs files
├── config/ — generated settings
└── data/ — saved plugin dataEdit its settings
A configurable plugin usually creates a matching JSON file in oxide/config. Edit it in Files and save, keeping valid JSON syntax. Enter oxide.reload MyPlugin in Console, replacing MyPlugin with the plugin name without .cs.
If it does not work
If the plugin loads but a command is denied, follow our Oxide permission guide. Rust owner access does not grant every plugin permission. For loading errors, check dependencies, framework updates and Console or oxide/logs.
For general file uploads, see connecting with SFTP. For game admin access, see adding a Rust admin. Compare Rust hosting plans.
Troubleshooting checks
| What you see | What to check |
|---|---|
| Plugin loads but its command is denied | Check the plugin’s required permission. Loading a plugin does not automatically grant every player access. |
| Plugin fails to compile | Use its supported release and dependencies, then read the first compile error before editing the script. |
Official reference: uMod plugin installation, uMod configuration, uMod permissions, Rust framework and reinstall settings.
Your feedback helps us improve our guides.
