RFC1920

Does your ruleset have Default Damage set to True? If so, you shouldn't have to add anything under block unless you want to. For the default ruleset, these are allow rules vs the default damage setting of False. For any other ruleset, you can set default damage to true to allow all damage EXCEPT for what you add under block. I am not sure if you can attach here, but please make a backup of your database and send it to me.

Have you selected a zone for the non-default ruleset?

I have noted that players can no longer dismount the piano, if that's what you meant. I am looking but so far cannot find a solution.

Perhaps /nomini ?

Were you killing a non-existent copter? Can you give some more detail about what you were doing when this fired?

Thank you. It is different than it has worked... ever. But, it made sense.

Changed Status from No Response to Closed Changed Fixed In to 2.1.5

This has been added in 1.0.47.

Changed Status from No Response to Closed

The only one I had seen that did that did so by attempting to pre-empt using its own timer to manage decay independently. I played with it for a bit and it was tedious and hurt performance significantly. Relocating the hook in oxide might be a better option assuming it can insert itself earlier in the process. Given time I will try to look into options for independently manage decay without killing the server. But, that is not a reality I have seen yet.

Changed Status from Pending to Not a Bug

If players put mats in their TC that match the building grade, then the plugin is not called, at least for that grade. We cannot currently bypass that and are dependent on decay being called in order to change it. You can mitigate some of that by preventing material placement of specific or all types in tool cupboards using NoDecay configs.

Changed Status from Pending to Work in Progress Changed Fixed In to Next Version

For the copters, you would need to set the multipliers for them. They won't actually get considered as part of the TC range at all.

Actually, tides are dependent on the moon, so night start and day end is closer to reality. However, the command for setting oceanlevel itself could be automated using TimedExecute if you like without Tides.

There are at least 2 ways now to automate this externally if you like. See the updated docs.

Changed Status from Pending to Closed Changed Fixed In to 1.0.3

Try setting the following if you want buildings to decay normally: "twigMultiplier": 1.0, "woodMultiplier": 1.0, "stoneMultiplier": 1.0, "sheetMultiplier": 1.0, "armoredMultiplier": 1.0, Anything else in the config you can set to 0.0 to disable decay for that type or 1.0 to enable normal decay. If you want things to decay faster than normal, set a number higher than 1.0. To protect entities in range of a TC, you will need to set: "requireCupboard": true, "cupboardCheckEntity": true, "cupboardRange": 30.0, Adjust the range as you wish, but it can also tend to overlap cupboards in range of your neighbors depending on how far away they are if you set it too high. Hopefully this is close to what you're requesting.

If you mean on server restart, then 1.0.2 hopefully fixes it. If you mean it won't load at all, please send any errors you can get from log files about Tides.

Please verify that the very first line of the plugin is commented out, or just download it again. Let me know.

However... I see you have 1.0.6 from somewhere anyway. Will look to see what I have pending for 1.0.7 to see if that has a fix.

Changed Status from Closed to Pending

Changed Status from Pending to Closed Changed Fixed In to 1.0.6

This must have been the first plugin I uploaded here and I have not kept up with the changes. Will be rolling it up to 1.0.6 one by one. Hopefully that version will work for you.

Glad to hear it.