Rust Raidable Bases Config Generator
Build a working config for Raidable Bases — the automated NPC-defended raid plugin by nivex.
Tune global event scheduling, buy costs and map markers once, then set NPCs, loot, rewards, PvP and arena rules per difficulty
across all five profiles (Easy → Nightmare). Copy the main RaidableBases.json and each profile file as clean, valid JSON.
This is the first web config generator for Raidable Bases anywhere — we don't touch the loot-table data files, and we say so.
Difficulty Profiles
Each difficulty is its own profile file. Pick a tier below and edit that profile's NPCs, loot, rewards, arena walls, turrets and PvP rules — all five profiles hold their own values at once, so switching tabs never loses your work.
About the Raidable Bases config generator
Raidable Bases by nivex spawns fully automated, NPC-defended bases on your Rust map for players to raid — PvE or PvP — for loot. It is one of the most heavily configured plugins in all of Rust, with 200k+ downloads and a config deep enough that the author warns you not to install it without reading the docs. This tool builds the admin-facing knobs server owners actually tune, then hands you clean JSON to paste in. It's the first web config generator for Raidable Bases anywhere.
The multi-file split
Raidable Bases isn't one config — it's several. The main RaidableBases.json holds server-wide settings: event scheduling, buy costs, map markers and raid management. Then each of the five difficulties (Easy, Medium, Hard, Expert, Nightmare) gets its own profile file carrying that tier's NPC counts, health, loot amount, rewards, protection radius, arena walls, turrets and PvP rules. That's why this generator emits six files, not one — a main config plus one profile per difficulty. The actual item loot tables live in a separate Difficulty_Loot / Base_Loot data domain that we deliberately do not generate.
Where the files go
- Main config:
oxide/config/RaidableBases.json - Profiles (Oxide):
oxide/data/RaidableBases/Profiles/Easy.json…Nightmare.json - Profiles (Carbon):
carbon/data/RaidableBases/Profiles/Easy.json…Nightmare.json— the data path changes tocarbon/data/on Carbon; the config path staysoxide/config/on both. - After dropping the files in, run
oxide.reload RaidableBases(oro.reload/c.reloadon Carbon) in the server console — no full restart needed.
Exact keys matter
Some Raidable Bases config keys have parenthetical hints baked into the JSON key itself — for example Health For Murderers (100 min, 5000 max) or Create Dome Around Event Using Spheres (0 = disabled, recommended = 5). Those parentheses are literally part of the key string; strip them and the plugin ignores the value. This generator emits the keys exactly as the plugin expects them.
Free vs premium
The free version lives on uMod; the premium version — five difficulties, buyable events, player lockouts, dynamic difficulties — is sold on Codefling. Both are by nivex. The five-difficulty model this generator is built around is the premium feature set, which most serious servers run. If you're on the free uMod build with fewer difficulties, use the profiles that apply to you and ignore the rest.
FAQ
Where do the Raidable Bases config files go?
The main file goes in oxide/config/RaidableBases.json. The five profile files go in oxide/data/RaidableBases/Profiles/ as Easy.json, Medium.json, Hard.json, Expert.json and Nightmare.json. On Carbon, the data path is carbon/data/RaidableBases/Profiles/ instead.
What are the five difficulties?
Easy, Medium, Hard, Expert and Nightmare — each a separate profile with its own NPCs, loot, rewards and rules. Servers ramp difficulty by making easy raids cheap and common and Nightmare raids rare and brutal.
Is it free? Free vs premium?
There's a free uMod build and a premium Codefling build, both by nivex. The five-difficulty model, buyable events and lockouts are premium. The free version has fewer difficulties. Credit and downloads go to nivex either way.
Why multiple files?
The main config is server-wide; each difficulty gets its own profile so tuning a tier doesn't mean scrolling one giant file. Loot tables live in yet another folder that this tool doesn't touch.
Do I need to restart?
No — run oxide.reload RaidableBases (or the Carbon equivalent) in console to hot-reload with the new config and profiles.
Related tools
- Rust server.cfg + start.bat generator — the vanilla server config this plugin sits on top of
- Common Rust server settings guide
- All GamesOMG generators
Raidable Bases patches often and its config is enormous. We track the admin-facing keys and re-verify against the real files. Spot a key that's drifted or one we should add? Hit Report an issue above. And if you run this plugin, go support nivex — they built it.