willkroboth

Currently waiting on `dev/command-build-rewrite` (currently https://github.com/JorelAli/CommandAPI/commit/1011fd52c31117c06826ae0f32cdb0365f1807a4 to https://github.com/JorelAli/CommandAPI/commit/22c2ffac8b4ac9f3e0ac47f63cbe82c88729e44d). I believe the changes there will allow the `InitialParseExceptionArgument` to become NMS independent _**and**_ platform agnostic.

Just a note that the command you implemented seems to have similar functionality to the `FlagsArgument` proposed by #483. Development on that is currently in progress on the `dev/command-build-rewrite` branch...

Yeah, subcommands are converted into `LiteralArgument`s, and you can't control the suggestions of literal arguments. However, in this case, you _could_ use a `StringArgument` instead with a [`CommandTree`](https://commandapi.jorel.dev/9.2.0/commandtrees.html), like so:...

I think delegated properties are still syntactic sugar for `CommandArguments#getUnchecked`. You could still accidentally put the wrong class, and you wouldn't know until runtime when there's a `ClassCastException` or something....

Are you able to provide the full server log using a site like https://paste.gg/? Just running a Paper server while registering commands doesn't have anything coming up for me. The...

I wonder if this could be added for Java as well. If I add this method to `AbstractCommandTree` and `AbstractArgumentTree`: ```java public Impl then(final N tree, BiConsumer consumer) { this.arguments.add(tree);...

Continuing the off topic, but it's fine :P > and it seems to make sense to use Optional Argument in 'thenNested()' after implementing #529? So, the thing about optional arguments...

I can't use the original test plugin, since the changes made by #8235 are currently incompatible with the CommandAPI (https://github.com/JorelAli/CommandAPI/issues/554). However, using #8235's API like so: ```java @Override public void...

I tested the original `TestPlugin` with an updated CommandAPI plugin that works with #8235, and verified that the orginal comment of this issue has been resolved.

I don't know if this is mentioned anywhere in Luckperm's documentation, but I discovered that at the literal bottom of the config file, they have a `resolve-command-selectors` option. If you...