Raidable Bases 3.1.5

@Devil-Steph

Your screenshot above with the two messages shows you leaving and then re-entering the event. Did you leave and re-enter, or only enter?

Your screenshot above with C4 is cropped, so I cannot see any important information. I need a full screenshot.

This is likely an issue with your Advanced Protection Radius in the profiles, it is 50 by default. oxide/data/RaidableBases/Profiles/

  "Advanced Protection Radius": {
    "Buyable Events": 50.0,
    "Maintained Events": 50.0,
    "Manual Events": 50.0,
    "Scheduled Events": 50.0,
    "Obstruction Distance Check": -1.0
  },

On 7/14/2026 at 10:26 AM, nivex said:

@Boozo

hi, I don't think there's an effective way to do that, no. 

Block Weapons From Use is in the config, not in the profiles, and they'd be able to exploit this with rockets by firing from outside of the dome 

Player Damage To Base Multipliers isn't much help for that either. you need to understand what damage type each weapon does first, and it's only for damage types. so you can't choose satchels but not c4

I think an option to restrict by item tier / workbench level is a good idea, but I don't like the idea of trying to control what specific items they can or cannot use individually 

Could you make it so to use rockets etc, you have to be in the raid dome. If you fire from outside they would not do damage to the structure, maybe do a true or false feature.  Then you could do a blacklist. 

@Boozo

heya, you can use the Block Damage Outside Of The Dome To Bases Inside option for this

I have implemented workbench level options next update too.

• Added "Allow players to raid with items up to what workbench level?" (-1 or 3 allows everything, but -1 is future-proof) - restrictions check weapons, loaded ammunition, fired projectiles, and explosives

hello Nivex, my players are reporting the /buyraid command is taking more scrap than expected, for example if a base cost 3K scrap and a player has 4K or moreon his inv, the /buyraid command is taking all of it.

@Demo_71

heya, this is fixed in the next update. you can use a different payment method (Economics or ServerRewards) until then.

if you don't want to wait, you can easily apply the fix yourself by editing RaidableBases.cs. simply replace lines 16521 to 16525 with this:

    int amount = Math.Min(slot.amount, amountLeft);
    amountLeft -= amount;
    slot.amount -= amount;
    slot.ReduceItemOwnership(amount);
    if (slot.amount <= 0) slot.Remove();
    else slot.MarkDirty();

optional in the next update, expand the buyraid ui to include options for PVE and PVP. an optional confirmation dialog is enabled to prevent accidental purchases. if pve or pvp buttons are enabled, then the player must click the respective PVE or PVP button instead. this is a functional difference, and I could default it to PVE but that would defeat the purpose of a having a PVE button. just click PVE if you want PVE. if you want PVP then click PVP.

this respects the Allow Players To Buy PVP Raids option when set to false. there is no functional reason to enable the pve/pvp buttons when that option prevents PVP purchases, but it is possible for anyone who likes the appeal of the extended UI.

this respects the raidablebases.buyraid.pvponly and raidablebases.buyraid.pveonly permissions

raidablebases.buyraid.free will now correctly show "FREE" as the cost to anyone with that permission.

raidablebases.buyraid.free will now bypass a configuration that has not enabled any costs. this can benefit shops indirectly, so please do not use this to circumvent the intended functionality. that is, if selling from a shop, then it will never be supported unless the shop sells it for free. this does not mean that it cannot work, but it means RB cannot handle a refund if the shop handled the purchase instead of RB.

many more exciting changes are awaiting in the next update too, only to be revealed when the update is released 

I know, it's not the prettiest but even ugly ducklings are loved by their mothers. there are config options to change colors, and text is in the language file for EN and RU.

the documentation has been rewritten to be easier to read and incrementally introduces you into deeper functionality of the plugin. this should help alleviate confusion and difficulty with setting up the plugin. it also hints at what is to come.