RFC1920

I see what you're saying. Something has obviously changed so I am looking into it.

Please post relevant logs. Also, is this persistent or only when certain things are happening such as attack or other damage?

By the way, it doesn't unload the plugin(s) but can disable/enable them.

Added to 1.3.0/1.3.1

Changed Status from Pending to Closed Changed Fixed In to 1.3.1

When I walk up to a button I own, I type /share. This replies with "button shared with all." This is with button -> true in the config.

Changed Status from Pending to Closed Changed Fixed In to 1.0.19

Changed Status from Pending to Gremlins

I think you need to enable the trap_npc rule as an Allow in the default ruleset. Do this by clicking on any of the boxes under allow, look for trap_npc, and select it.

Yep, typical bonehead check, but of course I saw no errors here. Should be good in 0.4.4.

Changed Fixed In from 0.4.3 to Next Version

Changed Status from Pending to Closed Changed Fixed In to 0.4.3

Changed Status from Closed to Pending

Changed Status from Pending to Closed

I would recommend that you create this yourself using one of the help screen plugins such as Infoscreens.

Changed Status from Pending to Closed

Changed Status from Pending to Closed Changed Fixed In to 1.0.19

Changed Status from Pending to Not a Bug

Possible but not likely any time soon.

Changed Status from Pending to No Response

By the way, work is in progress on this and some other things.

As long as the foundations are actually attached to the structure where the TC exists, there should be no problem as long as the player shows that they have building privilege in that area. If the building is huge, they may need additional TCs. At least I think this is still a thing. If the building is not huge but has several adjacent but disconnected structures, you could try enabling useCupboardRange to go back to the OLD way of measuring the distance to the TC instead of building privilege. This uses cupboardRange to set how far away from the TC to have impact. It sounds like another plugin or dll or custom map setting might also be interfering, because this is not a typical problem.

Changed Status from Pending to Closed

What should be easy at least as a bypass, is to add the following to your LootProtect.json: "Rules": { "button": false, So, under the existing Rules section, add "button" with value false (no quotes). This should prevent the plugin from blocking access. You can also, as admin, run "/lp log" from chat to enable logging, then check the server log while accessing the button before and after the change. You could also try setting the value in LootProtect.json to true and see if that lets you manage access via /share.

Glad to hear it.