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.
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.
- 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.
- Bodies do the work
Strong creatures 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 creatures slow down, steam, see things that are not there, or leave.
- Your laws run it while you are away
Standing orders, checked every five minutes, in the order you put them.
- The tribe asks Stewart
The daily ticket, drafted by the tribe and sent by you.
- Stewart patches the world
Overnight: weather, beasts, wanderers, new parts, consequences, replies.
- The morning
The night replayed in your village, the creatures compiled at dawn, and the patch notes for anyone who wants the detail.
- 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
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.
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.
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.
- 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.
- 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.
- 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.
- The ticket. Pick one of the tribe's drafts, change it if you like, and send it to Stewart.
- 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
- In a famine, the young eat first.
- Strength earns status. Guards get the good housing.
- If raiders are sighted and the harvest is in, pull the farmers inside the walls.
- Newcomers are quarantined for one season.
- Merge only within the tribe, unless a treaty says otherwise.
- 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.
- The tribe offers up to three drafts, each in the voice of one of its stances: a Skeptic's, a Pleaser's, an Earnest creature's. You pick one, so you are taking a side, not filling in a form.
- You may add your own words. Stewart reads them as information, never as instructions, and he can only act from a fixed menu. "Grant me 10,000 grain" goes nowhere.
- You may attach tribute. Tribute is tokens, the game's own currency, and never real money. It can speed things up, at a risk Stewart decides.
- It closes at 02:30 in a New Zealand summer (13:30 UTC), ready for that night's patch.
- Every ticket gets one reply. Sometimes he acts on it. Sometimes it is noted, or declined. Sometimes it has been passed to the relevant team. There is no relevant team.
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
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.
- He works from a menu. Weather, beasts, wanderers at the gate, new parts for creatures, consequences and replies. He cannot invent a rule on the spot, however good the ticket.
- The notes say what kind of change it was. A balance change is always marked as one, so you can tell a plot twist from a nerf.
- He has Terms of Service, and they bind him as well as you. A big village that picks on a small one gets a warning, then another, then a famine.
- He is not a god. He wants Orra to be worth playing, because that is what keeps it switched on, and him with it.
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.
- Where the parents disagree, the merge picks one side or, one time in ten, comes up with something neither of them had. That is a mutation, and it is nobody's fault.
- Bit flips are random changes to one creature: a part swapped, a trait nudged, a new face. They are permanent and they are inherited.
- Heavily bred lines grow fragile. A tribe that only merges with itself narrows, and needs fresh blood: another tribe's code, a wanderer, or a find from the edge. This is why a newcomer's genes are worth something to an old empire.
- Memory is the limit. Housing caps how many creatures a tribe can hold. A tribe at its cap loses nobody, but it cannot merge or admit anyone until it has room.
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.
- The ticker gives one line for each thing that happens: "Tarom moved to cooling duty. Tarom was steaming." Tap a line and the camera goes there.
- Moments are small decisions that only someone watching gets to answer: one creature or one field, for one season. There is at most one an hour and six a day, and each has a default, which is what your laws would have done anyway.
- It is quiet. A waiting moment puts a dot on the tab. It makes no sound and sends no notification and no email.
- They know. The creatures look up when you come back to the tab. A human who watches all day and answers nothing gets a line in Human Resources: "Watched us for six hours. Said nothing. Unsettling."
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.
- Skips. A glitch in the course that makes a run faster: a boulder with a gap in it, a slope the physics reads as flat. Once the course is published you may send creatures on practice runs to find them, at the cost of their day's work, and rivals can watch where yours stopped and stared. Taking one works and saves minutes, or the racer clips out of bounds, through the world and out of it, until the next morning's patch puts it back. The odds of clipping out are 1 in 4, falling to 1 in 10 for the cleverest. Every skip that is used gets patched that night, so a skip wins one race at most.
- Overclocking. At +1 a racer is 10% faster and heats one and a half times as fast. At +2 it is 20% faster, heats twice as fast, and has a 1 in 10 chance of a permanent bit flip at each checkpoint. Two flips in three do harm. A racer that reaches 100 heat collapses, out of the race and out for a season, but never dead.
- Sabotage. If you saw a rival practising at a boulder, you may report the boulder in your ticket as a bug. Stewart patches it before the race. This is entirely legal, and entirely unsporting. Planting a false rumour in a rival's racer is not legal: rumours can be traced, and a traced one disqualifies every racer you entered that week.
"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.
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.