-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support new execute command #450
Comments
In order to support this, we need some way of supporting recursive command arguments, e.g. chain of as, at, unless and run in |
I've been thinking about how to implement the new |
How exactly would this work? I understand we could introduce |
“requireCommandPrefix” would look at the last command that was used, not the last argument the user typed.
|
oh I see, but how would this let us choose when to begin the chain within the command? |
An alternative would be to add a dedicate system for subcommands... {
"commands": [
{
"commandName": "execute",
"arguments": [
{
"type": "subcommand",
"allowMultiple": true
},
{
"additionalData": {
"values": ["run"]
}
},
{
"argumentName": "command",
"type": "command"
}
]
}
],
"subcommands": [
{
"commandName": "execute",
"commands": [{...}]
}
]
} |
I think this won't be a big problem but I believe my latest proposal probably still makes more sense |
I like this format 👍 |
Available as of 1.19.10.20
The text was updated successfully, but these errors were encountered: