-
Notifications
You must be signed in to change notification settings - Fork 76
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Regarding allow-block-place & deny-block-break flags #226
Comments
Can you please provide an example what is defaultly needed to get basic interactions working again after doing this? If anyone ever stumbled upon this, just try it in a world first where you really need this and enable the worldguard permission feature just in the right world config.
This are just the permissions needed to allow an user to fight, drop and pickup items and place tnt in an wg region called mobarena1. Maybe they aren't even enough... Also do not forget to do Maybe they aren't even enough, but i figured them out the hard way with a second player Edit: Also do not forget to set the following to true in the
|
TL;DR: If you are interested in these flags, thumps up EngineHub/WorldGuard#1690 to prioritize the issue. Do not spam the issue.
Originally the plugin supported allow-block-place and deny-block-break flags. Unfortunately these flags had to be removed due to the breaking changes made in Spigot for the Minecraft 1.13 release and more unfortunately these changes were inconsistencies between different APIs. These changes forced some internal changes in WG 7 which ultimately breaks the way WGEF was overriding WorldGuard's decision on whatever the block placement was successful or not. For more detailed technical explanation of the problem you can read the #152 (comment).
This lead to bugs like #152 where the plugin broke WG's protection in certain cases and there is no easy way to fix this in the plugin itself without opening can of worms and resulting to even more bugs related to these flags in the future. This would burden both the EngineHub's team who receive complains about regions misbehaving and mine trying to track them down.
Due to the complexity of dealing with block specific actions its best to implement this natively in the WorldGuard itself. The best course of action is to upvote EngineHub/WorldGuard#1690 to prioritize the issue. Please do not spam the issue. Leaving a thumps up is enough.
Workaround
You might be able to take advantage of permission context (https://luckperms.net/wiki/Context) with the help of the extra contexts extension (https://github.com/LuckPerms/ExtraContexts) and combining these with build permissions or plugins like Essentials to allow/denying placing specific blocks by permissions.
The text was updated successfully, but these errors were encountered: