-
Posts
5,168 -
Joined
-
Last visited
Content Type
Profiles
Downloads
Forums
Store
Support
DOWNLOADS EXTRA
Services
Everything posted by nivex
-
heya, not quite. that option is Eject Mounts. you will want to look further down for the Eject Mountables Before Spawning A Base setting. yes, you can alter the Protection Radius in your profiles, oxide/data/RaidableBases/Profiles/
-
heya, if you are not getting any feedback from the commands and you do not see it running then the plugin is not loaded for some reason download the update again, and reupload it to your server and make certain that it compiles. you will see the feedback in the server console if you are using a web panel to operate the server then you will have a server console view there to look at
-
heya. if you didn't have it loaded for some time then it would have reset the times and started over again make sure you are updated to 2.1.6 as well double check that the default group has at least one permission (abandonedbases.basic, abandonedbases.veteran, abandonedbases.vip are the default perms) if no issue with the above then grant yourself abandonedbases.attack, abandonedbases.attack.time and go attack some bases to see the times on them you can attach your config here too
-
heya, sounds like fun! you can enable Eject Mountables Before Spawning A Base but there is no option for your second question. players are not allowed to be within the event area (Protection Radius) while the base is pasting until.the event starts there's nothing that would eject them when it despawns though. only when a new event is spawning
-
@Roofer hi, can you be more specific? when another player base is too close, or another abandoned base event? what do you mean by /sar doesn't work? does it do nothing, or does it give you a message? if you do not get any message then type /ab.debug and type /sar again. the /ab.debug command requires abandonedbases.admin permission
- 583 comments
-
- #rust
- #rust plugin
- (and 6 more)
-
heya. I'm well thanks I don't know of such a plugin it might be blocked by clientside checks and if so a plugin wont work you could try the new creative mode that Facepunch added and see if that allows it. if so then a plugin could be made to utilize that, possibly
-
hi, Allow Teleport will eject them after they reconnect and wake up if it is set false. there is no way around this except to set it to true. I will implement some workaround for it in the next update
-
Damage blocked to players if another raid is active
nivex replied to Ghosthunter's Support Request in Support
no, it is strictly for the hogging option -
Damage blocked to players if another raid is active
nivex replied to Ghosthunter's Support Request in Support
here is an alternate solution o.grant group default raidablebases.hoggingbypass -
Damage blocked to players if another raid is active
nivex replied to Ghosthunter's Support Request in Support
. -
@HAVOC805 you can either do it manually by editing the profiles within the oxide/data/RaiableBases/Profiles/ folder or by using a console command. example: rb.config add "Easy Bases" havoceasy1 havoceasy2 havoceasy3 rb.config add "Medium Bases" havocmed1 havocmed2 havocmed3 rb.config add "Hard Bases" havochard1 havochard2 havochard3 rb.config add "Expert Bases" havocexpert1 havocexpert2 havocexpert3 rb.config add "Nightmare Bases" havocnight1 havocnight2 havocnight3 etc replace the havoc file names with your new files, and take care to put them into the correct profiles respective by difficulty once you have completed this then you will need to remove the new profiles and use the existing above 5 profiles instead. otherwise it will still have a chance to spawn from the new profiles which you won't need anymore.
-
@HAVOC805 heya, all loot tables within the Difficulty Loot folder would be shared with all profiles of the same difficulty. no loot tables within the Base Loot folder are shared and will only work with a profile that has the same filename (RaidableBases\Base_Loot\Easy Bases.json will work with RaidableBases\Profiles\Easy Bases.json only) you have two options 1. move all of your new bases into the existing profiles so that they are all shared, or 2. create duplicates of the Base Loot tables and give them the same filenames as your new profiles
-
Damage blocked to players if another raid is active
nivex replied to Ghosthunter's Support Request in Support
what problem remains? it is not possible to get that message in PVP with the hogging options set to false ("<color=#FF0000>You must finish your last raid at {0} before joining another.</color>") what message are you getting and when exactly? -
Ive tried to use the bradley before but it wouldn't path properly if I implement a bradley that doesn't move then I will get endless complaints about it hopefully one day I can overcome the pathing issues
-
Damage blocked to players if another raid is active
nivex replied to Ghosthunter's Support Request in Support
yes, that is from the prevent players from hogging setting -
there are only a few steps required to get it spawning your own bases within a matter of minutes. you must have CopyPaste plugin installed. 1. download bases from Fortify, buy a tier package from me, buy a base package from third party sellers, or create your own bases 2. profiles are located in oxide/data/RaidableBases/Profiles or carbon/data/RaidableBases/Profiles/ there are 5 different profiles. put the filenames of your copypaste files into the respective profiles manually, or use the rb.config command. example: rb.config add "Easy Bases" raideasy1 raideasy2 raideasy3 3. edit the config from oxide/config/RaidableBases.json or carbon/configs/RaidableBases.json navigate down to Always Maintain Max Events and set it to true set Max Maintained Events to however many bases you want to spawn if no one is online then set Minimum Required Players Online to 0 4. save your files and reload the plugin. the bases will start spawning. they will use the Default Loot table (oxide/data/RaidableBases/Default_Loot.json or carbon/data/RaidableBases/Default_Loot.json) 5. read the documentation on how to set up your own loot tables. want buyable events with /buyraid? then set a cost under Buyable Event Costs (Economics Buy Raid Costs, ServerRewards Buy Raid Costs. Custom Buy Raid Cost) it's complicated to get everything exactly how you want it because there are so many settings. no guide is going to help you with that. you just need to go through each setting and set it to your servers specific needs. make a backup of everything as you go along setting it up. don't overwhelm yourself. take it 1 step at a time. if you get frustrated then take a break, and try again later. I can always answer your questions. that's what I'm here for.
-
oh, forgot #4 4. if the item spawns multiple times then it cannot stack a. if you see 10 stacks of 10000 then none of them will stack to make 100,000. they will be individual stacks of 10,000. this is not configurable. it wouldn't be worth the hassle, and it would cause a lot of confusion with fewer items in boxes b. if you see 10 stacks of 1000 then this is from #1, #2 or #3
-
heya. sorry, I missed your message somehow if you enable Always Spawn Base Table Loot then it will spawn before Difficulty Loot does. if you don't enable it then it will spawn both randomly. loot will spawn using 1. the stacksize amount set with the loot item (which is in the loot table, not some stack plugin). or, 2. if stacksize is set to -1 then it will use Use Stack Size Limit For Spawning Items from the config, or 3. if that isn't enabled either then it will use whatever the server allows
-
Damage blocked to players if another raid is active
nivex replied to Ghosthunter's Support Request in Support
Prevent Players From Hogging Raids and other will prevent you from trying to own more than 1 raid. I would need the exact message, from a screenshot is best and your config -
Damage blocked to players if another raid is active
nivex replied to Ghosthunter's Support Request in Support
heya, this hasn't changed Prevent Players From Hogging Raids is true by default Prevent Players From Hogging Purchased Raids is false by default -
Changed Status from Pending to Closed