Item presets
Splash potion preset with custom color
Splash potion preset with custom color is now a complete Give Potions workflow instead of a templated command note. Use this preset when a potion should read as a map item, boss-phase tool, healing burst, or scripted encounter cue instead of a generic vanilla bottle. The custom color makes the item recognizable before it is thrown, while the effect payload decides what happens at impact. 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 workflow keeps the splash potion item, visible name, lore, custom color, effect id, amplifier, duration, and generated Give output together. That is important because potion commands often fail from one mismatched field rather than from the item id itself.
Preset result
A custom-colored splash potion item and impact-style particle radius show the preset outcome clearly.
Output
Custom-color splash potion command
/give @s minecraft:splash_potion[custom_name={text:"Crimson Burst",color:"red",italic:false},lore=[{text:"Custom impact color",color:"gray",italic:false}],potion_contents={custom_color:11141290,custom_effects:[{id:"minecraft:instant_health",amplifier:1,duration:1,show_particles:true}]},custom_data={potion:"crimson_burst"}] 1The longest command line is 326 characters, 70 over the 256-character chat input limit. Pasting it into chat can truncate the line and make Minecraft report a syntax error even when the generated command is valid.
- Use a Command Block: run
/give @s command_block, place it, then paste this command into the block command field. - Use a
.mcfunctionfor a reusable datapack: save the line without the leading slash atsaves/<world>/datapacks/<pack>/data/<ns>/function/<name>.mcfunctionwith a minimalpack.mcmeta, run/reload, then run/function <ns>:<name>. Do not paste.mcfunctioncontent into chat.
Preset screenshot
Build the preset
- Open the Give workbench and set the item to `splash_potion`.
- Set the custom name to `Crimson Burst` and add lore that explains the impact role.
- Open potion fields and set a custom color value such as `11141290`.
- Add the custom effect, amplifier, duration, and particle visibility that match the map mechanic.
- Add `custom_data` so later commands can identify this exact potion.
- Review the `/give` output and save it to Project before adding encounter triggers.
- Run the command and confirm the item plus impact-style particle radius match the preset.
Why this Give Potions preset belongs in Project
Use this preset when a potion should read as a map item, boss-phase tool, healing burst, or scripted encounter cue instead of a generic vanilla bottle. The custom color makes the item recognizable before it is thrown, while the effect payload decides what happens at impact.
The workflow keeps the splash potion item, visible name, lore, custom color, effect id, amplifier, duration, and generated Give output together. That is important because potion commands often fail from one mismatched field rather than from the item id itself. 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
Potion colors do not replace the effect payload. A red or purple bottle can still carry a healing, strength, or custom effect, so keep the tooltip and lore honest about what the command actually gives the player.
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 with the encounter or reward commands that decide when players receive the potion, then test the impact cue before balancing the effect strength.
For adjacent effect workflows, compare the speed boost effect preset, strength effect boss phase preset, and potion boss fight preset.
FAQ
Can I paste this Give Potions 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 Give workbench, then adjust the preset fields for your world.