Use the Raidable Bases Plugin on Rust

Raidable Bases pastes ready-made bases onto your map, fills them with loot, optionally guards them with NPCs, and lets players race to raid them. It is one of the largest Rust plugins, so this guide sticks to what you need to get a first base on the map: what it requires, where its files go, how to spawn one, and how to turn on automatic spawning.

Checked against Raidable Bases 3.2.2 by nivex on uMod (released 6 October 2026), October 2026. uMod describes it as creating fully automated raidable bases with NPCs. It compiled and loaded on our Carbon test server (Carbon 2.0.262, Rust build 2635). The uMod download is the free edition: the plugin prints Free version initialized. when it starts, and options that exist only in the paid edition, such as Buyable Events, are not in it.

What it needs

Raidable Bases pastes bases with the CopyPaste plugin. The source checks for CopyPaste 4.3.0 or newer and otherwise prints "You must update or reload CopyPaste (v4.3.0+)". Install CopyPaste from the same Plugins tab first (How to use the Copy Paste plugin on your Rust server).

The bases themselves are CopyPaste save files. The plugin looks for them by name in the copypaste folder inside the data folder (oxide/data/copypaste on Oxide, carbon/data/copypaste on Carbon). Its default profile is called RaidBases and lists five base files: RaidBase1 to RaidBase5. Until files with those names exist, or you point a profile at files you do have, there is nothing to spawn. The plugin only reads these files from that folder, so you need to supply them.

Install it

Open the Plugins tab, search the Store for RaidableBases and press Install. How to install Oxide/uMod plugins on your Rust server covers the tab, Oxide and Carbon.

On Oxide, a newly installed plugin stays unloaded until you restart the server or type oxide.load RaidableBases in the Console. On Carbon it loads by itself within seconds, and the commands are c.load, c.unload and c.reload. The oxide.* commands, oxide.grant included, print nothing and do nothing on Carbon. Permissions only exist once the plugin has loaded, so grant them afterwards. The config is oxide/config/RaidableBases.json, or carbon/configs/RaidableBases.json on Carbon.

Add your base files

From the server Console, rb.config manages which base files belong to a profile. Its own help text reads Use: rb.config <add|remove|list|clean|enable_dome_marker|toggle|stability|inventories|maintained|scheduled|noexplosivecosts> [base] [subset] and its example is rb.config add nivex1 nivex4 nivex5 nivex6. Run rb.config list to see what is set up. The command needs the raidablebases.config permission. After editing profiles by hand, rb.reloadprofiles reloads them, and rb.reloadconfig reloads the config.

Spawn your first base

• In game, look at the spot and type /rbe. It needs the player to be an admin or to hold raidablebases.allow.
• On Oxide, from the server Console, type rbevent to queue a base: the plugin treats the server console as allowed for this command. On Carbon, type /rbe in game as an admin instead.
• You can name a base file after either command to choose it.

Both names are settings in the config: Event Command (rbe), Server Console Command (rbevent) and Hunter Command (rb).

Automatic bases

Nothing spawns on its own after a new install. In the config, Maintained Events has Always Maintain Max Events and Scheduled Events has Enabled, and both are false. To change them without editing the file, an admin can run rb.config maintained or rb.config scheduled, which flip the setting and save it. Maintained events keep Max Maintained Events (3 by default) on the map. Scheduled events open every Every Min Seconds to Every Max Seconds (3600 to 7200), up to Max Scheduled Events (3).

Permissions that matter first

The plugin registers more than twenty permissions in all, listed in the RegisterPermission lines of its source. Grant one with oxide.grant user <SteamID64> raidablebases.allow, or c.grant user <SteamID64> raidablebases.allow on Carbon. c.grant user <SteamID64> <permission> ran on our Carbon test server and answered Granted user 'Unnamed' permission 'kits.admin'.

Players see their score with /rb, and /rb ladder and /rb lifetime show the rankings.

Common problems

1. "You must update or reload CopyPaste". CopyPaste is missing, older than 4.3.0, or still loading.
2. "You cannot spawn a base that is not configured." The base file you named has no profile, or the file is not in the copypaste folder.
3. Nothing spawns by itself. Automatic events are off by default, as above.