In /particle, vibrations have extra fields for determining the destination:
particle minecraft:vibration{arrival_in_ticks:INT,destination:{type:"block",pos:[DOUBLE,DOUBLE,DOUBLE]}}The position, however, is limited to absolute coordinates, neither relative nor local coordinates work. This is making this particle basically useless in command systems, as they can only go from one position to another hardcoded position, not a position relative to the execution location or an entity.
With the addition of macro arguments in functions in 1.20.2, these particles can actually be moved to relative positions by using some scoreboard math, however for command blocks and chat-run commands, this is not available still.
Linked issues
is duplicated by 1
Comments 12
Can confirm in 1.20.1
Reply from @unknown:
Please do not confirm tickets for outdated versions. We are currently only accepting confirmations for 1.20.4 and 23w51b.
Can confirm in 1.20.1
Reply from @unknown:
Please do not confirm tickets for outdated versions. We are currently only accepting confirmations for 1.20.4 and 23w51b.
The format for this has completely been changed, now also supporting entity targets:
/particle minecraft:vibration{arrival_in_ticks:20,destination:{type:"block",pos:[0.0d,0.0d,0.0d]}}
/particle minecraft:vibration{arrival_in_ticks:20,destination:{type:"entity",source_entity:[I;0,0,0,0]}}}}However, the second command is not allowed according to the parser (despite giving syntax hints about needing source_entity), I'll make a separate report for that.
The block syntax still does not support relative/local coordinates though.
Also, relates to MC-277485 (entity argument not functional).Â
Can confirm 🙂