Entity presets
Attribute preset for max health
Attribute preset for max health is now a complete Attributes workflow instead of a templated command note. Use this preset when a boss, guard, or durable custom mob needs more health than the summon default. Keeping health as a separate attribute command makes balance passes easier because the creator can tune durability without rewriting equipment or passenger NBT. 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 target selector, attribute id, action, and value visible beside the output. The paired data merge matters because raising max health without setting current Health can leave the entity alive but not actually filled to the new maximum.
Preset result
A tagged boss receives a higher max-health value plus matching current Health.
Output
Max health attribute command
/attribute @e[tag=arena_boss,limit=1] minecraft:max_health base set 80
/data merge entity @e[tag=arena_boss,limit=1] {Health:80f}Preset screenshot
Build the preset
- Open the Attributes workbench.
- Set target to the tagged boss entity.
- Set attribute to `minecraft:max_health`.
- Use base set with a value such as `80`.
- Add a matching current Health data merge when the boss should start full.
- Save the attribute and Health lines together in Project.
- Run both commands on a tagged test entity before balancing damage.
Why this Attributes preset belongs in Project
Use this preset when a boss, guard, or durable custom mob needs more health than the summon default. Keeping health as a separate attribute command makes balance passes easier because the creator can tune durability without rewriting equipment or passenger NBT.
The Attributes workbench keeps target selector, attribute id, action, and value visible beside the output. The paired data merge matters because raising max health without setting current Health can leave the entity alive but not actually filled to the new maximum. 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
Always set current Health after raising max_health when the entity should start the fight at full health. Otherwise the max value changes, but the boss may begin the encounter with its old current health.
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 after the boss summon and before phase effects, bossbar setup, or damage testing.
For adjacent stat tuning, compare the movement speed attribute preset and scale attribute custom mob 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.