Replies: 2 comments
-
Commands were rewritten at some point and argument callback is currently missing its implementation. I created #1959 from this to track it |
Beta Was this translation helpful? Give feedback.
0 replies
-
@Ynverxe I also noticed this issue, as a workaround you can catch it inside the global exception handler. Btw, I didn't like the current command system for this and other reasons so I developed my own replacement. I think that changes to the current system are bound to be slow given the high cost maintainability |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I was programming a custom command and after a while I see that the ArgumentCallback is never executed when the argument could not be parsed but rather the default executor of the command is executed. This also happens with the test command published on the wiki. (I tried it)
https://pastebin.com/AqUxr9ms
Beta Was this translation helpful? Give feedback.
All reactions