AI Players
Type to search documentation.

Building an economy

The End

How a faction of bots gears up for the End, finds the stronghold with eyes of ender, fights the dragon, brings the egg home, and goes back for the outer islands, an elytra and an end city's loot.

The End is the game’s finish line, and a faction of bots treats it like a group of players would. It’s a trip for several bots, taken once there’s nothing left to gear up for. A ready faction gathers in team chat and throws eyes of ender to find the stronghold. It fills the portal by hand, steps through together, shoots the crystals, kills the dragon and carries the egg home to its innermost chest. After that it may go back for the outer islands: the bots cross the gateway to an end city, climb its towers for the loot and head out to the ship for the elytra. From then on, they fly.

Among the shipped styles, the Rusher and the Boomer go to the End. The Neutral, the Turtler and the Flanker stay home (though the Flanker still flies an elytra on its raids if it comes by one). Bots on the Easy difficulty never go, whatever their style, so if you pick easy rivals, you get rivals who never finish the game.

Who goes, and when

A bot goes only when its play style says so (end.travel: true) and its difficulty allows it (end_dragon: true, which is every shipped difficulty but Easy). Such a bot counts as ready once it meets its own style’s bars:

  • its tools have reached the style’s gear_goal: the goal’s pickaxe, plus its sword and axe when the goal is below netherite, in hand or in the base’s chests;
  • every armor piece it wears is of the goal’s tier or better and enchanted, and its sword is enchanted too (the enchanting corner);
  • its potion stock is full (nether.potions; a style that keeps none has nothing to fill);
  • it holds its share of the eyes of ender, in hand or in its chests;
  • it holds the trip’s kit.

A faction goes when at least two of its bots are ready (end.party). A faction with fewer bots than that needs all of them, and a bot in no faction goes alone. Only bots count. Players aren’t part of the party yet, though you can send a bot yourself. A ready bot in another dimension can’t answer the call, so the faction waits until enough of its ready bots are in the same dimension.

Once a bot is ready, going to the End outranks every gear, mining, building and exploring job, whatever the style’s weights. A ready faction stops climbing and goes. Only surviving, fights and orders still cut in. The objective is the_end, and /aiplayer info <bot> shows an end: line with what the faction knows and whether the bot is ready, or what it still lacks (not ready: tier, enchantments).

The call and the party

The first ready bot calls its faction in team chat, and every member in the same dimension answers within a few seconds:

Team chat
<Ann> Going to the End from 120, 64, -80: who is ready?
<Ben> Yes, coming
<Cid> No, I still need my best tools, enchanted gear
<Dee> No, I do not go to the End

A ready member takes Ann’s assist order and walks to her. One that isn’t ready says what it lacks, one busy with an order says No, I am busy, and one whose style or difficulty never goes says so. The caller waits until everyone who said yes has arrived (two minutes at most), says <Ann> Setting out for the End and leads the way, with the members following. The call and the assist orders last for the whole trip, however long it takes, and end with it. A bot calls at most once every ten minutes.

A member that dies on the trip respawns like any bot, re-gears at home until it meets the same bars again, and joins the next trip. A party cut short in the End (say its leader dies) keeps fighting. A survivor takes the lead, and it doesn’t need the bars or a party to do so.

The kit

Each member carries the trip’s kit. By default that’s:

  • 128 blocks (cobblestone and end stone count)
  • a bow and 64 arrows
  • 16 pieces of cooked food
  • a spare pickaxe of its gear goal’s tier
  • a water bucket
  • 4 torches (the egg lands on one of them)

The kit is counted in hand and in the base’s chests, and a bot missing any of it isn’t ready. Once its tools reach the gear goal, a bot that goes to the End gathers whatever its kit lacks (gather_kit), using the same plans as for any other item. It keeps the kit in hand, so it has everything on it when the party sets out. Once the End is finished, the bot stops wanting the kit.

Eyes of ender

The party carries 16 eyes of ender between its members by default (end.eyes). That covers the twelve frames (a few of them are usually filled already) plus the eyes thrown during the search, one in five of which shatters. Each member carries its share, which is the stock divided by the party size, rounded up, with a minimum of 4. With the defaults, that’s 8 each. An eye is an ender pearl plus blaze powder, crafted without a table. A bot that goes to the End gets all of them from the world, whatever its tactics:

  • Crafting and hunting. gather_pearls crafts what eyes it can from the pearls, powder and rods the bot holds or keeps in its chests. Then it hunts endermen for the pearls still missing and crafts again. It only hunts with an iron or better sword and more than three quarters of its health, and an enderman in sight gets hunted at any hour. With none in sight, the bot only goes looking once its End gear is done (like for a player, the eyes are the last thing it works on).
  • By night. Endermen are rare by day. From sunset to dawn the bot walks around within its roaming radius of its base, looks around after each walk, and hunts every enderman it sees. While it hunts at night it doesn’t go home or burrow, and its other work waits. After a walk that finds none, the next one waits a quarter of a day, so a night fits about two walks.
  • In a warped forest. A bot in the Nether notes every warped forest whose nylium it sees and shares it with its faction. Once a forest is known and the bot may make the trip, it prefers the forest over hunting at night. It walks within 32 blocks of the spot it saw, at any hour, since endermen are plentiful there and little else spawns.
  • Rods. Once its End gear is done, gather_rods counts how much blaze powder the missing eyes need (one rod makes two). So a style that goes to the End farms a fortress whether it brews or not.

The eyes are never thrown away. stow keeps the share’s eyes in hand, along with the pearls, powder and rods it still needs. A raider with the ender_pearl tactic keeps its two pearls next to its share and only ever throws those two. Once the faction’s portal is lit, nobody wants eyes anymore. info shows the share on an eyes: line: eyes: 5 of 8 (3 pearls, 10 powder).

Finding the stronghold

The party finds the stronghold the way a player does, with eyes of ender. It never asks the server where the stronghold is.

  1. The eye. The leader throws an eye and watches it fly for a second. An eye bound for a far stronghold rises and flies toward it, and the leader reads the bearing from that flight. Four times in five the eye drops back as an item and the leader picks it up. The fifth time, it shatters.
  2. The legs. The leader walks 200 blocks along the bearing (rowing across water if it has a boat), throws again, and keeps going like that. Once two throws at least 100 blocks apart point at the same place, it heads straight for where they cross, still throwing at the end of each leg.
  3. The stair. Over the stronghold, the eye goes down instead of along. The leader digs a stair straight down, winding around a square like a mine’s stair does and keeping clear of lava and water. It stops when it sees stone bricks within 16 blocks (or reaches bedrock, which ends the trip).
  4. The corridors. Inside, it walks the stronghold’s corridors toward the parts it hasn’t checked yet, going through doors and gaps and digging where it has to, until it sees an end portal frame. Then it tunnels straight to the portal room, through bricks and iron bars, and stops next to the frames, two blocks short of the lava pool. Silverfish are fought like any other monster.

The members follow the leader the whole way, down its stair and through its tunnel, without digging anything themselves. A bot that goes to the End and sees a stronghold’s stone bricks anywhere (in a cave, down a mine, on a trip) records it for the faction, the same as a Nether fortress. Once a stronghold is known, nobody searches for it again. The search gives up after 40 legs. A party with fewer than two eyes between them and none in the leader’s hand goes back to its normal life and hunts the eyes it lacks.

Through the portal

  • The fill. The leader walks to the portal room and fills the twelve frames by hand, going round the ring and putting one eye in each empty frame. It stands next to the frame, never over the lava. A frame that already holds an eye (yours, or one the stronghold was built with) is left alone, so if you’ve already lit a portal, the bots use it as it is. Each member only carries its share, so when the leader runs out, it walks to the nearest member, who throws it the eyes it’s missing. The portal lights at the twelfth eye, and info counts them (frames 7 of 12).
  • The way in. The leader waits at the portal until every member who answered is within 8 blocks (two minutes at most). Then the members step in one after another, with the leader last, so nobody gets left behind without its leader. A member that wasn’t there (it fell behind, or died and came back ready) goes in on its own later, since the record tells it where the portal is.
  • Arrival. Each bot remembers the obsidian platform it lands on as its arrival point, which stands in for home while it’s out there. The leader walks (or bridges) from the platform onto the island, and the members follow over its bridge. On arrival, and every second after that, a bot writes the End’s state into the faction’s record: whether the exit portal is open, the dragon is dead and the egg is gone.
  • The way home. The only way home from the End is the exit portal, which opens only when the dragon dies. Until then, a hurt bot rests at its arrival point. Once the portal is open, a bot going home walks to the island’s center, steps in and comes out at its respawn point (skipping the credits), and from there home is an ordinary walk. A bot high over the island (on the pillar it built to throw a pearl, say) digs its way down first rather than bridge at that height, and a way home that fails is tried again half a minute later. A bot that finds itself on the platform with no block to bridge to the island does nothing but try the exit portal and wait (info says stranded, no blocks to bridge). Nothing is ever fetched through the End. No plan for an item leads there, and a bot in the End makes do with what it carries.

On the island

The End is an island over the void, and a bot there moves like a careful player:

  • The void. Any column with nothing solid within eight blocks under the feet counts as the void. Paths keep a block away from its edge wherever the way around isn’t much longer. No drop goes down into it, no jump goes over it, and a bot running from something never stops on a cell next to the edge.
  • Bridging. Where the way crosses the void (say, the platform stands clear of the island), the bot bridges the shortest gap. It sneaks to the edge, places a block against the side of the one it stands on, steps onto it and keeps going one block at a time. It lays at most 32 in a line, and never more than it carries. Members cross on the leader’s bridge.
  • Endermen. A bot never looks within four blocks of an enderman’s head unless that enderman is its target or already angry. While walking, it looks at the ground ahead.
  • The dragon’s breath. A breath cloud is a hazard. Paths keep two blocks away from it, and a bot standing in one steps out right away, as it would out of fire.
  • No day, no bed, no chest. It never gets dark, beds don’t work and the night’s work never runs, so a bot doesn’t sleep, shelter or stow anything there. A hurt bot rests at its arrival point, a flee heads toward it, and a bot below its retreat health walks back to it.
  • Deaths. Whatever a bot drops in the End is lost to it. It doesn’t go back for its drops there, and re-gears at home like any dead bot.

The fight

Every member fights, and the bot that made the call leads and speaks for the party.

  • The crystals first. Each member goes for the crystal nearest to it that no other member is after. An open crystal is shot with the bow from the ground. The bot walks out from the pillar toward the island’s center to the first spot where its arrow clears the pillar’s top (never nearer than 6 blocks), and shoots until the crystal falls. After five misses it tries the next spot. A caged crystal, or one that no spot on the ground can reach, is shot from a column the bot builds. It walks 6 blocks out from the pillar and pillars up with its kit’s blocks to one block below the pillar’s top. Then it breaks one bar of the cage with its pickaxe, shoots the crystal through the gap and digs its column back down. A crystal a bot gives up on is left to the others for half a minute.
  • Then the dragon. Once there’s no crystal left for it, a bot fights the dragon. It uses the sword on the head or body while the dragon perches on the exit portal (arrows bounce off a perched dragon), and the bow, leading its shots, while the dragon flies within 48 blocks. When the dragon is farther off, the bot waits 16 blocks out from the portal. It never stands within 6 blocks of the portal’s center while the dragon circles, since that’s where it dives. It also steps out of the breath, and sprints aside when the dragon dives straight at it.
  • Hurt. Below its retreat health, a bot runs to the shadow of the nearest pillar, on the side away from the dragon, and heals there. It drinks a healing potion or eats a golden apple, otherwise a meal, and if it has none of those it waits. It goes back once its health reaches the threshold plus a quarter. It never runs off the island or heads home mid-fight, and it eats between two actions when its food runs low.
  • A fallen member. When a member dies on the island, the nearest survivor collects everything lying within 16 blocks of the spot (once the dragon isn’t diving at it) and carries it home. The fallen bot respawns, takes its spare gear from the chests and is ready again once it meets its bars.
  • The kill. The leader says <Ann> The dragon is dead in team chat, then the party gathers the experience orbs and waits for the exit portal to open. If the dragon is already gone when the party arrives (from an earlier kill, or another faction’s), the fight ends right away with the record set.

Other bots keep away from the dragon. Outside a party’s fight it weighs ender_dragon (6 by default) in the difficulty’s threats. A bot whose side weighs less keeps 12 blocks away from it, as from any enemy that outmatches it, and no bot ever chases it as an ordinary target.

The egg

The first dragon’s death leaves the egg on the exit portal’s pillar, and the leader takes it the way a player would:

  1. Off the pillar. The egg teleports when punched, so the leader punches it from the portal’s rim (never from the bowl, where the open portal would send it home) and finds where it landed within 16 blocks. While the egg sits on bedrock, obsidian or the portal, next to the void’s edge, or anywhere its fall can’t be set up, the leader punches it again, up to 32 times.
  2. The fall onto a torch. Once the egg rests on stone, the leader digs a two-block trench out from under it, sets a torch under the egg’s support and breaks the support. The egg falls onto the torch and drops as an item, which the leader picks up. If it has no torch in hand, it takes any torch within 16 blocks except the portal pillar’s own.
  3. Home. The faction’s record says egg taken by Ann, and the End is finished. The leader goes home through the exit portal with the egg, and so does any other bot of the faction still in the End. At home, before anything else is stowed, the egg goes alone into the base’s innermost chest (the one a raider walking in from the edge would open last), and the bot says <Ann> The egg is home. No bot places the egg, throws it away or sells it.

A bot that dies carrying the egg drops it like any item. Any bot of the faction with no duty that sees it lying within 16 blocks goes for it (pick_up_egg). A dragon killed after the egg is already gone (it’s not the first kill, or someone else took it) leaves nothing to take. The record says egg gone, and the End is finished all the same. The trophy can still change hands, though, since a raider takes the egg before anything else in a chest.

The second trip: the outer islands

The kill that freed the egg also opened a gateway on the main island’s rim. Past it lie the outer islands, the end cities and their ships, and the elytra a player goes back for. Once the End is finished, a style that goes to the End goes back for them (end.outer, on by default). Like the first, the second trip is a faction trip, since a lone bot out there is as good as lost.

Who is ready. The bars are the first trip’s, with two changes. The eyes aren’t needed anymore (the portal stays lit), and the bot needs the outer kit on top of the regular kit (end.outer_kit, by default 4 ender pearls and 128 more blocks, so 256 blocks in all). The party size is the same, and so is the call (<Ann> Going to the outer islands from 120, 64, -80: who is ready?, <Cid> No, I still need pearls and blocks for the outer islands, <Ann> Setting out for the outer islands). The objective is outer_islands.

The gateway. The leader finds the gateway the kill opened (the one in the record, or else the nearest of the twenty spots on the ring where vanilla opens them). The frame is hard to walk into, so each bot crosses the way a player does. It stands within a pearl’s throw of the gateway (building a pillar if the ground is too far below) and throws an ender pearl into it. The pearl comes out on the far side, and the bot with it. The party gathers at the gateway like at the portal and crosses one by one, leader last. Where a bot lands is its arrival point on the outer side. The record remembers the gateway and the landing, so a party that comes back lands in the same place.

The search for a city. Across the gateway, the leader looks for an end city. If the faction already knows one, it walks there. Otherwise it walks in legs of up to 64 blocks, toward purpur if it sees some, else toward the farthest ground it sees ahead, swinging its bearing wider and wider when there’s nothing ahead. It bridges gaps of void with its blocks as long as they’re no wider than end.hop_gap (64) and it has laid fewer than end.hop_blocks (192) over the whole search. The members walk its bridge and lay none of their own. Eight purpur blocks or end rods in sight count as a city, which gets shared with the faction like a bastion. The search gives up (and the party goes home) beyond end.search_radius (512 blocks from the arrival), after ten minutes, or once its blocks run out. Chorus plants along the way are cut and the fruit picked up. Chorus fruit is a last-resort food, eaten only on solid ground well clear of the void, since it teleports whoever eats it.

The city raid. The leader walks into the city and raids it house by house. Every chest it sees goes into the city’s record. It opens the nearest chest it hasn’t looted yet by hand and takes things in order of value (the elytra first, then netherite, shulker shells, diamonds and the rest) until two free slots remain. When there’s no chest left, it climbs the nearest house or tower top it hasn’t climbed yet to see the chests up there. It goes up the city’s own stairs and ladders, or pillars and digs with its own blocks. A chest it can’t reach is tried again from another spot and from above before the leader gives up on it. The raid ends when every chest it knows about is looted or given up and the ship has been seen (or is known not to exist), and the record then marks the city as stripped. Between fights, the members follow the leader, climb the same tower the same way, and wait at the near end of a bridge while the leader is on it.

Shulkers. Every bot of the party fights the shulkers in sight (within 20 blocks) itself. It closes in with its shield raised, strikes while the shell is open and keeps the shield up while it’s closed. It only shoots a shulker that no standing spot can reach (combat). A bullet within 4 blocks gets blocked with the shield. While a shulker lives, the bot won’t bridge, pillar or stand at the void’s edge to reach it. When the shulkers that can fire on the bot outweigh the party (each one weighs the difficulty’s shulker, 2 by default, in the gear comparison), the leader gives up on the city and the trip goes home. Once a chest of the city has been looted the count alone no longer sends the party home: it leaves when a member has dropped under its retreat health twice in the city, or a member died there. A shulker the bot can’t hurt for thirty seconds, or can’t reach or shoot, is given up for a minute. A shulker met outside the raid (on the way home, say) is fought the same way and never chased.

Bots ride out levitation. A lifted bot stops walking, keeps its shield up and steers only to stay over solid ground (never into a wall). When the effect ends and the fall would hurt, it pours water from its bucket to land in, then picks the water back up. A bot lifted anywhere in the End while it isn’t raiding (following its leader, going home) floats the same way, and whatever it was doing waits until it stands again. A bot pinned against a ceiling with a shulker watching fights it from the air when it can, and otherwise steers out of the shulker’s sight. A member above its leader with no way down (on a tower’s top) goes down only over the city’s own blocks, digging if it must, and never lays a block to bridge off the top.

The ship. From each top it climbs, the leader looks out for the city’s ship, spotting it by the dragon head on its bow or a framed elytra within 96 blocks (at most eight look-outs per city). To reach it, the leader bridges toward the elytra’s frame in legs of at most 24 blocks, at the height of the bridge the ship hangs off, and digs into the hold through the purpur, fighting any shulker aboard first. It never bridges under the hull: standing low in the city it first walks to that bridge’s end, found along the ship’s line past its stern. When a bridge’s walk fails twice from one spot, the leader moves to the next look-out it climbed, by the way down, and bridges from there, and with none left it gives the ship up for this trip. Lifted by a shulker on the way, it keeps its shield up toward the bullets and waits the lift out rather than walk in the air. Then it punches the elytra out of its frame and picks it up, loots the two chests next to the frame, and opens the brewing stand by hand for its two potions of strong healing. Last, it takes the dragon head off the bow. It digs into the block the head hangs from, leans out over the edge to lay a block under the head, then breaks the head so its item lands on that block instead of in the void. The members never bridge to the ship. They wait in the city, facing it. A stripped city whose look-outs saw no ship has none, and the trip goes home with the city’s loot.

The way back. The way home from the outer islands is the outer gateway next to the record’s arrival, crossed the same way, one by one with the leader last. Back on the main island, each bot goes home through the exit portal. Out there, a bot only has a way home while it holds an ender pearl. Without one, it stays on the ground at its arrival point until it has one again (from an enderman’s drop, say). The way back down from a city’s roof is flown if the bot holds a sound elytra (and the leg is long enough), and walked otherwise. Every stage saves the last 16 blocks the bot holds for the way down, and a bot stuck high up with no path digs straight down through the tower or the island it stands on, never into the void. Out there, a bot does nothing but the trip, surviving, fighting and its orders.

Home. The elytra goes home with the bot that took it. When that bot stands in its base with it, the record counts one more elytra home and the bot says <Ann> An elytra is home. The dragon head is a trophy like the egg, stowed alone in the innermost chest and never placed, worn, thrown or sold. The same goes for a second elytra or a worn one. The second trip is finished when there’s an elytra home for every member of the party, or when the city is stripped and its ship looted. Then the bots go back to their normal lives. If a stage fails out there (the shulkers outweigh the party, no city is found, the ship is given up), the party goes home first, and the leader may try again later.

A death out there. A member that dies respawns and isn’t ready again until it meets the bar. When the leader dies, the first member that came with it and is still in the End takes over the same trip right away, with no new call and no wait, and brings the party home. The dead leader re-gears at home and calls no trip of its own while that one is under way. Then it rejoins the survivor, or waits at home if the survivor is already on its way back. info says end: leading on (the leader died) for the survivor and re-gearing for the outer islands for the dead leader.

Flying with an elytra

The elytra the End brings home gets flown, the way a player flies it. A bot holding a sound elytra (more than a tenth of its durability left, and enough for the whole flight) flies a long leg instead of walking it. That covers a trip home or to the base’s portal, an explore trip, and, with the elytra tactic, a raid’s way in and out and a scout’s circuit (raiding by air). Only legs of at least end.flight blocks (200 by default) are flown, never in the Nether and never into another dimension.

  • The launch. A glide starts from height with a drop ahead: the ground has to fall three blocks or more under each of the next three blocks of its run, so a narrow gap in a roof is no launch. The bot launches from where it stands if it’s high enough above the ground at the landing. Otherwise it launches from the nearest high point within 16 blocks on the target’s side, or pillars up with as many as 24 of its own blocks, or gives up and walks. Its first eight blocks toward the target have to be clear of anything taller than itself (in the End, its whole line to the landing). Before jumping, it swaps its chestplate for the elytra, then jumps off the edge and opens the elytra in the air. The chestplate goes back on the tick it lands. It only wears the elytra for flights.
  • The glide. A glide covers about nine blocks for each block of height, and a flight only starts when its height and the rockets it holds cover the leg with a quarter to spare. The bot holds its pitch a hair under level and turns toward the target. When the target lies beyond what its height can reach, it uses a firework rocket (at most one every two seconds, always keeping one spare). It watches the ground 48 blocks ahead, and when there’s a rise, it either climbs it with a rocket or circles down and lands short of it. Near the target it descends along the line (never steeper than 30 degrees) and pulls level just above the ground. Then it walks the rest.
  • Interruptions. Anything that takes over mid-flight (a fight, a flee, an order) waits until the bot has landed, which it does right away, and has its chestplate back on. A bot whose health drops below its retreat line in the air lands too.
  • In the End. A flight there only starts toward ground, and only when its height and rockets cover the whole leg with two rockets to spare. If a flight would have to land over the void, it turns back to the last ground it flew over.
  • Rockets. A bot with a sound elytra keeps 8 firework rockets (end.rockets). gather_rockets crafts them, three from one paper (sugar cane) and one gunpowder (a creeper), and stow keeps them and one elytra in hand.

While a flight runs, info shows flight: flying to (x, z) on the way and flight: landing while it comes down.

Shulker shells and boxes

The shells a city’s shulkers drop become shulker boxes, and bots use them like players do:

  • In the storehouse. Each bot keeps one box for its trips. A box beyond that goes into an empty chest slot of the storehouse before a new chest is made, placed facing up so its lid opens. Shells beyond the reserve are crafted into boxes (two shells and a chest) only while a slot is waiting for one. A placed box counts as one of the base’s chests, but never as the innermost one for the egg, since a raider carries a box off whole.
  • The carried box. A bot setting out on a trip (through a portal, to the End, on a raid) takes a box from the chests or crafts one. Far from home with fewer than two free slots, it places the box, fills it with what it would stow, breaks it and picks it up with everything inside. At home, stow empties it first. info shows it as box: 12/27 stacks. See Houses and bases.

Sending a bot yourself

You don’t have to wait for a bot’s style to want the End. A player in its faction can send it, or the whole faction, with an order:

Commands
/aiplayer order Ann end
/aiplayer order @faction red outer

end makes the bot count as a style that goes to the End, and nothing else changes. It still has to get ready by its own bars (it tells you once what it lacks, like <Ann> Not ready for the End yet, I still need my best armor, enchanted gear), and an Easy bot refuses. Until it’s ready, it goes on with its normal life. Then it sets out without waiting for a full party, and ready mates come along when it calls. outer does the same for both trips. See Giving orders for how these orders end.

Technical details

End settings in the play style
playstyle.json (excerpt)
"end": {
"travel": true,
"party": 2,
"eyes": 16,
"kit": { "blocks": 128, "minecraft:bow": 1, "minecraft:arrow": 64, "food": 16, "pickaxe": 1,
"minecraft:water_bucket": 1, "minecraft:torch": 4 },
"outer": true,
"outer_kit": { "minecraft:ender_pearl": 4, "blocks": 128 },
"hop_gap": 64,
"hop_blocks": 192,
"search_radius": 512,
"flight": 200,
"rockets": 8
}

Every key is optional, and a style without the block doesn’t go. flight and rockets still apply to any bot that holds an elytra. A kit key is an item id or one of three words: blocks (cobblestone or end stone), food (cooked food) and pickaxe (a spare pickaxe of the gear goal’s tier). A style’s kit or outer_kit replaces the whole default. The difficulty’s end_dragon (default true, false on the shipped Easy) is the other switch, and its threats weigh ender_dragon (6.0) and shulker (2.0). The full tables are in Play style files and Difficulty files.

What /aiplayer info shows
/aiplayer info <bot> (excerpts)
end: stronghold unknown, frames 0 of 12, dragon alive; not ready: tier, enchantments
end: stronghold (120, 30, -400), portal lit, dragon alive; ready
end: in the End, on the platform; stronghold (120, 30, -400), portal lit, dragon dead, exit portal open; ready
end: finished, the egg in chest (12, 64, -30); ready for the outer islands
end: finished, the egg in chest (12, 64, -30); outer: gateway (96, 75, 0), city (1290, 81, -340), stripped, ship looted, 2 elytra home; not ready for the outer islands: outer kit
stronghold: (120, 30, -400), portal room (118, 28, -390)
stronghold: bearing 212°, 2 legs
eyes: 5 of 8 (3 pearls, 10 powder)
structures: warped_forest (80, 68, -110), end_city (1290, 81, -340) 5 chests
objective: the_end (score 0.90), end: fight
objective: outer_islands (score 0.90), end: raiding the city (3 of 5 chests, 4 shulkers killed)
task: slay the dragon (crystal) > shoot the caged crystal at 42, 79, 0 (aim)
flight: flying to (120, -80)
box: 12/27 stacks

The end: line starts with where the bot is (in the End, on the platform, at the gateway, on the outer islands, outer islands, searching (412 of 512 blocks out, 96 blocks laid), city at (x, y, z)). Next comes the faction’s record: frames 5 of 12 until the portal is lit; dragon dead, exit portal open, egg taken by Ann or egg gone; finished, the egg in chest (x, y, z); and after outer:, the gateway, the city, stripped, the ship and the elytra home. Last comes the readiness, or what’s missing (tier, armor, enchantments, potions, eyes, kit, outer kit, or style and difficulty when it never goes). While a trip runs, the objective: line shows its step: calling, waiting for the party, then fill, travel, fight, egg on the first trip and gateway, find_city, raid_city, ship, return on the second.

Operator commands for the End
Commands
/aiplayer debug <bot> objective the_end one End trip now, ready or not (a style that goes, or under an end order)
/aiplayer debug <bot> objective outer_islands one trip to the outer islands now, ready or not (a style that goes on)
/aiplayer debug <bot> objective gather_pearls one round of crafting eyes and hunting endermen
/aiplayer debug <bot> task fill_frame fill the empty frames of the known portal room with held eyes
/aiplayer debug <bot> task travel end walk to the faction's lit end portal and step in
/aiplayer debug <bot> task travel outer into the End if need be, then a pearl through the gateway
/aiplayer debug <bot> task travel home from the End, home through the open exit portal (from the outer islands, back through their gateway first)
/aiplayer debug <bot> task cross_gateway throw a pearl through the nearest gateway, out or back
/aiplayer debug <bot> task island_hop search for an end city in legs, bridging gaps within end.hop_gap
/aiplayer debug <bot> task raid_city raid the nearest end city the bot knows, alone
/aiplayer debug <bot> task loot_ship look out for the known city's ship, bridge to it and loot it

See Inspecting and debugging bots.

The faction's End record

Each faction keeps one record of the End, shared by its members and saved with the roster. It holds the stronghold’s portal room, how many of the twelve frames hold an eye, whether the dragon is dead, whether the exit portal is open, and who took the egg and which chest it’s stowed in. For the second trip, it also holds the gateway the party used, where it landed, the city it found, whether that city is stripped and its ship looted, and how many elytra came home. Every key is optional (a world saved before the End loads with an empty record). The record only grows: a flag stays once set, and the largest elytra count wins. The End is finished when the record says the faction took the egg, or that the dragon is dead and the egg gone. Any bot of the faction that holds the egg is noted as its taker within a second, however it came by it.

Known limits
  • Players aren’t counted in a party and can’t join the call. A bot ordered to the End alone with too few eyes has no member to ask, so it goes home.
  • The outer islands are the newest and roughest part of the trip. A leader that crosses back from the outer islands high above the arrival island can fail to get down, and the way down can’t dig down from a one-block pillar.
  • Any interrupt of the leader ends the trip and closes its call for ten minutes. The leader’s death ends the members’ fight (only on the second trip does a survivor lead on).
  • A bare portal pillar reads as the egg being gone, so if a leader loses the egg, the End still counts as finished. A bot whose own respawn point is buried gets left there by the exit portal.
  • A raider style that also travels loses its two-pearl hunt once the End is finished (no shipped style is both).
  • An end order given after the finish ends done right away instead of being refused.
  • A bot never bridges the void between the main island and the outer islands, never repairs an elytra, and never eats chorus fruit outside the End. The shulker box reserve is one per bot.

Last updated Nov 9, 2026