nivex

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

heya, yep, I've commented on this in the discussions. I am working on fixes for it

heya, I will fix the lootable sleepers option again noclip or vanish will still bypass this option once fixed. the glitch is caused by another plugin. the fix for the lootable option will prevent it from happening, but it won't fix the plugin that caused it to happen.

Changed Status from Pending to Closed

hi, glad it works. you're welcome, enjoy

Changed Status from Pending to Closed

hi that's great. you're welcome, enjoy:)

heya, you just need to enable a cost. you can use economics, server rewards or a custom cost like scrap. this is in the config file

you're welcome. we'll see what happens. I'm glad it's working for you now. you can use the imported workshop skins file in the RaidableBases data folder. you can add unapproved workshop skins so long as they're not sold or gated by Facepunch. plenty of those here. https://steamcommunity.com/app/252490/workshop/

this is the product page: https://codefling.com/plugins/raidable-bases this is a direct download link from the product page: https://codefling.com/plugins/raidable-bases?do=download I can confirm it is 3.1.9 and does not contain the errors from your first post, those errors are specific to version 3.1.6 if you have different errors post them and I can take a look

.

hi, the TOS option is disabled, and Skin Everything is enabled. that reskins my turrets and breaks their functionality. neither PVE nor PVP work as intended even though PVE appears to. set this to false in your config: "Skin Everything": false, this is the only solution at the moment. I may allow turrets to be skinned but its doubtful, or I may prevent the plugin from skinning them. undetermined at the moment

hi, the new version does not have those errors. if you are seeing them then the old version is being reinstalled each time. delete the previous RaidableBases.cs file and download a fresh copy.

heya, I tried your profiles and they're working fine on my end. there is one option that intentionally does this: Traps And Turrets Ignore Users Using NOCLIP there is no functional difference between PVE and PVP using noclip upon entry = ignored toggling off noclip after ignored will not clear the ignore. you can clear an ignore by attacking the turret you can clear an ignore by re-entering the event beyond the turrets trigger range, which you have set to 30 and 55 respectively tested and working if it's not this option then it's another plugin. ;/

no worries.

heya, you need to update the plugin. those errors are from an older version

hi, what pve plugin are you using? sounds like another plugin blocking it

hi, did you disable it in your in-game map then? don't know what else it would be if not that. it's definitely not broken

heya, its working here how do you have it configured? "Map Markers": { "Marker Name": "Raidable Base Event", "Radius": 0.35, "Radius (Map Size 3600 Or Less)": 0.25, "Use Vending Map Marker": true, "Show Remaining Loot When No Owner (PVE)": true, "Show Remaining Loot When No Owner (PVP)": false, "Show Owners Name on Map Marker": true, "Show If Purchased On Map Marker": false, "Use Explosion Map Marker": false, "Create Markers For Buyable Events": true, "Create Markers For Maintained Events": true, "Create Markers For Scheduled Events": true, "Create Markers For Manual Events": true },

heya, you would need to fix your Steam issue, or neither plugin will be able to spawn the base. RaidableBases will only allow 15 minutes before it despawns it. suppressing the errors wouldn't fix your Steam issue, but it is null checked in the next update anyway.

heya, that command would remove the difficulty. use rb.difficulty add instead rb.difficulty add "Colosal" this will create the profile: oxide/data/RaidableBases/Colosal Bases.json add the bases that you want to use. example: rb.config add "Colosal Bases" colobase1 colobase2 colobase3 set the options in the "Colosal Bases" profile: oxide/data/RaidableBases/Profiles/Colosal Bases.json copy a loot table from an existing difficulty and rename it. example: copy oxide/data/RaidableBases/Difficulty_Loot/Nightmare.json to oxide/data/RaidableBases/Difficulty_Loot/Colosal.json setup the options in the config file, and configure a cost. example, set Colosal under Economics Buy Raid Costs to 20000. reload the plugin. o.reload RaidableBases c.reload RaidableBases wait for the grid to load type /buyraid after the grid has loaded voice chat won't make this any easier, the steps above are all that is needed. copying an existing difficulty loot table and/or profile after the difficulty has been created is much simpler than trying to create or edit it from scratch.

heya, not a bug, someone added that to the config Difficulty Colors (Inner) and Difficulty Colors (Border) are the only two options with that name ensure those exist and delete or rename the other back to its original name