Is it possible to add a similar overload for the command?

[KocTu4eK]

Is it possible to add an argument like this "add" and "stop" to the command overload?

[KocTu4eK]

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

[KocTu4eK]

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 [].

[dreamguxiang]

This may not be possible

[dreamguxiang]

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

[KocTu4eK]

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

[dreamguxiang]

this?

[dreamguxiang]

You can refer to this paragraph

[KocTu4eK]

yes, thanks! I'll try it now

[KocTu4eK]

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 ...

[dreamguxiang]

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

[dreamguxiang]

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

Sorry I couldn't help you.

[KocTu4eK]

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.

[xiaoqch]

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

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

[KocTu4eK]

I'll now try it

[KocTu4eK]

what is the CommandParameterOption? what heading is it in?

[dreamguxiang]

add enum CommandParameterOption in your code

[KocTu4eK]

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

[KawaiiNahida]

• [TODO] BDS CommandRegistery API Docs

[KocTu4eK]

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).

[dreamguxiang]

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

[MCBEPluginModer]

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?