Presets

Summon presets

Spider jockey summon command preset

This preset recreates a spider jockey as an editable Summon command instead of relying on rare natural spawning. The workbench state keeps the spider mount, skeleton passenger, and rider equipment visible, while the in-game capture verifies the stack looks like a classic jockey before you place it in a dungeon or raid room.

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

Preset result

A skeleton rider on a spider, useful as a recognizable hostile encounter starter.

Output

Spider jockey summon command

/summon minecraft:spider ~ ~ ~ {Passengers:[{id:"minecraft:skeleton",equipment:{mainhand:{id:"minecraft:bow",count:1}}}]}

Preset screenshot

The preview gives a quick visual check before you inspect the generated passenger NBT.
Use the passenger panel to keep the skeleton on the spider instead of building a separate command chain.
The output is short enough for quick testing and can also be saved into a reusable command pack.
The final capture confirms the rider appears above the mount and reads as a spider jockey.

Build the preset

  1. Set the Summon root entity to Spider.
  2. Add a Skeleton passenger to create the jockey relationship.
  3. Give the skeleton a bow in the passenger NBT or equipment field if your version target supports it.
  4. Review the output panel for the Passengers list and equipment data.
  5. Copy the command into a command block or chat if the length check is still green.
  6. Test in Easy or higher difficulty so the skeleton passenger remains in the world.

A controlled version of a rare encounter

Natural spider jockeys are memorable but unreliable when you are building a map encounter. This preset turns that idea into a predictable command: the spider is summoned exactly where you run the command, and the skeleton is embedded as the passenger.

Because the skeleton is part of the passenger tree, you can add tags, names, or extra equipment in the same editing pass. Keep the first version simple, then save a Project copy before adding more encounter logic.

Equipment and version checks

The example keeps a bow on the skeleton rider so the encounter reads correctly. Equipment syntax is version-sensitive in modern Java, so keep the version selector aligned with the world that will run the command.

If you change the weapon or add armor, watch the output diff. A small equipment edit can make the command much longer and may push the command over the chat limit.

  • Use Java 26.1.2 output for the current capture.
  • Save a copy before adding more NBT.
  • Move to command blocks if the line grows past chat length.

Encounter placement

Spider jockeys move quickly and the rider can attack immediately, so place the command in a controlled arena or behind a trigger. For screenshots and QA, a flat test world makes it obvious whether the passenger is attached correctly.

If you need a non-moving showcase, add temporary NoAI only in a test copy. Keep the production preset focused on the actual encounter behavior players will see.

For adjacent rider structures, review the zombie riding spider preset, chicken jockey preset, and ravager rider preset.

FAQ

Why is the skeleton not holding the bow?

Check the selected Java version and equipment syntax. If the command was copied from another version family, regenerate it with the version selector matching your world.

Can this spider jockey command run in Peaceful?

No. Peaceful removes hostile mobs, so use Easy or higher while testing the skeleton passenger.

Is this the same as a naturally spawned spider jockey?

It creates the same visible relationship, but the command gives you control over position, equipment, tags, and future edits.

Open this workflow

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