Companions

A handful of companions, no supplies, no second chance: claw a settlement out of hunger, thirst and cold until it can carry itself — then send the one or two you can spare into a vast map of finds, secrets and dangers, while the larder back home still has to keep filling without them.

Where the build stands: the survival half and the self-running settlement are playable today. The far map is generated and worth crossing to look at — biomes, rivers, caves, landmarks — but its payoff is not built yet: outposts, hidden finds, unique gear and regional danger are Milestone 6 and 10.4 in ROADMAP.md. Today an expedition costs you a pair of hands at home and brings back map knowledge, not loot.

Living document · mirrors the in-game F1 help and extends it with developer reference · describes build v0.12.0 · last revised 2026-08-07

This build is not downloadable — only the newest release is kept. Get the current version →

Two halves: the Player Guide is everything you need to play, and mirrors the in-game F1 help. The Developer Reference below it maps each mechanic to its files, seams, tunables and console commands.

What changed in v0.12.0 short form

Everything this build brought, one line each — so this page says what it is before it says how the game works. The long form, with every reason and number behind them, is CHANGELOG.md in the repository.

v0.12.0 this build 2026-08-07

Added

• Special loot glitters and glows (LootShine)
• Every word of the rule language is now a card you earn (ROADMAP 11.15)
• The settlement is a thing now, not "every building on the map" (ROADMAP 10.3a)
• March as a column, and make camp (ROADMAP 10.3d)
• The floorplan stamp (ROADMAP 19.5)
• The heights are cold, the north is colder, and fur is the way in (ROADMAP 14.3)
• The handcart (ROADMAP 10.3c)
• Taking a settlement down is work now, and you drag a rectangle to do it (ROADMAP 10.3b)
• Climb, and the land opens up — the view from high ground (ROADMAP 10.4a)
• A newcomer tells you where they came from (ROADMAP 10.4b)
• A second crater lake per map

Changes

• The campfire stops being free

Changed

• Lighting a fire is an order of its own (user decision — "eine Menüoption zum Anzünden wäre gut")
• A fire is worked from right beside it (user decision — "Companions müssen sich direkt neben dem Lagerfeuer befinden")
• The fire exchange window dominates the screen (user decision — "das Lagerfeuer-Panel soll dominanter, größer sein")
• The wall costs wood, the floor costs planks, and neither will take the other (user decision)

Fixed

• The fisher's yard jammed at a single fish, and then ate it

v0.12.1 fix release on this line 2026-08-08

Fixed

• A found card is a card again
• A find is headed by its name, not by its mechanic

v0.12.2 fix release on this line 2026-08-08

Changed

• A patch release no longer touches the wiki or ships a build

Overview

What the game is, and the shape of a run.

You control a party of three companions from an RTS-style top-down view: box-select, right-click to command. There is no player avatar — the three are equals, and the party grows to at most ten by taking in wanderers you meet (see Your party). Every one has the full set of survival stats and can die individually; losing one is meant to feel tragic. On the hardest difficulty that loss is permanent (see Difficulty & saving). The only threats are nature — food, water, temperature, weather, seasons and distance — plus reactive wildlife that may defend itself. Nothing ever attacks your base.

A run is a cycle of three phases

1. The manual opening — everything by hand, no automation. Scout for a viable site, live hand-to-mouth off what you find.
2. The automated base — buildings unlock jobs, each companion's rule program runs the day, the settlement hums.
3. Exhaustion → migration — the land wears out, the party packs what it can carry, treks, and starts over stronger: skills, equipment and recruits persist, the place does not. Each year winters bite harder.

The 512×512 map is budgeted for roughly 3–5 settlement cycles — that is the designed run length. Phases 1 and 2 are playable today; phase 3 is not built yet — nothing yet forces you off a working settlement, so a run ends when you stop, not when the land does.

Build your party before the world exists

Play does not drop you on the island. It opens the three companions you are about to take there — and you can press Start the run the second it appears.

The party you get without touching anything is already complete: three named, differently coloured people with rolled bodies and rolled dice. Everything below is optional.

• Eleven hair silhouettes, six complexions, three marks. The marks — freckles, a scar across the brow, spectacles — stack, so their arrows walk the eight combinations (nothing, each alone, each pair, all three). All of it is cosmetic: no look on this screen changes anything a companion can do, and none of it says what they have survived.
• Six faces, and nobody smiles. The trait you pick is the face they wear when nothing is wrong — see Reading a companion for what happens on top of it when something is.
• Skills are not on offer. Everyone starts unskilled and learns by doing, exactly like a recruit who walks in later.
• Retry after a wipe comes through this same screen. When the party dies, you do not get three strangers the dice rolled — you build their successors, and the new run claims its own save slot instead of writing into the dead one's.

Move & look WASD · F · Tab

• WASD pans the camera (free look). The view stays where you put it — selecting or commanding never yanks the camera.
• F centres the camera on the selected character and follows it (a group is framed at its centre). Tab does the same while switching companions.
• Right-click commands every selected character (see Command); a green ping marks the ordered spot, and a green circle snaps briefly tight around the object you gave the order on. Hold right-click to steer continuously — the selection follows the cursor until you release.
• Dense forest and loose sand slow walking to 80%.
• Mouse wheel or +/- zoom; M snaps to the widest zoom. Mouse at a window edge scrolls the view (tune speed/width in Esc → Settings → Gameplay). Over a panel the wheel scrolls that panel — it never zooms the map underneath it.
• There is no minimap and no overview map — you never see the whole island at once. Reading and remembering the land is part of the game.
• The time-warp bar sits top right (pause, 1–10×). Switch on Esc → Settings → Graphics → Show FPS and the frame rate appears directly under it — green above 50, amber above 30, red below. It updates four times a second on real time, so time warp and pause do not change how it reads.

Your party 3 → 10 companions

• Characters are moved by right-click only. There is no keyboard steering — WASD always pans the camera, never a companion.
• Left-click a character to select it (green / blue / orange; a white ring marks it). Exactly one selected = it is "yours": E-gather and build use it, and it walks your right-clicks at full speed.
• Drag a box to select several and command them together.
• Left-click empty ground deselects — observer mode; everyone just runs its jobs.
• The bottom-left info panel follows the mouse: hover any tile for terrain + what stands on it (tree species & wood left, water salinity, buildings, stockpile usage, plant stock); hover a character for its current activity. Fog applies.
• Tab switches control to the next companion; 1–9, 0 select directly (tap twice to also centre the camera). Hotkeys are fixed for the run — a dead companion's number stays vacant.
• Companions learn by doing. Walking trains Running (speed), each trade trains its own skill, heavy trades & building train Strength (carry + build speed), and enduring cold/rain/exhaustion hardens Resilience (falls ill later). A run's veterans are made, and they are what you carry to the next settlement.
• Strangers come knocking. Every so often a wanderer walks in out of the wild and waits a few days at the settlement — the event log names the direction they came from, which is your only warning to go and look. Left-click them for their panel: name, body, base attributes — and nothing else, because a recruit arrives unskilled. Take them in or send them on; wait too long and they leave. The party is hard-capped at ten, and a new pair of hands eats before it earns.
• A newcomer brings a map, not just hands. Join one and they tell you where they came from — one line in the chronicle naming a direction, never a distance — and a patch of far-off ground stops being blank. It is marked explored, not visible: you get the lie of the land out there, not what is standing on it right now. That is a second reason to take somebody in even when the larder is tight — the next settlement has to be found before it can be built.
• Not everyone means it. Some wanderers are false companions: they work slowly, help themselves to the stores, and one night they are gone with whatever they could lift. Nothing on the panel gives it away — the event log does, over days (someone at the stores after dark; a day's work that came up short). A companion with Perception 8 or better names the culprit outright; below that the log only reports the deed. Expel anyone who joined from their character sheet (C) — and be wrong at your own cost.

Reading a companion at a glance

The figure on the map is not decoration. Three things can be read off it without opening a single panel — who it is, what it is carrying, and how badly it is doing.

• Who. The identity colour is worn loud on the scarf and the sleeve band (the coat only tints with it) and is the same colour as the selection ring and every swatch that names them in the interface. Beyond it, no two companions look alike: hair silhouette, hair colour, complexion and any marks are fixed by who they are — chosen in the creator, or dealt by the dice for everyone who walked in later. Grey hair means age, nothing more.
• What they carry. Carrying is equipping in this game, so the figure wears its own pack: an axe over the shoulder, a bow and quiver on the flank, a bedroll lashed above the shoulders, a rope at the belt, a straw hat, a lit torch — and the waterskin everybody has. Whoever is holding the only axe can be spotted across the camp.
• How they are doing. Every companion has a permanent expression, and trouble paints over it. The face on the map and the portrait in the party row are the same drawing, so the two can never tell you different things.

The thresholds are the same ones the HUD bars colour by, so a face can never disagree with the bar above it — see Buffs & debuffs for the numbers.

Command — right-click RMB

Right-click sends every selected character; what happens depends on what you click. Your word is absolute — a character never breaks off an order, even to save itself. It posts a red warning when critical and carries on; abort the order yourself if you want it to live.

Every click flashes a green ping at the ordered spot, and when the order was given on something — a tree, a bush, a stack lying on the ground, an animal, a fire, a stockpile, another companion, a cave mouth — a green circle snaps tight around that object for a moment. Feedback for the eye: on a crowded tile you can see what the party understood you to click, not merely where the cursor was. A plain walk onto open ground has nothing to ring and gets only the ping.

You can only order what you can see. On ground the party has never explored, a right-click means walk there and nothing else — no drink ring over a lake under the black, no harvest on a tree nobody has found, no left-click panel on a store or a fire out there, and no blueprint staked on unseen ground: choosing where to settle is meant to be scouting. Ground you have explored answers everything even when nobody is looking at it — the map does not forget where the water is. Wildlife is stricter still: an animal can only be clicked while its cell is in live sight, because a remembered deer is a deer that has long since wandered off. Walking into the dark is never gated; that is how you scout.

Shift+right-click queues the order as a waypoint. A plain right-click replaces the whole queue. Nobody looks after themselves at all — drinking, eating, warming and sleeping happen only on your order or through the rule program (T).

A bed someone else has claimed refuses the order: it is dropped with a warning rather than silently ignored, so a sleep command that "did nothing" is worth a look in the event log.

What a left-click opens

Right-click orders; left-click a building to look at it. The panel opens without touching your selection, so you can read a fire while a companion keeps working. This is also the only place the ranges below become visible.

• A campfire — which of the three states it is in (Burning / Embers / Cold) and how long that lasts, how much one log adds, what a light would cost on a cold pit — with a Light it button right there, above the night watch — and its three slots (see the fire window). It draws two circles on the map: an amber action ring and, well inside it, a smaller red warmth circle. Warmth is the small one — standing in the amber ring does not thaw anybody, and in bad weather that circle pulls in further still (the panel draws the pinched circle, not the fair-weather one).
• The night watch — the fire's panel also does a sum you should not have to do at dusk. A campfire filled to the brim burns about 7 in-game hours; a night lasts 12. A straw bed gives no warmth of its own and no roof, and a sleeping companion does nothing at all — so on a cold night a party that all lies down around the fire wakes up short a companion. The panel says plainly whether tonight needs somebody sitting up with it: red when it does, green when the fuel already covers the night, grey when the night is too mild to matter. It reads 03:00, the coldest hour, with today's weather applied — not the temperature you can feel right now. It counts the embers too, which buy a couple of hours after the flame is gone but do not warm a sleeper. Keep the night watch posts everyone selected there until first light: they hold position inside the warmth and feed the flame whenever it will take fuel. Set it at dusk, while there is still light to gather the wood by — the order holds through the evening and ends at the morning after the night, not at the next glimpse of day. It costs a night's sleep, so the watcher is tired the next day — rotate the duty. If the fuel runs out mid-watch it says so and ends, rather than standing there pretending.
• A well — what it serves and its action ring.
• A stockpile — what lies on it, how full its tiles are, and its acceptance rules.
• A construction site — materials delivered so far, progress, and the Cancel button; cancelling drops everything already delivered on the spot as loose stacks, so nothing is lost.
• A room (left-click inside it) — its comfort and its furniture, see Furnish a room.

Merely hovering a building draws its action ring too, without opening anything.

Gather — hold E E

Hold E next to a target; a ring fills over its harvest time. Gathered items go into that character's carry, limited by weight (~40 kg, raised by Strength).

• Trees → wood: each forest tile is one tree; the whole wood stock drops when it falls (the tile turns to grass). Strikes are banked — stop and finish later. Four species by shade: birch (10 wood), pine (20), spruce (25), oak (35).
• Rocks → stone and fishing take ~10× ordinary work — plan whole days; a mason's yard / fisher's hut put workers on them around the clock.
• Herbs, berries, roots regrow in place, but never in winter, and slowly enough to plan a walking circle around: herbs ~3 days, a berry bush ~2 days for the 5 berries it holds, hemp ~5 days. Foraging fatigue (below) stretches all three by up to 4×. Bird nests (spring only, gone for good when robbed), mushrooms (summer+autumn, forest edge), hazel nuts (all year, never rot, but a cleared bush is finished and the next grows out of sight), mussel beds (salt coast, year-round, spoil fast).
• The land wears out where you pick it. Berry bushes, herb patches, root beds, hemp stands and mussel beds remember being stripped: each unit taken leaves foraging fatigue on that patch, and a worked-over patch regrows up to 4× slower. Hover it to read the state — "picked over (40%, regrows in 3.2 days)". No dice: the wear fades on its own over about a week, in every season, so it is a tally of recent pressure, not a scar. Forage in a circle, not in one spot — and the longer a base stands, the further you walk for a full pack.
• Free ground pickups (a half-second stoop, gone once taken): twigs & leaf piles at the forest edge, loose stones on the plains. One node is one item — a campfire is three twig nodes, and they are everywhere.
• Wild hemp → plant fibre — grows only on damp ground beside fresh water (river banks and lake shores; never the salt coast, never inland). Tall fanned stalks, regrows in ~5 days outside winter. Fibre is not string: spin it into cordage on the Crafting tab, and cordage is what a bowstring and a fishing line are made of. No hemp in reach → no bow and no rod, so it is one more thing that makes a settling site good or bad.
• Hunting takes a bow (craft one once a Hunting lodge stands). Deer & pigs flee faster than you walk — you shoot them: embody a hunter, hold H, a swaying reticle rises, lead the moving animal, release to loose. A hit is aim, not luck. A shot spooks the prey — one clean opening shot, then it bolts. The Hunter rule shoots the same way on its own, and with nothing in sight it takes a stand instead of falling through to the next rule: it walks to the nearest known forest cell (failing that, anywhere outdoors — never under a roof) and waits there, reading "No huntable animals in sight - waiting". Hunting is mostly waiting.
• Fishing takes a rod (a pole plus a line of cordage; craft one once a Fisher's hut stands). The hut grants the fishing right to its water, the rod is the tackle: no rod in the pack → the companion will not fish, the Fisher rule stays blocked, and the hut's task postings are left for whoever is equipped. Rods are per companion — three fishers need three rods.

Eight creatures roam: deer & pigs are the herds you live off; pigeons & crows fly where you cannot follow; beavers keep to fresh water; badgers are slow enough to corner; wolves and bears hold their ground (a bear is the biggest meat on the map). Wolves belong to the tundra — the cold north is where they start, which is exactly where you go looking for hide. Nothing out there hunts you — yet.

Some things on the ground glitter. A find wears a breathing halo and a few sparks that flare and die around it, and from the second tier up the stack casts real light — which only shows once it is dark. It glitters in every place an item is drawn: on the ground, in a pack slot, in a panel row, on a stockpile tile. What glitters is the discovery, not the goods: the wood cached beside an old camp's cold hearth shines because finding it mattered, and it is ordinary wood the moment you carry it home. Half a screen away on dark ground, that is the difference between a landmark and nothing at all.

Game leaves a settlement. Every wandering step a herd takes leads to the quieter of the ground it can see, so deer and pigs drift off your built-up walking circle over the seasons. It is a drift, not a flight (they bolt only from a companion at close range), and it is not the same for everyone — pigeons and crows do not mind a settlement at all. Hunting turns into an expedition: one more reason for the waterskin, the bedroll and, in time, an outpost.

Stay alive

Health, Thirst, Hunger, Tiredness and Temperature drain over time; Mood is a secondary, non-lethal stat. Every companion is a compact row top-left; hovering a row unfolds it to full bars — and that is the only thing that opens a card, so the corner never rearranges itself when control moves. Buff/debuff badges beside the card say what is on a companion — green = boon, red/magenta/violet = malus. When any Health falls into the red, the whole screen sounds the alarm (red rim, heartbeat) so an off-screen death can't be missed.

A body mends itself only while nothing at all is wrong with it. Health then climbs on its own — awake as well as asleep, bed or no bed — as long as every bar sits over half, the body is comfortably warm and no sickness is on it. That trickle runs at 30% of a good bed's healing rate, and it never adds to a bed's: a sleeper mends at the bed's pace, not at both. Sleeping in a proper bed is still how somebody actually gets well; the waking trickle is what stops small damage from being permanent before there is a house to sleep in. Hover a hurt companion's Health bar and it says which of the two it is doing — the promised climb, or the one thing blocking it ("Thirst below 50%", "too cold", "sick") — and a green heart with a rising arrow joins the badges while it mends.

What hurts you doesn't let you heal: an empty Thirst/Hunger bar, or a freezing/ overheating body, suspends even a bed's healing — the sleeper rests off tiredness but wakes no healthier. Winter is the exam: farms lie dormant, plants stop regrowing, no animals are born. Stockpile in autumn; nuts, fishing and mussel beds work year-round.

Read the temperature bar before it bites. It shades its comfort zones — blue too cold, white all right, orange too hot — and carries two marks: the thick one is the body temperature that actually damages Health, the thin pale one is what the body currently feels and is drifting toward. When the thin mark runs into the blue well ahead of the thick one, you still have time to do something about it.

Buffs & debuffs — the exact numbers

Every condition a companion can carry, what it really costs, and how to end it.

Conditions show as badges beside the HUD card and under the portrait in the character sheet (C). The colour tells you the kind before you read anything: green = a boon, and magenta / blue / violet / red = something is wrong. Every slowdown below multiplies with the others: soaked, exhausted and ill at once is a companion barely moving.

Work & trades — how each one resolves

Gathering, felling, mining, fishing and hunting are not one mechanic — they cost different time and need different things.

Every trade trains its own skill by doing it, and the skill multiplies the pace back. Heavy trades and building train Strength (a bigger carry and faster building), walking trains Running, and enduring cold, rain or exhaustion hardens Resilience (falls ill later).

Tools & clothing carried, not worn

Gear is the thing that survives a migration. Three pieces exist so far — an axe, a coat and a hat — and all three are made at the crafting bench (K).

Clothing insulates — it does not heat

Worn warmth is added to the temperature you feel, but only up to 20 °C: it can lift a freezing companion toward comfort and can never push a warm one past it. So a coat is never a liability you cannot shed — it does nothing at all in a summer desert, and a roaring fire still beats it. Wearing a cloth coat and a hat is +8 °C, which is roughly the difference between a clear autumn night and a survivable one; fur and a hat is +16 °C, which is the difference between the tundra and the tundra with a plan. Carrying a spare coat does not double the warmth; only the warmest piece per body slot counts.

An axe wears out, and is mended where it was made

Chopping wears the axe down — deterministically, never on a dice roll: it lasts 400 seconds of real chopping, which is about nine in-game hours of it, a full working day at the trees. The sheet's carry slot shows the condition as a percentage that runs green → red, and the break itself posts one line to the event log. A broken axe simply stops helping — you chop by hand at the ordinary speed until it is mended; nothing is lost and nothing is destroyed.

To repair it: right-click the lumber camp with the worn axe in the pack. The companion walks over, pays 1 wood — out of its own pack, or fetched from the stores like a builder's materials — and the axe is full again. Repairing is deliberately far cheaper than crafting a replacement: that is the reward for keeping the workshop standing.

Wear follows the companion, not the axe. Hand a worn axe to a mate and it is fresh in their hands; take it back and your own wear resumes. So a shared axe is not a shared supply line — don't plan one around it.

The bow and the fishing rod are still pure gates rather than gear: carrying one is what lets you shoot or fish at all, but neither speeds anything up or wears out yet.

Moving goods — the one hand

There is exactly one hand in the game, and every window fills it the same way.

Pick a stack up in the character sheet's carry grid, in the transfer window, or straight off a stockpile tile on the map (Shift+right-click it) — it is always the same hand, so a stack can only ever be in one place. Closing a window keeps the stack in hand, which is exactly how it gets out onto the map: carry it to a construction site, a fire's hearth, a pile or a companion and left-click it down. Esc on a clear screen puts it back where it came from.

Putting something down happens at arm's length — walk the companion over first. A fire is the one exception: with fuel, raw food or untreated water in hand, left-click a fire anywhere on the map and the companion carries it over — on arrival the fire exchange window opens with your stack still in hand, so one click on a slot puts it in. Only the walk is done for you. A hearth that would refuse it (a pan already busy with another kind) says so at the click, rather than after the walk; and the window opens wherever you happen to be looking, even if you deselected that companion while it walked.

Tell each stockpile what it accepts

Every pile has its own acceptance rules, set from its panel: the presets Everything, Food only, Materials and Nothing, or a tick per item kind. This is how you sort a settlement — food at the fire, wood at the building site, ore at the mason's yard.

• A hauler only walks to a pile that accepts what it is carrying. If no pile in range does, the load has nowhere to go and you get a red alert.
• Rules never touch what already lies there, and never block taking things out. Setting a pile to Nothing is therefore how you drain one: it keeps serving, stops receiving.

A pile set too narrowly is one of the quieter ways to stall the whole automation, and the panel is the only place it shows.

Every workshop keeps its own yard

A job building — fisher's hut, lumber camp, farm, mason's yard, hunting lodge — holds a store of its own beside it: 20 units of that trade's produce and nothing else (fish at the hut, logs and boards at the camp, stone and cut stone at the yard, vegetables at the farm, meat at the lodge). Left-click the building to read it.

• Produce lands there only while the worker is standing at the building. Work a tree forty tiles into the woods and it fills the pack exactly as it always did — nothing teleports home, which is a quiet argument for siting the camp where the work is.
• The goods count towards the settlement's stores: edible, spendable, haulable, and standing at the workshop counts as standing at the stores.
• But haulers never dump anything there — it is an out-tray, not a shelf, and it accepts nothing but its own trade's produce.
• One tile, one kind: twenty logs leave no room for boards until somebody clears them. With no free tile left, an incoming load does not vanish and does not block the trade — it folds onto the newest batch of its own kind and takes the older of the two dates. A fold can age a stack, never freshen it, so nothing is ever made to keep longer by being stacked on. It is why a one-tile yard no longer jams at a single fish, and why that fish is not quietly given a new best-before.
• When the yard fills — or the worker's own pack does — the shift ends and the event log says which of the two ran out, because clearing a yard and bringing a load in are different jobs. That is the normal end of a shift, not a fault. A farm ordered out of season says so too, rather than standing there mute.

Getting the produce out — on the map. A yard stands where the work is, which is usually nowhere near you, so it answers the same two gestures a stockpile has always answered: Shift+right-click the building takes the stack lying in its yard straight into the hand, and right-click it with one companion selected offers Take produce on the context ring — that walks the companion over and opens the exchange window on the yard. The ring only appears when something is actually lying there, and a plain right-click still means work the trade.

Or from the building's own panel. Left-click the workshop and press Open the yard: the store opens beside the pack of the companion standing at it, in the same two-column window a stockpile uses — click a row to move the whole stack, Shift+click for a single unit. Where a pile shows its editable storage rules, a yard shows the trade's fixed fence instead: it is not yours to loosen. Putting goods back in is allowed as long as they are that trade's produce — the yard does not judge whether shelving them there is clever, and they age and spoil in it like anywhere else, so a yard used as a larder is a yard that will block the work.

Or let the settlement clear it. With a Planning table standing, a workshop whose yard is over three quarters full posts Clear the yard on the task board, and any companion running the 1-block Take a task rule carries the produce to a stockpile, load by load, until the yard is empty — then the posting is withdrawn and the trade itself is claimable again, so the work goes on without you. While a yard is full, nobody takes that trade on at all: there would be nowhere to put what they made. This is the usual bargain — by hand it always works, unattended it has to be earned.

“Full” is the worse of two things: how much the yard holds, and how much room is left in it. A yard with one crowded tile and nothing else free is full even though it holds almost nothing — which is the honest answer, because that is exactly when the work stops. The yard fill sensor in a rule reads the same number, so it hits 100 % precisely when production would block.

A fire is three states, not a fuel bar

A heat source is Burning, on Embers, or Cold, and the difference decides whether it can save somebody. Fuel is not the flame: wood thrown onto a cold pit just lies there.

The fire exchange window

Right-click a fire with one companion selected and pick Light fire, Tend fire or Boil water: the companion walks over and a window opens — its pack and waterskin on the left, the hearth's Fuel, Pan and Ready slots on the right. A banner across the top says Burning, Embers or Cold in that state's colour, with the time left and, on a cold pit, what a light would cost; a Light it button sits there too, and on a soaked pit it refuses in place and tells you why. Nothing is loaded for you: the verb you picked only names the slot to aim at (fuel to the flame, the waterskin onto the pan), and you drop it in yourself — one click, and you decide how much. Carrying nothing that fits, the companion still walks over and the window says so in red, because "I have nothing to burn" is exactly what you went there to find out.

Everything moves by the same gestures as the transfer window, and the slots are half again the size of a pack slot — this window is worked at a distance, not squinted at. A fire is worked from right beside it: an order sends the companion all the way onto the pit's own cell, not merely into its warmth. Boiled water taken off the Ready slot goes into the waterskin, never into the pack.

Build — press Space Space

You start with nothing. Space opens the build ring (radial menu): an inner ring of categories — Workshops, Structure, Supply, Demolish — where left-clicking a category opens it in a second, outer ring. Hovering any entry spells it out in the info panel below the circle, cost per material included (green = affordable now, red = not). Place it, and every selected character goes to build it (nearest one if none selected). R rotates the ghost before placing.

The centre always goes back one ring, and closes the menu on the top level — the same thing right-click and Esc do, so there is one rule for the way out. Space closes it from any depth. Only two rings are ever drawn: opening a category replaces the outer ring rather than adding a third, so nesting is free and the circle never grows. Greyed entries come in two kinds that must not be confused — a padlock is a player goal (the workshop that unlocks it does not stand yet), a dashed outline is a planned placeholder that does not exist in the game yet.

The cell raster appears when you need it. At rest the grid over the world is barely there — the island is meant to look like land, not graph paper, and there is no minimap to consult either. The moment you place anything — a building, a wall run, a room, a floor, furniture, a road, or the demolish tool — it snaps to full strength, because that is the moment knowing where one cell ends is information rather than clutter.

There is no ready-made house. Every house is designed out of walls, doors and floors, and is whatever shape you enclose. Job buildings stay simply placed and the farm stays drag-to-size — a workshop is equipment, not architecture; only the home is the player's design.

Every building is drawn as the thing it is, so a settlement can be read from across the map without hovering anything: the lumber camp is a lean-to over stacked logs with a sawbuck beside it, the fisher's hut hangs its catch on a drying rack, the mason's yard is an open working yard of dressed stone, the hunting lodge pegs a hide out on its frame, the smokehouse vents its two plumes, and the planning table carries the settlement plan. The storage box and the water barrel used to be told apart by tint alone; they no longer are.

The workshop craft queue

A workshop used to be a token: it unlocked a trade and posted a task, and nobody ever stood at it. Since 19.1 the lumber camp, mason's yard and smokehouse carry a craft queue — left-click one and tell it what to make.

The crafter fetches the inputs itself (its own pack first, else a trip to the stores — exactly what a builder does for its materials), works at the bench, and pockets the output. Progress belongs to the order, not to the worker: two companions at one bench stack their effort, and someone called away mid-craft loses the seconds banked and never the materials. The craft spot (the 1×1 site you pin anywhere from the Crafting tab, K) is untouched — it is still how the axe, bow, rod, bedroll, cordage, coat and hat are made.

Two prices for one building. A buildable may list alternative costs — the campfire's 3 twigs or 3 wood. Twigs lie on the ground everywhere, so the first fire of a run never has to wait for a felled tree; one twig node is one twig, so that is three stoops at the forest edge. The build ring lists both, each material coloured by what the settlement holds, with an or between them; a blueprint commits to one of them (whichever it can cover, primary first) and shows only that on the site. As long as nothing has been delivered yet it re-picks by itself, so a site that asked for wood asks for twigs the moment twigs are within reach; once the first material lands, the bill is settled in it. Demolishing refunds half of what the building was really paid for — a fire raised from kindling salvages kindling — and the salvage goes into the dismantler's own pack first, a stockpile in reach second, and only then the ground.

And two fuels for one fire. The same reasoning carries past the build: a fire that can be raised from twigs can be fed with them. But a twig is kindling, not fuel: roughly 10 twigs to the log, and a twig node yields one twig, so a night fed on kindling alone is a great deal of stooping for very little heat. Kindling raises a fire; wood keeps it. Logs are always preferred where there are any — every fuel run shops the list in order, so the party falls back on kindling only when the woodpile is empty. Everything that feeds a fire goes through the one list: the right-click order, the REFUEL rule, a claimed task, holding E at it, the world hand and the panel's FUEL slot (which counts in logs but takes either).

Draw walls, close a room

There is no ready-made house, so this gesture is how you get shelter. Walls are straight runs, not freehand:

• Left-click plants an anchor.
• Move the mouse and a straight run follows it — it snaps to whichever direction you have pulled furthest, so you cannot draw a diagonal by accident.
• Left-click again fixes that run and starts the next one from its end: that is how you turn a corner. Fixed runs stay put, and a corner is exactly where a door goes.
• Right-click ends the chain. Esc discards only the run you are currently dragging, never what you already fixed.

Buildings go on grass or sand only. Water and mountain refuse; a forest tile has to be felled first, and the grass it leaves behind then takes a building.

Furnish a room — left-click inside it

A self-designed house is not an object you can click, so the furniture panel hangs on the room: left-click any cell of an enclosed room and it opens, reading the room out (cells, shelter warmth, how homely it is) and listing the furniture that may go in it. Pick a piece and the ghost only accepts cells inside those walls — otherwise it is an ordinary construction site: builders fetch the materials and raise it. Click inside the same room again, or press Esc, to close. It resolves last of all map clicks, so anything with a panel of its own (a pile, a fire, a construction site) keeps the click.

The two beds are told apart by their labour, not by their price. Their materials are nearly identical: a straw bed goes up the instant its materials arrive, a proper bed is close to an hour of a builder's work. Helpers shorten it; the entry's tooltip quotes the time.

A room is not yet a home. Its comfort is the average over its cells of the floor laid on them and the furniture standing in them, and that comfort lifts Mood while a companion is inside — doubled while asleep. Over-furnishing simply finishes the room; it is capped, never an exploit.

Taking it down is work — and it is how you leave

Demolishing is not a click any more. Pick Demolish and drag a rectangle: every building inside it is marked with a red cross, not removed. A companion then has to walk over and take each piece apart, and half the materials go straight into that companion's pack — what the pack cannot hold goes to a stockpile in reach, and only what neither can take is left on the grass. Right-click a marked building to send your selection at it, and one order chains on to the next mark within 24 tiles, so marking a whole settlement and clicking once dismantles all of it. Drag over an already-marked run to take the mark off again. Marks are also posted to the task board, so an automated party packs up on its own. Construction sites are still cancelled outright — nothing has been raised yet.

This is the gesture the migration is built on: mark the camp the evening before, and leave in the morning carrying it.

Remember a floorplan, stamp it down again

In the build ring, Remember records a room you already built — hover it, click, and its walls, doors, floor and furniture are kept together as one plan. Stamp lays that plan down at a new site. It stakes out construction sites, not buildings: the materials and the labour are still owed, exactly as if you had drawn it by hand. Pieces that do not fit are skipped, so a plan laid over a boulder gives you the house minus a wall rather than nothing at all. The plan rides along in the save.

Record your house before you leave, and the next settlement goes up without you redrawing it — which is the whole point of a cycle that starts over stronger.

Automate — press T T

Automation is built, not switched on. Write each companion a program — an ordered list of rules reading WHEN condition(s) → DO action UNTIL release. Order is priority.

• WHEN — sensors: the body's bars (Health & Mood too), Wetness, Sickness, the clock, the season, precipitation, city stores, the own carry, the waterskin, fire fuel, a waiting site, a workshop's yard fill — and, if you find its card, the daylight left today. Conditions AND together (with The Or found, a joiner between two of them flips to OR).
• DO — actions: the trades (fell, fish, farm, quarry, hunt), drink, eat, sleep, warm/cool, tend fires, build, draw water, boil water (carry the skin's pond water to a fire and boil it clean), haul the carry to stores, fetch items into the carry, and take a task off the task board.
• UNTIL — the latch: "fell wood UNTIL stores ≥ 60" keeps a rule going past its trigger so companions don't ping-pong at the threshold.
• Nothing happens that nobody asked for: no companion carries its load home on its own. A full pack stops the work that would fill it further (harvesting into a full pack destroys the node for nothing) and the rest of the program runs on. Bring it in by right-clicking a stockpile, with a WHEN Carry full → Haul rule, or via the task board — a task's goal sits in the city stores, so delivering is the last leg of it. Any haul keeps a ration of every food kind and of drinking water: the load goes, the lunch stays.
• Blocks are budgeted: a rule costs 1 block, +1 per extra WHEN, +1 for an UNTIL; the whole settlement shares one budget (base 12, +6 from a Planning table). Rules past the budget don't run — top rules are paid first.

Every word is a card you earn

You cannot write a rule out of words the party does not own. Each sensor, each action, each trade and each piece of grammar is an automation card, and a card is earned by doing that thing by hand — three loads carried to a stockpile buy Take a task, six full drinks buy Drink and the Thirst sensor together, ten felled trees buy the Lumberjack. The sensors nobody can work for are learned by living through them: a companion falling ill teaches Sickness, a turning season teaches Season.

The vocabulary bar sits under the rules list: every word you own, in the colour it wears in the sentence, with its block cost as pips. Click a card to lay it into the rule that stands open (with no rule open it starts one). show locked folds out the whole set — each locked card carries its own counter (7 / 10) and one line saying what to go and do. The cards belong to the party, not to a place: they come with you when the settlement is abandoned.

A trade card lets you write the rule; the workshop lets it run. Earn the Fisher and you may plan for a hut you are about to build — until it stands the rule simply reads blocked. Lose the last workshop of a kind and its rules block again, but you never un-learn the word.

The task board (needs a Planning table): buildings watch their own needs and post tasks — a fisher's hut calls for a fisher while stores hold under 20 fish, a burnt-down fire calls for tending, a fire calls for boiling while the stores hold under 10 litres of clean water (a taker draws pond water, boils it and barrels it), a workshop whose yard has filled calls for it to be cleared onto a stockpile, open sites post themselves. One 1-block Take a task rule claims the nearest posting, so a new recruit is just one more taker — and taking one does earn cards, unlike a rule of your own. Trades still need their workshop to run: the card lets you write the trade down, the building is what makes it happen. Workers only seek what the party has already discovered. Each building's panel lists what it is posting and carries a Post tasks switch, so a single building can be told to stop asking without touching anybody's program.

Read the program while it runs

The editor is also the debugger: every line shows what it is doing right now, and time keeps passing while you read it.

A small program that keeps somebody alive through a winter looks like this:

Time & world

Read the land — wind, water, coast and soil

Every island has a wind, and it decides where the green is. The weather comes in off the sea from one direction, drops its rain as it climbs the high ground, and arrives on the far side wrung out. So the windward side is wooded and well watered and the far side of the high ground is dry — that is where the sand and the desert are. The direction is rolled fresh for every island, so it has to be read each run: walk up onto high ground and see which side the forest is on. There is no minimap, on purpose — this is what replaces it.

And high ground genuinely sees further. A companion's sight radius grows with the height of the ground under its feet — about double on the highest walkable ground, on a curve that gives most of the gain near the top, so a real climb is worth it and a low rise is not. The fog lifts in exactly the circle you can actually see, so climbing a ridge is the scouting move: walk up, look, walk on. Height costs you warmth while you are up there (see below) — a viewpoint is not a camp.

The island sheds its own water. Nothing is placed: rain runs off the high ground, threads gather into streams and streams into a few trunk rivers that widen as they go and empty into the sea, and water stands in the hollows as lakes, most with a brook draining out of them (one that would drain into the desert has none — see still water). A river is still deep and impassable — the only way across is a bridge — but where one is still a thread you can often walk around it, so following a river uphill makes the crossing cheaper.

The coast is not all the same. A beach (pale sand at the water) is open, buildable ground. A sea cliff (dark banded rock) is a wall: it cannot be climbed, built on, or come down to the water at, and about a seventh of the shoreline is cliff — so walking the coast is a real route choice. A marsh (dull grey-green, pooled with dark water) forms only where a big river empties into the sea: wadeable at little over half speed, never buildable, and rare enough — a handful of river mouths on the whole map — that the one you find is worth remembering.

Steep ground costs time everywhere. A hillside slows a companion to half pace at its worst, whether you are walking it yourself or a rule is walking it for you. A flat way round a hill often beats the short way over it.

The ground under a farm matters. Fertile bottom land is flat, wet, and has a lot of country draining through it — a floodplain. A farm there works at better than twice the pace of one on a dry slope. Hover any buildable tile and it says which you are standing on: bottom land, good soil, heavy going or barren. With water and wood, that makes three things to weigh when you pick where to settle.

Woods are thick or thin. Growth follows rain, height and steepness, so there is closed forest on the wet side, open groves inland, clearings, and a treeline above which nothing stands (and it sinks as you go north — cold means bare earlier). A tree in the wet lowland carries several times the wood of a stunted one at the treeline, and the crowns are drawn to match — so a wood worth walking to looks like one, and where a lumber camp stands is a real decision. Species follow the place too: oak in the warm wet lowlands, spruce in the cold heights, birch out at the thin edges, pine in between.

You are not the first party here. Out in the unexplored ground there are old camps — a cold ring of fire-blackened stones — and cairns stacked on the passes through the mountains. They are not scattered at random: a camp sits exactly where you would have settled, at fresh water with wood in reach, so finding one tells you the ground around it is good — and whoever left it usually left something behind on the ground to pick up: a cache that glitters, because a stack of wood on dark ground half a screen from the hearth is otherwise invisible. A cairn marks the one flat way through a range, which can save a long detour. Both are named the moment you see them and go into the chronicle (J).

Day/night and seasons pass; the clock, temperature (°C) and weather sit top-centre. Speed controls (or -/.) run pause / 1× / 2× / 5× / 10×.

Weather follows the seasons — sunshine, cloud, rain, hail, summer drought, winter snow. Hail hurts (bleeds Health in the open; only a roof or forest canopy stops it). Rain soaks (wet = up to 30% colder). Wet clothes dry fastest at a campfire or under a roof (~4 in-game hours from soaked through) — and out in the open as fast as the sky allows: ~10 h under warm sunshine, about a third of that pace when overcast, and nothing at all in cold air or while rain, snow or hail falls. A summer soaking dries itself while the work goes on; a winter one waits for a fire. In deep winter rivers and lakes freeze (wells keep serving); a summer drought dries small ponds until the next rain.

It does not rain on the desert. The sky is one sky for the whole island — the clouds and the falling rain you see are unchanged — but a rain, snow or hail spell reaches nobody standing in the sand. Out there nothing soaks you, hail cannot cut you, and no snow ever lies, in any winter. That cuts both ways: the desert is the one country where a hailstorm is not a reason to run for a roof, and the one where you can never count on the sky to refill anything.

Water has a quality as well as a salinity. Water that stands — a lake, a pond — is still water: drinkable, and every gulp builds the drinker's dysentery load — nothing on its own, but the pond you keep going back to breaks out as the illness. Running water is clean, and so are wells and hot springs. A lake stays still water even though a brook drains it: what matters is that the water sits, not where it eventually goes — so follow the outflow a little way downhill and you are drinking from a stream instead. Unless the outflow runs into sand: a lake whose drain would cross the desert keeps no brook at all — the water sinks instead of running — so there is nothing downhill to follow and boiling is the only answer. The green country just upstream of the desert is where most of those sit, and it looks like the best water on the map. A waterskin filled at a lake carries pond water with it until it is drunk dry. Choosing between a lakeside site and a river (or a well) is the point.

The cure is a fire. Right-click one and pick Boil water: with one companion selected it walks over and the fire exchange window opens on the hearth — pour the waterskin onto the Pan yourself, and take the clean water back from the Ready slot (it goes into the skin). With a group selected the unattended order runs instead: it pours, waits and collects by itself, and empty-handed simply collects what is already boiling. By hand it works too: right-click the tool slot in the character sheet (C) to pour the skin into your hand, then set it down on a fire (the whole skinful goes in), on a barrel, or on another companion to fill their skin.

Boiling costs time, and that is deliberate. A full waterskin — 5.0 litres, which is exactly what the pan holds — takes one in-game hour on a campfire; a stone hearth is three times faster at everything it cooks. The pan boils unattended while the fire burns, so you load it and walk away. A companion drinks 2–3 litres a day, so one fire keeps a small party in clean water and no more — and it cannot sear fish while it boils. Boiling is the stopgap at a pond; a river or a well is the answer.

The land itself has a climate. Most of the island is temperate, but three kinds of country are not: tundra (−10°C) on the high northern fringe, desert (+8°C) in the dry south, and swamp (soaks you like rain, and a fire can't dry you while you stand in it). The seasons turn both extremes inside out — knowing which half of the year a country is survivable in is worth more than avoiding it. Each is one connected region, but its edge wanders — lobed and ragged, never a ruled line — so where a country ends is something you find out by walking it.

And height is cold on its own. Ground loses warmth as it rises — up to 9 °C across the climb, so the highest walkable ground sits near −5.5 °C against the day's reading, on top of whatever the country and the season are already doing. It is not marked and it is not announced: a pass that was fine in summer is a different proposition in autumn, and a mountain camp is colder than the valley you can see from it. The north and the heights stack, which is why the tundra ridges are the hardest ground on the map — and why the fur coat exists.

There are two crater lakes on an island, and one set of hot springs. A run is meant to settle three to five times, and the most reliable water on the map being a single point made one of those settlements obviously right and the rest obviously second-best. Two of them means the good site you left behind is not the only good site there was. The standing stones are no longer only scenery: an automation card lies among them — the one that lets a rule ask how much daylight is left.

Caves bring a light

Mountains are not only a wall to walk around: search a mountainside for a cave mouth — a dark hole with a pale lip of broken stone and rubble spilled out below it. Right-click it, or walk onto it, and the party goes in; every rock cell touching the opening counts, corners included, so a near miss cannot set anyone mining the doorframe. Inside is a map of its own, and the way back is an arch of daylight in the wall. The world above keeps running the whole time — clock, weather, animals, everyone you left up there — so a scout can go down while the rest of the party works.

The mountain tells you how big the cave is — a lone rocky knuckle holds a fissure you cross in a few dozen steps, a proper range a warren, a gallery or a pillared hall. Size the massif up from outside before you spend a torch on it. Mushrooms and stone wait deep inside, always a good walk from the entrance, so a cave pays only the party that explores it properly. Nothing lives down there; the danger is the dark and the walk home.

Some caves hold water — a still pool of seeped snowmelt, drunk from or filled at like any river. Because rock has no weather it never freezes and never dries up, which can make a known cave the most reliable water on the map in exactly the seasons that close everything else. It is standing water, so boil it. Wet ground above means more of it: swamp mountains are wettest, desert caves bone dry.

Rule programs keep running underground. A companion you send into a cave still follows its plan, and when a rule wants something the cave has not got — a drink, a meal, the stockpile — it walks out through the mouth by itself, does the errand up top, and is free to be sent back down. You never have to fetch anyone out by hand.

And a cave counts as part of the settlement it opens into. Whatever you carry inside stays reachable from outside: a builder working at the mouth fetches timber from a stockpile you laid down in the cave, a tired companion claims a bed you unrolled in there, and a thirsty one walks in to a pool it has already seen rather than trekking to the river. The rule is simply that a cave is as far away as the walk into it — the mouth, plus however many steps deep the thing sits. So a pile just inside the entrance is practically next door, and one at the far end of a rambling warren is a real errand nobody will make automatically. Put your stores near the mouth if the camp outside is meant to use them. Only what the party has actually seen counts: an unexplored cave offers nothing, and neither does a pool in a corner you have never lit.

Sound Esc → Settings → Sound

Sound in this game is information, not decoration: where the camera is, what the weather is doing, whether the settlement is working, and how much fuel is left in the fire. It is built to be listened to rather than left on.

World sound is gated on the zoom. Pulled far out you hear the beds and the music and nothing else; zoom in and the work, the footsteps, the fires and the animals come up. So the detail you hear tracks what you are actually looking at, and ten companions never turn into a wall of noise.

Five sliders, one switch — Esc → Settings → Sound: Overall, Music, Ambience, World (work, footsteps, fires, animals) and Interface (clicks, windows, alarms and the mortal-danger heartbeat), plus a Silence switch that mutes everything and greys the sliders out. They are four genuinely different questions: before v0.10.0 one "SFX" slider carried the rain, the work loops, the heartbeat and every click at once, so turning the interface down turned the weather down with it. Turn Interface down, not World, if the clicking is what bothers you — and note that the heartbeat rides Interface, so muting that mutes your death-warning too.

Interface & keys

The companion window holds everything you do to one companion, as three tabs — each key opens its own tab (press again to close; Ctrl+Tab walks the tabs). All three are about the companion you're steering.

Only one window is ever open. Opening any of them — the companion window, a building, pile, site or room panel, the transfer window, the build ring, help, the chronicle — closes the one before it, so nothing overlaps. A stack in hand survives the switch: it is only ever put down where you put it down.

The event log — and the red alerts

Bottom right, a live feed of what the settlement is doing: arrivals and deaths, buildings raised, illnesses, level-ups, the traces a false companion leaves, season turns. Drag it by its top-left corner to move it.

A worker that cannot work says so, too. No tree in reach, no rock face, no farm, no water to draw, no bow or rod in the pack — the companion posts one red line naming the reason and stops, rather than standing there looking busy. It comes once per reason, so a new problem is never buried under a repeat. A farm in winter stays quiet on purpose: dormant fields are the rule working, not a failure.

How much it says is up to you: Esc → Settings → Gameplay offers Everything, Only what matters and Fewer. Verbosity only filters the live feed — the chronicle (J) always keeps the full history.

Difficulty & saving

Difficulty is chosen on the title screen, per run, and it decides what a mistake costs.

Each run gets its own named slot: the Esc menu names, overwrites and deletes them, the title screen loads any of them. The autosave interval is in Esc → Settings → Gameplay.

While the prototype is being tested, manual saving is left enabled on Brutal too.

Settings worth knowing about

Esc → Settings, four pages. The ones players actually miss:

• Gameplay — event-log verbosity, autosave interval, edge-scroll speed and border width (0 switches edge scrolling off).
• Graphics — resolution, window mode, anti-aliasing, quality, the FPS readout, and the scale of the whole interface.
• Sound — five volumes (Overall / Music / Ambience / World / Interface) and a Silence switch. Which one to reach for is in Sound.
• Keys — every binding above can be reassigned.

Architecture & conventions

Engine, layout, and the ground rules the codebase holds itself to.

• Engine: Godot 4.x, 2D top-down. GDScript only (no C#).
• Language: all identifiers, comments, node/scene names in English — no German anywhere in code or the scene tree.
• Naming: snake_case for vars/funcs/signals/files; PascalCase for classes/nodes/scenes; class_name for reusable scripts.
• Data-driven: tunables live in .tres Resources (resources_data/) and @export vars — not magic numbers. Numbers should be tunable without touching code.
• Decoupling: cross-cutting state lives in autoload singletons; systems talk through signals where it decouples them.
• A freed object compares == null as TRUE. So node != null short-circuits and never catches a freed one — is_instance_valid() is the only safe test. Any registry that outlives a scene teardown (cells → nodes, caches) must prune or skip stale entries with it.

Autoload map

The singletons every system reaches. Persistent autoloads must reset in WorldGenerator._ready (a reload doesn't re-instantiate them).

World generation & terrain

A cell has five orthogonal per-cell layers: terrain (what it physically is — world/terrain_types.gd: PLAINS/WATER/FOREST/MOUNTAIN/SAND/SHALLOW plus CLIFF and MARSH, the coast's own sorts), biome (its climate — world/biome_types.gd: temperate/tundra/swamp/desert, grown as one region each), landmark (world/landmark_types.gd: crater lake / hot springs / standing stones, and the traces somebody left — old camp / cairn), cave (world/cave_types.gd: where a cave opens — its mouth; the rooms behind it are their own map), and height (world/height_layer.gd: elevation, slope, rainfall and soil fertility — the physical field and what is derived from it per cell).

Caves

A cave is one cell on the world map — its mouth — and a map of its own behind it (world/cave_interior.gd, generated by cave_interior_generator.gd and owned by the CaveManager autoload). The mouth cell keeps its MOUNTAIN terrain, so the terrain renderer, the spawn rules and the walkable tally — and with them every spawn density — are exactly where they were.

How many: cave_count (18 since 2026-07-26, raised from 7) is a request, not a headcount — _carve_caves opens at most one mouth per mountain massif, so a world gets however many massifs clear cave_min_massif_cells (70) and cave_min_spacing (55): measured across five seeds on the 512² map, 13–17. Performance is not the limit and the number was set to saturate the land: an entered cave costs ~40 navmesh polygons (+0.5%) and ~1 MB. It used to cost ~4.5 ms on top of the wall-build freeze as well; since that freeze was traced to the navigation map's free-edge merge and switched off (2026-07-26), a wall costs ~21 ms with every cave in the world open — down from 1278 ms (tests/cave_scale_probe.gd, tests/nav_edge_probe.gd).

Each interior is laid out in a reserved band of world coordinates east of the island rather than in a separate scene. That is the whole trick: one World2D, one navigation map, one physics space, so nothing is unloaded and the surface simulation keeps running while the party is underground — and selection, right-click orders, the camera and every autoload work down there unchanged. TerrainManager stays the one map seam: is_walkable, is_underground, is_cave_dark, is_buildable and cave_sight_radius route off-grid cells to CaveManager, so no caller needs to know which side of the ground it is asking about. The band's one recurring trap (paid twice, 2026-07-26): GridManager covers only the 512² surface and answers “neither empty nor floor” for every band cell, so any predicate built on it silently rejects the whole underground. That is what made building impossible down there and destroyed a stack dropped in a cave (GroundItemManager._find_drop_cell found no cell and the caller threw the item away). Both now branch on is_underground and read the building/site dictionaries, which are keyed by world cell and have no bounds at all. Buildable.stands_underground() is the separate question of what may stand there: interior_placeable or stockpile. An interior is generated deterministically from the world seed and the mouth cell, so an unvisited cave costs nothing and still comes back identical.

The layout (re-carved 2026-07-26). The interior is scaled against the mountain massif behind the mouth — CaveManager._massif_cells flood-fills it lazily on first entry — on the square root of its cell count: 70 cells of rock give ~80 floor cells and ~29 steps of depth, 290 give ~275 and ~51 (tests/cave_layout_probe.gd, 200 seeds each). The same weight picks the cave’s form (fissure / warren / gallery / great hall), which drives its proportions, chamber count, corridor width and name; both axes are still drawn independently, so the ratio remains deliberately unrelated to the world’s. Chambers are wobbling ellipses, passages wander, two cellular passes smooth the result, dead-end spurs go nowhere on purpose, single rock pillars are left standing in the halls, and the interior is then trimmed onto what was actually carved. Pools (CaveInterior.Tile.WATER) are laid deep in the cave and draw back wherever they would cut a passage; TerrainManager routes is_fresh_water / is_still_water / is_drinkable_water through CaveManager.is_water, so underground water is real water to the drink order, the waterskin and the HUD — still, and never frozen or dried. Finds sit at least 8 steps along the walk from the exit (CaveInterior.depth_at, a BFS), and the renderer shades the floor with the same measure.

The doorway is one shape, drawn from both sides (world/cave_doorway.gd, 2026-07-26). CaveRenderer cuts it into the mountainside and CaveInteriorRenderer draws the same opening from within full of daylight, so walking in and looking back shows one door. It carries a rubble fan, a stone lip shaded from near-black to nearly white as it turns toward GamePalette.mountain_light, two or three chips out of the rim, an uneven doorstep and a darker throat behind the opening — everything hashed off the mouth’s own cell, so no two caves share a doorway and nothing is stored or seeded. It was tuned against screenshots, and the constants carry what the screenshots ruled out: too much rim wobble stops reading as a doorway, chips that reach too far in become fangs, and a bright stroke over the lit half is a smear of paint (hence a shaded band).

Key tunables — scripts/world/world_generator.gd

Rendering: world/terrain_renderer.gd (per-cell texture), terrain_snow.gdshader, tree_canopies.gd (crowns draw over walkers at z 4; _apply_walkers feeds the reveal+sway shader), room_floor_renderer.gd, fog_overlay.gd. All world colours live in resources_data/palette.tres via GamePalette. Nav: walkable_navigation_region.gd; collision: terrain_collision.gd.

Resources & animals

Companions

The companion rig is scenes/player/Player.tscn / class_name Player, instanced three times as nodes Character1/2/3 (a node name is a save key — rename via SaveManager.RENAMED_CHARACTER_NODES). Behaviour is split across small controllers on the rig.

How a companion is drawn — scripts/player/companion_figure.gd 2026-08-06

One painter, one look. CompanionFigure.draw(canvas, feet, unit, look) paints the figure in cell coordinates, and everything calls it: the map figure, every CharacterPortrait (HUD row, character sheet, transfer window, companion window — framed on head and shoulders), and the character creator's previews. Player draws nothing itself. The portrait's old private bust, with its own hair pools and its own beard rule, is gone — that is what let the party row stop looking like the companion on the ground.

A drawing change is only reviewable if it can be seen: tests/figure_sheet.gd renders every face, kit piece, view, silhouette, tone and mark into one PNG, and tests/creator_shot.gd renders the creator panel. Both want a real display (DISPLAY=:1). Console: look, expression.

Recruiting — scripts/world/wanderer_spawner.gd

A wanderer is a companion rig (Player.tscn) that has not joined — not a second kind of person. That is the whole design: its identity, carry, drawing and save entry are the ones every companion already has, so recruiting is PartyManager.recruit() → rename onto a free Character<N> (a node name is a save key) + Player.join_party(). A stranger is frozen while it waits (Player._halt_survival) and reveals no fog. Leaving runs the other way: Player.leave_party() attaches a fresh controller in LEAVING and the rig walks off the map and frees itself — expulsion and desertion share that one door.

Spawner knobs: first_possible_day (6), min_days_between (6), arrival_chance (0.22/day), linger_days (3), renegade_chance (0.3), approach_cells (45). One stranger on the road at a time; a full party is sent nobody. Console wanderer [spawn [renegade]|here|panel|recruit|send|desert].

Equipment — scripts/player/loadout.gd (17.1)

items/equipment_def.gd (.tres in resources_data/equipment/) is the data seam: id, slot (TOOL/VESSEL/HEAD/CHEST/HANDS/LEGS/FEET — append-only, a slot is a save key), applies_to (the same StringNames the skills use), work_multiplier, max_durability/wear_per_work_second, repair_workshop/repair_cost, warmth, and defense (shipped inert for 4.6). EquipmentCatalog registers them. A new tool is a .tres plus one preload line — the same rule animals and buildables follow. Today: axe (×1.5 lumberjacking, 400 durability, mended at the lumber camp for 1 wood), coat (+6°) and hat (+2°).

Carried = equipped (there is no equip gesture yet), so has_tool() reads the pack and worn gear is just carried items with tool: true in the ItemCatalog — which is what keeps a haul from shelving someone's coat. Warmth is applied by TemperatureController right after the biome offset as insulation (clothing_comfort_cap 20°): it lifts a cold body toward comfort, never past it, so carried gear is never a liability you can't shed. Wear rides the raw delta on the exact tick that reads the bonus, so it is deterministic — no dice, the contamination-load principle. Repair is Command.REPAIR (right-click the matching workshop). Console equip, durability, warmth.

The big tuning surface — scripts/player/job_runner.gd

Movement/work: move_speed, work_seconds, mine_seconds, fish_seconds. Needs/thresholds: need_trigger_ratio/recover_ratio, emergency_ratio, warm_seek_below/cool_seek_above, despondent_below. Automation: base_rule_slots (12), dev_self_care (re-enables the dormant self-care tiers — tests / a future easier difficulty). Hunting: hunt_range_cells, hunt_base/min/max_hit, hunt_giveup_seconds. Fatigue penalties live on player/player.gd (fatigue_walk_penalty, fatigue_work_penalty, mood_work_penalty).

The bedroll is a bed, not a charm 2026-07-26

Until 2026-07-26 JobRunner.has_bedroll() was the mechanic: carrying one upgraded a rough night from inside the pack. On the user's decision it must be placed first, so rough_rest_factor()/rough_metabolism_scale() no longer read the carry at all and has_bedroll() now means only “there is one here to unroll”. Everything else goes through the ordinary bed path — it is claimed by reserve_free_bed, walked to, slept in, saved and demolished like any bed.

Placing and packing up. BuildingManager.unroll_bedroll(character, container) lays one out on the nearest free cell within 4 (both orientations tried, since it is 1×2), paid straight from the carry (payable_from_carry) and stamped with BuildingNode.unrolled_by — the companion's node name, because that is what the save file already keys characters by. JobRunner._release_bed() is the one place a night ends, so the pack-up hangs there: self_unrolled_bed() gates it, so a companion rolls up only what it laid out itself and a bedroll the player placed stays put — that is how you tell an automated companion where to sleep. pack_up() calls remove_building(node, false): no half-cost salvage, because half of a one-item bedroll is nothing. Player-facing it is JobRunner.Command.PACK_UP on the right-click ring beside Sleep. Console bedroll.

The night watch — JobRunner.Command.WATCH 2026-07-28

The arithmetic behind the warning: a campfire filled to max_burn_seconds (324 s) burns 7.2 in-game hours and the night is twelve, so a party that all lies down around one on a cold night wakes up short a companion. Cold is the whole gate — the reading is taken at 03:00, the coldest hour, through WeatherManager.get_effective_temperature() asked about a future hour, because a watch is set at dusk while it is still mild. The order itself holds position inside the heat radius and refuels on every tick the fire will take, ends at first light (not at the next dawn edge — a watch set at dusk must not end immediately), and costs the watcher a night's sleep, which lands as ordinary sleep debt the next day. Console watch.

Sleeping and mending — player/vitals_controller.gd 2026-07-29

Buildable.sleep_metabolism_scale was deleted rather than set to 0.5 on every bed (2026-07-29, user decision): four beds each carrying their own copy of one number is how they came to say 0.5 / 0.6 / 0.75 / 1.0 in the first place. A bed now pays in rest, warmth, shelter and healing only. The waking trickle never adds to a bed's rate — _process applies the shortfall, so a sleeper mends at the bed's pace and 30 % cannot quietly become 130 %; a bed that heals less (the laid-out bedroll heals nothing) is topped up to it instead. Temperature is the only thing that still moves a sleeper's burn: the cold-hunger and heat-thirst terms keep running, scaled by the same half. Console regen.

A worker that cannot work says so — JobRunner._report_no_work(reason)

Until 2026-07-27 only the fisher announced it; a lumberjack with no forest, a stonemason with no rock face, a hunter with no bow and a water carrier with no source returned zero velocity and stood there, which from outside is indistinguishable from working. A farm in winter stays silent deliberately — dormant fields are the rule working. drop_work() now really does drop every alert latch, including _danger_reported, which had been swallowing the first mortal-danger alert of the next episode. The full tick order and the four layers are in docs/automation-and-jobs.md.

Automation internals

Work actions are gated by standing workshops (Buildings). Old saves migrate a painted schedule into time-window rules on load. Console: rules, prog, tasks, auto.

Buildings & construction

The workshop yard, and working a building by hand 2026-07-29

The order is WorkerCommands._cmd_work, and it deliberately owns none of the doing: it walks the worker in, latches reported for duty — it has to latch, because each trade's own search sends the fisher to the water and the lumberjack into the trees, so “am I still at the hut?” reads false a second after arriving — and then hands every frame to run_job, the same WorkAction the rule program and the task board drive. One implementation per trade. It resolves below REPAIR and CRAFT in CommandController, so no click that meant something yesterday means something else today. Console yard.

Items, inventory & storage

Time, weather & temperature

Temperature damage: cold below 4°C / heat above 35°C (temperature_controller.gd). Pacing: the 18-minute day and ×1.8 task lengths; HARVEST_TIME_SCALE is the harvest seam.

Audio & the sound library

Before v0.10.0, eighteen audio files carried the whole game and every path was a constant in sound_manager.gd: building, dying, hunting, fishing, tending a fire, crafting and every footstep were silent, and the sound of the game could only grow if somebody opened GDScript. It is now 223 rows across nine banks in resources_data/audio/, each with a plain-language description, and filling one is dragging a file into stream. Full write-up: docs/audio.md.

The nine banks: music (moods + stingers) · ambience_beds (place · weather · settlement) · ambience_spots · work (every job: start, loop, impact, finish) · footsteps (nine surfaces) · creatures · buildings · ui · world. Naming is bank/subject_variant — work/chop_impact_oak, amb/bed_forest_night. Use an AudioStreamRandomizer for variations and an AudioStreamPlaylist for a mood; both are Inspector-only. tools/gen_sound_banks.gd regenerates the banks from its table and never overwrites an assigned stream; rows that vanish from the table are reported, never deleted. docs/sound-checklist.pdf prints all 223 rows with tick boxes as a shopping list.

The mix — five buses, five sliders, one Silence

Master
├── Music      moods, stingers
├── Ambience   the three beds, the spots
├── World      positional: work, footsteps, fire, animals
│   ├── effect 0  low-pass   — the roof
│   └── effect 1  reverb     — the cave
└── UI         clicks, windows, alarms, the heartbeat

There used to be two buses and three sliders, one of which ("SFX") carried the ambience beds, every work loop, the heartbeat and every UI click — so turning the interface down turned the rain down with it. A pre-v0.10.0 audio_settings.cfg migrates: the old SFX value seeds Ambience, World and UI. Ducking is a tweened number, not a side-chain — a stinger names the buses it pushes down in its ducks field and SoundManager.duck() lets them back up over duck_release_seconds; a number is something a headless test can assert, and it does. Room acoustics are bus state, not sounds: underground the reverb comes up to 0.5 and the outside beds fall 12 dB, under a roof the low-pass closes to 4 kHz and they fall 7 dB, both owned by AmbienceDirector._set_room() off TerrainManager.is_underground() and BuildingManager.is_indoors() on the camera's cell.

The six layers

UI & panels

Save / load

Load order still matters, and is kept explicitly: _apply_saveable(key) places the order-sensitive members by hand (terrain before buildings, the task board after them, weather last) and an order-free tail sweep catches every other member — so both halves are safe against a newcomer nobody remembered. Members register with the literal group name, because SaveManager autoloads last, after them all. Session meta, CityInventory and the tree-walk collectors stay hand-written on purpose.

Node names are save keys (see Companions). Since recruiting (5.4) _collect_characters walks the tree, not a fixed name list, and _rebuild_character builds the rigs a fresh world doesn't have. Restore obeys a rank order (ground → structures → fixtures). A slot shorter than a stored Variant's 4-byte header (MIN_VARIANT_BYTES, checked in _open_for_read) is skipped without being read: a save interrupted mid-write leaves a 0-byte file, and get_var() on it prints an engine error GDScript cannot catch. Difficulty (Hard = free save/load, Brutal = suspend-only + slot wipe) is picked on the title screen. Console: saves, save, load, delsave, difficulty.

Console commands

Every command the dev console knows, what it does and one example each.

F12 opens the console (debug builds only); Esc or F12 closes it and the game pauses while it is open. Handlers live in scripts/ui/dev_console.gd — help inside the console is the authoritative list, and every new mechanic ships a command here.

Most commands act on the selection: the companions currently selected, or the whole party when nobody is. select 2 is therefore usually the first thing you type.

Companions & stats

Windows, items & the hand

World & terrain

Time & weather

Resources & animals

Building & automation

Sound

Saves, meta & staging

Testing & tools

Godot binary for this environment: ~/Downloads/Godot_v4.7-stable_linux.x86_64. After adding a class_name, rebuild the class cache before headless tests. Claude cannot see the running viewport — visual work is verified through the screenshot harness or by the developer.

Versioning

One number, one source, and the two things it is deliberately not.

The game's version lives in exactly one place: application/config/version in project.godot — the engine's own field, so an exported build carries it in the PCK for free. Everything in the game reads it through GameVersion (scripts/main/game_version.gd), a static class like BuildCategories: GameVersion.string() gives "0.5.0", GameVersion.label() gives "v0.5.0" — the one spelling every screen uses, so no label re-types the "v".

A release is not a build. The number only moves when a release is cut, so between two of them every build wears the same one — twenty-three commits and three features once all reported 0.5.0. Since 2026-07-26 the class answers both questions: GameVersion.string() is the release, build_id() is this build — <commits>.g<sha>, plus .dirty for an uncommitted tree, and empty when the build is the release. build_string() puts them together as 0.5.0+23.gb81e6d1. It is derived from git, never typed, and never a gate — pure provenance.

Scheme: plain semver. While the prototype runs at 0.x, MINOR goes up per completed feature batch and PATCH for fixes; 1.0.0 is reserved for the release that closes the run arc (ROADMAP Milestone 10, the migration cycle). Milestone-derived numbering was rejected — milestones complete out of order, so the version would have run backwards.

Where it shows: the title screen's bottom-right corner, the pause menu, every save's header, the console command version (which also prints the engine build and the save format), the Windows executable (mirrored into export_presets.cfg), and the line at the top of this page. The first four show the build — a save header carries build_id beside game_version, so two runs saved a week apart under one release number no longer read as the same game.

Cutting a release (full steps in CHANGELOG.md): bump project.godot, mirror the number into export_presets.cfg and this page, write the changelog section, run the headless suite, commit, then git tag -a v<version>. The suite fails if the three copies drift apart — that check is what keeps the mirrors honest.

A MINOR release costs more than a PATCH. Only x.y.0 freezes its own wiki archive — both languages plus a re-shot copy of every screenshot, roughly 10 MB per release. Paying that for a one-line fix is what made a bump a ritual, and a ritual that expensive does not get performed, which is how a whole day of work ended up sharing one number. A patch release therefore rides on the archive of its minor line: needs_wiki_archive() and release_line() are the seam, the suite checks a patch against v<major>.<minor>.0, and wiki/snapshot.sh declines to freeze a patch while still rewriting the version picker.

Publishing the build — one .exe, always the newest

The download button at the top of this page links companions_<version>.exe sitting next to index.html on the server, and exactly one build exists there at a time. Publishing is the last step of a release, after the tag:

The link is a mirror like the version number — cut_release.sh rewrites it and the suite fails if it drifts. It has to be strict: this vhost answers a missing file with this page and a 200, never a 404, so a link to an unpublished build would hand a reader HTML under an .exe name rather than fail visibly.

The wiki archive — one frozen page per release

This page is a living document: it always describes the build in development. So that it can also say what an older build did, every release freezes a full copy under wiki/v<version>/ — both languages and their own copy of the screenshots, because an archived page showing today's pictures would defeat the point of archiving it. The picker in the sidebar reaches every frozen build; a frozen page wears an amber banner and links back here.

Release order, and it matters: edit both pages for the release → wiki/shots.sh (so the frozen set is this build's) → bump project.godot, export_presets.cfg and both pages → wiki/snapshot.sh → changelog, suite, commit, tag.

Keeping this in sync important

When a player-facing mechanic changes (a control, a building, a gather target, a survival rule):

1. Edit HelpPanel.HELP_TEXT in scripts/ui/help_panel.gd — the single on-screen source of player help (its nav is derived from the section headers, so keep the [font_size=17][color=#9ec1ff][b]…[/b] header format).
2. Write the changelog entry under ## Unreleased. That section is this page's to-do list — see the next callout.
3. At the next MINOR release, update the matching Player Guide section here, and — if the change touches code structure (a new file, seam, tunable or console command) — the matching Developer Reference section, re-shooting the screenshot where it shows.

The developer reference is derived from the seam catalogue in the project memory index (memory/MEMORY.md), where each system names its one seam — the fastest place to confirm where a mechanic actually lives.

Companions — prototype developer wiki. Player Guide mirrors the in-game F1 help; Developer Reference maps mechanics to files, seams, tunables and console commands. Screenshots made with tests/screenshot.gd (seed 12345).