Presets

Summon presets

Zombie and two spiders passenger chain preset

This preset is the Batch 1 nested-passenger stress test. It starts with a spider, mounts a zombie on that spider, then nests another spider as the zombie passenger. The command is still readable, but the screenshots make the hierarchy explicit so you can tell root, middle passenger, and top passenger apart.

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

Preset result

A nested three-entity passenger stack with a spider root, zombie middle rider, and spider top passenger.

Output

Nested zombie and spiders summon command

/summon minecraft:spider ~ ~ ~ {Passengers:[{id:"minecraft:zombie",Passengers:[{id:"minecraft:spider"}]}]}

Preset screenshot

The preview confirms the stack is no longer a simple one-passenger jockey.
The nested passenger controls are the key review point for this command.
The output shows a Passengers list inside another passenger entry.
The capture verifies all three entities are attached in the intended order.

Build the preset

  1. Set the root entity to Spider.
  2. Add a Zombie passenger to the root spider.
  3. Open the zombie passenger row and add a second Spider as its passenger.
  4. Review the passenger tree so the top spider is nested under the zombie, not beside it.
  5. Check the output for nested Passengers brackets.
  6. Test in-game on Easy or higher and save the preset before adding more riders.

Nested passengers are order-sensitive

This command has two passenger levels. The first spider is the root entity at the summon coordinates. The zombie rides that spider. The second spider rides the zombie. If you place both spider entries at the same level, the visual result changes completely.

NBTForge helps by showing the passenger tree and output together. Use both views: the tree is easier to scan, while the output confirms the final bracket structure that Minecraft will parse.

Why this belongs in the quality gate

A one-rider preset proves the passenger field exists. A nested preset proves the editor, screenshot pipeline, and article copy can explain hierarchy without hiding behind a generic "stacked mobs" phrase.

The in-game capture is especially important here because a nested stack can parse successfully while still looking wrong if one passenger is at the wrong level.

  • Root level: spider.
  • Middle level: zombie.
  • Top level: second spider.

Extending the stack

Add tags before you add more riders. Tags make it possible to clean up, rotate, or inspect only this stack in a test world. If the command grows over the chat limit, move the summon line to a command block or datapack function.

When debugging, remove the top passenger first, test the two-entity stack, then add the third entity back. That keeps bracket mistakes from becoming a search through the whole command.

Use the zombie riding spider preset or spider jockey preset as a simpler baseline before extending this nested chain.

FAQ

Why did I get two separate riders instead of a stack?

The second spider was likely added beside the zombie instead of inside the zombie passenger entry. Reopen the passenger tree and check the nesting level.

Is this still safe for chat?

This example is compact, but nested stacks grow quickly. Watch the command length badge and switch to a command block or function when needed.

Can I use this as a Bedrock command?

No, Java nested Passengers do not map directly to Bedrock. Build a separate Bedrock ride sequence for Bedrock worlds.

Open this workflow

Start from the related Summon workbench, then adjust the preset fields for your world.