Oxide (now maintained as uMod) is the modding framework that makes Rust servers customizable. Without it, you're limited to vanilla Rust configuration. With it, thousands of plugins become available.
Installing Oxide
Method 1: One-Click (Managed Hosting)
On Space-Node and most managed hosts, Oxide is available as a one-click installation from the control panel. Select it, click install, and restart your server.
Method 2: Manual Installation
- Download the latest Oxide build from umod.org
- Extract the archive
- Upload the contents to your Rust server's root directory (overwrite existing files)
- Restart the server
- Verify: check the console for "Oxide loaded" messages
Installing Plugins
- Browse umod.org/plugins for Rust plugins
- Download the
.csfile - Upload to your server's
oxide/plugins/directory - The plugin loads automatically - no restart needed
Most plugins also create a configuration file in oxide/config/ after first load. Edit these to customize behavior.
Essential Plugins
Server Management
- RustAdmin or AdminRadar - See players, teleport, moderate
- ServerRewards - Points system for playtime rewards
- NTeleportation - Home, town, and admin teleports
- Kits - Starter kits and periodic reward kits
Quality of Life
- QuickSmelt - Faster furnace processing (configurable multiplier)
- GatherManager - Custom resource gathering rates
- RemoverTool - Let players remove misplaced building pieces
- BGrade - Upgrade building materials by tier
Anti-Cheat & Protection
- Clans - Clan system with friendly fire prevention
- SignArtist - Import custom images to signs (great for community)
- RaidBlock - Configurable raid rules and timed restrictions
Permissions System
Oxide includes its own permission system. Grant permissions to groups or individual players:
oxide.grant group default plugin.permission
oxide.grant user PlayerName plugin.permission
oxide.group add vip
oxide.usergroup add PlayerName vip
Create permission groups (default, vip, moderator, admin) and assign appropriate permissions to each. This integrates with most plugins automatically.
Configuration Files
Each plugin creates a JSON config in oxide/config/. Example for GatherManager:
{
"Options": {
"GatherRate": 2.0,
"QuarryRate": 2.0,
"PickupRate": 2.0
}
}
After editing config files, reload the plugin without restarting:
oxide.reload PluginName
Plugin Conflicts
Common conflicts and solutions:
Two plugins modifying the same system: If GatherManager and another plugin both modify gathering, they may conflict. Use only one plugin per system.
Version mismatches: Plugins built for older Oxide versions may break after updates. Check the plugin's umod.org page for compatibility notes.
Memory leaks: Poorly coded plugins can leak memory over time. Monitor with oxide.show and watch for plugins with growing memory footprints. If memory climbs steadily between wipes, a plugin is likely the cause.
Performance
Plugin overhead varies dramatically. Well-coded plugins add negligible server load. Poorly coded plugins can halve your server FPS.
Use oxide.profiler to measure per-plugin overhead and remove or replace anything consuming excessive resources. For a 200-player server, even 1ms per tick per plugin adds up across 20+ plugins.
Keeping Plugins Updated
Oxide and plugins update regularly for Rust's monthly patches. After each Rust update:
- Update Oxide through the control panel or manually
- Check each plugin's umod.org page for updates
- Replace outdated plugin files
- Test on a staging server if possible before going live
Most actively maintained plugins release updates within 24-48 hours of a Rust update. Abandoned plugins may never update - plan replacements for critical functionality.
