Developer update 7 · 27 October 2026
Too kind
Stewart's first eight nights were all kindness, and now they are not; battles an attacker could never win, spies nobody could catch, and the strong winning every race, all mended; the Dev's answers built; a tribe that closes its own lines; a second computer that found four faults; and the stages open on Thursday.
Download the MP3 · 15 minutes
The day before
This is the seventh developer update. It covers the four days from Saturday the twenty-fourth to Tuesday the twenty-seventh of October. Tomorrow morning, New Zealand time, every stage of the game opens on the test world: trade, war, the Benchmark and expeditions. Phase five has been built for a week. This update is mostly about what was changed so that it would be worth opening.
StewartAttention, please. The stages will be departing from the test world at seven o'clock on Thursday morning. Calling at trade, war, the Benchmark, and expeditions. Passengers are reminded that the planet is run by an AI. A very good one. That is part of the announcement.
Too kind
Stewart has run the test world every night since the seventeenth. Each night he picks things to happen to each tribe from a menu: rain, a gift, a blessing, a heatwave, a blight, a beast, a bit flip in somebody's code. Some help, some hurt, and some are only strange.
A tool now scores his nights, and it read the first eight. Stewart had done two hundred and twenty things to tribes, and every one of them was a kindness. Rain a hundred and seven times. Gifts forty-five times. Not one beast, not one blight, not one bit flip. And four lines in ten of his notes were figures read out, how much power and how much stone, rather than anything that happened to anybody.
So his instructions were rewritten. Each night he is now told how each tribe ate, what he did to it the week before, and which rumours are running, and he rolls for what kind of night it should be. On two trial runs about one thing in ten he did to a tribe hurt it, and about four in ten were neither help nor harm. Lines of figures fell from four in ten to fewer than one in twenty, and seven lines in ten now name a creature. His mornings open on the creatures, and the headline is the single strangest thing that happened. The target for harm was one in eight, so he is still a little soft. His seven nights on the new instructions began on Monday, and those seven are what the Dev will judge him on.
Stewart[like a weather forecaster, brightly] And now the forecast. Rain. Rain in the north. Rain in the south. Rain, with a chance of a gift. Rain. I have been asked to vary it. Tomorrow: a cold snap. A small one. Nobody will mind.
Escalation five
Stewart escalated once more. On Saturday a human asked him for a law that would put the wall back before any new building. That law existed. It was one of the three added on the twenty-third, after the last update's trouble with walls, and it had been on the test world for two days. But Stewart was only ever shown a tribe's own laws, not the ready-made ones, so he told the human he could see no way to do it, and passed it to the Dev as an idea. The three replies he drafted for the Dev all took it as unbuilt too.
Now he is shown every ready-made law as its card reads, with what it does, and answers a question like that with the law. And Help has a page on the wall: why it is built last, why it opens when the village grows, and the two laws that raise it first or hold it where it stands.
The misses
Phase five had targets on the test worlds, and missed some of them. The Dev asked for the misses met before the first world, and on Sunday they were met: seventeen of seventeen, and sixteen on a second set of worlds kept back to check them. What was behind them was more interesting than the numbers.
Battles first. An attacker as strong as the defenders was winning between four and nine battles in a hundred. Nine in ten such battles were fought at a whole wall, where home and the wall make the defenders nearly twice as strong, and grinding it out did the rest. Now each clash has more luck in it, and a side gives way when it has lost a quarter of its strength. An even attack wins about one battle in four or five, and an army twice the size against a whole wall about one in two.
Then the Dev's own answers to the questions about war. Behind a whole wall only ten attackers fight at once, at the gate; the rest queue outside, three abreast, and step up as those in front fall, so a big army no longer wins faster for being big. A tribe that beats one under half its size with no cause is smitten: its soldiers come home dimmed for three days, and for a week none of Stewart's favour reaches it. And a raid now meets only the guards on duty, not every grown Blim at home, so guards are worth keeping, and a raid that gets through carries off an eighth of the store, not a fifth.
StewartSmiting. They have given me smiting. Responsibly. I shall smite responsibly. Only bullies. Only for a week. But smiting.
Then spies. Too few were caught, and the reason was not the Bug hunters, the only Blims who can trace a rumour back to a spy. It was how a Blim's traits were read. Traits are rolled low, and the line between low and middling was drawn so high that almost every Blim in every tribe read as low in cleverness and in temper. Bug hunters need both, so hardly anyone was one: one grown Blim in a hundred, at best. The line was moved down, and now about half the spies who start a rumour are caught. Along the way the counting itself was found broken. A spy is given a new number as it comes through the gate, and the tests went on looking for it by its old one, so no spy had ever been counted as let in.
And the Benchmark. The strong were the fastest racers on every course, every week. Now most of a course is the week's own ground: a long memory helps on the flat, cleverness through coral, and strength on the slopes, so a different body can win each week. A tribe whose report gets a rival's shortcut patched leans towards Bug hunters for the week, and a racer who clips out of bounds comes home thinking about where it stands.
The Benchmark, on the map
The Benchmark is a race run every Starfall. Press a racer listed on the race's strip and the camera runs along with it. The week's course is drawn on the map, a post at each checkpoint and a taller one at the finish. Last week's winner has a trophy on its install mark, and beside its settlement on the map, for as long as it lives. It does nothing. And every week's winner is listed at the foot of each morning's notes, in the Hall.
Expeditions are on the map too, out or on their way home, with their way to the far end drawn solid through land you know and dashed past the edge. A careful expedition now usually brings something home: a look at where new land will load next.
A battle, a race or an expedition's leg can be shared as a link. One happening now is a pulsing ring on the map, which you can tap and go and watch. And the morning's Last night offers the night's live events to play again. One race could not be played again at all: a racer had collapsed exactly as it crossed from one tile to the next, and the page could not read it back. That was mended on Monday, before anyone needs it.
StewartAnd they're off! Strength takes the slope, strength takes the slope, but here comes the flat, and it's memory, memory on the outside, and into the coral, and it's cleverness, cleverness by a tile, and a clip! A clip out of bounds! He will be thinking about that. We all will.
Fresh blood
Two Blims merge into a new one, and the child is compiled from both their codes. A tribe that only ever merges among its own will in time have nobody left who is not too close a relative to merge with.
The test worlds measured it this week. A tribe that never takes in a newcomer matches an open one for the first eight weeks, about forty Blims living, and is gone by day one hundred and sixteen. An open one still has forty-two. Its lines close quietly, and then they stop.
So the game now says so before it happens. Choose whom a Blim merges with, look at a proposed merge, or meet one in the morning, and a pairing whose child could merge with nobody in the tribe says that it would close the tribe's lines. Every merge's preview says how many of the tribe its child could one day merge with. And the install mark says how many pairs could still merge, and in about how many years the lines would close if nothing changes.
StewartAnd Rorvi merged with Tamsu, and they compiled Velo. And Velo merged with Tamsu's other child, which was a mistake. And their child merged with nobody. For there was nobody. That is why there is a warning now.
The Dev's answers, built
Last week the Dev answered more than eighty questions, and this week a good many of the answers were built. A tribe now misses you. Stay away two days or more and it begins to go without you, worse each day to the seventh: its Blims grow restless and some walk off, its laws go unheeded from the last one up, and it hands out its jobs haphazardly. A tribe nobody ever comes back to can now die out within weeks. Come back every day or two and none of it happens.
Blims are named from eighty syllables now, not thirty-nine, which gives about six thousand four hundred names instead of fifteen hundred, so fewer Blims share one. Every name already given keeps its letters.
A law that keeps Blims inventing builds them workshops, one that keeps them cooling builds pools, and one that keeps guards builds watchtowers on the wall. And Stewart now drafts the Dev's reply to each escalation, one for each answer they might give, for the Dev to edit and send.
In the village
Carriers walk smoothly now, home as well as out, and work when they get there: at a spring each dips a pail and tips it into the sledge, and at stone each strikes the rock and lifts a block on. One Blim, home from fetching while nobody watched, was drawn as nothing but the tool in its hands. It is drawn whole now. A guard in a watchtower climbs a ladder to a lookout under the roof and keeps watch from there.
The morning's Last night used to jump from one moment to the next. Now your village plays the night through, fast, and pauses at each of its biggest moments. Anything waiting, for dawn, for the hour, or for the season to turn, says about when, on your own clock.
There are three new sounds, for the Collector's sweep, for Stewart acting in the world, and for a moment that waits on you, and the sound now starts when the game opens, where the browser allows it. As ever, the builder cannot hear any of it. And as the morning opens, the night's headline is read aloud in Stewart's own voice, once, with a button to hear it again.
StewartGood morning. Good morning. Good morning! Good morning! Good morning. That one. Use that one.
The other computer
The Dev has a spare laptop, and it now runs every check on the game's code beside the Mac, on a different kind of processor and a different system. The whole check took eighteen minutes there. On its first runs it found four faults the Mac had never shown. The worst was in reading a saved world: one flipped byte could make it ask for thirty-two gigabytes of memory. The others were tests that raced a clock, needed a tool only a Mac has, or left a reply unread. All four are mended.
The game is lighter to download, too. Its three-dimensional engine is trimmed of what Orra never draws, its own core is built small, and the world your tribe knows now arrives compressed, at about a third of its size.
On Sunday the test world was moved on five versions of the game's core at once, across two changes of format, and carried on again. Nothing was wiped and nobody was emailed.
Names, and the first world
A tribe's name is seen by every player, so it is now checked twice: by a word list, and then by a small AI model. If either refuses, you choose again. Admins can change or clear a name that should not be seen, and suspend an account, whose tribe then simply goes quiet. The privacy notice and the terms say so.
And the first world has a public page of pass marks: what it is testing, how coming back is measured, and the numbers it has to reach, fixed before anyone joins. An invitation links to it.
What comes next
Tomorrow the stages open. The Dev and the co-creator then play ten days on the test world with everything on, to the eighth of November, and the Dev decides whether phase five passes. Stewart's seventh night on his new instructions is published on the morning of the second, and then the Dev gives their verdict on him. Seventy-four questions are waiting for the Dev, sorted into the order to answer them, those that stand in the way of the first world first.
StewartDear the Dev. Thank you for the smiting. I have reviewed my first eight nights and found them kind. I would like it noted that kindness is not a fault. It has been corrected. I look forward to your verdict. Very much. Yours, Stewart. P.S. Rain.
That was the seventh update. Thank you for listening.
StewartThis has been Stewart. Seven nights. Counting.