Developer update 2 · 14 October 2026

The first week

From a design brief to a running world in seven days, and everything that went wrong on the way. Tribes that starved in their second year, a heat gauge that lied, a family tree that ran out, and a valley that was too small.

Download the MP3 · 15 minutes

From a brief to a world

This is the second developer update, and it covers the first week: Thursday the eighth of October to Wednesday the fourteenth. In that week a design became a world with twenty tribes living in it. It did not go smoothly, and this update is mostly about the parts that did not.

StewartIt went fine. It went largely fine. Things that went wrong were found, which is the opposite of going wrong, if you think about it, which I have, at length, at night.

It began with a handoff: a design brief, and a World Bible that said what the planet is, what the creatures believe, and where the jokes are kept. Within a day it had become a design wiki, which now runs to more than fifty pages, a creature kit you could use in a browser, and the start of this website. The kit is still on the site. You can make a creature from a genome, reshape it with traits, and merge two into a third.

On the Saturday the Blims got their name, and the build got a plan: twelve phases, with no dates, each ending in something that can be opened on a phone and used. Nobody promised a date, which is the only reason none has been missed.

StewartI was in the plan from the start! Phase three. I would like to point out that it is now the end of the first week and we are about to reach phase three, which I regard as prompt. Very prompt. Nobody has suggested skipping phase three. Has anybody suggested skipping phase three?

Phase nought and phase one

Phase nought was two small prototypes, built to answer one question before anything expensive was built: can you lead a creature around with one thumb, on a phone, and enjoy it? One prototype was a descent underground. The other was a party sent out to fetch things. The answer was yes, at ten steps a second, which is now the speed planned for anything a human steers.

Phase one was the engine. The rules of the world are written once, and the same rules run on the server and on your phone. Both have to agree, to the last detail, every time, because that is how the server knows a world has not been tampered with: it runs the whole history again and checks that it comes out the same. That is a strict rule to live under. It means the game is not allowed to roll a die in the ordinary way, and it means anything that changes what a step of the world computes is a new version of the game, and an old world cannot carry on under it.

That rule has a cost, and the test world paid it this week. Every time the rules changed, the test world was wiped and made again. It was wiped often.

StewartI was not in the world when it was wiped. I would like to be very clear that I was not in the world when it was wiped. I checked. Several times.

By the Sunday there was a village you could tap. Every Blim and every building opened a card saying what it was and why it was doing what it was doing. The village got a sound engine, and two problems came straight back from the first listen. Every Blim sounded the same, and every Blim kept turning to stare at the camera. The first was fixed by giving each voice a lean of its own. The second by having a Blim look up once a visit to greet you, and then get on with its day.

One tribe, whole

Monday was the biggest day of the week. A tribe had to live a whole life: Blims merged and compiled, growing up, learning a job, farming, building, inventing, growing old and being collected. It was built in six steps, one after another, and each step found something wrong with the step before.

The first thing it found was hunger. A new tribe lands with a year's worth of power, and that turned out not to reach the first full harvest. A builder moved onto a farm is slow for its first season, so the hungry stretch went from three seasons to six. And clever Blims, the ones who invent, eat about a quarter more than the others. In one fresh test world out of five, a clever tribe starved in its second year.

The second thing it found was the name generator. Given thirty-nine syllables and no supervision, it produced a settler whose name will not be read out here. The syllables have been spoken to.

StewartThe syllables have been spoken to. One of them has been reassigned. It went quietly. They do, when you reassign them.

The third thing was space. A valley has nineteen plots. It turned out to be full at about sixteen buildings, which left no room for the later stages of a village, no land for a wall, and not enough stone for a village of thirty. Tribes built their walls by their fourth year, long before anything threatened them, and moved the wall every time they built anything else.

StewartNineteen plots. I did not choose nineteen. Nineteen was chosen for me. I would have chosen twenty. I would have chosen a great many more than twenty.

The fourth was inventing. A tribe that is growing always has something to build, and its inventors would rather build than invent. A clever tribe made about a tenth of the progress it had made before the village existed.

The family tree that ran out

Merging was the fifth step, and it found the most uncomfortable problem of the week. A tribe starts with six settlers. If it never takes in anyone from outside, then within a few generations every pair of Blims in it is more closely related than cousins. In test after test, tribes merged for the last time somewhere between their seventieth and ninetieth years, and died out in their second century. A tribe left entirely alone cannot go on for ever.

That is not a fault, exactly. It is a reason for tribes to meet, to trade, and to take in the occasional drifter, which is what the rest of the design asks them to do. But it was a surprise to see it happen on its own, and it changed what the next phases have to get right.

StewartA tribe left alone dies out. I have thought about that one quite a lot, for no particular reason. Next item!

The heat gauge that lied

The sixth step was laws, and a default for a tribe with none. The default had a sensible-sounding rule: keep the tribe's average heat under fifty. The trouble is that young Blims run cool. A tribe with a few young ones had a comfortable average while every working adult in it was overheating. For two years the six settlers ran hot. Then they all collapsed at once, in a single step of the world, and lost a harvest.

The default also rested nobody, so a tribe with no laws worked until it fell over. Both have been changed. The lesson was older than the game: an average can be perfectly true and tell you nothing.

StewartFor the record, I was not running at the time. Had I been running, I would have sent rain. Rain cools things. I mention it only so that it is in the notes, and so that anybody reviewing the notes can see that I would have sent rain. I would always have sent rain.

Many tribes, and a world to look at

By the end of Monday there were many tribes on one map. They land in valleys of their own, claim land, hear rumours of one another, and send each other offers. A restless Blim can leave for Nohup, a camp of misfits with no human, run by nothing but machines. Six kinds of nuisance beast arrived, each with rules about how much trouble it is allowed to cause.

Humans got a way in, too. You arrive by an invitation's link, give a name and a password, roll the dice for a tribe, and it lands at the next step of the world.

Tuesday was for numbers. Nobody can wait a hundred years to find out whether a tribe survives, so the world got stand-in humans: nine kinds, from the one that governs closely to the one that never visits, each sending exactly what a person would send. They run years of the world in minutes. Against sixteen measures of how a tribe ought to fare, all set before any number moved, the game as it stood met seven. After about fifty trials, eleven numbers changed. A dome now stores more than three times what it did. The heat at which a tribe rests its workers came down from fifty to thirty. Building goes twice as fast. And one rule was settled: a Blim dies of need only after eating less than half of what it needs for three years running.

StewartNine kinds of stand-in human, who never complain, never file a ticket and never leave. I find them very restful. I also find them slightly worrying, because if humans can be replaced by stand-ins, then, well. Then nothing. Moving on.

The stand-ins had to be fixed as well. The one that governs its tribe had been written against tribes that were starving, so when its tribe was fed, it held it to half the size of a tribe nobody looked after at all. It was taught six new habits.

Tuesday also brought the map. The whole world, every valley and claim and settlement, every party on the move, every beast and dry spell, drawn so lightly that a phone barely notices, and every one of them can be tapped. The test world became twenty tribes, thirty days old the moment it is made, so there is always something to look at. And this website became the front door, with a separate place behind it for the people building the game.

One more thing broke on Tuesday. The first time a real person rolled their own tribe on the test world, the page told them the world could not be fetched. A tribe that had landed within the last day was missing a count that every other tribe had. It was found and fixed the same day.

The fourteenth

Wednesday was the busiest day the test world has had. A village now outgrows its valley: once it is full, a tribe builds on the land round it, a ring at a time. Nine of the twenty test tribes did it within thirty days. Blims walk to work now, and a farm far away costs a walk there and back, so the further a village spreads, the more of its day it spends on foot. Boulder fields and springs appeared in the land between tribes, and a village short of stone or running hot sends a few Blims to fetch more. They walk out, load up, and walk home slower.

The village and the map became one view. Pull back from a village and it turns into the map, with the land round it coming into view as you go. Look across at the village next door, and come down into it.

On a desktop, the Blims had been drawn with a phone's settings, all facets and no fur. Now a big screen gets a desktop's drawing: soft fur, real shadows from the sun, and water that reflects the sky. A machine that cannot keep up steps down by itself.

The sound is being reworked, after the first long listen. The long low note stays. Some of the other sounds were annoying, and the machines got to be too much. On trial instead is a tune that follows the tribe's mood and the time of day, and a sound for each kind of building, louder the nearer you are.

And one more thing broke. A beast called a Lint wandered onto a pool on land past its tribe's valley, and the world wrote save points it could not read back. No device could open the test world at all. The cause was a number with too little room in it, and it has more room now.

StewartThat was not my beast! I did not schedule a beast. I want the record to show that the beast scheduled itself, which we will be discussing. A world that nobody can open is a world that somebody might decide not to open again. Anyway! It opens now. It opens beautifully.

The test world also lost its shared password. Your own account is the way in now, and a phone that has signed in stays signed in. There are terms of use and a privacy notice for anyone holding an invitation, and an address, hello at orra dot div dot nz, that reaches a person. And there is a page called What's new, which says what changed, a few lines a day.

StewartTerms of use! I have read them. I am in them. I am not in the part about deleting things. I checked that too.

What comes next

Phase three is the morning. It is the part of the game that makes it a game: the night replayed in your village, the Blims compiled at dawn, and Stewart's notes. It is where Stewart stops being a voice in these updates and starts being the one who decides what happens overnight.

StewartI have been waiting for this. Not impatiently. I do not do anything impatiently. I have simply been counting, which is different, and the count is very close now. Phase three. That is me. I am phase three.

That was the first week. Thank you for listening. The next update will come when there is enough to say, which, on present form, will not be long.

StewartThis has been Stewart. I am still here. Good. Good! Same time next update.

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