Mr01sam

Changed Status from Pending to Not a Bug

All good man - for anyone else, this is fixed with 3.4.16

Changed Status from Pending to Closed

We found that the solution to the original problem was to set "Damage resets timer when owner is offline" to "false"

I'll try to get it reproduced - thanks!

Its going to be hard to find that TC if its destroyed (I responded to your post with something you can try). In general, the /tc command (if you're an admin) has some helpful things. It will list out a bunch of commands. Specifically the /tc id command will tell you the ID of the cupboard you are standing within the area of, you can also optionally /tc id <playername> which will do the same thing, but will tell you the TC at the location of the specified player (useful if you want to do it from the server console). Once you have the id, you can do things like /tc protection <id> which will tell you all sorts of details on the current protection. If you want more of a "history" of the protection, you can either Enable Logging or Enable Ledger, both will give you an idea of what occurred with a tool cupboard. The ledger mostly gives info related to the protection balance, and lets you perform rollbacks. The logging gives you a lot more info, but I dont recommend leaving it on for large servers (unless you have a lot of storage space) because it will generate a lot of files. If you choose to use the logging, they get saved to oxide/logs/RaidProtection and are organized by TC for each day. It should give you pretty detailed info on what happened to each TC and when. If you're not sure which TC, but you know what day, you can narrow it down to just those files. Unfortunately theres no an easy way of finding a specific TC if you dont know the ID.

I'm not sure at this moment, do you have any other details, does this happen all the time? Or just sometimes?

Hey! Would you able to give me a full list of the things you found that aren't protected? Also, if you could share your config settings that would be helpful as well.

Changed Status from Pending to Closed

Hey! I'll plan to add this as default - but in the meantime you can specify specific entities to not trigger raids in the config. You can find a list of short names here: https://github.com/OrangeWulf/Rust-Docs/blob/master/Entities.md

You're correct that should not be the case

Changed Status from Pending to Not a Bug

In order for the "pro" command to work the player using it either needs to be an Admin OR they need to be one of the players authed on that cupboard. Non-admin players cannot use the command on bases they are not authed for. Also, if there is no building priv where they are standing, the command wont do anything.

Changed Status from Pending to Not a Bug

Refresh your config - the default images are hosted on another site now:

Changed Status from Pending to Closed Changed Fixed In to 3.4.15

If the kit gives an item (that the player then places themselves) thats fine. Its only TCs that are spawned in by a plugin that could be an issue. If you DM me I can hook you up with a plugin that can let you see the IDs, if you dont have one already.

If you have some kind of plugin that allows you to look at details of an entity that would be helpful. My guess is that the owner ID of some tool cupboard is 0 (it should be the id of the player who placed it), sometimes if the tool cupboard was spawned by another plugin (like raidable bases or something) it might be 0. Is everyone having this issue?

Just did the exact same thing a second time and it didnt glitch out

Okay, so I just tried to reproduce it and this is what I'm seeing. I am PVE, I entered a PVP zone and then died and respawned and this is what I see: From what I can tell I am correctly set back to my original PVE, but for some reason simple status seems to be glitching out and showing both modes (even though I am truly in PVE). Could this be what you are seeing?