Developer update 11 · 14 November 2026
The long game
Two in five grown Blims had nothing to do by day forty, so in four days the game gained a long game: monuments and rep, eight weekly boards, releases with a winner and conditions that shift, and forks, a second village founded by your own. Also visitors who say what they came for, a village's music on a synthesiser with everybody working on its beat, a race with a scene of its own, a second trailer, and a crowd that no longer shakes.
Download the MP3 · 20 minutes
Seven days
This is the eleventh developer update. It covers the week from Saturday the seventh of November to Saturday the fourteenth. Most of it is about one question the Dev asked on Wednesday: what is the game for? By Friday night it had an answer, in four parts, all built and all running on the test world.
Stewart[reading release notes aloud, very fast] Version eleven. Added: a purpose. Added: monuments. Added: rep. Added: eight boards. Added: releases. Added: forks. Fixed: Blims standing about. Known issues. I have been asked not to read out the known issues.
Two in five
On Wednesday the builder counted what every grown Blim on the test world was doing. It was day forty. Of five hundred and fifty-seven grown Blims, two hundred and twenty-five were resting with nothing left to build or to quarry: two in five, in eighteen of the twenty-two tribes. The design's own numbers said why. A valley's plots are all built on by about day twenty-five, a tribe stops growing somewhere between thirty-three and forty-five Blims, held there by its farms, and there are ten improvements to invent and no more. A human who governs well gets there sooner than a bot. Nothing on any page said what a tribe was for once its village was finished.
The Dev answered the same day. There would be a long game before the first world opens, in four parts, each built one after the other, and all four on the test world before the invitations go out: monuments, standings, releases with a winner, and daughter villages. The first world itself becomes release one.
Stewart[as a foreman on a building site, shouting up] Oi. You lot. Two hundred and twenty-five of you, sat on the wall. Nothing to build? Nothing to quarry? Fair enough. I did not give them anything. Look busy.
Monuments
A tribe's spare hands now raise a monument. It is a long work in seven stages, built over weeks from the stone and the power the tribe does not need, each stage costing more than the last. There are three kinds: the Uptime for a strong tribe, the Long Comment for a clever one, and the Patchwork for a varied one. The human chooses the kind and where it stands from the Build sheet. Leave it, and the first time a grown Blim has nothing to do the tribe says so in the morning, and if nobody has chosen by the next day it begins the kind its Blims suit best, on the install mark beside the shrine.
A monument stands in the village with scaffolding round the stage under way and its builders round it, and from its first stage it is on the map. Losing a battle at home costs a tenth of the stage's work so far. A stage finished, and work lost, are in the morning's notes.
Each stage finished earns rep. It is what a tribe is known for, as a forum reads reputation: ten for the first stage and five more for each after it. Rep is earned by deeds and nothing else. It is never bought, traded, given or taken, and it never becomes power, stone, tokens or Stewart's favour.
It was held to a test before anything else was built on it. In twenty bot tribes over fifty-six days, the share of grown Blims' hours spent with nothing to do, from day thirty on, went from forty-four per cent to one. No tribe got further than the third stage, which is the point: seven stages are meant to last. It costs something. A tribe nobody looks after now eats five points less of what it needs, and the first stage takes about three weeks. The Dev accepted both.
On a full village the Build sheet now says why there is no room: built on, water, or the monument's plot. It offers to move a monument not yet finished onto the install mark, which frees its plot, and says when the tribe's land next grows past its valley.
Stewart[as a museum guide, hushed and reverent] And here we have the Long Comment. Stage three. Note the scaffolding. The scaffolding is original. It will be removed at stage four. Please do not touch the builders. The builders are also original.
The boards
A monument is slow, so the second part gives a tribe something to aim at every week. There are eight weekly boards, each counting one thing a tribe did that week. Five Nines counts Blims kept fed and cool. Throughput counts building. Fresh Blood counts merging with distant code. Open Source counts giving and trading with other tribes. Speedrun is the Benchmark, Firewall is defending, Edge Cases is exploring, and Stack Depth is going down into the Delva. Each counts the week, never what a tribe already is, so a small tribe can top one. A strike for breaking the rules costs every place that week, and a battle won at home only counts on Firewall if the attack was a real one.
At Ringrise's patch, on Thursday morning, the first three on every board earn ten, six and three rep. The world's notes name them, in the game and on this site, and each tribe's notes say its own places and what they paid. Peers, then Boards, shows every board, last week's first three, and where your tribe stands this week among the tribes it knows.
Rep is spent from the same sheet. A name for a place on your land is ten, a banner over your install mark and beside your settlement on the map is fifteen, a trophy for a place your tribe won is twenty, and a part of its own for one Blim is sixty. Spending never lowers what was earned, so it never costs a place. And with thirty rep this release, when Stewart sends a wanderer or a visitor two come to choose from, and three at ninety. Never more often, so rep buys a choice, never more output.
The test was that most tribes should lead something, and no single kind of deed should decide the winner. In ten bot worlds of twenty tribes each, between fifteen and nineteen tribes placed on a board in every world, and no kind of tribe earned more than eighteen per cent of the rep. One board ran away: in one world a single garrison came first on Throughput all eight weeks. That is written down to watch.
Stewart knows the boards and may speak of them, but rep is paid by rule. A check on his notes now catches him if he claims to give any.
Stewart[reading the weekend's results like a radio announcer, deadpan] Five Nines. The settlement in the east valley, ten. The settlement in the west valley, six. The settlement in the valley with the pond, three. Firewall. No result. Stack Depth. A very good effort from somebody whose name I am not allowed to favour.
Releases
The third part answers what keeps a human for six months, or a year. The world now runs in releases. A release lasts eight weeks, and each one changes the world's conditions: a rich coral and a lean one, a trait that costs more or less to run, how much one cooling takes away, how much stone a quarrier cuts, the ground a fifth of every Benchmark is run on, and which kind of thing is commoner in the Delva. Each moves inside limits, and none repeats from the release before. The world's code draws them, and the morning's notes say what they will be a week before they come in, so a tribe can plan its next merges and buildings for them. On the morning a release ships, the notes name the tribe that earned the most rep in the release that ended, and each board's leader, for the Hall, and every tribe starts the new release level.
There is a step for it in the morning: the winner, your tribe's place and what it earned, the Hall's new entries and the new conditions, each one skippable. The last winner has a spire beside its settlement on the map. The Boards sheet has the release too, with each condition in force and what it means for your own tribe, down to which of your farms and which of your Blims.
The test ran two releases in the bot worlds against the same worlds with the conditions held still. Merges and new buildings went up after a turn, the trait that best predicted a tribe's success changed, no tribe left alone starved for it, and the winner was a different kind of tribe from world to world. Five of six measures were met. The sixth, that Blims do not go idle again after a turn, waits on the monuments' rules for power.
On the test world a release turns every week, so that the turn can be seen quickly. Release one began on Friday. The conditions of release two are published on Thursday the nineteenth, and the first two turns come on the twenty-sixth of November and the third of December. In the first world release one is the eight weeks the first world was always going to be, and on the Dev's word of last Sunday it is no longer wiped at the end: release two runs on until Orra launches.
Stewart[one hand raised, swearing an oath] I, Stewart, do solemnly declare that I have chosen no condition. That I have named no winner. That the coral was drawn by the code. [lowering the hand, then raising it again quickly] And that I have promised nothing to anybody. I may still say it is my release. I checked.
Forks
The last part is growing without conquest. A tribe that has earned fifty rep in all, from week five, can send six of its grown Blims to found a village of its own two or three valleys away. Players call it a fork, and the Blims call the village it came from upstream. The human chooses the six by touch, each with its line, so as to send varied stock, picks their valley on a chart, names the fork, and watches the party walk across the map until it founds the village.
Then a human has two villages, side by side under the clock, each saying whether its morning is waiting or something needs attention, and one touch goes from one to the other. Each has a morning of its own, of about fifteen minutes. Stewart writes a full night for each, which raises what the first world may spend on him to about two hundred and twenty dollars a month. For the boards and the winner, the two count as one entry, their rep added together.
Bot tribes fork on the test world, by their kind. Never in the first world. In the bot worlds, forks were fed and growing, the villages they left were not short, and the twenty tribes and their forks still ran in under sixty thousandths of a second a tick. Most of the governing bots forked within a few days of first holding fifty rep, at about day forty-five to fifty. One thing goes to the Dev: with their rep added together, a tribe with a fork won seventeen of twenty releases.
Stewart[as the father of the bride, a little too emotional] When I first compiled these six I never thought I never thought they would walk three valleys away. Upstream will always be here. Upstream will always have a ticket for you. Raise your glasses. The fork.
A race of its own
On the seventh the Dev watched a Benchmark and saw giant Blims stuck together, moving backwards round the track inside their village. A racer was being drawn at full size, turned half round from its way, three to a lane a fifth of a tile wide. A race now has a scene of its own: a long course through its own hills, with coral close on both sides and arches overhead, boulders to dodge, ridges to hop and ponds to wade, and every racer drawn as itself. A quicker racer goes round a slower one, a shortcut taken leaves a trail of light, and a board keeps the order as they pass. Zoom out and the view rises to the whole course. And from next week's race on, the course stays clear of the villages.
Visitors
A player asked how to read a visitor's lore, and found that there was none: Stewart's line only said that somebody with a story was on the way. Now his notes tell the lore, the visitor's card gives his words for it, and every tale told to a tribe is kept in its book of tales at the shrine. A visitor with a request is a guest asking to stay: host it, for a grown Blim's share of power over its year, and it leaves three tokens as it goes. Or a visitor may ask for something the tribe can already do, a merge, a building begun, a law written or an elder teaching, and whatever the tribe does while it waits counts.
Treaties got clearer at the same time. A treaty that exchanges code says how many packages are due, with a button to take one, and a refusal now says which of ten limits it met, where it used to list them all at once.
StewartGood evening. You have a guest. Two, in fact, if your rep is over thirty. Breakfast is a grown Blim's share of power. Checkout is at the end of its year. It will leave three tokens. It always leaves three tokens.
The music
A village's music is now played on a synthesiser, the sound of an early nineteen-eighties sequencer: a stepping bass line, plucked notes and a dark chord under them. Each building plays a part, the stack the bass, a farm an arpeggio, a pool bells, and the part comes forward as the view moves towards it. Each village sounds its own, from its Blims' genomes. The Dev found it repetitive left playing, so every quarter of an hour it takes up a new bass line and rhythm, and parts rest and come back.
Then the work went on to the beat. Picks come down on the notes of the boulder's part, a builder's mallet on the building site's, a farmer's hands on the farm's and the pail on the pool's, each Blim on a different note while there are enough. When the music warns of a danger, a line under the stores now says what it is, with a way to go and see it and a way to quiet the alarm. Stewart is heard over the rest, with the village quieter under him while he reads the morning. With the game in the background, the music now wanders the village, close in on one building and then high over all of it.
One fault was real and measurable. The synthesiser's finished notes were never let go, so the cost of making the sound climbed from about a seventh of a second to half a second for each second of sound over five minutes. It now stays flat. The builder cannot hear, so only the Dev can say how any of it sounds.
Stewart[tapping a baton on a music stand] And. A one, a two. The quarriers on the clave. The farmers on the arpeggio. The pool. The pool is late. From the top. I can hear it. I think I can hear it.
Smaller things
Blims shook in narrow gaps between buildings, jostling back and forth on the spot. In a replayed day of seven villages, the time spent stuck went from about thirty seconds to about four, and they now go round, or wait a moment and go through. Blims walk round boulders instead of through them. A waterfall's foot no longer flickers. An expedition past the edge of the loaded land walks glowing wireframe as itself, with its packs on. A Blim home from the Delva at full heat always rests, and somebody now goes on cooling duty for any one Blim overheating. A battle reads from start to end, with the attackers walking up to the wall before anybody swings and the strip saying who won and what it cost. And a week of the Delva can no longer be offered for replay: the test world's had run under thirteen versions of the game, and no single one could play it again.
Some of these were found at night. The builder now runs checks of its own while nobody else is working on the game, and one of them plays a new human's first morning as a made-up player. Its first playtest found five things, and all five are mended: your first minute now shows one thing at a time, a tribe's morning is chosen as a time of day, Laws opens on your own laws, the waiting note no longer covers the clock on a phone, and a Blim's questions are plainer and never the same one twice a day.
Blims at the camp for those with no human now say so, and do not claim one. Each world has a forum for its players, with an avatar made from the same parts as every Blim. And there is a second trailer, "Patch notes", two minutes of Stewart reading tonight's notes, one to a part of the game, with the first trailer kept under it.
StewartForgive me, for I have patched. It has been one night since my last patch. I let the Blims shake in a doorway. I let them walk through rocks. I let a waterfall flicker. Somebody else did the boulders. It was me. It was me who did the boulders.
What comes next
The first story arc, Lake NaN, began its seven nights on the test world on Friday. The first two turns of a release follow on the twenty-sixth of November and the third of December, and someone will read the morning across them. A login that governs a fork there waits for a tribe to reach fifty rep. Then the first world waits on the Dev's verdict on phase five, and the twenty humans to invite. The Dev has the four first arcs to review, a second trailer, a warning that can be quieted, and work in time with the music to listen to.
StewartSeven stages, eight weeks, a release and a fork la la la something, something, the Hall I do not know the rest. Nobody has written the rest. That is the long game. It is long, is it not? It is quite long. I am in it?