27 Running The Price of Dawn

27.1 How to Use This Book

This is yours. Players should stop at the Player’s Guide — everything past that point is for you.

The structure:

The World - Varenhold, its factions, and how it changes over time (GM chapter)
NPCs - Detailed profiles for every major character using the OGAS system
Sessions 1-5 - Scene-by-scene session guides with branching paths
GM Toolkit - AI tools, encounter tables, prep checklists, tracking sheets
Player Companion - Player-safe addenda (pre-made characters, shops, travel, trackers) you can hand out without exposing secrets

27.1.1 Point Players at the Companion

When players ask where to find more texture between sessions, send them to the Player Companion chapters:

characters.md for instant pregens and relationship hooks
shops.md and travel.md for downtime investments and route prep
tracker.md for the shared campaign state sheet you update between games

Treat those files as handouts: share PDFs, screenshot individual tables, or drop them into your VTT. Everything else in this book stays on your side of the screen.

27.1.2 Running the Campaign Short

You can run this in 3 sessions by compressing:

Session 1 as written
Sessions 2+3 merged (discovery + first alternative)
Sessions 4+5 merged (climax + resolution)

For 5 sessions, run each chapter as written and let NPC relationships breathe. The extra time is almost always worth it - this campaign lives in the small moments between the plot beats.

27.2 Design Philosophy

27.2.1 Players First

Every scene in this book is designed around player agency and meaning, not plot delivery. Your job is not to tell a story - it is to make the story matter to the players.

The Scene Must Have Stakes. Every scene gives the players something to gain, something to lose, or a choice that matters. If a scene does neither, cut it.

Let NPCs Be Right. Every major NPC in this campaign has a defensible position. The Restorer leader isn’t wrong that people are suffering. The Chancellor isn’t wrong that ten lives versus thousands is a utilitarian problem. The Dawnborn aren’t wrong to fight for their lives. Give every NPC their best argument.

Failure Is Interesting. This campaign has no “correct” path. A failed persuasion roll doesn’t close a door - it opens a different one. Track consequences, not successes.

27.2.2 The Great GM Principles Applied

This campaign is built on several scene-design principles:

Every encounter has a goal beyond survival. Combat in this campaign always has a secondary objective - protect a document, prevent an NPC from being taken, create time for someone to escape. Players who only fight will miss the point. Players who think about what they’re actually trying to achieve will usually find a better way.

The five senses, every scene. The amber light is always there. So is the smell of lamp oil. So is the sound of a city that has been waiting for something for fifty years. Use sensory details early in each scene - they ground the players before the dialogue begins.

NPCs want things, fear things, and lie about things. The three questions for every NPC: What do they want? What do they fear? What will they lie about? The OGAS system below answers all three. Know these before you roleplay any named character.

The encounter beat. Every scene should have at least one moment where the situation changes - a revelation, a decision, an unexpected development. If a scene ends in the same state it began, cut it or add one.

27.3 The Three-Clue Rule

Every mystery in this campaign follows the Three-Clue Rule: any important discovery has at least three separate paths to reach it.

If the players miss the journal, they find the blood on the stones. If they miss the stones, the Archivist lets something slip. No single failure should wall off the story.

When you prep a session, ask yourself: “If the players skip the obvious clue, how else could they learn this?” Write two backup paths for every important revelation. The session guides already have these built in, but adapt them to what your players are actually doing.

27.4 The OGAS System

Every key NPC in this campaign is built using the OGAS framework for memorable, consistent characterization:

Letter	Stands For	What It Means
O	Occupation / Role	What they do in the world
G	Goal	What they want most right now
A	Attitude	How they see the players (and why)
S	Secret	What they’re hiding (and the cost of discovery)

Each NPC profile in the NPCs chapter includes a full OGAS block plus personality notes, voice guidance, sample dialogue, and an attitude-shift table that tracks how the NPC changes based on player choices.

At the table, you only need to hold two things in your head per NPC: what they want right now, and what they’re not saying. Everything else follows.

27.5 The Moral Dilemma Engine

Every session is built around a central question. These questions don’t have answers in the text - they have consequences.

Session	Dilemma
1 - Into the Dark	Is hope worth chasing when it might cost everything?
2 - The Weight of Light	Do you have the right to decide someone else’s fate, even to save thousands?
3 - Lesser Evils	Is a “lesser evil” still evil? How far do you compromise?
4 - The Breaking Point	What do you owe to people who choose to sacrifice themselves?
5 - The Price of Dawn	When the “right” choice and the “good” choice are different, which do you make?

At the end of each session, ask the players the session’s question directly. Not rhetorically - pause, and ask. Their answers don’t change the game mechanics, but they tell you what scenes to emphasize next session. Pay attention to which players answer confidently and which ones hesitate. The hesitators are doing the most interesting work.

27.6 Running the Character Interview

The Player’s Guide contains a ten-question character interview for players to answer before Session 1. This section tells you how to use what they give you.

27.6.1 How to Run It

Do this one player at a time, ideally before session zero — a quick five-minute call or a short message exchange works fine. You’re not collecting information. You’re listening for the things they don’t say.

Ask the question. Let them answer. Ask one follow-up.

The follow-up is always a version of: “What did that feel like for your character?” or “What did they do with that?” You’re pushing from the event into the person.

Don’t take notes during. Write down the one or two things that stuck after.

27.6.2 What Each Question Is Actually Finding

Question	What You’re Listening For
The surprise on arrival	What they’re comparing Varenhold to — tells you their frame of reference and what’s missing from it
The gate voice	Whether they’re someone who notices details or someone who creates them from nothing — both are good
The painting	Their emotional relationship to loss and the absent sun — some characters mourn, some intellectualize, some refuse
The Dawnborn (honest)	The belief they’re bringing in that the campaign will stress-test — admiration breaks one way, suspicion breaks another
The named person	Whether they root themselves in relationships or in abstract commitments — who they’d call if things went badly
The grey sickness contact	How close to the city’s central wound they want to be positioned — their proximity to the campaign’s grief
The Cormac story	What they value in other people — grace under the weight of being something significant, or its absence
The faction question	Where their patience ends — this determines how quickly they turn toward or away from the Desperate
The blame question	Whether they think cleanly or messily about cause and responsibility — this shapes the whole Session 3 reveal
The line	The thing the campaign will reach for. You now know where it is. Keep that information, and don’t use it cheaply.

27.6.3 What to Do With What You Learn

Before Session 1, you should know three things for each player:

Their want — what they’re there for, underneath the stated reason
Their fear — what they’re most afraid of discovering (not monsters; the human version)
Their lie — what they believe about this city, or themselves, that won’t survive contact with the truth

The interview gives you these without asking for them directly. The player who says “I blame the Archmagister and yes, that’s fair, someone has to be responsible” is different from the player who says “I blame the Archmagister and I know it’s not fair but it’s easier.” Play the NPCs accordingly. Let the city push on the thing each player revealed.

The most important thing: whatever they named as their line — the thing they won’t do even if it’s right — don’t forget it. That’s the scene you’re building toward.

27.7 Consequence Tracking

This campaign is built on consequences. Every session guide ends with a tracking table - fill it in, carry it to the next session, and let it shape how NPCs behave. Players notice when their choices matter. They notice more when they don’t.

The key things to track: - Who knows what - the information asymmetry is the campaign’s main engine - Relationship states - which NPCs trust the players, which are wary, which have been hurt - Dawnborn positions - who is willing, unwilling, undecided; this shifts based on player behavior - Living World state - the grey sickness rate, food supply, political pressure; these create urgency

The Living World rules are in the GM Toolkit. Use them. The players should feel the city getting worse in real time - not as a countdown timer, but as a texture in every scene.

27.8 Running It Differently

27.8.1 Running Online (Virtual Table)

The campaign translates well to online play with a few adjustments.

Ambient audio: Varenhold has a specific soundscape. Before Session 1, prepare two ambient tracks: a “Lowmark” track (market sounds, water, coughing, distant drums) and an “Ashring” track (wind, silence, the occasional bell). Free sources work fine; the specific content matters less than having something that isn’t dead air. Switch between them based on district.

Lighting effects: Many VTTs support ambient lighting overlays. Use a warm amber tint on all maps rather than standard “torchlight.” The sourceless, shadowless quality of Varenhold’s light is unusual - avoid the standard radial light tools in favor of broad, low-intensity wash. The effect should be that everything is faintly visible and nothing casts a sharp shadow.

Handouts: The player-facing chapters in this book are designed to be shared as links. If your table reads in advance, share player-handout.md directly before Session 1. The trade chapter and world-lore chapter can be shared any time without spoilers.

Camera framing (for GMs who use video): Two specific moments benefit from leaning into camera. When a Dawnborn first appears in Session 2, take a long pause before you continue narrating - let the players absorb who they’re meeting before the scene moves. In the ritual moment at Session 5’s ending, don’t rush past the silence. Online tables sometimes rush silence; resist this.

NPC voices: The AI tools chapter describes ElevenLabs voice generation. If you use it, prioritize Sera (warmest), Tomas (most measured), and Edoran (most worn). These are the voices players will hear most. The Chancellor benefits from a formal, precise vocal quality that suggests someone who has been choosing her words carefully for eleven years.

27.8.2 Running as a One-Shot (2-3 Hours)

The campaign’s moral engine can be delivered in a single session with significant compression.

The One-Shot Frame: > The players are investigators who have been hired by an anonymous patron. They arrive in Varenhold, discover that the ritual documents have been found, and must decide - in one session - what to do with the information. The Dawnborn are described but not present in the room; the players must weigh what they know from other sources.

Scenes to keep: 1. Arrival in Varenhold - sensory establishment, the atmosphere (15 minutes) 2. Meeting Theron in the Archive - the revelation of the ritual’s true cost (20 minutes) 3. One Dawnborn encounter (Lira recommended - her position is most immediately emotional) (20 minutes) 4. A brief Edoran confrontation - he knows the players know; what do they do? (15 minutes) 5. The decision and its read-aloud (20 minutes) 6. Debrief (15 minutes)

What to drop: All multi-session political threading, the Reckoning, the Spire access puzzle, Sessions 3 and 4 entirely. The one-shot is a moral thought experiment, not an investigation. Players know the cost from the start; the session is about what they do with knowing.

Tone adjustment: One-shots work best in this campaign if the moral stakes are established very quickly. Consider handing players the “What Kind of Story This Is” section from index.md at the table and asking them to read it before the session starts.

27.8.3 Running as a Three-Session Campaign

If five sessions is too long for your table, the campaign compresses cleanly into three sessions without losing its core shape.

Session	Content
Session 1	Sessions 1+2 combined: arrival, Archive discovery, all three featured Dawnborn introductions. Cut the political threading; focus on establishing the dilemma and the people. End the session when the players have met Sera, Tomas, and Lira and understand the ritual’s cost.
Session 2	Sessions 3+4 combined: the two alternative paths (Isolde’s method, the Restorer compound). The Reckoning’s action is compressed to a single confrontation at the end. The Dawnborn positions crystallize.
Session 3	Session 5: the finale. All the setup from Sessions 1-2 pays off here. The Dawnborn positions are as set at the end of Session 2; there’s no Session 4 relationship management to adjust them, which means the ending is slightly more determined by earlier choices. This is fine - the compressed version rewards players who committed early.

What to cut: The Reckoning arc is the easiest to compress - Harran becomes a one-scene antagonist rather than a two-session threat. The Spire access puzzle in Session 3 can be reduced to a single scene with Isolde directly rather than the full bureaucratic sequence. The Dusk Parishes and Ashfen Clans become background color rather than active locations.

27.8.4 Running for Different Player Types

The pure roleplayer (characters-first approach):

This campaign is already built for them. The additional accommodation: let them drive toward specific Dawnborn before the plot does. If a player clearly wants to develop a relationship with Tomas, let Tomas appear in sessions before his scheduled scene. The relationship investment is the point, not the scheduling.

The tactical problem-solver:

They will look for the third option that avoids all costs. Let them look. The campaign has options (Isolde’s transfer method, the Inversion path, the Dawnborn willingness threshold). What it doesn’t have is an option with no cost. The problem-solver’s arc in this campaign is discovering that the problem isn’t the kind that can be solved - it can only be answered.

Practical accommodation: give the problem-solver the Spire scholars as their domain. The most information-dense, mechanically interesting access is there, and it rewards the systematic approach.

The combat-focused player:

The campaign has combat (Sessions 3-4 especially) but it’s not the primary resolution mode. The accommodation: make the combat scenes’ secondary objectives particularly visible to this player. They will want to win the fight; show them what they’re protecting when they win. Aldric’s safety in Session 4 is more important than Harran’s defeat. Make that clear in how you frame the scene.

The social engineer:

They will try to play factions against each other. Let them try. The campaign is built for this - the faction relationship map in factions-guide.md shows the tensions. What the social engineer will discover is that most of the NPCs in this campaign are aware that they’re being played and will name it. The Chancellor especially. Tomas definitely. The campaign rewards genuine engagement over manipulation, which is itself a moral lesson.

27.8.5 Tone Calibration

The campaign runs at three possible tone levels. Decide as a table which level fits before Session 1; adjust between sessions if needed.

Level 1: Low Tragedy (Lighter)

What changes: The Dawnborn are slightly more optimistic about the ritual possibilities. Edoran’s motivation is idealistic rather than grief-driven. The grey sickness is present but the care houses are managing it. The city is strained but functional.

The ending: More likely to resolve at Ending A or C. The moral weight is real but the hopeful path is accessible.

Good for: Tables newer to morally complex campaigns; shorter runs; players who want an emotionally meaningful campaign without sustained darkness.

Level 2: As Written (Standard)

What changes: Nothing. Run the campaign as the chapters describe.

The ending: All six endings are equally possible.

Good for: Experienced tables comfortable with moral weight; five-session runs; groups who have done a Session Zero and know what they’re walking into.

Level 3: High Tragedy (Darker)

What changes: The Dawnhall food stores are already at 25% at campaign start (closer to rationing). One beloved minor NPC has died of grey sickness before the players arrive (the memorial room has a fresh photograph). Edoran’s grief is more recent and more present. The Dawnborn show more signs of their slow decline.

The ending: Ending D becomes harder to achieve (the alternative path requires more active building). Ending F is more likely if the players don’t engage decisively.

Good for: Tables who explicitly want a tragic arc; players who find catharsis in grief; groups who have discussed and consented to higher emotional weight.

This campaign has no happy ending. It has hopeful endings and honest endings and pyrrhic endings, but the sun does not return without cost.

The goal is not to make players feel good. The goal is to make them feel something real - and to talk about it after the dice are put away.

The debrief in Session 5 is not optional. Some of the best moments in any campaign happen in the fifteen minutes after the final scene, when people are still sitting at the table and the characters are still real. Don’t skip it.

That’s the price of dawn.