Mr01sam
-
Posts
1,441 -
Joined
-
Last visited
-
Days Won
26
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Support
DOWNLOADS EXTRA
Services
Everything posted by Mr01sam
-
I do not have an ETA, but it is on the suggestion board!
-
If you click on Info and then go to Owners, who does it say the founder is?
-
I can look into this, but before I do, could you post your config or a screenshot of your admin panel? I want to verify that you have PUBLICCONTAINERS set to be lootable - thats what vending machine shops fall under.
-
@beetle this plugin is still updated! Just no support tickets have come in yet, so I wasn't aware of any issues. I can take a look into this. You are correct, in that if the item is left on the corpse, it should not be marked LOOTED. Same for dropped backpacks. -
You mean like if you upgrade using a TC upgrade plugin?
-
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.
-
Thats going to be really difficult, however if you know the users that were authed on it you can try to find it within the ProtectedCupboards.json within the data folder. If you CTRL-F for the steam user id of the player, you might find them amongst the OwnerUserIds. Destroyed tool cupboards do get removed from here though, so its a good chance it wont be in there - but worth a shot perhaps. -
I appreciate the support! Yeah, that's a difficult scenario to remedy, the best option (currently) is to have it be a server policy to forbid such a thing - just like many servers may forbid grouping more than X players. I do have a couple ideas in mind for the future - for example, we could make it so PVE players cannot pick up items dropped by PVP players (and vice versa) which would make it much more difficult to trade items cross modes. Again, this wont solve this in all cases (no solution will), but if you have other ideas I'd be open to them 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
-
Yes, in the config file you can set this setting to false
-
Does it still occur if you reload Raid protection?
-
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:
-
Authorize friend dont add players to raid protection
Mr01sam replied to mark bergervoet's Support Request in Support
Changed Status from Pending to Closed Changed Fixed In to 3.4.15
