I am seeing this in my console:

Calling hook CanLootEntity resulted in a conflict between the following plugins: PreventLooting - False (Boolean), LootDefender (True (Boolean))

BetterDeadThanZed

You said that Prevent Looting should return true and I have no clue what that means. I assume that the dev of that plugin will need to do something.

The Prevent Looting plugin dev will need to make the CanLootEntity hook return true. They will know what this means if you show them the error.

For context, plugins can use hooks to tell Oxide to skip a particular section of Rust code and substitute a prescribed value into a variable to achieve some desired behavior. When two plugins are called for the same hook and provide different values, this is considered a conflict and Oxide picks one of those values, which can result in undesirable or unpredictable behavior. To resolve, one of the plugins will need to be updated to basically return the same value as the other, or no value if the event context is not relevant to the plugin (for example, return false to block looting, true to force allow, null if you don't care). There are multiple ways to avoid a conflict, one being that the plugins could directly talk to each other, but the most common solution is to just write smarter logic that deterministically avoids the conflict. Most commonly, one of the plugins was just coded incorrectly and needs a simple change. As long as the dev of that plugin knows the correct value their plugin needs to return, they can figure out the code changes to get there.