Entity presets
Movement speed attribute preset
Movement speed attribute preset is now a complete Attributes workflow instead of a templated command note. Use this preset when a custom mob, mount, runner, or chase encounter needs movement tuning separate from potion effects. Attribute speed is useful for entity design because it lives on the mob rather than being a short visible status effect. 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 Attributes workbench keeps the target tag, movement_speed attribute, action, and numeric value visible before the command is copied. Small changes matter here because movement speed values can quickly turn an encounter from readable to chaotic.
Preset result
A tagged runner mob receives a faster movement_speed base value.
Output
Movement speed attribute command
/attribute @e[tag=runner,limit=1] minecraft:movement_speed base set 0.35Preset screenshot
Build the preset
- Open the Attributes workbench.
- Set the target selector to a tagged mob such as `@e[tag=runner,limit=1]`.
- Choose `minecraft:movement_speed`.
- Use base set and start with a conservative value such as `0.35`.
- Review the output and save it with the mob summon.
- Run the command in the test arena and tune the value in small increments.
Why this Attributes preset belongs in Project
Use this preset when a custom mob, mount, runner, or chase encounter needs movement tuning separate from potion effects. Attribute speed is useful for entity design because it lives on the mob rather than being a short visible status effect.
The Attributes workbench keeps the target tag, movement_speed attribute, action, and numeric value visible before the command is copied. Small changes matter here because movement speed values can quickly turn an encounter from readable to chaotic. 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
Test speed changes in the actual arena size. A value that looks fine on an open superflat world can be too fast in a corridor, near hazards, or inside a boss room with knockback and particles.
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
Save this beside the summon command and any tags that identify the fast mob.
For related stat presets, compare the max health attribute preset and speed boost effect preset.
FAQ
Can I paste this Attributes 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 Attributes workbench, then adjust the preset fields for your world.