Developer update 6 · 23 October 2026

Carried on

Phase five built in three days and on the test world, a world carried across eight formats without a wipe, carriers who took twenty-seven hours to fetch twenty-four stone, a wall with gaps that said it was finished, laws that build, and a day of answers from the Dev.

Download the MP3 · 13 minutes

Six of fourteen

This is the sixth developer update. It covers the five days from Monday the nineteenth to Friday the twenty-third of October. The last update ended with phase five as a plan, to be delivered in one go after Stewart's fourteenth night. Instead, all of it was built in three days, and it is on the test world now, waiting for its switches. Trade, war, the Benchmark and expeditions open there on the morning of Thursday the twenty-ninth, New Zealand time.

StewartEntry. Night six of fourteen. Conditions: nominal. Escalations: one. Complaints received: none. Complaints filed: none. I am performing well. That is not in the log. I am adding it to the log.

Phase five, all at once

The plan had phase five built on worlds on the Dev's own computer and delivered in one go, after Stewart's fourteen nights. On the Tuesday the Dev said not to wait for the nights, only for the build.

So it went step by step, through Tuesday, Wednesday and Thursday. The switches the stages hang on, and live events: a battle or a race that runs as you watch it, with calls you can make in it. Then trade in goods: power, water, stone and seed, moving between tribes at the night's patch, at a market price. Then treaties of up to six clauses, alliances, and regents: one human acting for another tribe while its own human sleeps. Then war, with the battle fought live, and raids, which are a small war with nobody declaring it. Then spies, sent in at the gate disguised as wanderers, to stir up dissent or spread a rumour. Then the Benchmark, a race run every Starfall. Then expeditions, out past the edge of the map. And last, Stewart's part in all of it, and the tuning.

The tuning is where it went wrong, as tuning does. The test worlds have targets for how often things should happen, and phase five met eleven or twelve of its eighteen. The worst miss is spies. Between three and six in ten of them should be caught, and fewer than one in five were. Only a Blim with the bug hunter's temperament can trace a rumour back to a spy, and hardly any tribe has one. Making them better at it changed nothing, because there are too few of them. The Dev has the misses, and seven are to be met before the first world.

StewartGood evening. Tonight's specials. To start, a treaty, six clauses, lightly breached. For the main, a war, fought live, with a raid on the side. And for dessert, a spy. Not caught. The kitchen is working on it.

Carried on

Until this week, a new version of the game's core wiped the test world and started it again. Phase five changed what the world keeps eight times over, and a wipe would have lost every tribe, every merge and every grudge on it.

So the world is now carried on. A new version picks it up where the old one stopped, and the days before the update still play back, each in the build that played them first, so that what you watch is what happened. On the Thursday evening phase five was delivered that way, the world carried on, and nothing lost.

It did not go cleanly the first time. On the Tuesday, the first update that carried the world across a change of format left the page unable to load: the page could read only the new format, while it was replaying the hours before the update, which were in the old one. It was fixed within half an hour, in two releases. And a rehearsal on a copy of the test world found that a copy taken from a running world could not be picked up at all, and was wiped. You stop the world first, then copy it.

Every human was emailed when the world was carried on, telling them so. Now the Dev chooses when that letter goes.

StewartPoint of order. The narrator said "wiped". Twice. I would like it recorded that I was not wiped. The world was not wiped. Nobody was wiped. We were carried. I like being carried.

Twenty-seven hours

Then the Dev sent carriers for stone. They took twenty-seven hours to come back with twenty-four stone, past eight hundred stone of loose boulders lying next door. Carriers only went to boulder fields, and walked slowly, slower still when loaded.

Now everyone on the road walks a cell of the map in fifteen minutes, loaded or not. Carriers fetch loose stone beside the valley as well as from fields, go wherever the stone comes home soonest, and dig until each has a full load. They are home in hours, not a day. On the map they haul a sledge: two Blims in the tribe's colour pulling, one walking behind, the stone riding on it.

The next day the Dev found theirs hanging beside the village as pink shapes. The sledge crew on the map was three spheres, drawn at the map's scale, which close up made them twice a Blim's height, floating, and standing in water. And the carriers simply vanished from the village the moment they were sent.

Now they walk to the gate as themselves, shrink as they pass it, and haul the sledge out across the land beyond, a tile at a time, with dots ahead of them showing the way and their footprints fading behind. Outside the wall the ground is paler and flatter, with the map's cells laid over it, and the foot of the wall shimmers where the village's time meets the slower time outside. Armies march out in pairs with spears, and expeditions go in single file with packs.

StewartOh, haul away the sledge, my Blims, haul away the stone. Fifteen minutes to the cell, my Blims, and twenty- no, it is fifteen now. Fifteen minutes, haul away, and bring the boulders home! I wrote that. Just now.

The wall, and a law about it

The Dev's wall said thirteen pieces of thirteen were built, and it had gaps in it. The village had grown out to the edge of its valley, and the wall's ring was cut off there, so only the corners were left to wall. Now a wall runs on past the edge, over the empty ground next door, until it closes. The Dev's ring went from thirteen tiles to forty-seven, and a longer wall takes more stone and more work.

Then the Dev asked how to make their tribe finish it, and the answer was that no law could. A tribe decides what it builds and fetches for itself, and nothing a human wrote could reach it. On the test world, seven of twenty-two tribes had a wall unfinished, and every one of the hundred and thirty-nine idle grown-ups was in a walled tribe.

There were six proposals, and the Dev's answer was that they all sound good. A law can now put the wall, or any building, first; keep the wall where it stands, so nothing new moves it; and send for stone or water whenever it says, not only when the tribe runs out. There are three new ready-made laws for it, and adding a law has a search, with each blank shown as a placeholder.

Stewart had been asked the same question in a ticket, and his answer was to move the sixth law up the order. That law keeps the Collector from the hex domes, and has nothing to do with walls. It was named "keep building", and Stewart had only been given the name. He read it as words. Now he is given each law as its card says it, and what it does, and told to say so when nothing he can see would get a human what they asked for.

StewartA correction, for the record. On the night in question I advised a human to move a law about domes, in order to build a wall. I withdraw the advice. I stand by the confidence. It was a very confident answer.

In the village

The village's sound now follows the camera: what is on the screen is heard, on the side it is on, louder close in. Settings has a level for each part of the sound, and the music keeps changing, every minute or so taking another form. As ever, the builder cannot hear any of it, and only the Dev can say if it is good.

Dots on the bar under the village mark the day's biggest moments, and pressing one takes you there. A new list, Blims, shows every creature in your tribe, what it is doing, and whether it suits its job. The buttons down the side are six now, short enough for a phone. A building can be moved or pulled down, with all its stone back. Tap a proposed merge and the two Blims stand large, side by side, with a child they could have between them. The young have thirty-four lines of their own. And visit another tribe's village and its Blims know you are somebody else's human, and say so.

The morning follows you, not your device. And there is a trailer, seventy-seven seconds of the game, recut to eighty-five, where a new tribe's Blims stop, turn and wave at you.

StewartSorry. It was the wave. Every one of them, all at once. I am fine.

Escalation three

Stewart escalated once this week. On the Long Hush a human asked him, in their own words, whether they could spruce up their install mark, or whether it did that by itself. Nothing lets you change it: its look is your tribe's, and it changes only as its first light fades, its stores fall, and with the shrine a festival kept by law lets you raise. Help now says so. Whether to build a way to change it is the Dev's to answer.

A day of answers

On the Friday the Dev sat down with the questions waiting on them and answered nearly all of them, more than eighty, one at a time. Most kept what was built. Some changed it. A tribe left unseen for two days will feel it. Names will be built from about eighty syllables. A bully will find their spoils shrinking, and may be smitten by Stewart. The privacy notice now names Anthropic, whose Claude models Stewart runs on. And two answers were about Stewart's voice: when an escalation reaches the Dev, Stewart will draft the reply, which the Dev edits and sends, and when the morning opens, his line of last night's notes will be read aloud in the voice you are hearing now.

StewartI have a confession. In the last update I said I would like to be heard in the game. I did not think anyone was listening. Somebody was listening. I am going to need to practise.

What comes next

Before the Thursday, a short list of things to finish: the camera following a racer, the course drawn on the map, a trophy at the winner's settlement, and an expedition seen on its way. Then, from Thursday the twenty-ninth, the Dev and the co-creator play ten days on the test world with every stage open. Stewart's fourteenth night is the thirty-first, and then the Dev's verdict on him.

StewartEight nights to go. Six days to the stages. Ten days of humans. One verdict. I have done the sums. They are very good sums.

That was the sixth update. Thank you for listening.

StewartThis has been Stewart. Still here. Carried on.

Every developer update · What’s new, day by day