nivex
-
Posts
5,547 -
Joined
-
Last visited
-
Days Won
193
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Support
DOWNLOADS EXTRA
Services
Everything posted by nivex
-
support regarding raid protection plug in from mr01sam
nivex replied to TheRiddledNote's Support Request in Support
heya, the raid protection plugin would need to exclude the abandoned bases using the EventTerritory API. if you enable Remove Ownership in the Abandoned Bases plugin then Raid Protection should not protect it as it isn't owned by a player then, skipping the need for it to use the EventTerritory API no, there is no way to prevent it from converting a base with raid protection. it strictly uses the abandoned time limit set in the config file furthermore, I'm not sure why you would need both plugins as they effectively do the same thing. except mine works on a strict time limit instead -
hi, best bet is to type: rb.config list make sure there's no spelling errors copypaste files are case sensitive / must be identical copypaste folder must be lowercase
-
@BoyFrary yes, you would use the id number setting it to 0 will allow it to be random per Skins => Loot Items in the config file not sure what -1 would do but looks like it may prevent it from being skinned -
name - the display name of the item. like turning paper into cash by using a skin and changing the name to "Cash" name "Cash" shortname "paper" skin - any skin to change how the item looks, https://steamcommunity.com/workshop/browse/?appid=252490 amount - max amount - how many of this item to spawn using a random value between min and max amountMin - min amount probability (0.0 to 1.0) - items must be pooled and randomly picked first, and only after that will this modifier determine if it spawns or not stacksize - this option ignores the servers stacksize limit when above -1. if you have ammo.rifle with min/max of 1024 and a stacksize of 256 then you will get 4 stacks of 256. this will count as 4 items @BoyFraryglad you all are having fun with it
-
Changed Status from Pending to Closed
-
Changed Status from Pending to Closed
-
@The Real Butter I don't know what plugin would be doing that. damage isn't blocked on my end.
-
hi, no, this feature has been disabled until it can be reworked. I will likely remove it completely if it requires much code at all to make it work again
-
hi, no problem. bases become raidable after X days of being inactive - do not think of it as purge, that is a different feature purge day is when every single base on the server becomes raidable. you must run the commands sar purge and sab to enable it. by default each base despawns after 1800 seconds so on purge day you may want to set this time to 0 so they do not despawn until you wipe the map no, you cannot avoid purge day for specific people unless they have exempt perm it is advised that you run the purge commands after a restart and before anyone logs on. this can be very stressful on the server and kick players otherwise. it is not recommended to use this feature until the next update can resolve this either way, TruePVE and Abandoned Bases should always be unloaded on purge day anyway
-
@CsaszyKJnot possible - the time starts when he buys a raid, is reset when he completes the raid and again when the raid despawns. it effectively begins when the raid ends. a new raid showing up is not going to reset the time. @J2click the arrow and move the ui
-
hi, normal mode is available in the free version only be sure to update from this site only if using an auto updater or rust server manager then exclude / blacklist raidable bases from auto updating
-
heya. there is no such option anymore. you can change stability using the command: rb.config stability false or rb.config stability true
-
Changed Status from Pending to Closed
-
Changed Status from Pending to Closed
-
ya, noclip will bypass quite a few things as well
-
hi, enable the eject settings in the profile as it states to do oxide/data/RaidableBases/Profiles/ just search for the word eject and youll find the 4 settings np
-
Changed Status from Pending to Closed
-
glad you enjoy it
-
heya. that's not how probability works. 1.0 does not guarantee an item spawns - it only guarantees it spawns if it first randomly picked from a pool of the 800+ items that are available in the game the range is 0.0 to 1.0 and 1.0 is 100% so it should not be set above 1.0 configure base loot with the few items that you want to always spawn, and enable Always Spawn Base Loot Table in the profiles put the reminder of the loot into the difficulty loot tables so that it can pick randomly from it this is explained in depth in the documentation. enjoy
-
np
-
Items in lockers not included in the loot count
nivex replied to LandOfTheBlind's Support Request in Support
Changed Status from Pending to Closed -
hi, edit the profiles, oxide/data/RaidableBases/Profiles/ change Despawn Dropped Loot Bags From Raid Boxes When Base Despawns to true
-
Items in lockers not included in the loot count
nivex replied to LandOfTheBlind's Support Request in Support
hi, not bugged. if you want lockers to be included as part of the box/tc requirement then you would need to add "locker" to Additional Containers To Include As Boxes "Additional Containers To Include As Boxes": [ "locker" ], like this -
hi, remove them from your loot tables. oxide/data/RaidableBases/Base_Loot and oxide/data/RaidableBases/Difficulty_Loot they should only be in the latter should delete the oxide/data/RaidableBases/Default_Loot.json if you haven't already.
