Command syntax help doesn't handle optional argument chains correctly
To reproduce
- Type in /particle crit ~ ~ ~
- Add a space
- Hit esc
- Look at the command syntax help: [<delta>] <speed> <count> [force|normal]
The displayed syntax suggests that the <delta> argument can be left out while still specifying <speed> <count> [force|normal].
Attached screenshot shows similar situation with /particle's 18w02a syntax.
Linked Issues
Created Issue:
Command syntax help doesn't handle optional argument chains correctly
To reproduce:
1. Type in /particle crit
2. Add a space
3. Hit esc
4. Look at the command syntax help: [<pos>] <delta> <speed> <count> [force|normal]The displayed syntax suggests that the <pos> argument can be left out while still specifying <delta> <speed> <count> [force|normal].
relates to
discovered while testing
To reproduce:
1. Type in /particle crit
2. Add a space
3. Hit esc
4. Look at the command syntax help: [<pos>] <delta> <speed> <count> [force|normal]The displayed syntax suggests that the <pos> argument can be left out while still specifying <delta> <speed> <count> [force|normal].
To reproduce
- Type in /particle crit ~ ~ ~
- Add a space
- Hit esc
- Look at the command syntax help: [<delta>] <speed> <count> [force|normal]
The displayed syntax suggests that the <delta> argument can be left out while still specifying <speed> <count> [force|normal].
Attached screenshot shows similar situation with /particle's 18w02a syntax.

I use /particle name (for example /particle block diamond_block)without and furthur arguments, and the command works fine.