Presets

Entity presets

Invisibility effect preset for NPCs

Invisibility effect preset for NPCs is now a complete Effects workflow instead of a templated command note. Use this preset for invisible armor stands, marker entities, dialogue anchors, click helpers, and NPC tricks where the player should not see the technical entity. The command keeps the helper in the world while removing its visible body from the scene. 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 long duration, target tag, invisibility effect, amplifier, and hidden-particle choice visible. That matters because visible particles can reveal the helper and because a broad selector can accidentally hide entities the player should see.

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

Preset result

A tagged NPC helper becomes invisible while remaining targetable for map logic.

Output

Invisible NPC helper command

/effect give @e[tag=npc_helper,limit=1] minecraft:invisibility 999999 0 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 tagged NPC helper becomes invisible while remaining targetable for map logic.

Build the preset

  1. Open the Effects workbench.
  2. Set target to the helper tag, not all entities.
  3. Choose `invisibility` as the effect id.
  4. Set a long duration such as `999999` seconds for persistent map helpers.
  5. Keep particles hidden so the helper does not reveal itself.
  6. Save the command with the helper summon and interaction logic.
  7. Run it in-game and confirm the technical entity disappears without hiding unrelated entities.

Why this Effects preset belongs in Project

Use this preset for invisible armor stands, marker entities, dialogue anchors, click helpers, and NPC tricks where the player should not see the technical entity. The command keeps the helper in the world while removing its visible body from the scene.

The Effects workbench keeps the long duration, target tag, invisibility effect, amplifier, and hidden-particle choice visible. That matters because visible particles can reveal the helper and because a broad selector can accidentally hide entities the player should see. 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

Invisibility does not make every carried item or equipment piece disappear in every setup. Test the exact entity, equipment, and particle setting in the target version before using the command as a production NPC trick.

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, tag, or interaction command that creates the helper entity.

For adjacent helper workflows, compare the text display floating label preset and cross-edition summon checklist.

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.