nivex

yes, you can spawn 1 event only and go to it then interact with the event and when the console spits conflicts then report what caused it that is how I fixed most of it already or you can try this DangerousTreasures.cs

no, in the .cs file line 16067

I can't help you with floating doors. that's from the CopyPaste plugin. ignore them

if (entity.IsKilled() || entity.ShortPrefabName == "item_drop_backpack") find that in the .cs and change it to this if (entity.IsKilled()) tell me if that solves it

it might be helpful to use ent who on some building blocks. they should always say 0 and if they don't then this might explain why this happens. otherwise I don't know without some way to reproduce it. Despawn Dropped Loot Bags From Raid Boxes When Base Despawns, this is in the profiles (oxide/data/RaidableBases/Profiles/) and I had people enable this as a workaround before. if this still works then let me know the log file option, Log Debug To File is useless. it always says the base was despawned when it wasn't. that means the despawn was called but it didn't work for whatever reason. server log might be helpful. if you don't know what a server log is then have your host help you find it or enable it if it's not enabled. logs are sometimes called log.txt, server.log, latest.log, and may be found in root server folder, /logs/2023/07/20/ for example. if you don't see any of those then your host must help you to enable it. these are not server logs. anything with oxide in the filename is not a server log either.

ok great ask your host to enable the server logs for you

hi. it's a needle in a haystack really. try this for easiest solution DangerousTreasures.cs

you haven't sent me the server log that is the oxide log and won't contain the full error. I don't know what is causing it without having the full error from the server log

hi, that is a warning not an error an error includes a message and stack trace. you have shown me the message above "NullReferenceException: Object reference not set to an instance of an object" but without the stack trace this error is not helpful

attach the log and I will find it unless you have restarted since then it's gone

hi, sorry to hear that. I would need the full error from the server log though. it should be called log.txt server.log latest.log etc and be in your server's root folder where the oxide and server folders are.

Changed Status from Pending to Closed

hi, I've responded to your other ticket. in short, no, it's not normal but I'll help you in the other ticket

Hi, floating doors that cannot be killed are a visual bug within the game client. you can ignore this as it's harmless and pertains to the CopyPaste plugin bases not despawning is a separate issue and is most commonly because 1. bad copypaste file 2. linux missing libgdiplus library 3. a bug 4. an error which I'd need the message for you can use the /rbe kill_cleanup command at any base this happens with to remove them I've closed the duplicate thread here https://codefling.com/files/support/8353-not-removing-old-bases/

hi, this is explained in the documentation under all 3 loot sections, and your question is too vague.

Changed Status from Pending to Closed

no problem. enjoy

disable Require Cupboard Access To Place Ladders in the nightmare profile

what does it say

no problem

hi, that plugin hasn't been updated in 5 years I've edited it so it should work with raidable bases now. edited to include support for pvp in raidable bases events, too NightPVP.cs

.