Skip to content
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 response to commands violating restrictions #38

Closed
Davnit opened this issue Mar 7, 2017 · 0 comments

Comments

@Davnit
Copy link
Collaborator

commented Mar 7, 2017

Specifically observed with the /add command when trying to add a user with a flag that you don't have permission to. The command processor expects each restriction to specify an error message to be used when it is violated, but none are defined for this command. Other commands also likely lack these elements.

My suggestions:

  • Have a generic "access denied" message sent when commands.xml does not define its own message.
  • Allow a command to define a single error message to cover all of its restrictions.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
1 participant
You can’t perform that action at this time.