Raidable Bases

Allows player to use the available ADMIN commands. This is NOT recommended as players can use the command 'rb' already.

raidablebases.canbypass permission (or to be flying) to bypass dome restrictions (this previously worked for admins, but now requires the permission instead)

raidablebases.blockbypass permission to bypass Owning More Than One Raid settings for Clans/Friends/Teams

raidablebases.mapteleport Teleporting to map marker now simply requires this permission and to be enabled in config

raidablebases.ddraw allows support for FauxAdmin users

raidablebases.config allows use of the rb.config command in-game (server console does not require this permission)

raidablebases.banned bans the user from entering any raids - DO NOT GIVE THIS TO THE DEFAULT GROUP LOL

rb - for players to see the ladder (also for admins to see the status of each raid going on, which includes showing the allies and owners of each raid)

For admins, or players with the admin permission raidablebases.allow:

rb grid - see the grid and all monument names

rb debug - shows important debug information about why a maintained or scheduled event is not spawning

rb resettime - reset the time for the next scheduled event

rbe - spawns a base at the position you are looking at. You cannot spawn a base on a player (including yourself)

rbe draw - draw the raids radius

rbe despawn - despawn a base near you

rbe despawnall - despawn all bases

rbe [basename] [difficulty] - spawn a raid at the location you are looking at

rbe expire steamid|playername - removes a lockout for a specific player

rbe expireall

rbevent [basename] [difficulty] - spawn a raid randomly on the map - and teleport to it if using the command in-game

rb.reloadconfig - allows you to reload the config without needing to reload the plugin. Some changes are not applied immediately, and no changes are retroactive to bases that are already spawned.

rb.config - allows you to edit the config by adding, removing, and listing bases. Requires the permission raidablebases.config when not being used from the server console.

rb ui [lockouts|status] - toggle ui on/off, or optional the lockouts or status

rb.toggle - toggles Maintained Events and Scheduled Events on/off, if enabled in the config, until plugin reloads

rbe setowner name - Sets the player as the owner of the raid

rbe clearowner - Clears the owner of the raid

Additional Bases allows you to add additional files to an existing base so that all bases in that list share the same configuration as the primary base/profile. This is great for setting up a list of bases for easy, medium, hard, expert and nightmare.

Command 'rb.populate' will populate a loot file in RaidableBases/Editable_Lists folder with every item in the game (items are disabled by default as their amounts are set to 0)

Configure the items to your liking then copy the files contents into a loot table that you would like to use (for example Difficulty Loot/Easy.json)

You cannot use loot tables in the config file anymore. Use the data directory (oxide/data/RaidableBases)

You MUST read this documentation. This plugin is simply too complicated to not do so. Take your time to understand each option before changing it. You will not get anywhere by trying to cut corners. Carefully go through each option in the configuration and read about it so that you understand what it does. If it has no explanation then it's self explanitory. Please look for answers in the documentation before asking a question. I have no issue helping anyone that has difficulty with this plugin. It is not easy to setup.

The plugin comes with some very basic items (Default_Loot.json) that only serve as a demo loot list for you to either delete or expand upon. In order to make any use of the plugin (beyond demonstration) you will have to create your own loot lists instead.

It will take a very long time to configure your loot tables, and fine-tune each to your specific needs. To start, I recommend that you use the rb.populate all command. This creates a loot file in the Editable_Lists folder that contains every item in the game. Edit the file and set the amounts for the items that you want to spawn, and remove those that you do not want to spawn. It may look intimidating editing a list of 660 items, but don't underestimate how easy it is to delete items from a list compared to adding each one manually.

Items that have their amount (not amountMin) set to 0 will not spawn. So you may either delete these items from the list, or come back to them later. If you set amountMin to 0 then chance will determine if the item spawns or not, and another item will not replace it unless there are extra items available (as of 1.7.3).

You can set the item skin that you want to use, but I suggest using the Skins settings in the configuration file to use random skins, or none at all.

The rb.populate command which populates the Editable_Lists folder also includes items already inside of your Difficulty_Loot folder. This allows you to easily repopulate lists in order to re-evaluate which items spawn at a later date.

Files inside of the Editable_Lists folder must be copied into an existing loot file in order to use the loot table. As the name implies, it is for editing only.

If you want to use Editable_Lists/Normal.json for your Normal bases then copy the contents of the file into the Difficulty_Loot/Normal.json file.

If you want to use Editable_Lists/Normal.json for the NormalBases.json profile, then you must copy the contents of the Normal.json file into the Bases_Loot/NormalBases.json file

Loot is pulled from all datafiles within the oxide/data/RaidableBases/ folder with the exception of the Profiles folder which is used to configure bases.

oxide/data/RaidableBases/Base Loot - If a loot table exists in this folder with the name RaidBases.json then all of the bases will use this loot table, otherwise it will pick the first file it finds. If you want items in this loot table to always spawn then you must enable Always Spawn Base Loot Table in the respective profile. You cannot have multiple files in the Base Loot directory as it will pick the first file it finds when it cannot find one that matches the name of the profile.

oxide/data/RaidableBases/Difficulty Loot - Items will be chosen from the Normal.json loot file for each profile.

If Use Day Of Week Loot is enabled then it will choose the loot table for that specific day. Otherwise, it will pick from Default_Loot.json. This is the default list, and is only used when all other loot tables do not have a sufficient amount of loot to spawn based on the Amount Of Items To Spawn setting.

Allow Duplicate Items - This is useful when you do not have enough items in your loot tables , and you want to spawn Amount Of Items To Spawn by using the same items more than once.

Amount Of Items To Spawn - This is the number of items that you want to spawn. If you do not have enough items in your loot tables then it will only spawn the amount that you have available. It will not spawn items if the container does not have enough space.

Divide Loot Into All Containers - This allows you to divide loot evenly from all of your loot lists into all containers when enabled. You MUST increase or decrease Amount Of Items To Spawn respective to how many items you want in each container. This includes large boxes, small boxes, coffins and vending machines. Optional settings include (in order of priority) cupboard, bbq, oven, fridge and lockers.

Allow Players To Pickup Deployables (false) - As name implies, overridden by Entities Not Allowed To Be Picked Up

Allow Players To Deploy A Cupboard (true) - Block players from placing a TC after destroying the TC in the base.

Drop Container Loot X Seconds After It Is Looted (false) - Prevent players from cherry picking items and leaving the rest, in order to despawn the raid quicker.

Drop Container Loot Applies Only To Boxes And Cupboards (true) - As name implies

Empty All Containers Before Spawning Loot (true) - Useful if using CopyPaste files that contain loot already - I suggest leaving this true as it can complicate how many items spawn if there are too few inventory slots remaining.

Ignore Containers That Spawn With Loot Already (false) - Useful if you want specific loot to spawn from a copypaste file.

Require Cupboard Access To Loot (false) - Prevent all players from looting until they reach the TC, or destroy it.

Skip Treasure Loot And Use Loot In Base Only (false)" - Useful if you want all loot to spawn from a copypaste file - not recommended - will allow players to memorize which boxes to raid and ignore the rest.

Always Spawn Base Loot Table (false) - Very useful if you want items in the Base_Loot file to always spawn (such as C4, rockets, ammo, etc) (the free version limits this to ONE file allowed in the Base_Loot directory)