RFC1920

PreventLooting also adds the share and unshare commands. It's doable, but I'm not sure why one needs the be the monolith.

I usually use PreventLooting for that, which is why it's not included.

Please set the config variable useSchedule to true if it is not. If that clears it I have a fix.

On restart is there anything about this in the server or oxide logs?

This is not setup to work with that version. You would have to use the version from remod.org.

Changed Status from Pending to Closed Changed Fixed In to 0.3.0

Disable outputMundane in your config.

Changed Fixed In to 0.2.9

cctvcontrol.admin appears to allow it, even if the user is not in the admin group.

Well, it definitely works for some and nothing has changed to make it stop working that I know of. If you can do the check with logging enabled it would be helpful.

Looks like you are building blocked, which has nothing to do with this plugin.

If you have the config "usePermission": true, you must assign the permission to users. If you would rather just have it apply to everyone anyway, you can set that to false and reload.

Do they have the permission assigned?

It was a problem with sleepers and turrets afaik.

I am not seeing any issues. Perhaps another plugin is blocking it? If possible, type /nodecay log in chat, wait a couple of cycles (5-10 minutes) and paste some of the resulting log from nodecay (in oxide log): (17:09:14) | [Oxide] 17:09 [Info] [NoDecay] floor owner 7656119830@#04196 has NoDecay permission! (17:09:14) | [Oxide] 17:09 [Info] [NoDecay] NoDecay checking for block damage to floor (17:09:14) | [Oxide] 17:09 [Info] [NoDecay] NoDecay checking for local cupboard. (17:09:14) | [Oxide] 17:09 [Info] [NoDecay] CheckCupboardBlock: Checking for cupboard connected to stone floor. (17:09:14) | [Oxide] 17:09 [Info] [NoDecay] CheckCupboardBlock: Block owned by cupboard! (17:09:14) | [Oxide] 17:09 [Info] [NoDecay] Decay (stone) before: 0.8299426 after: 0 (17:09:14) | [Oxide] 17:09 [Info] [NoDecay] Decay (floor) before: 0.8299426 after: 0, item health 500

BC, you need to update to 1.0.9.

For example: Decay (1module_cockpit_with_engine) before: 1.967593 after: 0, item health 84.13244. Unclear what is not working. As for the building parts, it appears to be still working for me.

Changed Fixed In from 1.0.49 to Next Version

whoops

Changed Status from Pending to Closed Changed Fixed In to 1.0.49

I have added a new check for the vehicle parts in 1.0.49.

Changed Fixed In to Next Version

If the data file contains only the word null, then that was an error that crept in from the previous version. If that is the case then delete the file manually. Otherwise I do not understand why this is happening.

Then it cannot possibly ever be explained... I guess.

Well, not exact overall. If it isn't these two conflicting it could certainly be another plugin. This hook is one of the more common ones and a lot of plugins use it. Working from the case of only these two and adding others one by one might be the only way to be sure where the problem starts.