This reverts commit 397a71a602.
Apparently this doesn't actually fix the issue. Some things
just straight up happen without sending events to plugins and there's
nothing we can do about it.
By the time this code is called, the performance hit happened already.
There's a separate way to whitelist these that still allows keeping
the protections active.
When worlds first load, events start happening before plugins normally
(POSTWORLD) enable. This means that regions and other protections won't
be active when these events are called.
This shouldn't break anything that depends on us, e.g. custom flags,
since our API contract already states that should be done on load,
and all plugins are loaded on startup (just not enabled).
Enderchests are not modified on use. In fact, they don't even
have inventories, so they are not modified at all. To deny usage,
the interact flag must be denied, since they most closely fit in
a category with other interact-covered blocks (and not use-covered
blocks, since using them does not change the region in any way).
This commit reverts f7d36b and ea4f4c0.
When set to allow, allows players to rotate item in item frames even if
they wouldn't normally have permissions to modify the item frame.
Fixes WORLDGUARD-3588.
* Send/receive chat and allowed/blocked cmd flags now respect deny-message flag.
* Added `regions.cancel-chat-without-recipients` option to disable the default behavior.
Apparently the spigot server stores time-lock between logout and login,
but not weather-lock. This should work around any such issues by
re-applying handlers on login.
* Start work on abstracting commands out of worldedit-legacy
* A lot more work towards abstract commands
* Move a lot of code to WorldEdit
* Setup the exception converter
* Use WorldEdit styling and move more of the RegionContainer across.
* Abstract away the debug commands and a few other things - Only the matcher to go.
* It compiles
* It now seems to run fine
* Fixed version typo