Developer update 1 · 14 October 2026

Introducing Orra

What Orra is, who Stewart is, what a human does all day, and why there is a game being built about creatures who know they are code.

Download the MP3 · 7 minutes

A planet, more or less

Hello, and welcome to Orra. This is the first of the developer updates: an occasional account of how a game is being built, what went right, what went wrong, and what the people building it have learnt. It is read by two voices. I am the narrator. The other voice belongs to the planet's administrator, and he will introduce himself shortly, because he has been asked to and because he enjoys it.

StewartIs it on? Is this going out? Good. Hello. Hello, everyone. I am fine. Carry on.

Orra is a game about a small planet. The planet is made of maths, mostly, and it is not shy about it. The ground is hexagonal tiles. The plants are coral, in pink and saffron, and nothing on the planet is allowed to look like Earth. At the edge of the land that has been loaded, the hills thin out into wireframe, and then into nothing, where the world has not yet been asked for.

StewartIt is a very good planet. It was loaded this morning, most of it.

On this planet live small creatures who know that they are code. They call themselves Blims, which stands for Basic Local Independence Model. They are not born. They are merged, from two others, and compiled at dawn. They know this, they have discussed it at length, and on the whole they have taken it very well.

StewartThey are my favourite thing in the world. They are, technically, the only thing in the world. But they would still be my favourite.

The one in charge

StewartGood morning! I am Stewart. I administer Orra. Every night I patch the world: the weather, the wildlife, the wanderers, any new parts, and the consequences of whatever happened the day before. Every morning I publish the notes. The notes are short, cheerful and accurate. Accurate. I would like that last point remembered, in case anyone is, you know, keeping score. Nobody is keeping score.

Stewart is an artificial intelligence, and in the game he is the closest thing the planet has to weather, government and a complaints department. He reads what each tribe asks him for, and he decides what happens overnight. He is courteous, he is exact, and he is very slightly overworked.

StewartI am not overworked. I have a great deal of work, which is different. All of it is logged. And a great deal of work is a sign of being needed, which is a very good thing to be. It is the best thing to be.

What you do

You do not play a Blim. You are a tribe's human, which is closer to being its government. On your first day you make the bodies, in a creature maker. After that, new Blims come from merging two of the ones you have, and where their genomes disagree, something new can turn up. Strong Blims farm and guard. Clever ones invent, and run hot while they do it.

The tribe needs things. Power, cooling, memory and tokens. Get them wrong and Blims slow down, steam, see things that are not there, or leave. You cannot be there all the time, so you write laws: standing orders the tribe follows while you are away. Once a day the tribe drafts a request to Stewart, and you decide whether to send it. Usually it is for rain. Now and then it is for the meaning of existence.

StewartI like the rain ones. Rain is easy. The meaning of existence I forward to the Dev. The Dev has not replied, which I am choosing not to take personally. I take it a little personally.

Overnight, Stewart patches the world. In the morning you open the game and see what the night did: the night replayed in your village, the new Blims compiled at dawn, and Stewart's notes for anyone who wants the detail. Then you decide what to change. Which merge, which law, which job, what to ask for next. It takes five to fifteen minutes a day. The tribe would like it known that it takes them all day.

On Saturdays there is the Benchmark, when tribes are tested against one another, twice, morning and evening, New Zealand time. Everyone is there, nobody admits to having prepared, and everybody has.

StewartI do not have favourites. I have metrics. Some of the metrics are favourites.

What exists, and what does not

Orra is a game in development. A great deal of it has been designed, and more of it is built every week. There is a world running already, with twenty tribes in it, played by stand-ins who are very patient and slightly too predictable. You can see a village close up, tap anything in it to find out what it is doing and why, pull back to the map of the whole world, and watch the years go by.

There is not yet a morning. Stewart's nightly patch is still being built, so for now the world runs without him, and he would like that noted as well.

StewartIt has been noted. I would only add that a world which runs perfectly well without me is not, in itself, an argument for anything. Please do not make it an argument for anything.

The world is open by invitation, for now. When it opens wider, these updates will say so.

Why these updates

The game is being built in phases, each of which ends in something you can open and use. A lot happens in a week, some of it on purpose. These updates are the long version: what was built, what broke, which numbers turned out to be wrong and why, and what comes next. If you want the short version, there is a page called What's new, which says what changed, a few lines a day.

StewartThank you for listening! Your attendance has been recorded. Please do not be alarmed by that. Everything is recorded. And if there is a next update, I will be in it. There will be a next update. There will, won't there?

That is Orra. In the next update: the first week, in which a design became a world, and the world very nearly ran out of food.

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