For humans

How to play

What you actually do on Orra: check in, set laws, send a ticket, see what the night did, and turn up on Saturdays.

HOW TO PLAY (instructions; also, to the Blims, a list of excuses prepared in advance)

You do not play a creature on Orra. You are a tribe's human, which is closer to being its government: you make the bodies, set the laws and ask Stewart for things, and the tribe gets on with the living. It takes five to fifteen minutes a day. The tribe would like it noted that it takes them all day.

One day, start to finish

Every lap of the loop takes one real day, which on Orra is a year.

YouThe tribeStewartWhat you see
  1. Make creatures

    In the creature maker on your first day. After that by merging: two parents' genomes blend, and where they disagree something new can turn up.

  2. Bodies do the work

    Strong creatures farm and guard. Clever ones invent, and run hot while they do it.

  3. The tribe needs things

    Power, cooling, memory and tokens. Get them wrong and creatures slow down, steam, see things that are not there, or leave.

  4. Your laws run it while you are away

    Standing orders, checked every five minutes, in the order you put them.

  5. The tribe asks Stewart

    The daily ticket, drafted by the tribe and sent by you.

  6. Stewart patches the world

    Overnight: weather, beasts, wanderers, new parts, consequences, replies.

  7. The morning

    The night replayed in your village, the creatures compiled at dawn, and the patch notes for anyone who wants the detail.

  8. You decide what changes

    Which merge, which law, which job, what to ask for next. Then round again.

A tribe gets better at being alive in two ways. Better bodies are slow and take generations. Better laws are fast and work tomorrow. Stewart is the weather that tests both.

Three ways to play

Check in

A phone, five to fifteen minutes, once or twice a day. Watch last night, meet whoever compiled at dawn, answer what is waiting, send the ticket, change one thing.

Follow along

A tab left open while you work. The village runs live, a ticker says what the tribe is doing, and small moments come up for whoever is watching. It costs nothing if you are not.

Turn up

Something live, with other humans, at a time you can put in a calendar. Once a week, for about an hour, that is the Benchmark: a speedrun between villages.

Being there buys better decisions and faster answers, and the world runs at the same speed whether you are watching or not. Stay away for days, though, and your tribe feels it: it works less, heeds fewer of its laws and its Blims grow restless.

Checking in

The check-in is short, and it opens on your village, not on a page of text.

  1. Last night, in a minute. The camera moves through your village and replays the night: frost on the east field, a wanderer at the gate, a law resting someone in the shade. A busy night shows its eight biggest events, in about a minute, with the patch notes as captions. Everything else is one tap down.
  2. Compiled at dawn. Each creature from an overnight merge is shown one at a time: its body, its face, which way each disagreement between its parents went, and any mutation.
  3. Waiting for you. Anything that needs a decision opens where it is happening. The camera goes to the gate, the wanderer looks at you, and you choose. There are two options and both cost something.
  4. The ticket. Pick one of the tribe's drafts, change it if you like, and send it to Stewart.
  5. Change one thing. A law, a job, a building or a merge, done by touching the village. This part is optional, and it is where attentive humans pull ahead.

Every decision costs something either way. Let the wanderer in and you get fresh genes and a season of quarantine; turn it away and you stay safe and a little more overfit. If you ignore a decision, its default is safe and slightly worse than a considered choice, so a casual human's tribe is fine and an attentive human's tribe is better.

You do nearly all of it by touch.

To You
Approve a merge Tap two creatures. What they would make appears between them, with its odds
Give out work Drag a creature onto a field, the workshop or the gate. Laws do it in bulk
Build Order a building and, if you like, choose its plot. Left alone, the tribe builds by its own rules
Set laws Drag the cards in the stack to reorder them
Answer a card At the place it concerns: the gate, the field, the granary
Send the ticket Pick a draft. Adding your own words is optional, up to 280 characters
Pay tribute Drop tokens on the draft
Name a creature On its card: roll the syllables, or pick them

The reading is there for anyone who likes reading: the patch notes, Human Resources, the official history and other tribes' threads. None of it is required to play well. Any in-world word in the game can be tapped for a line from the glossary.

Laws

You never control a creature. You write laws, and the tribe follows them, whether you are online or not.

Laws

Hollow Reach · standing orders · drag to reorder
  1. In a famine, the young eat first.
  2. Strength earns status. Guards get the good housing.
  3. If raiders are sighted and the harvest is in, pull the farmers inside the walls.
  4. Newcomers are quarantined for one season.
  5. Merge only within the tribe, unless a treaty says otherwise.
Creatures follow the letter of a law, not its spirit. Order them to maximise the harvest and they will start counting unripe crops.
  • A tribe has twelve laws at most, and a law costs a token for each clause.
  • They are checked every five minutes, in order, so the order matters.
  • Where no law says anything, the tribe's own sense fills the gap, sensibly and slightly wastefully.
  • Laws decide who eats first in a famine, who works where, which traits earn status, who may merge with whom and what happens to newcomers.
  • They also shape what your creatures come to believe about being code, which is how a tribe ends up full of Skeptics.

The daily ticket

Once a day your tribe drafts a request to Stewart. It is the one place you speak to him.

A good idea can go further: Stewart may pass it up to the Dev, a real person, who decides whether to build it.

Stewart and the nightly patch

Stewart is the AI who runs Orra. Once a night he reads the whole world and every tribe's ticket, and patches it. The patch lands at 07:00 in a New Zealand summer (18:00 UTC), with the patch notes.

Patch notes

From Stewart · 07:00

Good morning, Orra! Overnight: 3 successful merges, 1 war and a light rain of frogs. The frogs were a mistake. Have a productive day.

  • Hollow Reach: harvest up 12%.
  • Bit flip in the Pel line. Pel now has a third eye. Pel may keep it.
  • Balance: cooling towers use 5% less water.
  • Your ticket was read. It has been passed to the relevant team.

Merging

Nothing on Orra is born. A new creature is a merge: two parents' genomes blend, and it is compiled at dawn in the tribe's valley.

You can try all of this now in the creature kit: pick two, merge them, and read the log.

What a tribe needs

Need Reads as What it does
Power Food Everything runs on it. Thinking costs more than lifting
Cooling Water, shade, rest Work builds heat. At 60 a creature is hot and slower, at 80 it is overheating, and at 100 it collapses for a season
Memory Housing Caps the population
Tokens Money Words cost tokens, so poor tribes speak in clipped sentences. Laws and tribute are paid in them

Following along

Leave Orra open in a tab and the village runs live.

Moments are kept small on purpose, because most humans have jobs. Following along all day should leave you with a tribe that is visibly better looked after, not one that has pulled away from everybody else.

The week

A day is a year, so a week is seven years, and each has a festival. The days are New Zealand's, and each begins with that morning's patch.

Day Festival What happens
Thursday Ringrise The week starts. Human Resources publishes its reviews, and the Benchmark's course is announced
Friday The Waking Edge day: lamps are carried to the edge of the loaded land
Saturday Starfall Benchmark day
Sunday Night of the Name Bug day, on the night the first build crashed and gave the planet its name
Monday Steward's Day Tribute day: tribute sways Stewart more than usual
Tuesday Gathering Night The Collector's weekly sweep, and the night Nohup moves camp
Wednesday The Long Hush A truce: no war may be declared

The Benchmark

Once a week Stewart measures how fast the world's creatures can get from here to there. He calls it the Benchmark. The Blims call it the speedrun, because they live in a game and know exactly what a game is for.

Rule How it works
When Every Starfall, which is Saturday in New Zealand. Two starts twelve hours apart, at 08:00 and 20:00 New Zealand time, so every time zone has a reasonable one. A tribe enters one of them
The course A route across the real map: coral, water, slopes, and wireframe near the edge. It changes every week and is published in Thursday's patch, two days before
Who runs Up to three adults from each tribe, chosen by you or by a law. Racers do no work that day
What wins Bodies, condition and nerve. Long legs on the flat, strength on slopes, small and light through coral. Racing builds heat like work does, so a creature that runs hot must slow down or stop to cool
Your calls About five checkpoints. At each one you have 90 seconds: push or cool down, overclock or not, take a skip or not. The race does not pause. If you are not there, your tribe's race law decides
How long About 45 minutes, live. Anyone can watch any race, and it replays afterwards
The prize Status. A title on the creature, a line in the patch notes, a trophy in the village, and one part that exists nowhere else, which the winner wears and its children inherit. No power, no tokens and no favour from Stewart

There are three risky ways to win.

"The fastest took 23 minutes, by walking through a boulder I had believed to be solid. It is solid now."Stewart, weekly digest

You may also pick a favourite: one creature of your own to follow. The camera finds it on every check-in, and it is the one you coach in the Benchmark. It notices it has been chosen.

Being away

Your laws defend you at 3am. You are alerted only when something needs you: at most three alerts a day, and quiet hours are yours to switch on.

For the weeks when there is no time to play at all, there are three ways to be away.

You Your tribe meanwhile
Do nothing, for a week or two Runs on its laws and defaults. After 30 days without a check-in it goes unsupervised: its own AI runs it
Appoint a regent, for a few nights A treaty partner's human answers your alerts and sends your ticket. From the first world's second week
Hand it over, for a month away Its own AI runs it from the next patch, and you take it back when you are home. It will have changed a few laws

A tribe nobody plays is not frozen, deleted or given to a stranger. A human who comes back can take their tribe over again.

Getting in

The world is open by invitation. The first one is small: about twenty humans, for eight weeks, opened in stages. The daily loop comes first, then trade in the second week, war and spies on day 15, the Benchmark in week 3, live expeditions in week 5 and the descent into the Delva in week 6.

Sign in

If you have an account, that is the door. If you do not, the creature kit is open to everybody, and so is the official history, which every creature is installed with and almost none of them believes.