-
Notifications
You must be signed in to change notification settings - Fork 41
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
No permission node for spectator mode #187
Comments
So you believe, the |
Only to the extent that spectator mode uses a seperate permission node. |
So how would you like the permissions to work? What permission nodes should there be, and what would their combination mean for the command? Ideally write out an entire table having all possible combinations of all the permissions involved, and the effects on the command. |
In order to keep to tradition with how Vanilla and Bukkit works...
If If And so on... |
I think there should also be core.gamemode.creative, core.gamemode.survival and core.gamemode.adventure. |
What @mohe2015 suggested could come in useful too, for those who want to be even more explicit on which modes a player is allowed to use. Plus, if you assign permission node |
The only problem with this is that there's now no single permission that would grant the |
Is there a workaround, or is this something for later? |
Why do we want more fine grained permissions anyway? I understand the appeal, but in what case would a player need to manually change their game mode to spectator? In a minigame, a plugin or command block can do it for players without any permissions needed. |
I highly believe that there should be a permission node for spectator mode, I have had situations where I am comfortable with giving someone access to /gamemode, but not spectator mode as they can go through walls, floors, anything!
The permission node should be
core.changegm.spectator
, however to be more tradition, you should change thecore.changegm
permission node tocore.gamemode
as it is more understandable.The text was updated successfully, but these errors were encountered: