-
Notifications
You must be signed in to change notification settings - Fork 14
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
Improve documentation please #34
Comments
I actually went and tested the following configuration:
Using this configuration vanilla admin commands are available to non ops. If I omit the commands bits, the vanilla permissions arent respected and vanilla commands dont work. Non vanilla command do work. I would think that the preferred method would be to not change anything unless explicitly asked to? Maybe im wrong. |
I would actually like to see the chat formatting only part of this released, if possible? I would pay $ |
Specifically, what are the default permissions for commands were I to just utilize the chat formatting, and forgo making any specific command rules, basically this:
I understand I can test this, but I feel like the default behaviour of this plugin isnt explained. Could a non-op use /spreadplayers for example? or a command block? Does it override the normal vanilla permissions in this case?
What if the commands bits was omitted completely? Would vanilla permissions take over?
Thank you. I like this plugin alot :)
The text was updated successfully, but these errors were encountered: