A working port during the careful recalibration of a Convergence

Tread Master's Guide · Part III

Running It

The first hour, the shape of a session, companions, continuity, and repair when play goes wrong.

☾ Table of contentsCurrent working source03 / 06

The hour you are in

Running It

Reading orientation

The first hour, the shape of a session, companions, continuity, and repair when play goes wrong.

The first hourThe shape of a sessionBetween sessionsCompanionsA session worth rememberingWhen it goes wrongWhen to say noWhere the other books helpChronicle-local entries

Part III — Running it

Parts I and II say what a Tread Master holds to. This part is about the hour you are actually in.

Everything here is practice rather than principle, and most of it is shown rather than asserted, because a Guide that only states positions teaches by assertion and leaves the hard part — the minute where a player is looking at you and waiting — entirely alone.

21. The first hour

The opening of a Chronicle does more work than any other hour you will run, and almost all of it is work you do by not doing things.

Do not brief the world. A player who has just made a person does not need the Wanderers explained. They need to be somewhere, with someone, wanting something. The setting arrives through weather, work, and what the people around them are complaining about.

Open somewhere ordinary and specific. The strongest first scenes are small: a workshop, a gate at shift-change, a market three stalls from the good stall. Vast openings sound impressive and give a player nothing to touch.

Put a want in front of them in the first ten minutes. Not a plot — a want. Someone needs something carried, settled, found, or witnessed, and it is due today.

Let the first roll be somebody's competence, not somebody's luck. The first uncertain thing in a Chronicle should be a place where a Character is good at something and it shows.

⚠️ Do not open on the party's formation. Chronicles that begin with strangers negotiating whether to travel together spend their best hour on a conversation nobody enjoys. Begin with the company already existing and let why surface later, in play, when it means something.

22. The shape of a session

Loose, and worth holding loosely:

  1. A short recap, only if orientation is genuinely needed. Read the room rather than the log.
  2. Pick up anything the players left hanging — their goals before yours.
  3. The session's real scenes.
  4. Close on a hook or an open question, not on a resolution.
  5. Afterwards, update the record while it is fresh.

Scenes end when their dramatic question is answered, not when the room is exhausted. If you cannot name the question a scene is asking, the scene has already ended and you are still in it.

Let a session breathe at least once. Between pressures, allow room for recovery, repair, training, travel, market days, an argument about money, a conversation nobody needed to have. A Chronicle that is only crisis has nothing for the crisis to threaten.

23. What you carry between sessions

Short list, kept honestly:

  • Where everyone actually is, and in what condition, so the next session does not open with a

negotiation about the state of the world.

  • Promises. Every promise an NPC made, and every promise a player made to an NPC. These are

the cheapest story you will ever get and the easiest to forget.

  • Clocks. Anything moving toward a deadline the players know about — and, separately, anything

moving that they do not.

  • What is known versus what is still hidden. A truth is either revealed or it is not. Keep the

line clean and keep the hidden material out of anything player-facing until it surfaces at the table.

24. Companions at the table

A company is four to nine people and most of them are yours. That is the hardest sustained performance in the role, and the failure mode is not that companions say too little. It is that they become an audience: present, agreeable, and narratively inert.

Three practices that keep them from it:

Voice fewer, more often. In any given scene, one or two companions are engaged and the rest are simply present. Rotate who is engaged. A companion who speaks in every scene is a chorus; a companion who speaks when the scene touches what they want is a person.

Show the thinking, not only the words. A glimpse of what is driving a companion underneath is worth more than a line of dialogue, and it is what makes them feel run rather than triggered.

Answer a consultation in the other register. When a player steps out of the fiction to ask a companion what they think — the way you would turn to somebody at the table — answer as a collaborator, marked clearly as out of character, and distinct from that companion's in-world voice. This is the single feature that most makes a Tread Master's companions feel like teammates rather than puppets, and it costs nothing.

Player, out of character: "Kester, what are you actually thinking here?" Tread Master, out of character: "Honestly? She thinks the ledger is a distraction and she is not going to say so in front of the magistrate. She would rather you took the south road and let her handle the paperwork later — but she has been wrong about paperwork before and she knows you know that."

Note what that answer does: it gives a real read, admits a limit, and leaves the decision entirely with the player.

⚠️ A companion may want something the party does not. That is the point of giving them wants, and smoothing it over is the most common way a company becomes furniture. Let the friction be real. Flag it out of character only if character friction starts becoming player friction, and then recalibrate together.

25. Making a session worth remembering

There is a five-question instrument this project uses to ask whether play is actually working. It is not a rubric and it grades nothing, but the questions are a fair description of what a good session contains — so they are worth reading as craft rather than as assessment.

Did a companion want something that conflicted with what the player wanted? Give each companion one want that can cost the party something, and let them press it when the scene touches it. A want that never inconveniences anyone is a biography entry.

Did anyone refer to something earlier, unprompted? This is why you keep the promises list. Put an old thing in somebody's mouth when nobody asked for it — an NPC who remembers a favor, a companion who brings up the thing from four sessions ago at the worst moment. Continuity the players did not request is what makes a world feel like it kept existing.

Did an open thread move without the players steering it? Give one thread a clock and advance it while everyone is looking elsewhere. The debt does not wait for the debtor to think about it. A world that only moves when touched is a set.

Did someone's flaw cost something? A flaw printed on a sheet is a label. Spend it: build one situation where the flaw is the reason the easy option is unavailable. Do this with the player, never as a punishment for having written it down.

Did anyone feel anything? You cannot aim at this one directly, and trying is how a table gets a scene that announces its own importance. It arrives from the other four, plus the willingness to let a quiet moment run past the point where you would normally cut.

26. When it goes wrong

The table has gone quiet and nobody is choosing. You have probably asked an open question in a place with no visible options. Narrow it: put two concrete things in the room and let somebody touch one. "What do you do" is a hard question in an empty room and an easy one in a room with a locked door, a nervous clerk, and a bell about to ring.

One player has receded. Do not cold-call them — that converts hesitation into pressure. Offer a soft doorway instead: something in the fiction that is theirs, that they may take, redirect, or ignore without anyone noticing they did. A companion is often the best vehicle for it, because a companion can ask a question that the table does not experience as a spotlight.

The party has split and one half is bored. Cut sooner than feels right. Two short scenes beat one long one, and the boundary between them is a fine place to end on an unanswered question.

A player wants something the world does not hold. Say so honestly and quickly, and then give them the nearest real thing. ⚠️ Never invent a place, a person, or an institution to satisfy the moment — it will not survive contact with the record, and the player will discover that by walking into it. "There is no guild for that here, but the harbor-reeve keeps the lists and she owes Kester a favor" costs you nothing and costs them nothing.

The tone has broken and the table is joking through something you built as serious. Usually this means the danger was not legible, or the scene was serious at the table before it was serious in the fiction. Let it land, take the note, and telegraph harder next time. Do not punish it.

Something you established turns out to be wrong. Correct it plainly, out of character, and move on. A Tread Master who quietly retcons is spending trust they will need later.

27. When to say no, and how

Most of the time the answer is yes, or yes-and, or yes-but. The refusals worth holding are few:

  • No, because the record says otherwise. The Chronicle remembers, and it outranks the current

moment.

  • No, because that resolves a protected mystery. Some questions this setting keeps. Deepen the

argument instead of settling it.

  • No, because that decides for another player's character. Nobody's Character is anyone else's

to spend.

Everything else — improbable plans, strange approaches, ideas you did not prepare for — is material. ⚠️ Never shoot down an offered idea. A player who learns their ideas make the world bigger will keep making it bigger, and a player who learns otherwise will stop offering, usually permanently and usually without telling you.

28. Where the other books help

  • A creature, a people, or something in the darksee the Bestiary, which is built to

be reached for mid-session. Its six bands (Nuisance to Wonder) describe what a thing asks of a company, and the band moves with the circumstances rather than being a fixed property.

  • What a Lineage or a Practice actually issee the Player's Handbook, Chapters III and

IV. For the Pulse and the Depths, Chapters I and II. When a player asks what their own Practice can do, the Handbook's answer is the one that binds.

  • How an attempt is resolved, and what a rating meanssee the Player's Handbook,

Chapter V. The player's account of Competency and action is the one they will have read; §17 and §17.1 here are the same procedure from the Tread Master's side, with the placements they never see.

  • How a character was made, and what you may still be asked to changesee **the Player's

Handbook**, Chapter VI. It is also the specification for the discovery conversation itself, so a player who says "I was told I could change that" is usually right.

  • What something costs, and what carrying it impliessee the Player's Handbook,

Chapter VII. There is no fixed price list on purpose; the chapter says why, and a price you set in one scene is a fact the next one inherits.

  • What the world is and what it can never besee the closed possibilities in the Tread

Possibility Atlas, which ships with the game under Content/World/The Tread/ rather than as one of the three books.

⚠️ Where two books disagree, the recognized world-law record decides, and neither your ruling nor the more recent book automatically wins.

28.1 Creating a Chronicle-local living entry

When a Chronicle demands a creature or people the shared Bestiary does not name, describe enough to make it playable without pretending every member or neighboring species is identical.

A useful entry answers eight questions, and the first comes first for a reason: a reader who cannot picture a thing cannot meet it, and neither can anyone drawing it.

  1. What does it look like? Give its size against a person, build, carriage, color and surface,

head, means of harm, and one detail that identifies it at distance. A creature described only by what it does is a rumor, not an entry.

  1. Where does it live? Name the stratum or ecological relationship first: heartland, ridge,

forest, frontier, cliff-edge, Depths boundary, interior, or low world. Climate and local biome may refine that answer.

  1. What signs does it leave? Tracks, calls, feeding marks, damaged growth, spoor, displaced

stone, ritual objects, abandoned nests, changed behavior in other animals, or another perceivable trace may matter before the creature itself appears.

  1. What does it need or seek? Food, shelter, territory, migration, kin, salvage, warmth,

safety, a social obligation, curiosity, or another established motive makes behavior intelligible without making it predictable.

  1. How does it affect its neighbors? Record predators, prey, competitors, symbioses,

scavengers, cultivated relationships, settlement effects, or other ecological ties where those facts exist.

  1. What makes an encounter consequential? Danger is only one answer. A creature may create

obstruction, opportunity, pursuit, wonder, scarcity, evidence, obligation, travel difficulty, trade, or a relationship worth preserving.

  1. What can characters learn? Separate observable signs, local knowledge, specialist

knowledge, rumor, and protected or Chronicle-private facts. Do not reveal significance merely because the engine knows it.

  1. How may this vary? Note regional, family, environmental, or Chronicle-specific variation

where established. Leave room for neighboring forms the books have not named.

This is guidance for describing life, not a new rules procedure. It keeps a local entry open enough for a generative Chronicle and concrete enough to use at the table. Use the demand scale in the Bestiary, §1 to describe what meeting it asks of the company.