Presets

Feedback presets

Portal particle preset for map transitions

Portal particle preset for map transitions is now a complete Particles workflow with tool screenshots, generated command output, and a Minecraft result capture. Use this for teleport pads, chapter transitions, nether portals, puzzle exits, and command-block moments where players need a visible marker before movement. The gallery keeps setup fields, output review, and the visible HUD or chat result together so the preset can be audited before it becomes part of a map event, scoreboard loop, or command-block chain.

Read inENRUDEESPT中文日本語VIFR한국어IDPLTR

Preset result

A tall portal particle column that marks a teleport or scene transition point.

Output

Portal transition particle command

/particle minecraft:portal ~ ~1 ~ 0.45 0.9 0.45 0.02 36 force @a

Preset screenshot

The preset uses a tall Y spread and moderate count so the portal effect reads as a vertical gateway instead of a flat sparkle on the floor.
The second shot highlights the setting that controls player-facing behavior or state.
The output shot keeps the final command visible before in-game testing.
A tall portal particle column that marks a teleport or scene transition point.

Build the preset

  1. Open the Particles workbench and confirm the target selector or id.
  2. Set the player-facing name, text, objective, or status value first.
  3. Tune color, style, timing, display slot, or value fields before copying.
  4. Review the generated command output and command length warning.
  5. Save the command to Project when it belongs to a multi-command workflow.
  6. Run the command in a clean test world and confirm the visible result matches the workbench.

Why this Particles preset matters

Use this for teleport pads, chapter transitions, nether portals, puzzle exits, and command-block moments where players need a visible marker before movement.

The preset uses a tall Y spread and moderate count so the portal effect reads as a vertical gateway instead of a flat sparkle on the floor. 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.

Testing and version details

Portal particles can be visually noisy near UI prompts. Keep title or actionbar text short when the transition effect is running in the same moment.

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.

Where to go next

Save this beside the teleport command and any title or ambient sound that frames the transition.

For adjacent map feedback, compare the ambient sound preset and title quest message preset.

FAQ

Can I paste this Particles command into chat?

Yes for a quick smoke test if the command is short enough and the selector is safe. For repeatable map behavior, move the command into a command block, function, or Project export.

Why include an in-game result image?

The result image confirms the command affects the HUD, chat, sidebar, sound marker, particle effect, or display entity in Minecraft, not only in the workbench output panel.

Should this be saved with related commands?

Yes. Bossbars, titles, tellraw prompts, and scoreboards usually need setup or follow-up commands, so keep the preset near the rest of the workflow.

Open this workflow

Start from the related Particles workbench, then adjust the preset fields for your world.