Is it possible to add a similar overload for the command? about levilamina HOT 24 CLOSED

Certainly you can add an enum argument

from levilamina.

Maybe #115 can help you

from levilamina.

No, you misunderstood me. I meant no <name: type> argument, just text like "add" and "stop".

from levilamina.

argument <op: string>?

from levilamina.

for example, the camerashake command has two overloads: the first "add" and the second "stop".
"add" and "stop" do not have <op: string>, they are just text without <> and [].

from levilamina.

This may not be possible

from levilamina.

For example, MC's /gametest is the same,

from levilamina.

I hope there is a way, because without this it is impossible to beautifully implement different functionality for one team.

from levilamina.

this?

from levilamina.

You can refer to this paragraph

from levilamina.

yes, thanks! I'll try it now

from levilamina.

seems to work, but very strange.

here is my command:

and whatever I enter, the parser throws me on the inspect overload:

Upd: I guess the parser has priority for short commands ...

from levilamina.

With two String, BDS can't tell if it's the first or the second. This is no longer part of the LL discussion.

from levilamina.

Please use back to enum, this may also be the reason why BDS uses that method internally

Sorry I couldn't help you.

from levilamina.

thanks for trying to help.

I hope that soon it will be possible to add something like "names" to overloads, like add & stop in camerashake, etc.

from levilamina.

No, you misunderstood me. I meant no <name: type> argument, just text like "add" and "stop".

you should call CommandParameterData::addOptions()
for example:

from levilamina.

I'll now try it

from levilamina.

what is the CommandParameterOption? what heading is it in?

from levilamina.

add enum CommandParameterOption in your code

from levilamina.

ok, but it doesn't solve my current parsing problem.
or am I missing something?

from levilamina.

• [TODO] BDS CommandRegistery API Docs

from levilamina.

Sorry i didn't get the gist of addOptions() yesterday.
Today I figured out what you advised me, and everything works, thanks!
I think the question can be closed (but the documentation for the CommandRegistry API will still be useful).

from levilamina.

Thank you for your reply. Documentation will be available as soon as possible

from levilamina.

Thank you for your reply. Documentation will be available as soon as possible

How to make the parser work adequately with different arguments in 2 overloads?
For example:
/cmd
/cmd enum
And if I enter /cmd enum, then it would choose enum, and not the first overload option?

from levilamina.