nivex

you're welcome. you can always add flat terrain or islands to your custom maps so RB has space to spawn at. this comes with its cons though, if you allow players to buy raids and your islands are all taken by events then those purchases can still fail. so you would need to add 5 islands + however many for purchased events, or simply use a better map to avoid that mess. RB will be able to spawn in much tighter areas soon, but of course the required terrain will always depend on the size of the base. good luck.

heya, copypaste files in the oxide/data/copypaste folder the folder needs to be lowercase, copypaste, not CopyPaste the files need to go into that folder, not sub-folders within it

heya, then it's not installed properly. follow the instructions in the tier 3 package's zip file. everything needs to be installed into its respective folders on your server. so if a file is in the oxide/data/copypaste folder then it belongs in the oxide/data/copypaste folder on your server too. install latest CopyPaste plugin from uMod, this is required. o.reload RaidableBases if installed properly then bases will automatically spawn when at least 1 player is online. /buyraid must be configured first. you can configure costs for this in the config under Economics Buy Raid Costs, ServerRewards Buy Raid Costs or Custom Buy Raid Costs. automatic events are not the same, then run independently and automatically already.

177 potential points is not sufficient, and would explain why only a couple bases spawned. you need at least 1,000 potential points. those are not spawn points, they're potential points and most of them are clusters. in short, you need a better map. the plugin is dependent on the map having sufficient terrain, either that or the config is limiting the available space too much which is why I asked for the config your rbe debug is one continuous repeat of the previous output. it should collect data for a few minutes, be toggled on to show output, then toggled back off. it's not useful here though, the 177 points is the exact reason it doesn't work.

heya, nothing changed regarding this in 3.2.0 send me your config and I can take a look.

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

this particular bug is limited to weapons. my npcs only try to cycle weapons, so armor would be something else you're welcome. still working on a couple nav issues with the npcs then I will release the update.

this means you can still allow players to loot the sleepers if you want but the lootable option will be fixed in the next RB update, and you can continue using the Kits plugin with the next RB update as well.

hi, so it's RB causing this. Kits just triggers the bug so it appears as if it's causing it when it's not. though this does not happen on my end, "plus have a heavy scientist suit over whatever armor was already being worn" and clothing works normally. my npcs periodically try to equip and hold an item: the issue is that they're trying to do this when a player has taken those items from them, so the player ends up holding the items instead. it's fixed in the next update.

yes, it is affecting everyone. I am working on fixes =] this fix is done already, I am working on a separate issue before releasing it.

please do not attach the files here, send in a private message. if you can zip/archive them all together that would make it easier =]

heya as mentioned, the lootable option is fixed in the next update. this option will not fix your issue, it can only prevent it. like turning off the water to a leaking pipe, the leak (bug) still needs repaired or the pipe replaced. I see nothing in the Kits plugin that could cause this to happen. my understanding from your initial report is that a person's inventory can contain 2 items in the same exact inventory slot. seeing two different weapon models is normal, having two different items equipped in the same slot is not. that requires something to bypass the game's native inventory/wear validation, such as another plugin overriding CanMoveItem or CanWearItem. neither of which is used by the Kits plugin. the Kits plugin contains CanWearItem, but not as a hook, only as an internal helper method. send me the configs, data files and plugin .cs files for all 3 plugins in a private message. Kits, RaidableBases and CopyPaste. if I am unable to reproduce with your exact files, then the issue is still caused by another plugin (or harmony mod). either way, I don't mind helping you locate this issue. it's interesting enough =p

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