-
Posts
5,812 -
Joined
-
Last visited
-
Days Won
199
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Services
Downloads Plus Support
DOWNLOADS EXTRA
Everything posted by nivex
-
- 634 comments
-
- 1
-
-
- #rust
- #rust plugin
- (and 6 more)
-
- 634 comments
-
- 2
-
-
- #rust
- #rust plugin
- (and 6 more)
-
it's planned but there's no way to currently do this. there are far too many issues to resolve before it can be implemented because the event can overlap other bases if players build too closely. those overlapped bases won't be raidable, but it is difficult to determine who should be ejected. in the next update there is a new option to prevent players from looting anything in the abandoned bases, and I will likely add a second Eject Enemies option to remove players when they step on a foundation unless I can find an elegant solution to eject them when they enter the dome instead. either way, it will serve the same purpose and be just as effective.
- 634 comments
-
- #rust
- #rust plugin
- (and 6 more)
-
@Tomato_Jesus Do Not Destroy Base When Despawn Timer Expires Do Not Destroy Manually Converted Base When Despawn Timer Expires Conversions Before Destroying Base (fixed in next update) sar cancel - requires abandonedbases.convert and abandonedbases.convert.cancel - allows the user to cancel the event, optionally requiring it be looted and/or requiring a configured amount of time before the command can be used sar claim - requires abandonedbases.convert and abandonedbases.convert.claim - allows the user to cancel the event, take over the base and become the owner. optionally requires them to have looted the base first. this does not unlock key locks but will next update. those will prevent the base from despawning and will allow it to be converted again @Robert Stevens Abandoned Bases If you enable Abandoned Bases in the integration config, then bases that are labeled as Abandoned will not receive raid protection. quote from the Raid Protection plugin. otherwise no, abandoned bases does not look at how much protection the base has from that plugin. I don't see a reason to use both plugins, but if you want then I can add support for it anyway. mine works strictly on how long since the players of the base have been offline before it considers the base to be abandoned.
- 634 comments
-
- #rust
- #rust plugin
- (and 6 more)
-
hi @Blackbird that isn't possible Time To Wait Between Spawns will wait the configured time between spawns but this does not start when a base is raided. it starts after the first base has spawned. so if you configure 10 easy bases to spawn and set this to 60 then all 10 easy bases will take 600 seconds or 10 minutes to spawn. Maintained Events will keep a specific number of bases spawned at all times limited by Max Amount Allowed To Automatically Spawn Per Difficulty. Scheduled Events will spawn a specific number of bases on a schedule that is limited by Max Amount Allowed To Automatically Spawn Per Difficulty too. if this time elapses and this max limit has been reached then it will wait until a base despawns.
-
@Porky nice, thank you. you will need to configure a buyable event cost so that /buyraid will work. Custom Buy Raid Cost are below these settings too "Buyable Event Costs": { "Require Custom Costs": true, "Require Economics Costs": true, "Require Server Rewards Costs": true }, "Economics Buy Raid Costs (0 = disabled)": { "Easy": 0.0, "Medium": 0.0, "Hard": 0.0, "Expert": 0.0, "Nightmare": 0.0 }, "ServerRewards Buy Raid Costs (0 = disabled)": { "Easy": 0, "Medium": 0, "Hard": 0, "Expert": 0, "Nightmare": 0 },
-
- 634 comments
-
- 1
-
-
- #rust
- #rust plugin
- (and 6 more)
-
@MeinRustthank you Mein @Commo if you're going to change it in the config then you should unload the plugin and delete the UI data file. this is because each players offsets are stored so changing config will apply to new offsets or unchanged offsets only. you can use the arrow to move each ui window too to make this easy oxide/data/RaidableBasesUI.json - be careful to not delete the wrong data file.
