Closed raffel080108 closed 1 year ago
The problem seems to be the amount of arguments - If I remove one (or more) arguments, the command works perfectly fine. I tried removing different arguments and the result was the same
yes, it's an internal issue. I believe its related to optional arguments
fixed with b2b5333 will be included in alpha.3 release
I have this command (I replaced the actual command logic with some basic test printing, to make sure it's not an issue on my end)
When trying to execute the command an exception is thrown
As said, in it's current form, the command does nothing but print a value and reply with a random string, so it has to be something with the command itself that is going wrong... This is the entire debug log: