Design

Designing an encounter deck where no choice is obviously correct

A trail-survival game is not really a game about a trail. It is a deck of small decisions, dealt one at a time, each one asking you to give up something you want in exchange for something you need more. The scenery is a costume. The design work is entirely in the deck.

Which means the deck has exactly one rule it must never break, and everything else in this piece is a consequence of it: no option on any card may be obviously correct. The moment a card has a right answer, it stops being a decision and becomes a formality — a keystroke the player performs on the way to the next real card. Ten of those in a row and the game is a slideshow.

What a card actually is

The working shape is deliberately narrow. A card has a speaker, three or four lines of body text, and two labelled options. That is it. No sub-menus, no inventory screen, no dialogue tree. You read a small situation, you pick a side, and the trail moves.

Underneath, each option is a bundle of adjustments to a handful of meters — how much food is in the wagon, how sound the wagon itself is, how the party is holding up in body and in spirit, how far you got today and how many days it cost. The player never sees a spreadsheet. They see two sentences and, at most, a hint of which meters are in play.

The narrowness is the point. With two options and five meters, a card is a single clean question: which of these five things can I most afford to spend right now? Widen it to six options and the question dissolves into optimisation, which is a different and much less interesting activity — and one a phone screen is a bad place to perform.

Why "obviously correct" is so easy to write by accident

Here is the trap, and it caught me: a card is usually written as a scene first and a trade second. You picture a family on the roadside who have been walking for two days. You write the option where you share what you have, and the option where you can't afford to. Then you assign numbers, and the numbers are chosen to feel right — generosity costs food and buys morale, refusal saves food and costs morale.

That one works, because each side takes from a different pocket. But now imagine a river crossing late in the run, and the two options are pay for the ferry or take the mountain road. The ferry ought to cost money. If the game's money is not actually spendable at that moment — if paying is a word in the label rather than a number in the effect — then the ferry option gives you speed, morale and a whole wagon, and the mountain road gives you a broken axle and a slower week. It is not a decision. It is a button labelled yes.

I know it is a trap because it happened. Reviewing the deck card by card against the rule turned up exactly one card with a strictly dominant side, and it was that one: an option whose stated price never got charged. Every axis favoured the same choice. From the outside it read as a dramatic fork in the road; from the inside it was a formality with good lighting.

The audit

So the deck gets read against the rule, on paper, one card at a time. It is dull work and it is the single highest-value hour in the project.

The audit asks four questions of every card:

The audit also flags the near-misses, which are more interesting than the outright failures. One card in the deck deals with a birth on the trail, and its safe option is unusually generous — stopping heals the person in question and lifts the whole party's spirits substantially, while pressing on harms her and costs morale. On paper that is close to dominant. It survives the audit only because stopping costs two days, and days are the scarcest thing in the game. It reads as a deliberate authored beat — you should stop for this — bought with the one currency that can pay for it honestly. That is a judgement call rather than an arithmetic result, and the audit's job is to put it in front of a human rather than to decide it.

Structure versus variance

A deck that deals the same fifty cards in the same order every run is a puzzle you solve once. A deck that deals them in a completely random order is a slot machine. Both are worse than the thing in between.

So the cards are split into two populations. Structural cards are the spine: the departure, the first river, the illnesses, the wagon breaks, the winter. They always appear, gated by how far you have travelled, so that the shape of a run is recognisable — you know roughly when the country turns hard, and you can provision against it. Hazard cards are the weather: each one has a real chance of simply not being in the deck on any given run. About fifteen of them sit in that pool, and a given run sees roughly seven in ten of them.

The effect is a game that is the same story with different details. Two players comparing runs will both recognise the mountain crossing and both have opinions about the ferry, but one of them will have had a prairie fire and the other will never have seen it. That is the texture you want: shared structure, private incident.

The mile gate, and why it matters more than the shuffle

Every card carries a distance before which it cannot be dealt, and a few carry a distance after which they stop. That single field does most of the pacing work in the game.

It means the early trail can be forgiving without being boring — the cards available at mile fifty are the ones where a bad decision costs you a few days, not a person. It means an illness that would be devastating in the first week arrives when you have had a chance to buy medicine for it. And it means the winter cards genuinely are a third act, not a random event that might land on day three and end the run before it started.

It also lets the deck tell a story with no cutscenes. The cards that can appear near the coast are cold, thin, and about running out of things. The cards near the start are about weight and choices and the sheer optimism of loading a wagon. Nobody writes "act two begins here." The gates do it.

The cards that ask who

Most of the deck is a plain two-sided swipe that hits the whole party. A smaller group asks something different: who do you send? You pick a person, and how well it goes is graded by that person's aptitude for reading a situation — with the odds clamped at both ends so that the best person in your party is never a certainty and the worst is never hopeless.

These are the cards that make the party feel like people rather than a health bar with names attached. They are also the ones that most need the fallback: every "who do you send" card also offers a plain way out — cross where you stand, go around, leave it alone — because a card that requires a specialist you did not hire is a card that punishes you for a decision you made two hours ago with no idea it mattered.

Roughly one card in five works this way. That ratio was arrived at by feel and then left alone, because it turns out to be about the frequency at which a mechanic stays special. More often and the party-picker becomes the game; less often and players forget it exists.

What the deck is for

The honest summary of all this is that the deck is a metronome. It is not trying to kill you and it is not trying to tell you a story. It is trying to make you spend, at a steady rhythm, from a set of pockets that are all slightly too shallow — so that four hundred miles later you find yourself short of exactly the thing you decided you could spare.

Which is, more or less, what the journey it is about was actually like.