Chapter 10: Campaigns, Timers, and Consequences

Fate's Edge GM Guide — Chapter 10

In Fate's Edge, campaigns are not a sequence of disconnected adventures — they are pressure systems. Every choice the players make pushes on something: a faction, a threat, a relationship, a belief. Over time, those pressures accumulate, shift, and eventually break.

Your job as GM is not to hide this pressure — it is to shape it, reveal it, and let the players decide where it lands.

This chapter presents the core tools for doing that work: Timers, Fronts, the Crown Spread, and long-term campaign structures. Used well, they create momentum without railroading and stakes without arbitrary escalation.

Foundational Principles for Campaign Design

Before diving into tools, internalize these rules of thumb. They will save you more prep time than any other advice.

Set Situations, Not Plots

A situation is a stable condition with inherent conflict. A plot is a sequence of events you expect the players to follow.

• Plot: "The players must retrieve the Sunstone from the Ruined Tower, then defeat the necromancer, then close the rift."
• Situation: "The necromancer has claimed the Ruined Tower. The Sunstone inside could seal the rift. The village is starving because crops wither near the rift."

Situations give players agency. They can negotiate with the necromancer, steal the Sunstone, collapse the tower, divert a river to flood the rift — any solution that fits the fiction.

Design Timers, Not Every Element

You do not need to know exactly how a faction will act in session 12. Instead, give them a timer with a trigger condition.

"The Cult of the Eternal Night [6] advances when the players fail to protect a solar shrine or when the GM spends 2+ SB on occult activity."

When the timer fills, the cult achieves its goal — and you improvise the specifics based on the current fiction.

Read Your Player Sheets

Your players have already given you the best campaign hooks. Look for:

• Bonds: "I owe my life to the Vault-Queen's wardens." → The Vault-Queen calls in the debt.
• Complications: "A sealed hold refuses you entry." → That hold is now a key location.
• Patrons: Any Patron choice is a promise to involve that Patron's agenda.
• Skills at 3+: If a player invested in Lore 3, they want to discover ancient secrets.

Use Obligation as a Story Engine

Obligation (to Patrons, terrestrial patrons, or even the party's own Trust) is not a punishment — it is a guarantee of future adventure. When a player marks Obligation, note it. When their capacity is near full, introduce a demand.

"Your Patron, the Traveler, appears in a dream. The road to Highpass is washed out, and a pilgrim family is trapped. Guide them safely, and clear 2 Obligation. Refuse, and mark Fatigue 2 — the road will not open for you again until you do."

Embrace the Cascade

A single failure should never end the campaign. Instead, let it cascade into new problems.

The party fails to stop the ritual. The demon is summoned. Now the campaign is not "stop the ritual" but "contain the demon before it corrupts the capital."

Each failure should change the situation, not end it.

Let Timers Be Visible

Timers are not hidden GM tools. Show them to the players. Write Cult Influence [6] on an index card and place it on the table. When you tick it, announce: "The cult's ritual advances. You feel the ground tremble."

Visible timers create tension and informed choices. Players can prioritize which timer to slow.

Ask Questions, Then Use the Answers

During Session Zero and between sessions, ask:

• "What does your character fear will happen if you fail this mission?"
• "Who in your past might try to stop you?"
• "What secret are you hiding from the rest of the party?"

Use these answers to seed complications. The player who fears losing their family? Their family is now in danger.

Design for Your Tier

• Tier I–II (0–90 XP): Local scope, 3–5 session arcs. Threats affect a village, a guild, a noble house.
• Tier III (91–150 XP): Regional scope, 6–10 session arcs. Threats affect a city, a province, a trade route.
• Tiers IV–V (151+ XP): Continental scope, 15+ session arcs. Threats affect nations, the natural order, reality itself.

Do not give a Tier I party a world-ending prophecy. Give them a rival who stole their map.

Core GM Mechanics

Understanding the core resolution loop is essential for effective campaign design. Every meaningful action follows this cycle:

1. Declare intent and approach (Attribute+Skill)
2. GM sets DV (2–5+) and Position (Dominant/Controlled/Desperate)
3. Roll dice pool (Attribute+Skill d10s)
4. Count successes (6–9=1 success; 10=2 successes)
5. Apply outcome using the Outcome Matrix
6. GM spends Story Beats (SB) to introduce complications

Difficulty Values (DV)

• DV 2: Routine — clear path, no pressure
• DV 3: Pressured — mild opposition (default)
• DV 4: Hard — serious resistance
• DV 5: Extreme — dramatic gamble

Default DV is 3. Don't inflate DV to "challenge" players — use Position instead.

Position

Position tells you how risky the action is and changes how dice behave:

• Dominant: You press advantage — re-roll one failure
• Controlled: Balanced normal risk — no re-rolls
• Desperate: You act under duress — re-roll one success

Spending 1 Boon improves Position by one step before rolling. The GM may spend SB to worsen Position.

Outcome Matrix

• Successes ≥ DV, SB=0: Clean Success — Intent achieved, no complication
• Successes ≥ DV, SB>0: Success with SB — Intent achieved; GM spends SB
• 0 < Successes < DV: Partial — Progress; gain 1 Boon
• Successes = 0: Miss — No progress; gain 2 Boons; GM spends SB

A Partial is not failure — it moves the story forward. A Miss is never "nothing happens." The GM must introduce a complication.

Resources: Boons and Story Beats

Boons (Player Resource)

• Earned on Partial (1 Boon) or Miss (2 Boons)
• Maximum 5 Boons held; reduce to 2 at scene end (excess lost)
• Spent to: re-roll a die, activate an Asset, or improve Position by one step
• During downtime: convert 2 Boons → 1 XP (max 2 XP/session)

Story Beats (GM Resource)

• Earned when players roll a 1 on any die
• Spent to introduce complications:
  • 1 SB: Minor — noise, distraction, tick a 4–6 segment timer +1
  • 2 SB: Moderate — alarm raised, lose advantage, worsen Position
  • 3+ SB: Major — reinforcements, scene shifts, break an Asset
• Be aggressive with SB — unused pressure is wasted momentum

Campaign Tools

The Crown Spread (Session Zero)

The Crown Spread is a five-card (or six-card) oracular tool for seeding a campaign's major elements. Use it during Session Zero or at the start of a new arc. It creates a web of relationships, not a railroad.

What You Need

• A standard 52-card deck (jokers optional).
• A table or whiteboard to record the spread.
• 15–20 minutes of quiet thinking.

The Spread Positions

Draw one card for each position. Lay them in a semicircle (the "Crown").

Interpreting the Cards

Use the suit to determine the nature of the element, then interpret the rank to refine it.

Connecting the Elements

After the draw, ask yourself:

1. How does the Rival relate to the Site?
2. How does the Pressure affect the Site or Rival?
3. How can the Leverage help against the Pressure or Rival?
4. What does the Hidden Force want, and how does it complicate the others?

Draw a simple relationship map. You now have a campaign skeleton.

Timers for the Crown Spread

Create one visible timer for each element that will take time to resolve. Use these defaults:

Tick these timers during play when players fail relevant rolls or ignore the element. When a timer fills, that element's situation worsens dramatically.

GM Quick Cues

• Don't over-plan. The spread is a seed, not a script. Let players discover connections through play.
• Be flexible. If a better idea emerges, replace an element — the cards are oracles, not chains.
• Use the Wild card for surprise. Even you don't have to know what it is until it appears.
• Tie every character to at least one element. During Session Zero, ask each player: "How do you know about the Rival?" or "Why does the Pressure affect you personally?"

Timers: The GM's Primary Tool

Timers are the single most useful tool in Fate's Edge. Use them for:

• Threats: Reinforcements Arrive [4], Ritual Completes [6]
• Opportunities: Alliance Forming [6], Weakness Discovered [4]
• Travel: Journey to the Pass [8]
• Social: The Duke's Patience [4], Rumor Spreads [6]

When to Tick a Timer

• On a Miss or Partial — even if the player otherwise succeeds.
• When the GM spends Story Beats (1 SB = 1 tick typically).
• When the fiction demands it (e.g., "While you argue, the fire spreads").
• At the end of a session (for long-term timers like Cult Influence).

Timer Size Guidelines

• 4 segments: Short-term tension (a patrol arrives, a door breaks).
• 6 segments: Standard scene timer (a ritual completes, a rival escapes).
• 8 segments: Multi-scene or session timer (a faction consolidates power).
• 10+ segments: Campaign timer (a war, a prophecy, a curse).

Factions and Fronts

A faction is any organized group with goals that intersect the party's. A front is a collection of related factions and timers that represent a major threat.

Faction Sheet (Quick Template)

Running Faction Turns

Between sessions (or at the start of a session), run a quick faction turn to keep the world alive. A faction turn takes 5–10 minutes.

1. List active factions. Keep no more than 3–5 that directly interact with the party.
2. For each faction, roll 1d6. Use the table below.
3. Advance or retreat their Agenda Timer.
4. Note one concrete change. Write one sentence per faction.
5. Read the changes aloud at the start of the next session.

Optional: Faction Standing

For factions that are not pursuing a single agenda but merely have an attitude, track a simple −3 to +3 scale:

• −3: Enemy — actively works against the party.
• 0: Neutral — indifferent.
• +3: Ally — will sacrifice for the party.

Shift standing by ±1 after major interactions. No dice needed — just fiction.

Rival Parties

A rival party is a faction of 3–5 NPCs with their own Patrons, assets, and a visible Rival Agenda timer (6–8 segments). Tick their timer when the PCs ignore them or the GM spends SB on their off-screen activities. When the timer fills, the rivals achieve a major milestone.

Reveal their progress through:

• Rumors: "The Ashen Cord was seen leaving the Sunstone vault."
• Found scenes: A burned camp, a dead informant, a signature left behind.
• Direct confrontation: They show up during a critical moment.

For a full template and example (The Ashen Cord), see the Appendix.

Complications and Hazards

Complications are the narrative, mechanical, and environmental consequences that arise from failure, pressure, or the GM spending Story Beats. Hazards are ongoing complications that require action to avoid or mitigate.

Using Story Beats for Complications

When spending SB, follow this menu:

• 1 SB: Minor pressure — noise, distraction, tick a relevant timer +1, worsen Position by one step
• 2 SB: Moderate setback — alarm raised, lose cover/advantage, lesser foe appears, split the party briefly
• 3 SB: Serious trouble — reinforcements arrive, key gear breaks (temporarily), major twist shifts the scene
• 4+ SB: Scene-shaping turn — a trap springs, authority arrives, the environment changes dramatically, a Patron manifests an omen

Hazard Timers

Represent active hazards (fire, flooding, toxic gas) with Threat Timers:

• Tick the timer on missed rolls, GM SB spends, or at scene intervals
• When the timer fills, the hazard triggers (e.g., collapse, wave of fire)
• Characters may attempt to slow or disable the hazard (e.g., Craft to seal a leak, Arcana to freeze spreading flames)
• Treat as a Progress Timer when players work against it

Social Hazards

• Rumors: A timer that advances when the party fails social rolls; when full, a faction turns hostile
• Scrutiny: Worsens Position for stealth or deception
• Reputation Damage: Future social rolls start at worse Position

Magical Hazards

• Backlash Zone: An area where free casting automatically generates +1 SB per spell
• Ward/Seal: Requires a roll to pass; failure triggers a consequence (harm, alarm, etc.)
• Leaking Veil: Spirits or fey occasionally manifest spontaneously (GM spends SB to introduce)

Settlement Generator

Use this generator to create a memorable settlement — village, town, or city — in any region of Fate's Edge. Draw cards or roll dice to determine size, dominant faction, a pressing problem, a local resource, and a regional quirk. Then add hooks that tie the settlement to your campaign.

Step 1: Settlement Size

Roll 1d6 or draw a Spade (♠) and consult the rank.

Step 2: Dominant Faction or Power

Roll 1d10 or draw a Heart (♥). Adjust for region as needed.

Step 3: Settlement Problem

Roll 1d10 or draw a Club (♣).

Step 4: Local Resource or Leverage

Roll 1d10 or draw a Diamond (♦).

Step 5: Regional Quirk

A settlement's quirk gives it an unforgettable flavor. Use one of the two methods below.

Method A: Draw from the Regional Generator

For a settlement in a specific region, draw a single card from that region's deck (or use a standard deck and interpret by suit). The suit tells you the quirk's nature; the rank tells you its intensity.

Rank guidance:

• 2–5: Minor, easily overlooked (a strange sign, a whispered rumor).
• 6–10: Noticeable, affects daily life (a locked tower, a weekly bell that rings nine times).
• Jack–King: Major, defines the settlement (a noble's curse, a bridge that tolls memories).
• Ace: The Hollow is close; the ninth taboo is woven into the settlement's bones.

Example: In Thepyrgos, a draw of 9♣ might be a Cistern Taint that glows green, or a Synod Summons posted on every door. In Ubral, a Queen♥ could be a Lady of Tor who rules from a cairn, or a Bride-Carrier who walks between feuding clans.

Method B: d6 Quirks by Major Region

If you prefer a quick roll, use the tables below. Each table offers six quirks drawn from the region's established flavor.

Kahfagia (Creole Thalassocracy)

Ecktoria (Marble & Fire)

Acasia (Broken Marches)

Vhasia (Fractured Sun)

Viterra (Hedge-Law Realm)

Thepyrgos (City of Unfinished Proofs)

Aeler (Under-Vaults)

Ykrul (Wolf Standards)

Vilikari (Laurels & Longhouses)

Linns (Skerries & Storm-Oaths)

Ubral (Stone Between Spears)

Step 6: Hooks

Every settlement should offer immediate reasons to engage. Roll twice (or pick from each column).

Example: Rolling a Settlement

Draw / Roll

• Size: 3 → Village (401–900)
• Faction: 9 → Foreign Enclave (Sidhi lighthouse keepers)
• Problem: 7 → Unquiet Dead (ghosts walk at night)
• Resource: 4 → Spice / Coffee (high-value trade)
• Regional Quirk (Thepyrgos, d6): 3 → Every contract must be witnessed by a bell-ringer.
• Hooks: 1 + 5 → Protection from raiders + A hidden vault with old records

Settlement: Wharfstead of the Green Lamp (Thepyrgos borderlands)

A Sidhi enclave in a dry river valley, surrounded by olive terraces. The Sidhi keep a small lighthouse that burns green, witnessing every contract. At night, drowned ferrymen from the Black River walk the streets, asking for passage home. The local coffee is famous, but a band of reivers has been raiding the warehouses. In the lighthouse basement, a vault holds Astroegro navigation charts — and a fragment of a forbidden record.

One-Card Quick Settlement (For Improv)

If you need a settlement right now, draw one card.

Rank determines severity (low = local, high = regional). Face card means the settlement has a named leader with a secret. Ace means the Hollow is watching — the ninth taboo has been broken recently.

Running Travel as a Medieval Trek

Travel in Fate's Edge is not a line on a map. It is a medieval journey — uncertain, weather-beaten, dependent on local guides, hospitality, and the kindness (or cruelty) of strangers. For full procedures (weather tables, road condition dice, regional decks), see the Travel Framework in GM Guide Chapter 8, and Player's Guide Chapter 14. This section gives you the GM principles.

Lead with Weather, Not Distance

Open each leg with a weather description, then set Position based on that weather (e.g., Desperate for navigation in fog, Controlled for stealth in rain). The weather is the terrain.

Maps Are Lies; Guides Are Truth

Require a Guide role for each leg (PC or hired NPC). The Guide's roll (Wits + Lore) determines if they find the safe route, the short route, or the one that leads to a cultist ambush.

Hospitality as a Resource

When the party seeks shelter, draw a Heart from the regional deck — that's the host. Their attitude affects what they offer. Spending a String (e.g., "I helped this village last year") can improve the outcome.

The Travel Timer as Mood Tracker

Do not just tick the timer on successes. Use it to track the feeling of the journey (Optimism → Fatigue → Desperation → The Edge). When the timer fills, describe the arrival — mud-caked and grateful.

Genre Shifts Through Borders

When the party crosses from one region to another, the dominant fantasy subgenre shifts. Use the travel deck to introduce the new region's flavor immediately (e.g., from Ecktoria's political intrigue to the Mistlands' folk horror: the road grows silent, fog rolls in, a bell tolls without wind).

Traveling Without a Map

Fate's Edge does not use hex crawls. Travel is abstracted into legs, each with a Travel Timer (4, 6, 8, or 10 segments). You need only know how many meaningful scenes stand between two locations — not the miles.

Pacing and Arc Structure

Session Energy Management

Aim for three "beats" per session:

1. Opening hook (5–10 minutes): Re-establish stakes, remind of timers.
2. Rising action (60–90 minutes): 2–3 scenes with escalating tension.
3. Climax or cliffhanger (20–30 minutes): A major roll, a timer filling, or a hard choice.

Arc Length by Tier

• Tier I–II (0–90 XP): 3–5 session arcs. Local scope, personal stakes.
• Tier III (91–150 XP): 6–10 session arcs. Regional influence, branching paths.
• Tiers IV–V (151+ XP): 15+ session arcs. Continental scope, world-shaping consequences.

Between Sessions: The GM's Sacred Trust

Between sessions, update timers, track complication debt, and prepare scenes. Use the Between-Session Checklist in the GM's Appendix. Remember: your preparation is the quiet magic that transforms random encounters into meaningful episodes.

The Finale: Calling or Forcing the Crown

The campaign reaches its crescendo when one of two thresholds is met — the moment when accumulated influence and mounting pressure collide in a final reckoning.

The Finale Procedure

When the Crown is called, run the three-beat finale:

1. Reckoning: Defend or sanctify the record of accomplishments. Draw upon the Rival's established motives. Place the Pressure rail that will drive the scene forward.
2. Crossing: Stage the kinetic rail (Escape/Hunt/Hazard) that threatens to end the scene prematurely if not managed carefully.
3. Coronation: Use the Diamond Leverage to sign, seal, or swear the oath that cements the campaign's legacy.

Twist Collision (Finale Clause)

Exactly once, when the Rival's Spade Twist contradicts their Club Belief, the table chooses:

• GM gains +1 SB to complicate matters, or
• Players reduce two ticks total across the active rails, gaining breathing room.

Legacy Conversion: Epilogue

After the Finale, each PC draws 2 cards and answers epilogue prompts by suit. Then convert campaign elements into lasting legacy:

• Major Asset → Institution (12 XP): A safehouse becomes a school, a spy ring becomes an intelligence service.
• Seasonal Endorsement → Doctrine Rider (4 XP): Temporary support becomes permanent policy.
• Follower (Cap 3+) → Stationed NPC (0 XP): Loyal companions become custodians of the new order.
• Rival → Fixture: Surviving adversaries become recurring elements of the setting's fabric.

The Legacy Bond

When a PC retires or dies, their successor (a follower or a new character) inherits a Legacy Bond. This bond represents the predecessor's enduring influence. Once per session, the player may invoke the Legacy Bond to gain 1 Boon when acting to uphold the predecessor's values or complete their unfinished business.

Character Arc Management

Help players develop meaningful character growth through the legacy process:

1. Establishment: Define the character's current state and potential conflicts.
2. Development: Create opportunities for growth and choice.
3. Crisis: Present challenges that test the character's core beliefs.
4. Resolution: Allow meaningful transformation based on choices.

Quick Start Campaigns

The Sunstone Gambit (Tier I–II, 4–6 sessions)

A medium-difficulty introduction set in Acasia.

Premise: A scholar hires the party to retrieve a sunstone from a ruined tower before a rival adventuring company does.

Key NPCs: Scholar Mira (quest-giver), Captain Voss (rival leader), the Tower's Guardian (ancient spirit).

Timers: Rival Progress [6], Tower Collapse [8], Spirit Wakening [4].

Session breakdown: Commission → Travel → Exploration → Confrontation → Climax → Aftermath.

The Dying Sun (Tier III–IV, 6–8 sessions)

A regional crisis campaign. The sun-spirit is fading; a cult of eternal night seeks to extinguish it permanently.

Premise: The party must rally factions, recover a lost ritual, and confront the cult before the winter solstice.

Key NPCs: High Priestess of the Sun, Cult Shadow-bound, Reluctant Ykrul Chieftain.

Timers: Sun's Fading [10] (ticks each session), Cult Influence [6], Alliance of the Dawn [8].

Acts: Investigate the cult → Gather allies → Raid the cult's lair → Final confrontation.

Campaign Worksheet

Use this one-page worksheet to capture your campaign's key elements.

Narrative First: The World Remembers

Campaign design in Fate's Edge is not about railroading players along predetermined paths — it's about responding to player choices with consequences that accumulate like stones in a river, gradually shaping the flow of the narrative itself. Let the world shift in response to their actions. Let factions rise and fall based on their allegiances. Let the dice sing the song of a universe that reacts.

And when the Crown is finally crowned — when the last card is played and the final timer ticks to completion — let the echo of that moment be heard across the entire Amaranthine, a testament to stories well-lived and consequences fully earned.

Remember: Your preparation between sessions is the quiet magic that transforms random encounters into meaningful episodes and mechanical challenges into memorable stories. The investment in this sacred trust pays dividends in player engagement, narrative coherence, and the creation of campaigns that will be remembered long after the final dice have been rolled.

Optional Player-Character Death

By default, Fate's Edge treats death as rare and dramatic. Use any of the following modules (singly or in combination) to tune how lethal your table feels. All options respect Story Beats (SB) and Obligation as core currencies.

Baseline (Default)

PCs do not die on ordinary failures. Instead, they suffer Harm, Conditions, lost opportunities, or narrative costs. Death only occurs when a rule below is in play or the table agrees a scene warrants it.

Option A — Severe Harm Death

Trigger. When a PC would take a third instance of Severe Harm (or escalate past the top of your harm track), they instead face death.
Stave It Off. The player may avoid death by choosing one: (1) mark 2 SB and take a Maimed permanent Condition, (2) accept a Patron's Claim (see Option D), or (3) convert the blow into a Last Stand (Option C).

Option B — Death Timer

Trigger. Catastrophic consequences (falls, crushes, mortal wounds) fill a named Death Timer (4 or 6 ticks).
While Ticking. Actions that stabilise reduce the timer; taking further punishment advances it.
When Full. The character dies unless one of the following occurs immediately: spend 2 SB to hold at full (buy a single action), accept a Patron's Claim, or another PC succeeds at Pull From the Brink (risky, effect = timer −2 on success).

Option C — Last Stand

Trigger. On lethal harm or a full Death Timer, the player may declare a Last Stand.
Effect. For the remainder of the scene, the PC acts with +1 Effect and ignores new Harm. Each action automatically creates 1 SB. When the scene ends, the character dies unless a miracle is secured (Patron rite, relic, or equivalent).

Option D — Patron's Claim

Trigger. On death, the PC's Patron (or a circling power) intervenes.
Bargain. The GM offers 1–3 non-negotiable terms (e.g., Obligation +2, forfeit a Gift, become a vessel for a season). If accepted, the PC lives; mark the costs immediately and record the Claim as an ongoing front. Refusal means the death proceeds.
Note. Claims should change the campaign; use sparingly.

Option E — Dramatic Exit & Inheritance

Dramatic Exit. The player may choose a meaningful death that resolves a question or saves others.
Inheritance. The next PC created by that player inherits one of: (a) a Relationship (bond, contact, or rival), (b) a Tool (asset degraded one step), or (c) a Lesson (start with +1 XP toward a Talent used in the exit). Record how the world remembers them.

Option F — Return From Beyond

Trigger. A body, a name, and a path (rite, gate, bargain).
Cost. Treat as a High Rite with Obligation appropriate to the transgression. Set DV using the Rites system. On success, the PC returns changed: apply a Scar (permanent Condition) and 1 SB to the rescuer. On failure, choose: lose the body, or return with a Patron's Claim.

Implementation Timeline

Use this timeline to introduce optional player mechanics gradually over the course of a campaign.

Sessions 1–3

Investment Tracker, Information Trading (via Boons/Bargains), light Complication Bargaining.

Sessions 4–6

Timer Manipulation (Boon/Momentum/SB), Cultural Immersion, Faction Awareness, Momentum Banking.

Sessions 7+

Cross-Cultural Synergies, Escalation Management, advanced pacing choreography.

GM Reference: Concept Story Hooks & Legacy

The following table collects the story hooks and legacy notes for each example concept. Use these to generate plot threads, tie character backgrounds to the campaign, and plan for eventual character retirement or ascension.

Use these hooks to tie character backgrounds directly to your campaign arcs, and the legacy notes to plan for eventual character retirement or ascension (see the Legacy Engine chapter).