Java 26.2
Particles
Position
Delta
Flame
20 particles at ~ ~1 ~
/particle minecraft:flame ~ ~1 ~ 0.25 0.5 0.25 0.01 20 normal
Visual effects
The /particle command takes more positional arguments than most: after the particle id come the position, the delta that spreads the particles, a speed value and a count. Several particles also take their own parameters — dust needs a colour and a scale. Fill them in here rather than counting arguments by hand.
Flame burst
/particle minecraft:flame ~ ~1 ~ 0.25 0.5 0.25 0.01 20 normalPosition, delta spread, speed and count in the canonical order.
Hearts, forced visible
/particle minecraft:heart ~ ~1 ~ 0.25 0.5 0.25 0.01 10 forceforce mode renders beyond the normal particle distance and count limits.
Portal swirl for one viewer
/particle minecraft:portal ~ ~1 ~ 0.25 0.5 0.25 0.01 50 normal @pA trailing selector limits who sees the particles.
Particles beyond the client particle-render distance are culled, and normal mode drops particles when many are on screen. Use force mode to render them regardless of distance and count, and check the position is where a player can actually see it.
The dust particle takes its own parameters: an RGB colour (0-1 per channel) and a size. The editor exposes a colour picker and size field, so /particle dust <r> <g> <b> <size> is built for you.
The three delta values spread particles randomly around the position (a box radius), and speed scales the motion of directional particles. Count is how many to spawn. Together they control whether a particle is a tight point or a wide cloud.
No — Bedrock uses different particle identifiers (often prefixed minecraft:) and a different argument order. The generator targets Java particle syntax; treat Bedrock particle output as unsupported.
Java 26.2
Position
Delta
20 particles at ~ ~1 ~
/particle minecraft:flame ~ ~1 ~ 0.25 0.5 0.25 0.01 20 normal