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.

Sign up for GitHub

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

Jump to bottom

Command invocations which start with valid commands thrown unknown errors #109

Open
finnbar opened this issue Jan 6, 2022 · 1 comment
Open

Command invocations which start with valid commands thrown unknown errors #109

finnbar opened this issue Jan 6, 2022 · 1 comment
Labels
IMPORTANT These are serious things to focus on

Comments

@finnbar
Copy link
Collaborator

finnbar commented Jan 6, 2022

.sayblah will cause an "unknown error", while .cube (or another command that doesn't exist) will correctly complain that "No command with that name was found!".
@L0neGamer
Copy link
Collaborator

Additionally, typing .sayblah's results in no error at all, despite it being an invalid command.

One way to "fix" this is when the bot gets an invalid error, no error is sent at all. If the first suggestion from #9 is implemented, an error can be sent if an invalid command is requested to this kind of prefix.

finnbar added a commit that referenced this issue Jan 28, 2022
@finnbar
Tiny fix for #109
f0de7ea 
For .sayblah, chunk was correctly consuming "say", but then we got an
unknown error when it tried to consume spaces
@finnbar finnbar mentioned this issue Jan 28, 2022
Merged
@finnbar finnbar added the IMPORTANT These are serious things to focus on label May 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
IMPORTANT These are serious things to focus on
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@finnbar @L0neGamer