Presets

Summon presets

Strider jockey preset command guide

Strider jockey preset command guide is now a full Summon workflow with the root entity, passenger relationship, output review, and in-game result shown together. Use this for lava-route patrols, Nether travel set pieces, or passenger tests where the mount needs to read differently from spider and horse examples. The page treats the summon line as encounter data that needs visual review, not only syntax validation. The gallery keeps the workbench state beside the spawned result so the root entity, passenger stack, equipment, and final output can be inspected before the command becomes an encounter trigger.

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

Preset result

A strider mount with a Zombified Piglin passenger holding a warped fungus on a stick for Nether patrol testing.

Output

Strider jockey summon command

/summon minecraft:strider ~ ~ ~ {PersistenceRequired:1b,NoAI:1b,CustomName:{text:"Lava Patrol",color:"gold",bold:true},CustomNameVisible:1b,Passengers:[{id:"minecraft:zombified_piglin",equipment:{mainhand:{id:"minecraft:warped_fungus_on_a_stick",count:1}}}],Tags:["lava_patrol"]}
Too long for Minecraft chat

The longest command line is 279 characters, 23 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 .mcfunction for a reusable datapack: save the line without the leading slash at saves/<world>/datapacks/<pack>/data/<ns>/function/<name>.mcfunction with a minimal pack.mcmeta, run /reload, then run /function <ns>:<name>. Do not paste .mcfunction content into chat.

Preset screenshot

Start with strider as the root entity so the preview and output agree.
The second shot highlights the entity relationship or equipment detail that makes the summon preset specific.
The output shot keeps the final /summon command and copy controls visible before testing.
The in-game result confirms strider jockey with a Zombified Piglin rider renders as intended in a clean capture world.

Build the preset

  1. Open the Summon workbench and set the root entity to strider.
  2. Add or review the passenger and equipment details that make the strider jockey with a Zombified Piglin rider readable in-game.
  3. Check the preview and passenger tree before copying the command.
  4. Review the output panel for the final /summon line and command length.
  5. Copy the command for a smoke test, or save it to Project before adding follow-up commands.
  6. Run the command in a clean test world and confirm the in-game result matches the workbench tree.

Why strider jockey with a Zombified Piglin rider needs a preset

Use this for lava-route patrols, Nether travel set pieces, or passenger tests where the mount needs to read differently from spider and horse examples.

The useful part is the structure: strider owns the summon position, while the visible passenger, equipment, or display data gives the preset its encounter identity. Keeping that tree visible prevents bracket mistakes before the command leaves the workbench.

Use the preset when the encounter should be easy to audit later. The workbench screenshot records which entity owns movement and collision, the second screenshot records the passenger or gear detail, and the output screenshot keeps the generated /summon line visible. The in-game capture then confirms Minecraft renders the same relationship, which is the check that a text-only example cannot provide.

Testing and version details

Strider behavior depends on terrain and lava placement. The preset freezes the first capture for readability, but a real map should test movement, pathing, and cleanup near the intended lava route.

Run the first test in an open Java world and watch the command length warning. Compact rider presets can be pasted directly, while longer boss or equipment variants should move into command blocks or datapack functions.

Keep the first smoke test small before attaching effects, loot, sounds, or scoreboards. Hostile passengers may move, burn, despawn, or behave differently by dimension and difficulty, so confirm the basic rider or equipment stack under controlled conditions. Once the visual result is stable, add tags and follow-up commands that target those tags rather than relying on display names or nearby selectors.

  • Keep the root entity and passenger roles distinct.
  • Use tags before adding cleanup or follow-up commands.
  • Test difficulty and dimension behavior before publishing the encounter.

Where to go next

Add tags, patrol triggers, or a reset function before placing the strider jockey in a Nether encounter.

For adjacent rider examples, compare the piglin riding hoglin preset, skeleton trap horseman preset, and ravager rider preset.

FAQ

Can I paste this strider jockey with a Zombified Piglin rider command into chat?

Use the command length warning as the decision point. If the generated line is under the chat limit, a quick chat test is fine; otherwise move it to a command block or datapack function.

Does this work in Bedrock Edition?

Not as a Java Passengers command. Bedrock needs a separate ride workflow because it cannot embed the same recursive Java passenger NBT.

Why include an in-game screenshot?

The screenshot confirms the passenger tree or entity setup renders correctly in Minecraft, not only in the workbench preview.

Open this workflow

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