MC-78965particle command wrong count parameter
The /particle command has wrong count parameters. You can use values of the int size (2^31-1) and you won't get an error message back that the number was not in the valid range. This is wrong, because the maximum is 16384 (since the 1.9 snapshots) (even if you set a higher value).
Attachments1
Created Issue:
particle command wrong count parameter
The /particle command has wrong count parameters. You can use values from 0 till infinite. This is wrong, because the maximum is 4000 (even if you set a higher value) and when you use 0 it will default the value anyways to 1.
Attachments1
The /particle command has wrong count parameters. You can use values
from 0 till infinite. This is wrong, because the maximum is 4000 (even if you set a higher value)and when you use 0 it will default the value anyways to 1.The /particle command has wrong count parameters. You can use values of the int size (2^31-1). This is wrong, because the maximum is 4000 (even if you set a higher value).
The /particle command has wrong count parameters. You can use values of the int size (2^31-1) and you won't get an error message back that the number was not in the valid range. This is wrong, because the maximum is 4000 (even if you set a higher value).
The /particle command has wrong count parameters. You can use values of the int size (2^31-1) and you won't get an error message back that the number was not in the valid range. This is wrong, because the maximum is
4000(even if you set a higher value).The /particle command has wrong count parameters. You can use values of the int size (2^31-1) and you won't get an error message back that the number was not in the valid range. This is wrong, because the maximum is 16384 (since the 1.9 snapshots) (even if you set a higher value).
![[Mod] redstonehelper](../../../data/avatars/users/10122.svg){kind=small}
Setting the count to 0 changes the behaviour of the dx, dy and dz arguments. For some particles, they will set the velocity. For others, they set the color. For most, they simply do nothing.
Ok then at least there should be the 4000 limit
4000? Why? I don't think it's infinite, but it's certainly laggy. It may become of good use if the particle is tiny, like townaura. For the 0 part, it changes the arguments of dx, dy and dz. Some particles like mobSpell and reddust, dx, dy and dz changes color, for others, it changes the direction it is executing in. For example, changing dy to 3 summons a particle that has a 1.5 length below, and 1.5 above you. For dx, it is east and west, for dz, it is north and south. Numbers in dx, dy and dz seem to count by decimals, for example, 0.2 on all dx, dy and dz makes a complete square of the specified particle. Same goes for 0.4, 0.6, 0.8, 1.0 and so on. Keep in mind that odd numbers work too.
Well ok, I understand that 0 is intended, but 4000 is the limit given by the game, it won't show more. At least the debug screen (P: 4000) says that (see screenshot).
The 16384 limit is only client side, The server has no problem with sending even more particles. Given 2 players, if the server spawn 100000 particles, they will both end up seeing a maximum of 16384 particles, but depending on their position, they will see different particles.
There should be a limit on the count parameter because sending 2^31-1 make the game freeze.