Presets

Entity presets

Effect preset for speed boosts

Effect preset for speed boosts is now a complete Effects workflow instead of a templated command note. Use this preset for race starts, parkour sections, temporary kit rewards, lobby boosts, and movement-based adventure moments. The command is short, but the target selector, duration, amplifier, and particle visibility still need review before it becomes part of a map trigger. The article keeps the setup fields, output review, Project placement, and result capture together so the command is easy to audit before it becomes part of a map setup, event trigger, or reusable command pack. The Effects workbench keeps the selected effect, seconds, amplifier, hidden-particles flag, and target selector visible next to the output. This prevents a speed boost from lasting too long, hitting every player, or hiding feedback when the map actually needs the buff to be visible.

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

Preset result

A speed boost command applies a short movement buff and confirms the target in the HUD.

Output

Speed boost effect command

/effect give @p minecraft:speed 45 1 true

Preset screenshot

Start with the Effects controls that define the preset state.
The second shot highlights the setting or companion command that changes player-facing behavior.
The output shot keeps the final command or command pair visible before it enters Project.
A speed boost command applies a short movement buff and confirms the target in the HUD.

Build the preset

  1. Open the Effects workbench.
  2. Set action to `give` and target to the player or kit selector.
  3. Choose `speed` as the effect id.
  4. Set duration to `45` seconds and amplifier to `1` for Speed II.
  5. Enable hidden particles only when the boost should be quiet.
  6. Review the output and run the command in a clean test world.

Why this Effects preset belongs in Project

Use this preset for race starts, parkour sections, temporary kit rewards, lobby boosts, and movement-based adventure moments. The command is short, but the target selector, duration, amplifier, and particle visibility still need review before it becomes part of a map trigger.

The Effects workbench keeps the selected effect, seconds, amplifier, hidden-particles flag, and target selector visible next to the output. This prevents a speed boost from lasting too long, hitting every player, or hiding feedback when the map actually needs the buff to be visible. A copied command is only useful when the surrounding assumptions are visible: selector scope, world state, order inside the pack, and the exact output that will be pasted into Minecraft. Treat this preset as a checkpoint where those details can be reviewed before the command leaves NBTForge.

The gallery is structured around that review. The first shot shows the workbench state, the second shot calls out the field or companion module that changes player-facing behavior, and the output shot keeps the command or command pair visible. When the preset has a visible result, the in-game capture confirms the same idea in a restored test world rather than relying on a generic overlay.

Testing and scope checks

Amplifier values are zero-based in command output. An amplifier of `1` is Speed II, not Speed I, so write the player-facing description around the actual command value rather than the UI label you remember from potions.

Run the first smoke test with a narrow selector and a clean world state. Environment, utility, routing, and feedback commands can look harmless, but they often affect every player or the whole world. Confirm the command changes only the intended state, then save the exact output beside the setup or follow-up lines that explain why it exists.

If the command becomes part of a function file or command-block chain, test the copied artifact, not only the live workbench state. That catches stale selectors, wrong command order, missing setup lines, and effects that only appeared to work because a previous test left state behind.

  • Keep selectors narrow until the full pack is reviewed.
  • Place world setup before encounter-specific overrides.
  • Save feedback commands next to the state change that triggers them.

Where to go next

Pair this with a reward sound, particle cue, or timer reset so players understand why their movement changed.

For related status effects, compare the strength boss phase preset and invisibility NPC preset.

FAQ

Can I paste this Effects command into chat?

Usually yes for a one-command smoke test if the selector is safe and the line is short. For repeatable map behavior, save it to Project and copy the ordered pack or function-style output.

Why include a result capture for a utility-style preset?

The result capture proves the command changed visible world, HUD, routing, or feedback state in Minecraft instead of only looking correct in the output panel.

What should I check before sharing this preset?

Check selector scope, command order, target version, and whether the command belongs in setup, encounter logic, feedback, or cleanup. Those categories decide where it should sit in a Project pack.

Open this workflow

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