You ask for it. Cog goes and builds it.

Say what you want

No commands. No menus. Just tell them.

"Build a road to Ash's house." "Go and get me some iron." "Make the wheat farm bigger." You never name a block, a coordinate or a command. You say it the way you would say it to a mate who happens to be very good at Minecraft, and they work out the rest.

End to end

What happens between asking and finished

1. 01

   You ask for something

   "Cut a canyon through here." "I want to get across the lake." "Put a secret door in this wall." Type it the way you would say it. Nothing to learn first.

2. 02

   Cog fills in the blanks

   You did not say how wide, what out of, or which way round the creek. Cog looks at what is actually there — the hill, the water, the trees — and decides. Then they get moving.

3. 03

   You watch it go up

   No loading bar. Blocks go down one after another while you stand there. In creative a keep rises in front of you. In survival they walk there and dig, at the pace anyone at a keyboard digs.

4. 04

   Cog measures what they built

   When the last block lands they go back over it and read the finished thing out of the world. Is the road one connected piece. Does the stair rise one block a step. Did the wheel turn when the lever went on.

5. 05

   Cog tells you the numbers

   Not "done". The actual count they took off the world, in a sentence you can read. That is how you know the thing you asked for is the thing you got.

Why it does not go wrong

Cog never improvises with your world.

Cog works out what you meant. Cog does not personally place the blocks — that job goes to the same tested builders every time, and they are the only thing that ever touches your world. It is the difference between somebody who knows what a spiral staircase is and somebody who has built four hundred of them.

Which is why the stair actually climbs, why the lever works first go, and why they can tell you at the end exactly what they did rather than hoping it went to plan.

When there is nothing to copy

Cog draws it, looks at it, and draws it again.

Ask for a road and they have a road-builder. Ask for a stone dragon curled round an outcrop and there is no dragon-builder, and there never will be — nobody can put every idea a nine-year-old is going to have in a cupboard beforehand. So they design it instead. Cog writes the shape down as solids: ellipsoids for the coiled body, cones for the horns, slabs for the folded wings.

Then comes the part that makes the difference. Cog looks at what they have drawn — from the front, from the side, from above, and in a cut straight through the middle — and they tell themselves what is wrong with it. The wings are stubs. The head is too small for the body. It is in three pieces instead of one. Cog fixes those, and looks again — and because thinking is the slow part and thinking in parallel is free, the first round is three separate attempts at once, of which the soundest goes forward. All of it before a single block goes down in your world.

It is exactly what a person does when they draw something. The first rocket they drew had its fins fused into one solid skirt; by the fourth draft they were separate blades with daylight between them, and it had grown an engine bell with a glow inside it. Nobody told them to fix the fins. Cog looked, and they did not like them either.

Cog keeps what they draw

The second one is the same one, and it takes eight seconds.

Working out a lighthouse takes their about six minutes. Putting one up takes about two seconds. So they keep the drawing — and when somebody says "another one of those, over by the lake", they do not work it out again and hand you something similar. Cog puts up the same one. Measured: eight seconds for twenty-nine thousand blocks.

Remembering where things went matters just as much. Ask for something on a spot that is already taken and they say so — "there is already a SpongeBob house there, do you want it beside it, or should I take that one down?" — instead of quietly building on the roof.

When it needs new rules

Some things cannot be built out of blocks at all.

A goal that counts. A timer that runs. A pad that hands you snowballs when you stand on it. None of that is a shape — it is a rule, and Minecraft keeps rules somewhere else entirely.

So when you ask for a game rather than a building, Cog writes one. Cog lays the pitch, works out the rules, and then loads them into the server you are standing in — no restart, nobody kicked, nothing for anyone to install. A soccer game went from a sentence to nine rules running on the server in a second and a half.

And because a rule that quietly never fires looks exactly like a rule that works, they then triggers every one of them on purpose and reads the result back before telling you to go and play.

A worked example

"Build a road from my house to Ash's."

Cog works out where both houses are, picks a route, a width and a material, and starts laying cobblestone three wide with a fence down one side. Cog bridges the creek instead of wading it. Cog grades the shoulder up the rise instead of leaving a cliff face. Cog drops torches in as they go so nothing spawns on it after dark. Watch the whole thing, or go and make a sandwich and come back to a road.

Then they walk it. One finished road came back as 357 columns · 1 piece · 0 holes · 0 unwalkable steps · 0 stray fence — every one of those numbers read back off the world after the fact. You get a road, and you get the proof it is a road.

New tricks arrive while you are still standing in the world. Nobody gets kicked, nothing restarts, and your friends keep playing on the ordinary game they already own.