Tutorials

Entity

Entity command guide: passengers, ride, teleport, effects, and attributes

8 min read

Entity workflows become difficult when a command mixes passengers, equipment, targeting, and edition differences. NBTForge keeps the entity preview, passenger tree, and output warnings in one place.

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

Goal

A reusable entity setup with previewed passenger structure and safe edition warnings.

Annotated screenshots

The canvas preview shows the mounted entity stack while controls below edit the passenger tree.
Bedrock cannot embed Java Passengers NBT, so NBTForge warns before you copy unsupported output.

Step-by-step guide

  1. Start in Summon when the entity itself is the source of the workflow.
  2. Use passenger controls to add a rider, stack another entity on top, or mount the whole stack on another mob.
  3. Switch to Java when you need recursive Passengers NBT in one command.
  4. Switch to Bedrock only when you are prepared to use follow-up ride commands instead of embedded Java NBT.
  5. Use Teleport, Effects, and Attributes as follow-up commands in Project for full entity setups.

How passenger logic maps to commands

Java stores riding stacks on the mount/root entity with recursive Passengers NBT. NBTForge models this as a tree so a spider with a zombie rider can later become part of a larger mounted stack.

Bedrock uses different command workflows for riding, so NBTForge avoids pretending that Java passenger NBT can be copied directly into Bedrock.

When to split entity commands

Use one Summon command for the base entity when possible, then add follow-up commands for effects, attributes, and teleports when those operations are clearer or edition-specific.

Project is the best place to keep these lines together because it preserves command order during copy.

  • Summon the entity first.
  • Apply attributes or effects next.
  • Teleport or rotate last if position matters.

Publish-ready check

Use this entity tutorial as a repeatable workflow, not only as a one-time screen tour. After the command works in the workbench, copy the final Output or Project pack into a clean test world and confirm the copied text behaves the same way.

When a command depends on version syntax, selectors, saved project entries, or datapack resources, write those assumptions into the project title or surrounding notes. That makes the tutorial useful when another creator opens the same workflow later.

  • Test the copied command, not only the visible builder state.
  • Keep the Edition and Version choice attached to the workflow.
  • Use Project for multi-command setups and future edits.
  • Recheck warnings after importing old commands or switching modules.

FAQ

Can a zombie ride two spiders?

A single rider cannot ride two mounts at the same time in one final in-game state. NBTForge can build stacked passenger trees, but the root/mount relationship must still follow Minecraft entity rules.

Why does Bedrock output drop Java NBT?

Bedrock command syntax does not accept the same Java entity NBT payload. NBTForge warns instead of generating a misleading command.

When is this workflow ready to share?

Share it after the copied output has been tested in a clean world or command block, and after any required version, selector, datapack, or Project assumptions are written down.