On this page

The Legacy Engine

Fate's Edge Player's Guide — Chapter 17

Planning for Legacy

If you are playing a long campaign or enjoy the idea of your character's influence outlasting them, consider investing in a Follower (Cap 3+) early. That follower can become your successor when your character retires or falls — inheriting your faction standing, one unresolved burden, and a Legacy Bond. See the checklist at the end of this chapter for steps to prepare.

Succession & Faction Building

“Your legacy is not what you build — it is who you build.”

The Legacy Engine is a narrative and procedural framework that helps your campaign grow across generations without losing emotional continuity. It treats succession as a story event — earned through action, consequence, and choice — rather than a conversion of one character sheet into another.

This chapter is for tables where characters retire, die, or pass on their cause to a follower. It is not required for every campaign, but when the moment comes, these tools help the transition feel earned and the new character feel connected.

Core Philosophy

The Legacy Engine follows three principles:

  1. Narrative Primacy — Succession happens because the story demands it, not because a timer fills.
  2. People Before Power — A follower becomes a PC because of who they are, not what they can do.
  3. Consequences Persist — Every legacy creates debts, rivals, and unfinished work that the successor must carry.

Legacy is not inherited cleanly. It comes wrapped in obligation.

When Does Succession Happen?

Succession is not automatic. It emerges from play. Common triggers include:

In all cases, the transition should be discussed openly at the table. The GM and player collaborate to find the right moment.

Choosing a Successor

A successor should already exist in the fiction. Typically, this is a Follower with whom the PC has a meaningful relationship. It could also be a family member, a student, a loyal lieutenant, or even a rival who earns respect.

What Makes a Good Successor?

If no suitable follower exists, the GM and player can create one retroactively — but that character arrives with less established history. The player may need to spend a session or two building them up before succession feels earned.

The Succession Arc

A smooth transition usually follows three beats. They can span one session or several, depending on the table's pace.

1. The Call

The follower faces a moment where they must act beyond their role. Examples:

This scene answers: Why this person, now?

2. The Trial

The follower is tested. The trial can be:

Success is not guaranteed. Failure does not end the story — it changes it. A follower who fails may still become a PC, but they carry a scar, a doubt, or a broken promise into their new role.

3. The Ascension

At a dramatically appropriate moment — often during downtime or immediately after a crisis — the follower formally takes up the mantle. This might involve:

The departing PC may be present, or they may be gone. Either way, the scene marks the end of one chapter and the beginning of another.

What the Successor Inherits

When a follower becomes a PC, they do not simply copy the old character sheet. Instead, they inherit three things:

1. Faction Standing

The successor begins with the same reputation, allies, and enemies that the previous PC cultivated. The GM may adjust specific relationships based on how the succession occurred (e.g., a contested succession might lose one ally but gain a bitter rival).

2. One Unresolved Burden

The player and GM choose one burden that the successor must carry forward. Examples:

This burden is a narrative hook, not a mechanical penalty. It gives the new character immediate purpose.

3. A Legacy Bond

The successor records a guiding value and a memory of the predecessor. Once per player per session across all Legacy Bonds, committing to a meaningful action upholding that value can grant 1 Boon before resolution. Describe the memory and the risk or obligation accepted. Normal Boon limits apply. The operating procedure below specifies timing, shared limits, and how the value can change. Memories provide characterization, not automatic secret knowledge or success.

Building a Faction Through Succession

Each time a character passes the torch, the faction (or cause) grows. It accumulates history, traditions, and institutional memory.

Growth Through People

Rather than tracking territory or wealth, track the faction's reach through the people who are now part of its story. Each successor adds:

The GM keeps a simple list: “The Banner of the Broken Wheel,” “the annual vigil at Sootfall Abbey,” “the debt to the Mistland ferryman.” These are the faction's real assets.

Faction Timers (Optional)

For tables that want mechanical weight, the faction can track two simple timers:

Use the optional operating procedure below to define triggers, progress, reduction, and completion. Crisis is the former Health timer, renamed to show that filling it means trouble.

Legacy at the table: the operating procedure

Scope and changes. These procedures clarify the Player’s Guide’s Legacy Engine. Succession remains a choice made through play. The additions specify a handover record, the Legacy Bond’s timing and limit, inheritance boundaries, and optional Growth and Crisis timers. Crisis is the former “Health” timer, renamed because filling it means trouble. No new skill, character tier, or replacement for the core loop is introduced.

1. Write a Legacy record

Record the predecessor, prospective successor, cause, one guiding value, one unresolved burden, and the people who recognize the succession. List each asset, follower, and obligation separately, with its current controller, condition, upkeep, creditor, and any dispute. Name the player who keeps the record. Review it at each succession and campaign downtime.

A Cap 3+ follower is a well-established candidate, not a mandatory purchase. A family member, student, or other suitable character can succeed them. Becoming a PC ends that character’s follower entry: the same person cannot provide follower assistance to themselves, manage assets as an off-screen follower, and act as a PC simultaneously.

2. Set the handover before building the successor

  1. Agree on the replacement budget. Use the campaign’s current replacement-character creation procedure. Follower Cap and the predecessor’s spent XP are not a second XP allowance. If using the existing optional 4–8 XP inherited-training bonus, set the amount consistently for the campaign and grant it once on this successor’s creation; it does not accumulate through a chain of predecessors.
  2. Carry standing, not automatic obedience. Record inherited allies, enemies, and reputation. Identify which offices and relationships recognize the successor and which are contested. Resolve a contested claim through an appropriate scene; a failed trial complicates the claim rather than forbidding the player from playing their new character.
  3. Choose one burden. State who cares about it, what would discharge it, and what foreseeable event makes it urgent. The burden grants no automatic XP and imposes no blanket dice penalty. Existing debts and obligations remain on their own records; choosing one spotlight burden does not erase the others.
  4. Transfer custody explicitly. With the GM’s agreement and a credible handover, one existing Minor or Standard personal asset may carry over. Preserve its condition and upkeep; this transfers the same asset, not a duplicate or an XP refund. Major assets and disputed offices require recognition or securing control through play. Shared faction assets remain with their existing faction rather than becoming free personal purchases.
  5. Resolve personal commitments. A successor does not automatically inherit talents, rites, patron access, personal Boons, or another person’s magical bargain. Establish any new access under its normal rules. A debt changes debtor only when the relevant agreement permits it; otherwise record who still owes it and why the successor might choose to help.

Archive the predecessor’s sheet and mark transferred entries. Do not erase the history. A contact or inherited title is fictional access, not automatically a rated Asset or Follower. Use the acquisition rules when that mechanical benefit is desired.

3. Invoke the Legacy Bond

Once per player per session, across all Legacy Bonds: when your successor commits to a meaningful action upholding a recorded value of their predecessor, describe a specific memory and the risk or obligation you accept. Before resolving that action, gain 1 Boon and mark the invocation used. It can be spent using the normal Boon rules, including on that action where timing permits. The normal cap and scene-end trim apply; there is no overflow store.

The same action cannot also claim a separate Bond-driven Boon award for the same remembered relationship. Ordinary outcome awards still apply when earned. Repeating a safe gesture, invoking an additional predecessor, or switching characters does not refresh the session limit. Memories can always inform portrayal, but do not automatically reveal secrets, improve Effect, change DV, or guarantee a result.

When the successor rejects or transforms the inherited value, discuss the new wording at downtime. Keep any resulting debts and relationships in the fiction. Rewriting the value grants no extra invocation and is not a refund of prior consequences.

4. Build something that can outlast you (optional)

For a Legacy project, write a concrete public benefit, a steward, beneficiaries, necessary permissions or materials, an upkeep plan, and a completion condition. Choose a Growth [6] timer for a focused local institution or Growth [8] for a project with several substantial dependencies. A realm-wide undertaking should contain distinct projects with distinct benefits, not an arbitrarily huge timer.

Agree on these lengths before work begins. One meaningful project action advances one Growth timer by 2 on Clean Success or Success & SB, 1 on Partial, and 0 on Miss. Apply the core outcome, awards, costs, and Story Beats as usual. These progress amounts are the optional Legacy project default, not a change to all timers or crafting. If a specific subsystem supplies its own project procedure, use that procedure instead.

At most one action per project per campaign downtime can earn these default ticks. Extra PCs and followers can assist or resolve dependencies under their usual rules; they do not multiply the same action into several progress awards. A separately played milestone scene may also advance the project if its stake was agreed beforehand. Do not demand a roll for routine work with no meaningful uncertainty; an agreed completed milestone can receive its stated progress without manufacturing danger.

A filled timer delivers its written benefit once. Establish prerequisites before attempting the finishing action; do not invent a missing permission after success. If work creates an opportunity to acquire a rated asset, write that explicitly as the benefit and use normal acquisition costs. If the project is being conducted under an acquisition procedure already paid for, do not charge twice. Record its steward and ordinary upkeep when it opens. Growth never creates free recurring XP, Boons, or additional actions.

5. Give institutions vulnerabilities (optional)

Use a Crisis [6] timer for a named threat to the institution. Write observable warning signs, the event at completion, and concrete triggers: an unpaid upkeep deadline, loss of a supplier, or a rival’s successful move. It is not a second health bar and does not replace an asset’s existing condition rules.

At the campaign review, mark 1 tick at most for a declared scheduled trigger that occurred during that review period. No trigger means no scheduled tick. An on-screen consequence or a legal Story Beat spend can also advance it when justified by the normal rules and the stated stakes. Log the cause: do not count one event twice as both a scheduled trigger and an extra consequence unless two distinct effects were declared.

A successful action that removes the trigger prevents its future scheduled ticks. A meaningful crisis-reduction action removes 2 ticks on Clean Success or Success & SB, 1 on Partial, and 0 on Miss, to a minimum of zero; resolve other costs and consequences normally. These are Legacy defaults and apply only where the declared action can actually relieve that pressure. One such action per institution per campaign downtime earns these default reductions.

At six ticks, play the announced crisis. Do not silently destroy every inherited resource. Record the actual outcome, use normal rules for any affected asset or follower, and close the timer when the crisis is resolved. A new threat needs a new trigger and warning; do not refill the same timer merely because the institution survived.

6. Review, then move the story forward

At downtime: resolve declared projects and recovery, pay or adjudicate upkeep, check each scheduled pressure trigger once, and record changed custody, debts, and relationships. Show the record to the players. On a generation jump, agree on the interval and resolve a small number of consequential turning points; do not mechanically charge decades of session-by-session upkeep or grant decades of free project actions.

At campaign end, each player names one lasting mark supported by play and the people who maintain it. An epilogue is not a guaranteed permanent immunity from history. A later campaign can explore its fate without treating that possibility as a reason to deny the earlier characters their achieved ending.

Example: The Fallen Captain

Miranda has played Michael, captain of the Iron Tide mercenary company, for two years. Michael dies defending a village from a wyrm. The player wants to continue the story.

The Successor

Michael's second-in-command, a grizzled scout named Vesper, has been a follower (Cap 3) for many sessions. Vesper once disobeyed an order to save wounded civilians — a defining moment.

The Call

At Michael's funeral pyre, the company looks to Vesper. No one else steps forward.

The Trial

Vesper must negotiate a new contract with a wary noble who doubts the company's future without Michael. The player rolls, succeeds with cost — the noble agrees, but demands a hostage.

The Ascension

Vesper takes up Michael's banner. The player archives Michael's character sheet and creates Vesper as a new PC (starting XP based on campaign tier). Vesper inherits:

The campaign continues without missing a beat.

Legacy Planning Checklist

Before your character retires, dies, or steps aside, work with your GM to prepare your successor. Use this checklist to ensure a smooth transition.

Player's Legacy Planning Checklist

  1. Name a Successor — Choose a Follower (Cap 3+), family member, or loyal ally. Give them a name, a face, and a voice.
  2. Clarify the Relationship — What does your character mean to them? What do they owe each other?
  3. Identify One Unresolved Burden — What task, oath, or problem will the successor inherit? (e.g., “Find my stolen sword,” “Protect the village,” “Pay the guild debt.”)
  4. Pass Down an Asset (Optional) — If your character controls a Minor or Standard Asset, the GM may allow the successor to retain one such existing asset with suitable narrative justification (e.g., “The family safehouse,” “The guild seat passes to the heir”). Major or Tier III Assets usually require the successor to earn them through play.
  5. Settle Outstanding Obligations — Clear or transfer any standing debts to terrestrial patrons before stepping down. Unpaid debts may become part of the successor's burden.
  6. Hold a Ceremony (On-Screen) — A funeral, a passing of the torch, a swearing of oaths. This scene marks the transition and gives the new PC immediate presence.
  7. Create the New Character — Build the successor using standard character creation rules, adjusted to the campaign's current tier. If the campaign uses the optional 4–8 XP inherited-training bonus, apply its agreed amount once to this successor; it does not stack across predecessors.
  8. Keep a Legacy Note — Write one sentence that the old character leaves behind (a proverb, a scar, a rumor). The GM can use it as a future story hook.

Campaign End: The Final Legacy

When the campaign ends, the player may describe one lasting mark the faction leaves on the world. Examples:

The story ends — but the legacy remains.

A character dies. A faction endures. A story echoes forward.