Skeleton trap horseman preset

Use this when you want the visual language of a skeleton trap without waiting for natural lightning behavior or rare spawning.

The useful part is the structure: skeleton horse 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.

Natural skeleton traps involve extra game logic. This preset focuses on the visible horseman stack, so add follow-up lightning, sound, or trigger commands separately.

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.

Place the horseman behind a trigger and test cleanup tags before using it in a real encounter.

For other rider structures, compare the piglin riding hoglin preset, spider jockey preset, and ravager rider preset.