nivex

medium, hard and expert don't have a difficulty configured easy and nightmare do

hi, zip the config and oxide/data/RaidableBases folder and DM me it

oxide may have reset the settings if that's the case you can first try by changing the difficulty back to what it should be oxide/data/RaidableBases/Profiles on the very first line,

good! I'll have to remember that one

hi, config: Lock Treasure To First Attacker Bypass Lock Treasure To First Attacker For PVE Bases Bypass Lock Treasure To First Attacker For PVP Bases Lock Raid To Buyer And Friends profiles: Eject Enemies From Purchased PVE Raids Eject Enemies From Purchased PVP Raids Eject Enemies From Locked PVE Raids Eject Enemies From Locked PVP Raids

I sent debug version in DM It will log the despawn reasons to oxide/logs/RaidableBases/despawn I advise you do not make any mention of this debug logging to anyone and just send the log when the issue happens again someone could be causing this to happen and we must find the exact reason without any interference

07/08/2023 17:48:31 Spawning raidmed7 N/A (0) @ R25 (547.9, 1.0, -1706.5) 07/08/2023 17:48:31 Init raidmed7 N/A (0) @ R25 (547.9, 1.0, -1706.5) 07/08/2023 17:48:31 Spawned 143 raidmed7 N/A (0) @ R25 (550.0, 0.0, -1700.0) Despawned 07/08/2023 18:55:16 Despawned raidmed7 vakoaa (76561198278424826) @ R25 (550.0, 0.0, -1700.0) 3 minutes later he responds 18:58 [Info] [Better Chat] [Global] [Player] vakoaa: same problem again, base disappeared during raid there are no problems shown in any logs. I will add some debug for you and send this version for you to use

ok

how many minutes / hours ago did this happen?

nah, the oxide log

Ok, that looks fine attach the oxide log

hi, attach your config using the button below

ya you should update manually from this site and not from umod no problem!

as I said, you have the free version installed

you need to install the premium version from this site. installing the free version removes all of your premium settings so you have a few options: 1. reinstall the package if you didn't edit much 2. reinstall the config or profiles from the package only 3. or you must redo the premium settings after reinstalling the premium plugin this is common with auto updaters and plugin managers - they should never be allowed to update this plugin either way, the difficulties are not configured because they don't exist, and they will default to 0 (Easy) when you do install the premium version

you have the free version installed

.

.

you will have to set the difficulty in the profiles oxide/data/RaidableBases/Profiles/

Changed Status from Pending to Closed

i understand that. but as I said, it is for those commands and the buyable cooldown only. regardless, good luck

that permission has no relation to damage raidablebases.allow permission is only for /rbe, /rbevent, /rb savefix, /rb tp, and buyable cooldown in the config

if it's blocked then another plugin is blocking it. they should not be given allow perm either - that is strictly for admin rights to the plugin, and no perms are required to deal damage

Changed Status from Pending to Closed