Posted 2 years ago

How to setup RaidableBases correctly in Rust October 2023

Hello everyone! 😊 It's been about 8 hours of googling for me to find how to setup RaidableBases properly because of the lack of recently updated information. I've spent lots of personal time and want to help others pass their way much easier because the official video is partly outdated.

Also I want to thank misticos for the CopyPaste and of course nivex for the RaidableBases plugins and srtbull for his funny but professional instructions on YouTube. You're breathtaking guys!

My job here was to check the difference between old and new srtbull's videos and change many confuguration values to understand what's happening a bit easier than it's told in the full documentation and howtos.

Disclaimer: I am sorry if something I've explained isn't correct in English a bit. It is not my native language and I'd like if you correct me. It will help both you and me to bring & update the important information to others.

GoTo Checklist

First of all let's keep sure you have all of your knowledge and courage for the successful installation:

You have the latest version of Rust Dedicated for Windows / Linux - https://wiki.facepunch.com/rust/Creating-a-server.
You have the latest version of Oxide for Windows / Linux - https://umod.org/games/rust correctly placed in \RustDedicated_Data.
You have set up the correct configuration file server.cfg placed in the \server\$yourservername$\cfg.
Obviously, you know how to set up Oxide plugins and how to give necessary permissions for them.
Obviously [2], you're admin of your server. It is necessary to push some plugin commands into the chat.

If it's OK for you, let'go into the instruction. It will be explained:

Why bases don't appear in RaidableBases
Why they appear but look incorrectly

Step 1. Plugins installation.

Just put their .cs files into your \oxide\plugins directory. If you're running server do not forget to use o.reload all / o.reload RaidableBases CopyPaste commands. And don't be afraid if you're using tons of plugins, I had the same situation before adding RB:

If you're just doing experiments, it's better to reset your server by deleting database files after seting up RB to regenerate grid and place bases a bit more correctly in the future. Moreover, this step will regenerate your units population balance and fix some performance issues.

Step 2. Adding bases for the CopyPaste.

The main highlight you need to know is that RaidableBases uses CopyPaste for the structures generation in your server. Without base files sharp and shiny placed into the \oxide\data\CopyPaste folder RB doesn't know what to do and can't add bases to its profiles.

You have at least 2 possible ways:

Download Fortify, create bases you'd like to see on your server and save them by using Rust Copy-Paste JSON button. Then copy files which always save in \Fortify_Data\Saves.
Just Google 'copy paste rust bases'. Seriously. It will bring you to the Fortify Communities world with great enthusiansts and professional Rust gamers who share their works. Lots of them are completely free for downloading, but please check if the authors allow their bases to be on your public server.

Anyway let's keep one or many .json files in the \oxide\data\CopyPaste folder. I recommend you to rename them in the format of <type><difficulty><number>, like 'pvpeasy002.json' or 'pvenightmare003.json'. It will help you in future, really. By the way, create CopyPaste folder in \oxide\data if it doesn't exist.

Step 3. Getting ready with the main RaidableBases configs.

Just for you to know - CopyPaste doesn't contain any useful settings for our task. Keep its json configuration as it is... instead of \oxide\config\RaidableBases.json which is exactly what we're looking for.

nivex patiently explained LOTS of stuff about this and another RB configuration files earlier so I will highlight what we need to test everything quickly:

Please do not forget to o.grant group admin raidablebases.* and o.revoke group admin raidablebases.banned. It's the quick way to grant all of the permissions to the server owner but don't ban yourself to get into the raid zones.
/rb grid shows which map zones are defined for the future bases to be spawned in.
/rbe (manual starting of the raid event and spawning base) will say to you that there's no configured bases. It's OK, that's exactly what we will do next.
In the RaidableBases.json please take a look at Scheduled Events object. For the tests that can show result much faster please compare and change these parameters:
"Enabled": true,
"Every Min Seconds": 60.0,
"Every Max Seconds": 120.0,
"Max Scheduled Events": 50,
"Max To Spawn At Once (0 = Use Max Scheduled Events Amount)": 2,
"Minimum Required Players Online": 1,
"Maximum Limit Of Players Online": 300,
"Time To Wait Between Spawns": 1.0
With these values your bases will spam server by their continious spawn but it's good not to waste your time and rapidly check the results, isn't it? 😉
Please do not forget to o.reload RaidableBases within your server terminal after saving changes to the .json file. It will also despawn bases every time after this command, it's OK.
Next step is pretty similar to the official videoguide - insert the command below:
rb.config add "<yourConfigName>" <basename1> <basename2> etc. That's why I've suggested to rename them earlier.
Example: rb.config add "TestBases" pvpeasy002 pvenightmare003 -- the base names MUST exactly match the files you placed in the \oxide\data\CopyPaste!
Let's check them via rb.config list command as it've been told in the video. For me they were:
RaidableBases > Profile
base001, base002, base003
Ignore if you see some 'This file does not exist' lines for the default config bases, it's not necessary to fix now. But if you see your base you've tried to add like:
base001 > This file does not exist
it means you were wrong with the base name and it didn't add to the Profiles! Please double-check and try again.
Oh, forgot to say. You don't need to create lots of easy, medium or hard profiles for the quick test. You will spent lots of time by configuring loot and difficulty of your bases but it's not what we need for now. 😉

Step 4. Loot and polishing configurations.

rb.populate all server console command will automatically create necessary loot configurations. By the way, for me after completing this command bases become to rapidly spawn on my local server with tons of the Murders and Scientists.
Go to the \oxide\data\RaidableBases\Base_Loot directory. You will see <yourProfileYouTyped>.json file. Example: TestBases.json. And it's empty. And we don't need to do anything with it for the test. 😇
Go to the \oxide\data\RaidableBases\Profiles directory. You will see <yourProfileYouTyped>.json file. But it won't be emply because you filled it with the data by completing Step 3.6.

This is a place for your imagination for changing default paramaters. For me they were:
- Arena Walls - 'Enabled: False' // because I've already placed hardcore and huge HQM bases with lots of autoturrets. It's pathetic to hide them in the walls. Moreover, bots will attack you as soon as you've getting closer.
- NPC Levels - 'Level 2 - Final Death': true // JFF lmao
- NPCs // all of their weapons, accuracy and cloth are up to you
- Amount Of <somebody> To Spawn -- I've double increased every of them to do benchmarks for my i9-11900K and 32 GB RAM
  
  Anyway it isn't necessary to change default parameters to see if everything finally works. Good luck to you! ✊
  If anything will change I'll try to update this topic rapidly. Thank to everybody for the attention.