nivex
-
Posts
5,889 -
Joined
-
Last visited
-
Days Won
199
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Services
Downloads Plus Support
DOWNLOADS EXTRA
Everything posted by nivex
-
@beetle glad you enjoy it here's the fix. on line 10592 in the .cs, change: VendingMachine vm = GameManager.server.CreateEntity("assets/prefabs/deployable/vendingmachine/vendingmachine.deployed.prefab", Location) as VendingMachine; to: VendingMachine vm = GameManager.server.CreateEntity("assets/prefabs/deployable/vendingmachine/vendingmachine.deployed.prefab", Location.WithY(-400f)) as VendingMachine; -
@beetle I see. it must be the vending machine created by the Explosive Costs then so not a copypaste issue no problem ill fix it next update. I can give you the fix tonight
-
@beetle paste the base with /paste to verify it happens again then yes report it
-
@beetle i don't think rb would change its position. that should be copypaste
-
@Roofer I added multi-TC support, so 400 radius will not work unless it is away from all TC owned by others. you can still set Sphere Amount higher to darken the bubble, but I would not set it too high because it would impact performance. -
@Kk the IQTurret author needs to modify his plugin. IQTurret needs to add the entities as a child or parent them. IQTurret is spawning those entities, so it is responsible for removing them too. if it adds them as a child or parents them then they will despawn when the turret is killed. which includes at the end of the event.
-
@Kk hi, IQTurret needs to add the entities as a child or parent them.
-
@Roofer heya, 400 radius is way too large. the plugin will not function properly with such a large radius. the maximum radius should be around 75
-
@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
-
@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
-
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.
-
@LeaF_ heya. you put the plugin into the plugins folder like you would any other plugin no, you must configure the plugin yourself and provide your own copypaste files, or you can buy a tier package. please read the documentation and watch the video too see my next post
-
@muhendisbey hi, the base was not copied properly. you need to /paste and /copy it again if someone modified height settings in the profiles then that could cause it too. otherwise recopy the base.
-
@Chloe_Glano can you send be the base? not having an issue with new door controllers here
-
@Chloe_Glano ok, I will take a look tonight then @Raiven_007 hey this is what it is:
-
@Chloe_Glano yes, copypaste issue. the fix is to paste the base, replace the door controller, and copy it again. it will work with new door controllers only. its possible for the copypaste developer to add support for old controllers but easier to replace the old.
-
hi, that's a copypaste plugin issue iirc
-
Released 2.9.2 to resolve issues with players becoming stuck on mounts at events, sam sites not targeting mlrs rockets, collection modified errors, and issue with base loot when more than one profile exists with the same difficulty enjoy damn bugs squash squash
-
@sykosmurf heya. base will despawn when the plugin unloads or the server restarts, but you can enable Wait To Start Despawn Timer When Base Takes Damage From Player in the config file so they remain until then, or until someone attacks the event edit: plugin, not player, lol
-
@Kobani heya, Allowed Zone Manager Zones will allow the bases to spawn in those specific zones, and anywhere else on the map but if you enable Use Grid Locations In Allowed Zone Manager Zones Only then it will force every base to only spawn there you would not need spawns plugin with the last option @HunterZ thank you. good to know that it works well.
-
Released 2.9.1 to resolve issues with elevator error spam and bases not spawning inside of Allowed Zone Manager Zones if you have zones, and you want bases to spawn in those zones, then you must add them to Allowed Zone Manager Zones in the config file. alternatively, if you want bases in zones only then you may enable Use Grid Locations In Allowed Zone Manager Zones Only enjoy
-
a quick note for anyone NOT using zone manager and bases do not spawn this means if you have Include PVE Bases set to false in your config and every profile has Allow PVP set to false then nothing is going to spawn because every profile would be PVE and you are excluding them all solution? set Allow PVP to true, or Include PVE Bases to true use Convert PVE to PVP if you want bases to be PVP regardless of the Allow PVP setting use Convert PVP to PVE likewise for PVE Include PVE Bases and Include PVP Bases are for servers that have profiles with Allow PVP set to true and others set to false. it's a more advanced setting whereas Convert settings are straightforward (and override Allow PVP setting in the profiles)
-
@Eddie Flats @Kobani the issue is something has broken with the Zone Manager support. I am not sure how to fix it but I am trying. I suggest removing Zone Manager Zones from your spawn points for the time being (just disable the zone in Zone Manager. you don't need to delete it) alternatively, if you move your spawns database into the profiles then you can enable Prevent Building Until Base Spawns and remove the need for Zone Manager entirely
-
2.1.6 has been released. It requires the Rust update to compile. Enjoy
- 634 comments
-
- 2
-
-
- #rust
- #rust plugin
- (and 6 more)
