On this page

Chapter 2: Running the Game — Core Procedures

Fate's Edge GM Guide — Chapter 2

Running Fate's Edge — Core Procedures in Brief

Your Job: Frame pressure, track consequences, let the fiction move forward.

Default Settings — DV = 3 · Position = Controlled · One short Timer

The Core Loop (every meaningful action)

Player declares intent & approach (Attribute + Skill)
You state Position & set relevant Timers
Player rolls d10s; count Successes (6–9 = 1, a 10 = 2) & Story Beats (1s)
Compare to DV → use the Outcome Matrix
Apply consequences & update the fiction

Outcome Matrix (what you do)

Clean Success (S ≥ DV, SB=0) → intent achieved, no complication
Success with SB (S ≥ DV, SB>0) → intent achieved, spend SB for a twist
Partial (0 < S < DV) → progress made, player gains 1 Boon
Miss (S = 0) → no progress, player gains 2 Boons, spend SB to escalate

Story Beats (SB) — spend them to create drama

1 SB: Minor — noise, tick a timer, small setback
2 SB: Moderate — alarm raised, lose advantage, worsen Position
3+ SB: Major — reinforcements, scene shift, break an asset

Golden Rule
When in doubt, make a ruling that keeps the story moving.
Set DV=3, Position=Controlled, ask for the roll, and resolve with the Outcome Matrix.

Position (Dominant/Controlled/Desperate) = How risky is this action? — determines severity of failure and re-rolls.
Effect (Limited/Standard/Great) = How much do you achieve on a success? — determines scope, scale, or quality.

Example: Disarming a trap — Limited Effect lets one person cross, Standard lets two, Great lets all four.

First-Time GM? Start Here

You do not need to memorize this chapter before your first session. Here is what you actually need:

The Core Loop (above) — know the five steps.
DV 3, Position Controlled — your default settings.
The Outcome Matrix — Clean/SB/Partial/Miss.
Spend SB early — one strong complication is better than three weak ones.

Everything else in this chapter is reference material. You can run a complete session with just these four things. The examples at the end of the chapter will show you how.

When you forget a rule — and you will — fall back on the Golden Rule. The story comes first.

Selling the Action — When Players Give You Gold

"Don't just tell me you swing your sword. Show me the dust in your eyes, the tremble in your arm, the desperate prayer you whisper to the Traveler."
"And don't just paint a pretty picture — show me what your character risks, fears, or loves in this moment."

When a player sells the action — not by piling on adjectives, but by revealing what their character cares about, what they stand to lose, or why this moment matters — you have permission to give them a mechanical edge. This is a reward for roleplay investment, not vocabulary.

How to Rule It

Basic description: "I attack the goblin." — No bonus.
Tactical description: The player uses the environment, positioning, or a clever tactic. Example: "I feint high, then drive my shoulder into the goblin's shield, shoving it aside to open its flank." → Improve Position by one step (e.g., Controlled → Dominant) for this roll.
Character-driven description: The player states a stake, invokes a bond, reveals a fear, or makes a hard choice visible. One heartfelt sentence counts more than a paragraph of adjectives. Example: "I think of my mother, who died because I wasn't brave enough. I won't let that happen again. I plant my feet and dare the goblin to come through me." → Improve Position by one step and bank 1 Story Beat (or upgrade Effect by one step, your choice).

What Counts (and What Doesn't)

Counts:

Stating a clear stake ("If I fail, my sister doesn't eat.")
Invoking a bond mid-action ("I owe Michael my life. I'm not letting him face this alone.")
Revealing a fear or hope tied to the roll ("I'm terrified of fire, but I grab the beam — the children are behind me.")
Making a hard choice visible ("I could run, but I don't. Running is what got me exiled.")

Does not count:

Piling on adjectives ("gleaming," "mighty," "ancient") without stakes.
Passive sensory laundry lists ("the cold wind, the wet stones, the dim light").
Repeating the same florid description for every roll.

Guidelines for Fair Play

No penalty for plain speech. Never punish a player who is tired, shy, or simply prefers quick resolution. The bonus is a gift, not a tax.
Be consistent. Reward genuine investment, not vocabulary. A quiet player who delivers one honest sentence deserves the bonus as much as an eloquent storyteller.
Let the fiction guide the bonus. A desperate, reckless action described with real stakes might upgrade Effect but worsen Position — the mechanics should mirror the fiction.
Invite quiet players. Ask leading questions: "What's at stake for your character right now?" or "What are you afraid will happen if you fail?" Gentle prompts help shy players find their moment.
Group "selling." If the whole table contributes to describing a group action (a coordinated ambush, a joint ritual), grant the bonus to the primary roller or give each participant a small benefit (e.g., a one-time +1 die).

Example

Basic: "I sneak past the sentry." (No bonus, roll as normal.)

Tactical: "I wait for the wind to rattle the shutters, then pad across the wet cobblestones — heel-toe, heel-toe — keeping the stack of barrels between me and the sentry's gaze." The GM nods: "Great. Because you're using the wind and the barrels, roll at Dominant Position."

Character-driven: "My little brother is in that camp. I've hidden from every fight since we left home — but not this time. I creep forward, not quiet anymore, because he needs to know someone came for him." The GM: "That's the heart of it. Roll at Dominant Position, and I'll bank a Story Beat to make his reaction matter."

The dice still decide success or failure. But a well-told action makes the story richer — and earns the player an edge when the dice fall.

How to Think in Fate's Edge

Running Fate's Edge is less about adjudicating difficulty and more about managing momentum. Your primary job is not to block success, protect outcomes, or simulate realism—it is to frame pressure, track consequences, and let the fiction move forward.

If you catch yourself asking "How hard should this be?" you are already one step behind. Instead ask:

What is at stake right now?
What happens if this goes wrong?
What pressure is already in play?

The rules exist to answer those questions—not to replace them.

GM Mindset: The Pressure Engine

Think of each scene as a pressure engine:

Dice	create outcomes
Timers	track fallout
Story Beats	fuel escalation
Boons	reward risk

Your job is to keep that engine turning—not to decide where it ends. Let the procedures do the work. Your attention belongs on the fiction.

The Core Loop

The full procedure is The Core Resolution Cycle, below, and the panel at the top of this chapter is the version you keep on the screen. The thing worth saying here is what the loop is for:

Do not go looking for the right roll. If the action matters, the procedure applies — the same eight steps, whether it is a swordfight, a forged charter, or an apology. If the action does not matter, do not roll at all; say yes and move on.

Your Defaults

When in doubt, trust the fiction. The system will follow. Fall back on these defaults:

DV: 3
Position: Controlled
Consequence: Fatigue, time pressure, or exposure
Timers: One short timer tied to the scene

Escalate only when the fiction demands it.

What You Are Not Doing

You are not:

calling for rolls to gate progress
inflating difficulty to "challenge" the players
protecting NPC plans from disruption
hiding information behind unnecessary checks

If the players act decisively, the world must respond decisively.

What You Are Doing

You are:

stating Position clearly and confidently
letting partials move the story forward
spending Story Beats to make failure interesting
allowing success to create new problems

The game works best when nothing stalls.

Narrative Time: Rounds, Turns, Scenes, and Arcs

Fate's Edge measures time by narrative weight, not real seconds. Use these shared definitions to keep the table aligned.

Round: Spotlight turns for all participants in a conflict (including Actions, Moves, and Reactions). A round ends when everyone present has had an opportunity to act.
Turn: Spotlight for an individual player: one Action and one Move (see the Core Resolution Cycle in the SRD). Turns are the basic unit of player agency.
Significant Time: Three or more rounds of structured conflict, or any period outside of combat where extended effort is required (e.g., a ritual, a chase, or several hours of travel). Use Significant Time to trigger long-term timers and downtime actions.
Scene: A unit of narrative play covering a specific conflict, location, or situation. Equivalent to a D&D "encounter" (but avoid that comparison; a scene may be social, exploratory, or a montage). A scene ends when its central question is resolved.
Session: One play session (typically 3–6 hours). A session may contain one major scene or several smaller scenes, and ends with Experience Point awards and timer updates.
Arc: A complete story arc (3–6 sessions) that advances character goals, resolves a major front, and moves a campaign timer. At the end of an arc, the GM may call a Crown Spread or trigger a finale.

Significant Time in Play

When the fiction calls for Significant Time (e.g., performing a ritual, climbing a cliff, or resting for an hour), the GM may:

Advance a relevant timer by 1 segment.
Allow the party to clear 1–2 Fatigue (if conditions allow).
Call for a single roll to represent the entire extended effort (DV set by the scope of the task).

The Core Resolution Cycle

When a player rolls, they engage the world through risk, consequence, and discovery.

Declare Action & Approach: Player states intent, Attribute + Skill.
Set Difficulty Value (DV): Based on narrative stakes.
Establish Position: Dominant, Controlled, or Desperate.
Roll Pool of d10s.
Count Successes (6–9 = 1, a 10 = 2) and Story Beats (1s).
Check Against DV using the Outcome Matrix.
Apply Outcome: Clean Success, Success with SB, Partial, or Miss.
Spend SB for complications and twists.

Clean Success. The action succeeds as intended. No Story Beats generated unless specified. Fiction advances cleanly.

Success with SB. Action succeeds but generates Story Beats. Success stands; cost is GM spending those SB, ideally applied to the inciting action or its immediate consequences.

Miss. Action fails and generates Story Beats. GM uses those SB to introduce complications, advance opposition, or shift the situation against the character.

Partial Success (GM Adjudication). A Partial indicates progress but not full resolution. How that manifests is determined by the GM, based on context, scale, and narrative stakes.

Partial results may:

Improve the character's Position on a follow-up attempt
Reduce the effective DV of the next roll
Achieve the goal at reduced scale or limited duration
Succeed fully but generate a Story Beat as cost or complication
Reveal information or create a new opportunity instead of immediate resolution

Guiding Principle. Partials represent meaningful progress. Convert progress into advantage, resolution, or complication, depending on what best serves the fiction.

Position Effects

Position	Mechanical Effect
Dominant	May re-roll one failure (die < 6).
Controlled	Default state; no re-rolls.
Desperate	Must re-roll one success (a die of 6–9), keeping the second result. A 10 is never re-rolled.

Difficulty Ladder — Beginner Focus

DV	When to Use
2	Routine: clear path, no pressure, almost guaranteed.
3	Default: mild challenge, some risk — use most often.
4	Hard: serious opposition, bad angle, or strong resistance.
5+	Extreme: major boss encounters or dramatic gambles.

Position & Difficulty Value

Position and DV are your primary dials for setting stakes and difficulty. They work together but answer different questions:

DV (Difficulty Value) — How hard is the task? (2 = routine, 3 = pressured, 4 = hard, 5+ = extreme)
Position — How risky is the attempt? (Dominant = safe, Controlled = balanced, Desperate = dangerous)

DV 3 as Default

Unless the fiction clearly indicates otherwise, start at DV 3. This gives a roughly 50–60% success rate for an average pool (4–6 dice) and leaves room for partials and misses. Do not inflate DV to "challenge" players — use Position, Timers, and SB spends instead.

When to Worsen Position

Worsen Position when the fiction puts the character at a disadvantage:

Exposed or surrounded → Desperate
Rushed or distracted → Controlled or Desperate
Surprised or ambushed → Desperate

Never worsen Position just to make a roll "harder." Position is about narrative danger, not arithmetic.

The Golden Rule

Golden Rule

When in doubt, make a ruling that keeps the story moving.

If you cannot remember a rule, set DV = 3, Position = Controlled, and ask the player to roll. Resolve the outcome with the Outcome Matrix. You can look up the rule after the session.

Example: Using SB to Escalate a Scene

Spending SB for Drama (The Bridge)

The party is negotiating a narrow mountain bridge. A rival mercenary captain demands a bribe.

Player rolls a Partial. The GM gains 2 SB.
GM spends 1 SB: "The captain leans on his sword — you notice his hand creeping toward the hilt. Tensions rise." (Tick a new timer: Tempers Flare [4].)
GM spends the second SB: "A loose stone falls from the bridge and splashes into the river far below. The captain's archers nock arrows. Position worsens to Desperate."

The player still succeeded in negotiating a lower toll, but the GM used SB to introduce escalating pressure and a visible timer. The scene now crackles with danger.

Outcome Matrix

Roll Result	What Happens
Successes ≥ DV, SB = 0	Clean Success — intent achieved, no complication.
Successes ≥ DV, SB > 0	Success with SB — intent achieved; GM spends SB for complication.
0 < Successes < DV	Partial — progress with complication; player gains 1 Boon.
Successes = 0	Miss — no progress; GM escalates with SB; player gains 2 Boons.

Remind players that they can spend 1 Boon before a roll to increase Effect by one step.

Armor Conversion & Fatigue Clearing

Your job as GM is simple: When a player character takes a hit, you state the incoming Harm value. The player applies their own armor conversion using the Armor Conversion Table on their sheet. This keeps your hands free for narration and pacing.

You say: "You're hit. Harm 3."
The player: Consults their armor type on the table, applies the conversion, and describes the result.
You: Narrate the fiction based on what they mark.

The table itself is player-facing (see Appendix A.5). Your only responsibility is to announce the Harm value and trust the player to handle the math.

GM Tip: The Roller-Coaster Effect

This creates dramatic narrative swings: When Harm is applied and armor conversion reduces it, the shock of injury may clear existing Fatigue. This represents a "second wind" — a character near collapse who takes a wound and suddenly finds clarity through adrenaline.

Let the player describe what this looks like. A fighter who was gasping for breath (Fatigue 3) takes a glancing blow (Harm 1, converted to Fatigue 1, triggering overflow) and suddenly stands tall, bleeding but focused. The mechanics and the fiction reinforce each other.

Your job: Ask the player: "What does that look like?" Let them own the moment.

Learning Through Examples

This section walks the same situation through multiple passes, adding one rule at a time. Use it as a mental template when you improvise.

Example 1 — No SB, No Boons

Lyra tries to sneak past a guardian in a narrow hallway. (Body + Stealth = 5d10).
GM: normal risk, DV 3, Controlled Position.
Roll: 3, 5, 6, 7, 9 → 3 successes (6,7,9).
DV 3 with 3 successes = Success.
GM: "You slip past the guardian quietly. You're in position behind it if you want to act."

Example 2 — Adding Story Beats

Same situation. Lyra rolls 5d10: 1, 4, 6, 6, 8.
Successes: 3 (6,6,8). One 1 → 1 SB for GM.
DV 3 with 3 successes = Success with 1 SB.
GM spend (1 SB = Minor): "You get past the guardian, but your cloak snags and tears. The sound echoes — the next room has a -1 Position penalty for stealth checks."

Example 3 — Adding Boons

Later, Lyra scales a loose stone wall (Athletics + Body = 4d10). DV 3.
Roll: 2,3,4,5 → 0 successes = Miss.
GM awards 2 Boons. "You slip and land hard, taking 1 Harm. Mark 2 Boons — you can use them later to turn the tide."
Next attempt, Lyra spends 1 Boon to re-roll a die, turning failure into success.

Example 4 — SB + Boons + Position

The party flees as the tower collapses. A crumbling staircase blocks the exit.
GM: "Desperate. DV 4 to get everyone across safely."
Lyra leads, rolling 6d10 (Body + Athletics + help): 1,2,6,7,7,9.
4 successes vs DV 4 = Success. 1 rolled 1 = 1 SB to GM. Desperate Position.
GM: "You all make it across, but the last step collapses behind you. I spend 1 SB: your exit path is gone. You'll need a new way out."
Lesson: Even on a success, SB let you bend the fiction toward drama without erasing the player's win.

Core Loop Flowchart

The following summarizes the chapter's core-loop flowchart as a linear procedure.

Frame the scene (what's at stake?)
↓
Player declares intent (Attribute + Skill)
↓
GM sets Position (Dominant/Controlled/Desperate)
↓
GM sets DV (default 3)
↓
Player rolls dice pool — count successes (6–9 = 1, a 10 = 2) and 1s (SB)
↓
Compare successes to DV:
- S ≥ DV, SB = 0 → Clean Success (no SB)
- S ≥ DV, SB > 0 → Success with SB
- 0 < S < DV → Partial (gain 1 Boon)
- S = 0 → Miss (gain 2 Boons)
↓
Clean Success passes directly to next player. Success with SB, Partial, and Miss route through: GM spends SB (complications, timers)
↓
Pass spotlight to next player

Chapter Summary: Core Procedures in One Page

Your job: Frame pressure, track consequences, keep the fiction moving.
Default settings: DV 3, Controlled Position, one short timer.
Core loop: Declare → Set Position/DV → Roll → Outcome → Consequences.
Outcomes: Clean Success, Success with SB, Partial (gain 1 Boon), Miss (gain 2 Boons).
Story Beats: Spend 1 (minor), 2 (moderate), 3+ (major).
Golden Rule: When in doubt, rule in favor of the story. Look it up later.

Risk

Why risk is the engine of this game — and why safety is boring — is Chapter 1. What follows is the part you use at the table: what a Story Beat actually is, and when to spend one.

What Are Story Beats, Really?

New GMs often ask: "What are Story Beats really? Are they just complications? Are they a resource I should hoard for the big moment?"

The answer is simpler and more profound than you might expect. Story Beats are the game's permission to make things interesting.

Every time a player rolls a 1, they are inviting the world to push back. The dice have spoken: something has gone slightly wrong, or slightly awry, or slightly unexpected. The SB is your license to honor that invitation. It is not a punishment. It is not a penalty. It is the universe saying, "Yes, and…"

The GM's Secret Weapon

Story Beats are your primary pacing tool.

A scene without SB is a scene where the players are in control. A scene with SB is a scene where the world pushes back. The two should alternate. If you spend SB early and often, you create pressure. If you hoard them, the scene feels flat.

"Do not save your Story Beats for the climax. The climax is made of the Story Beats you spent along the way." — The Gray Wanderer

What SB Are Not

SB are not:

Punishments. They are not the GM's way of saying "you failed." They are the world's way of saying "something interesting happened."
A finite resource. You are not limited by SB. If the fiction demands a complication, introduce it—even with 0 SB. SB simply tell you: Players rolled 1s here; they want the world to push back.
One-time effects. A single SB can create a complication that ripples through the entire session. A guard who is alerted now will be a problem later.

What SB Are

SB are:

Narrative fuel. They give you permission to escalate, to twist, to surprise.
Player-generated pressure. The players rolled 1s. They are telling you, "Make this interesting."
Tension creators. Each SB spent is a moment where the players' plans go slightly wrong—or become more complicated.
Story seeds. A minor complication now can grow into a major plot thread later.

A Practical Example

Imagine the party is sneaking past a guard. The rogue rolls Stealth and gets 3 successes against DV 3—a Clean Success. But one of the dice shows a 1. The GM gains 1 SB.

What does the SB mean?

It does not mean the rogue fails. It means the world notices. The guard does not see the rogue, but a loose stone skitters across the floor. The guard looks up, peers into the darkness, and mutters, "Probably just a rat…" before returning to his post. The guard is now slightly suspicious. Later, when the party is deeper in the compound, that guard will be more alert. A later failure might trigger a full alarm.

That is a Story Beat. A small consequence that grows over time. A seed planted for future drama.

The SB Spend Menu

Use this menu to guide your spending. The listed costs are guidelines, not rules. A 1 SB complication in one scene might be a 2 SB complication in another.

SB Cost	Effect
1 SB	Minor pressure: Noise, distraction, tick a 4–6 segment 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, major twist shifts the scene, authority arrives, environment changes dramatically.

Pro tip: One strong beat (e.g., 3 SB for reinforcements) creates more drama than three weak beats (1+1+1 SB for noise). Be generous—unused SB is wasted momentum. One strong beat creates a memory. Three weak beats create a blur. The players will remember the reinforcements. They will not remember the three times a guard looked up.

Spend your SB. Spend them early. Spend them often. The big moment is made of the small moments you already spent. However, remember to have big moments.

The SB Cycle

The SB economy creates a virtuous cycle:

Players roll. They succeed or fail, but the dice show 1s.
GM gains SB. The world is given permission to push back.
GM spends SB. A complication is introduced.
Players react. They adapt, overcome, or fail again.
The cycle repeats. Each roll generates new SB, new complications, new drama.

The cycle never stops because the dice never stop rolling. A Miss generates 2 Boons and the GM spends SB. A Partial generates 1 Boon. Even a Clean Success with a 1 generates SB. The story always moves forward.

"The SB economy is the engine of drama. It turns every roll into a question: What happens next?" — The Gray Wanderer

On Difficulty Values and Challenge

A player with 8 dice can handle DV 3 easily. That is not a problem. That is the system working as intended.

Do Not Inflate DVs Arbitrarily

The temptation is understandable: a player is rolling many dice, so you want to make things "harder." So you set DV 4 where DV 3 would do. Then DV 5 where DV 4 would do.

Do not do this.

Here is why:

Low DVs are not a failure of challenge. A player who invested in a high dice pool earned the right to succeed routinely at baseline tasks. DV 3 is the default. That is intentional.
Success with no Story Beats is still success. A Clean Success (S ≥ DV, SB = 0) is a valid outcome. The player succeeded cleanly. Their competence was rewarded.
Clean Successes starve the Boon economy. If a player rolls 8 dice against DV 3 and succeeds cleanly, they earned no Boons. That is not a bug—it is the trade-off for being highly competent. They traded dramatic reversals for reliability.
Arbitrary DV inflation breaks the math. If you set DV 4 for every routine lock, you are effectively punishing the player for investing in their skills. The game's probabilities assume DV 3 is the baseline.

When to Raise DV

Raise the Difficulty Value when the fiction demands it:

A mundane lock is DV 3.
A masterwork lock, crafted by a guild artisan, is DV 4.
A magically warded safe, sealed by a Runekeeper, is DV 5.
The five wards on the vault door are not a single DV check—they are a Timer.

The DV tells the player how hard this specific lock is. The fiction tells them why.

The Timer: A Better Tool Than Inflated DV

Consider the vault door with five wards. A single roll to crack all five is a high DV (5+), but it is also a boring roll. Instead:

Establish the goal: "The vault has five wards. Each one must be broken in sequence."
Set a visible timer: Vault Wards [6].
Each successful Craft or Arcana roll (DV 3–4) clears one segment of the timer.
Each failure ticks a Threat Timer: Guard Patrol [4] or Alarm Progress [4].

Now the player's 8 dice are still rolling against a reasonable DV (3–4), but the challenge is in the accumulation of successes, not the arbitrary height of a single target. The player feels competent. The tension is real. The story moves forward.

Players Should Seek Harder Challenges

As characters grow, players should want to seek out greater challenges—not because the GM has inflated DVs, but because the world presents them:

A Tier I rogue picks locks for a living. DV 3 is her bread and butter.
A Tier III rogue cracks vaults for a living. She does not pick the same locks—she picks better locks. The locks are DV 4 because they are better locks, not because the GM decided to make things harder.
A Tier V rogue does not pick locks at all. She negotiates with the door's spirit, or walks through the wall using a Rite, or has already bribed the locksmith. The challenge has transformed.

The GM's role is not to make old challenges harder. It is to present new challenges that match the characters' growth.

The Golden Rule of DV

Set DV based on the fiction, not the player's dice pool.

A lock is DV 3 because it is a lock. A ward is DV 4 because it is a ward. A vault is a Timer because it is a vault.

If the player invested in a large dice pool, let them enjoy it. They earned it. Their reward is reliability—the ability to succeed at baseline tasks without drama.

If you want drama, use:

Position: Make it Desperate.
Timers: Add a clock.
Story Beats: Spend SB to complicate success.
Fiction: Give them harder locks to pick, not harder rolls to make.

A Practical Example

The party's rogue has Wits 4 and Craft 3. She is rolling 7 dice to pick a lock.

Wrong: GM: "The lock is tricky. DV 4."

Right: GM: "The lock is a standard guild lock. DV 3. You pick it easily—Clean Success. No Boons. That's the benefit of being a master."

Later: "The vault door has five wards. Each one is a DV 3 check, but you have to clear all five before the guard patrol completes its circuit. I'm starting a Guard Patrol [6] timer."

The player rolls 7 dice against DV 3, succeeds repeatedly, and clears the timer. She feels competent. The challenge was in the time pressure, not the arbitrary difficulty of a single roll.

Final Thought

Low DVs are not easy mode. They are the baseline. The player's high dice pool is not a problem to be solved—it is a feature to be celebrated.

Let the player enjoy their competence. Then give them new problems that demand a different kind of skill.

"A master thief does not pick harder locks. She picks different locks—locks that guard secrets, locks that speak, locks that were never meant to be opened. The game is not about making the roll harder. It is about making the choice matter." — The Gray Wanderer

Can I Roll Fewer Dice? No!

A question that comes up often, especially from players who have experience with systems where rolling poorly is punished, is:

"I'm rolling 8 dice. That's a lot of chances to roll 1s. Can I choose to roll fewer dice to avoid generating Story Beats?"

No. Absolutely not. Here is why.

In some games, rolling a 1 on a die is a failure state—it means something bad happens. Players learn to fear those faces. They try to minimize their dice pools to avoid bad outcomes. Fate's Edge is not that game.

In Fate's Edge, a 1 is not a failure. It is a Story Beat (SB)—a resource that fuels the narrative. When you roll a 1, you are not being punished. You are handing the GM a spark to light a fire that makes the story burn brighter.

The Golden Rule of Dice Pools

Never reduce a player's dice pool.

The dice pool is the player's primary expression of their character's competence. A character with Body 4 and Melee 4 has invested significant XP—they have earned those 8 dice.

If you want to make a challenge more difficult, use:

Position: Make it Desperate. The player re-rolls successes.
DV: Raise the Difficulty Value when the fiction demands it.
Timers: Add a clock. The player must succeed before it fills.
Story Beats: Spend SB to introduce complications.

Do not take away their dice. They earned them.

A player who asks to roll fewer dice is asking for a safe outcome. They want to avoid complications. But Fate's Edge is not a game about safety—it is a game about risk, drama, and the joy of rolling a handful of dice and seeing what happens.

"The dice are not a resource to be rationed. They are a declaration of competence. Let the players roll their full pool. Then use Position, DV, and SB to shape the outcome. That is the game." — The Gray Wanderer