Explosion particle preset without damage

Use this for fake impacts, spell hits, scripted traps, door blasts, and boss attacks where the map needs visual force without actually exploding terrain.

The preset keeps the explosion particle count low but the spread wide, making the effect readable without turning the whole screenshot white. A screenshot-only snippet is not enough for these commands because the visible UI state has to match command output and map logic. Keep the preset as a checkpoint where the readable label, selector, id, and generated command can be reviewed together before the command is copied.

Explosion particles are short-lived. For screenshots or telegraphed attacks, run them from a short repeating command block or function loop, then stop the loop after the cue ends.

Run the first smoke test in a restored world with only the needed commands active. HUD, chat, bossbar, and scoreboard results are easy to confuse when old objectives or bars remain from a previous test, so create or reset the state before judging the screenshot. Keep selectors narrow when the final map should affect one player.

• Use stable ids for stateful commands.
• Keep player-facing feedback short enough to read or recognize quickly.
• Save related setup and update commands together in Project.

Pair the visual with playsound, knockback, or damage commands only after the particle timing is readable.

For related combat visuals, compare the flame particle boss attack preset and trial chamber particle preset.