MC-124288Parameter count of /particle changes depending on particle
The bug
The parameter count of the /particle command changes depending on the used particle (see also MC-122181). While the command syntax help at least colors the additional parameters in the same color as the particle name, text editors and currently command blocks do not do that. This makes it rather hard to understand what the arguments mean unless you know all parameter a particle has by heart. Additionally it prevents leaving out a parameter to use a default value.
Something like the following might be better:
dust[r=1.0,g=1.0,b=1.0,size=1.0]
dust[color={r=1.0,g=1.0,b=1.0},size=1.0]
How to reproduce
Type the following
/particle dust
→ 
The next parameter is suddenly not the x-coordinate anymore but instead the r-color value
Normal
Created Issue:
Parameter count of /particle changes depending on particle
Relates to MC-122181
The bug
The parameter count of the /particle command changes depending on the used particle (see also MC-122181). While the command syntax help at least colors the additional parameters in the same color as the particle name, text editors and currently command blocks do not do that. This makes it rather hard to understand what the arguments mean unless you know all parameter a particle has by heart. Additionally it prevents leaving out a parameter to use a default value.
This is kind of similar to how you had to provide block states in the past, but there the state properties were at least one parameter of the command and allowed default.
Therefore something like the following might be better:
dust[r=1.0,g=1.0,b=1.0,size=1.0] dust[color={r=1.0,g=1.0,b=1.0},size=1.0]
Relates to MC-122181
The bug
The parameter count of the /particle command changes depending on the used particle (see also MC-122181). While the command syntax help at least colors the additional parameters in the same color as the particle name, text editors and currently command blocks do not do that. This makes it rather hard to understand what the arguments mean unless you know all parameter a particle has by heart. Additionally it prevents leaving out a parameter to use a default value.
This is kind of similar to how you had to provide block states in the past, but there the state properties were at least one parameter of the command and allowed default.
Therefore something like the following might be better:dust[r=1.0,g=1.0,b=1.0,size=1.0] dust[color={r=1.0,g=1.0,b=1.0},size=1.0]Relates to MC-122181
The bug
The parameter count of the /particle command changes depending on the used particle (see also MC-122181). While the command syntax help at least colors the additional parameters in the same color as the particle name, text editors and currently command blocks do not do that. This makes it rather hard to understand what the arguments mean unless you know all parameter a particle has by heart. Additionally it prevents leaving out a parameter to use a default value.
Something like the following might be better:
dust[r=1.0,g=1.0,b=1.0,size=1.0] dust[color={r=1.0,g=1.0,b=1.0},size=1.0]How to reproduce
Type the following
/particle dust→
![[Mod] Michael Wobst](../../../data/avatars/users/37868.png){kind=small}
Relates to MC-122181
The bug
The parameter count of the /particle command changes depending on the used particle (see also MC-122181). While the command syntax help at least colors the additional parameters in the same color as the particle name, text editors and currently command blocks do not do that. This makes it rather hard to understand what the arguments mean unless you know all parameter a particle has by heart. Additionally it prevents leaving out a parameter to use a default value.
Something like the following might be better:
dust[r=1.0,g=1.0,b=1.0,size=1.0] dust[color={r=1.0,g=1.0,b=1.0},size=1.0]How to reproduce
Type the following
/particle dust→
relates to
![[Mojang] Nathan Adams](../../../data/assets/gravatar/dinnerbone.png){kind=small}
[Mojang] Nathan Adams[Mojang] Nathan Adams![[Mod] violine1101](../../../data/avatars/users/92858.png){kind=small}
![[Mod] Greymagic27](../../../data/avatars/users/92875.png){kind=small}
![[Mod] LateLag](../../../data/avatars/users/92884.png){kind=small}
relates to
Affects 1.17.1. Relates to MC-211606.
A comprehensive fix to this issue would probably require the syntax to accept string arguments, yielding commands like