/killall permission granularity #4189
Unanswered
dublindevil
asked this question in
Ideas and Feature Suggestions
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Problem:
With the /remove and /killall command, there is only one root permission node of essentials.remove. There is no permission node to grand or revoke certain targets such as "named" or "all".
Another minor issue is that there is no permission to specify world based or radius based killall, so a player has the capacity to /killall boats rather than only being able to do it in a certain radius.
Solution:
Add more granular permission nodes such as essentials.remove.all and essentials.remove.boats etc.
Add a permission node to specify if the player is allowed to /killall in a radius or in a world, perhaps with a config option for max radius
My Use cases
Allow a player to ONLY killall drops in a set radius
Allow a player to ONLY be able to killall/remove boats and arrows in a radius
Beta Was this translation helpful? Give feedback.
All reactions