nivex

heya, your lockouts are configured properly. lockout ui should not appear after completing a purchased event. lockouts are given to automatically spawned events. custom monuments require a monument marker and building/monument topology to cover the bounds of the entire monument or it will not be blocked properly. if events can spawn partially inside of monuments then this is why. you have 5 workarounds: ensure it has a monument marker, seen by a visible name on the in-game map. if it has this, then only its topology needs to be fixed. this is not ideal for your current wipe. block them using Block Spawns At Positions in the config. next update will let you block by grid as well. spawn cupboard.tool at the position to block RB events in that area. this is the easiest solution. allow players to reset their buyable cooldowns by using /buyraid reset when Reset Cooldown Costs are enabled. not ideal. #3 is the easiest solution. increase Extra Distance To Spawn From Monuments beyond 100 meters, but that's not ideal as it affects all monuments, and it's not recommend to set this above 50 for that reason. there is no way to bypass a buyable cooldown being set when using /rbe despawn. I can add an option for that in the next update.

heya, I don't think it's unbalanced, but it's not possible to provide a package that every server will agree with though, because each server has their own economy and needs and what they consider balanced. players will always find something to complain about though, especially loot. they always want more but loot profits should be a gamble, not a guarantee. there's a very good loot table editor made by beee that you can use to make adjustments: https://codefling.com/tools/raidable-bases-boats-loot-editor/ or you can simply increase Amount Of Items To Spawn or Loot Amount Multiplier in the profiles. the packages are working and will receive an update soon too =]

Changed Status from Pending to Closed Changed Fixed In from Not set to Next Version

heya, I understand. Kill Deployables Before Spawning A Base is set to false by default. its purpose is to delete player deployables when set to true and an event spawns on deployables. so yep, if you manually spawn an event inside of your base it will delete them. I'll block unknown arguments in the next update, but /rbe by itself will always spawn a random base where you are looking at. that is its purpose. the command shouldn't be used inside of someone's base though

hi, i can change it. players should not be given raidablebases.allow though, thats an admin perm. players only need raidablebases.despawn.buyraid to despawn their own events

ah ya that would explain it no worries

heya, tier 1 has 2 bases per difficulty level. if you have 8 per difficulty then install the config again as this cannot happen with the tier 1 config which enables Require All Bases To Spawn Before Respawning An Existing Base I recommend getting some additional bases too. you can find more on Codefling or download them off Fortify on Steam:)

Changed Status from Pending to Closed

you're welcome, enjoy

hi, players should only be ejected when trying to enter the base, not the sphere. events can overlap other players bases so this is necessary.

Changed Status from Pending to Closed

haha no problem. enjoy!

hi, costs are shown by default. delete your language file and reload the plugin oxide/data/lang/en/RaidableBases.json if the issue persists then restart the server because Oxide is not loading it properly

hi, delete the default loot table or make its contents [] oxide/data/RaidableBases/Default_Loot.json then use rb.reloadtables or reload the plugin

heya, the free version doesn't have that command and contains 1 difficulty Normal which is green. the plugin is sold separately, if you want to use the other difficulties and the buyraid you can get the plugin too.

Hi, sorry for no response. The plugin is a mess and was missing a lot of functionality for many lights. I started work on it recently. It will remain a free plugin and be updated to my standards. I will release it once it's completed, not sure when that will be but the work I've done so far looks promising. 104 lights supported now.

Changed Status from Pending to Closed

Changed Status from Pending to Closed

Changed Status from Pending to Closed Changed Fixed In to 3.1.6

Changed Status from Pending to Closed

Changed Status from Pending to Closed Changed Fixed In to 2.2.7

Changed Status from Pending to Closed

Changed Status from Pending to Closed

Changed Status from Pending to Closed