How to Summon a Chicken Jockey in Bedrock Edition

Chicken jockeys are one of Minecraft's most chaotic and oddly lovable mobs — a baby zombie (or variant) riding a chicken, sprinting toward you at terrifying speed. In Bedrock Edition, they can spawn naturally, but if you want one on demand, you'll need to use commands. Here's exactly how it works, what variables affect the outcome, and why your results may differ from what you expect.

What Is a Chicken Jockey?

A chicken jockey is a rare mob combination where a baby zombie (including baby zombie villagers, baby husks, or baby drowned) mounts a chicken. In Bedrock Edition, there's approximately a 5% chance that any naturally spawning baby zombie will spawn as a chicken jockey — meaning they don't show up reliably through normal gameplay.

The chicken behaves like any other chicken (it runs, it flaps, it lays eggs), but the zombie riding it inherits standard zombie behavior: it targets players and moves with the chicken's erratic speed. The result is a surprisingly fast and annoying enemy.

Summoning a Chicken Jockey with Commands 🎮

To summon a chicken jockey in Bedrock Edition, you'll use the /summon command with a rider tag. Bedrock Edition handles mounted mob spawning differently than Java Edition, so the syntax matters.

Basic Method: Summon a Chicken with a Zombie Rider

/summon chicken ~ ~ ~ minecraft:entity_born 

This alone won't produce a jockey. To get the rider attached, use:

/summon zombie ~ ~ ~ minecraft:as_baby 

Then immediately summon the chicken in the same location — but this two-step method is unreliable. The cleaner approach uses spawn events and behavior packs, or the following command structure:

Using the /ride Command

Bedrock Edition has a dedicated /ride command that lets you pair two entities directly:

1. Summon a baby zombie:

   /summon zombie ~ ~ ~ minecraft:as_baby 

2. Summon a chicken in the same spot:

   /summon chicken ~ ~ ~ 

3. Then use /ride to connect them. You'll need the entity IDs, which requires either targeting by type or using selectors.

A cleaner single-command approach:

/ride @e[type=zombie,tag=jockey] start_riding @e[type=chicken,tag=mount] teleport_ride 

This requires you to tag both entities first after summoning them separately. It's not as elegant as Java's NBT inline method, but it's how Bedrock's command system operates.

Why Bedrock Doesn't Use NBT for This

In Java Edition, you can nest entity data inside a single /summon command using NBT tags, creating a chicken jockey in one line. Bedrock Edition does not support NBT in commands. This is one of the fundamental differences between the two versions. Bedrock uses a separate entity system, which means riding relationships have to be established after both entities exist in the world.

Variables That Affect Your Results

Not every attempt will look or behave the same. Several factors shape the outcome:

Zombie Variants You Can Use

The chicken jockey isn't limited to standard zombies. You can ride any of these on a chicken:

• Baby Zombie — the classic version
• Baby Husk — desert variant, doesn't burn in sunlight
• Baby Zombie Villager — has villager skin, same behavior
• Baby Drowned — aquatic variant; odd on land, but it works

Each uses the same command structure — just swap zombie for husk, zombie_villager, or drowned.

Natural Spawning vs. Command Summoning

If you're playing survival mode without cheats, chicken jockeys can still appear naturally, but the odds are stacked against you. They're most likely to spawn in low-light areas where zombies already have high spawn rates. Some players report better luck in flat biomes at night, but there's no reliable method to force natural spawning — it's a percentage roll every time a baby zombie spawns.

Command summoning bypasses that entirely. For map-making, adventure modes, or just wanting to see one, commands are the practical route. 🐔

Behavior Packs as an Alternative

If you want repeatable, single-command chicken jockey spawning without the two-step process, a custom behavior pack can define a new entity that combines the rider and mount automatically. This involves creating a JSON entity file that defines the riding relationship at spawn. It's a more involved setup but gives you full control — useful if you're building a custom map or modded survival experience.

Platform Differences Within Bedrock

"Bedrock Edition" covers a wide range of platforms: Windows 10/11, Xbox, PlayStation, Nintendo Switch, iOS, and Android. Command functionality is consistent across these, but:

• Console players may find entering long commands less comfortable without a keyboard
• Marketplace/Realm settings may restrict cheats or command use
• Realm operators need to ensure experimental features or behavior pack permissions are enabled depending on the Bedrock version

The /ride command specifically was introduced in a relatively recent update, so players on older versions or those who haven't updated may not have access to it. Checking your current Bedrock version before troubleshooting is worth doing. ⚙️

What Works Depends on Your Setup

The core method — summon both entities, then use /ride to connect them — is consistent in modern Bedrock Edition. But how smooth that process feels, whether you need a behavior pack, and which zombie variant suits your purpose all come down to what you're actually building or doing in-game. A survival player, a Realm admin, and a map creator are each going to land on a slightly different workflow to get the same result.