Add more information to UnknownCommandEvent

[NonSwag]

Is your feature request related to a problem?

When working with the UnknownCommandEvent there is no safe way to detect whether a command failed because of syntax errors or because it doesn't exist, or the sender has no access to it

Describe the solution you'd like.

Adding a method to check whether the command failed to parse or cannot be performed and maybe even the command instance

Describe alternatives you've considered.

Checking if the command exists and whether the sender can perform that command (doesn't work reliably on brigadier commands)

Other

No response

[electronicboy]

"syntax errors or it doesn't exist" is generally considered the exact same thing by the brigadier dispatcher, I don't think that there is much that can be exposed here which wouldn't involve us trying to inject that sort of context, which has no real safe way of passing that info up anyways...

[NonSwag]

Technically there is a difference
the root command node in the unknown or incomplete command message is red if the sender can't use it or the command doesn't exist
if it does and the sender can use it the label is gray and everything after that is red, so there is definitely an internal difference

[electronicboy]

But that is purely derived on the basis of the pointer, it's not an actual state of "this did not exist" that is passed up

[Machine-Maker]

Every command that doesn't execute successfully is an unknown command. I could easily just make a command for which the values entered did successfully execute. There is no difference between an unknown command and invalid syntax.