I check the rule before spending GM points - not just the pool. Before you spend, check the trigger, timing, cost, target, and effect. Even 1 point needs a rule that permits its use; it isn’t permission to undo a completed success.
Here’s how I keep these resources separate:
- Daggerheart Fear: The pool caps at 12, and unused Fear carries between sessions. Some moves cost 1 Fear; named features use their listed costs. Failed rolls and rolls with Fear can also trigger free GM moves.
- Fate Core GM fate points: Each scene starts with 1 point per PC present for the shared NPC pool. Invokes and certain other effects cost points; ordinary NPC actions don’t. Some earned points carry into the next scene.
- Bite: I’d need the game and published rules before stating how it works.
My rule of thumb: <u>check what the rule allows</u>, then pay its cost. Having points and having permission are two different things.
GM Points Compared: Daggerheart Fear vs. Fate Core
1. Daggerheart - Fear
Gains and Pool Limits
The GM starts a campaign with 1 Fear per player character and carries unused Fear between sessions. The pool caps at 12 Fear; any excess is lost.
Gain 1 Fear whenever a PC rolls with Fear, meaning the Fear die is higher than the Hope die. This applies even when the action roll succeeds. A short rest grants 1d4 Fear. A long rest grants 1d4 Fear plus 1 Fear per PC and lets the GM advance a long-term countdown.
Legal Spend Timing
Spend Fear only when a rule allows it. Gaining Fear doesn't mean you can spend it immediately, unless the rules require that spend.
Costs and Effects
Spend 1 Fear to interrupt with a move, make an additional GM move, add another adversary spotlight, or add an adversary’s Experience to its roll. Adding Experience affects that roll only - it doesn't grant a separate action.
For adversary and environment Fear Features, follow the printed cost and requirements. Don't assume every activation costs 1 Fear.
No-Cost GM Actions
A GM move costs no Fear on a failed action roll or a roll with Fear. Setting difficulty and describing the world are also free unless a specific rule says otherwise.
When the GM takes the spotlight, one adversary spotlight is free. Additional adversary spotlights require Fear. Fear pays for effects defined by the rules, not arbitrary setbacks.
Fate Core handles GM points differently, with its own refresh and spend timing.
Using Fear in Daggerheart! | Get Your Sheet Together
2. Fate Core - GM Fate Points
Unlike Fear, Fate Core resets the GM’s point pool each scene.
Gains and Pool Limits
Each scene starts with 1 Fate Point per PC present. All NPCs share this pool; individual enemies don’t get their own points. Unused points normally disappear at the end of the scene. The GM’s compel supply stays separate from the NPC pool.
When the table accepts a player-driven compel against an NPC, add 1 Fate Point. If the scene ends, carry that point into the next scene. Points from concessions carry forward, too: gain 1 point per consequence the conceding NPC suffered, plus 1 more if the GM concedes for all NPCs to end the scene.
Legal Spend Timing
The GM spends points at the same step in resolution that a player would. This applies to invokes, NPC stunts with a Fate Point cost, and refusing a compel against an NPC. Every invoke must connect to a relevant aspect.
Compelling a PC’s aspect draws from the GM’s separate compel supply. The GM pays 1 point if the player accepts; the player pays 1 point to refuse. Each compel must target a specific aspect and offer a real choice.
Costs and Effects
A standard invoke costs 1 Fate Point for either +2 or a reroll, provided the aspect fits. Refusing a compel against an NPC also costs 1 point. NPC stunts follow their listed costs and effects.
No-Cost GM Actions
NPCs can attack, defend, move, create advantages, and concede without spending points. The GM also spends no points to roleplay NPCs, choose tactics, or handle ordinary reactions.
Legal Spends: Timing, Costs, and Effects
Each resource has rules for when you can spend it, what it costs, and what it changes.
| System | Authorized trigger | Timing window | Cost | Target | Result and limits |
|---|---|---|---|---|---|
| Daggerheart | Interrupt play and take the spotlight | During player actions or between turns, if the rules allow an interruption | 1 Fear | The current action sequence | Take the spotlight and make a legal GM move. |
| Daggerheart | Make an additional GM move | When the GM gets a move | 1 Fear | Scene, character, adversary, or environment | Make one additional GM move. |
| Daggerheart | Spotlight an additional adversary | During a battle’s spotlight structure | 1 Fear | One additional adversary | Let that adversary act within its rules. |
| Daggerheart | Activate an adversary’s Fear Feature | When the named feature is activated | The Fear amount listed by that feature | The feature’s listed targets | Apply only the listed effect. |
| Daggerheart | Activate an environment’s Fear Feature | When the named feature is activated | The Fear amount listed by that feature | The feature’s listed targets | Apply only the listed effect. |
| Daggerheart | Add an adversary’s relevant Experience to a roll | Before the applicable roll | 1 Fear | The adversary’s attack roll or a roll made against it | Add the relevant Experience modifier. |
| Fate Core | Invoke a relevant aspect | After rolling, before finalizing the result | 1 Fate point | The NPC’s roll, or another eligible roll | Gain +2 or reroll the dice; justify the aspect’s relevance. |
Fear Feature costs stack with other spends. Spending 1 Fear to interrupt, then activating a feature that costs 1 Fear, costs 2 Fear total.
These examples show what a legal spend changes - and what it does not.
Daggerheart: A rogue crosses a collapsing bridge on a successful roll that generates Fear. Before the next player acts, the GM spends 1 Fear to interrupt and reveals that an enemy cuts the bridge’s final support. The rogue’s success stands; the interruption adds a new complication instead of undoing the crossing.
Fate Core: An NPC with the aspect Knows Every Alley in the City rolls Stealth while escaping through back streets. After rolling but before finalizing the result, the GM spends 1 Fate point, explains the aspect’s relevance, and chooses +2 to the Stealth total or a reroll of all four Fate dice. The invoke changes the unresolved roll, not a completed outcome.
GM Actions That Require No Points
Routine GM adjudication costs no points. A spend is required only when a rule explicitly calls for one. Here’s how that works in play.
| System | No-cost action | Required trigger | Boundary |
|---|---|---|---|
| Daggerheart | Resolve an unavoidable consequence | The fiction has already established the danger. | Follow the established consequence. |
| Daggerheart | Respond to a golden opportunity | The fiction creates an opening that calls for a response. | Keep the response proportionate to the opening. |
| Fate Core | Apply a completed roll’s outcome | The action and defense have been resolved. | Do not revise the resolved outcome. |
Daggerheart’s triggers allow an appropriate move - not every possible escalation. In Fate Core, an NPC’s active opposition roll is part of resolving the action. It doesn’t use a separate action.
The examples below show where a triggered move ends and a paid effect begins.
Daggerheart rooftop chase: A character fails an escape roll while fleeing a pursuer. The GM can have the pursuer close the distance without spending Fear. If the result is a failure with Fear, the GM also gains Fear; gaining that point is separate from making the triggered move. Any later spend still needs a permitted Fear spend.
Fate Core rooftop chase: The GM can describe the pursuer’s movement, establish rooftop opposition, and resolve the NPC’s roll without spending a Fate point. A point is needed only if the GM uses a defined point mechanic, such as invoking a relevant NPC or scene aspect - not simply because the pursuer acts.
Conclusion: Check the Rule Before Spending
The rule, not the resource, determines what the GM can do. Fear and fate points pay for specific rules effects - not arbitrary setbacks.
Bite remains unverified here. Don’t apply Fear or Fate rules to it until its published text is confirmed.
Before spending, check the rule, trigger, cost, timing, target, and effect. Spending a point does not rewrite an already-resolved result. If the rule doesn’t allow the spend, the point stays unspent.
Keep a system-specific reference table covering point gain, pool limits, and spend rule references. Mark Bite unverified until its published text is confirmed.
FAQs
What should I do if I spend GM points incorrectly?
Own the mistake with your players to maintain trust and keep the game moving. Use it as a chance to learn the system’s rules more thoroughly.
If the error had a major effect on an encounter, consider changing the outcome after the fact, giving players extra resources to make up for it, or turning the unintended result into a new challenge. Explain how you’ll apply the rule in future sessions so everyone knows what to expect and rulings stay consistent.
How can I explain a disputed GM spend to players?
Explain what the cost does mechanically and which rule, if any, requires it. Make clear whether spending the resource was mandatory under the rules or an optional change to the encounter.
If no specific rule applies, explain the story purpose behind the cost - such as building tension or strengthening a character’s motivation. Use the rules as a guide, listen to player concerns, and keep the challenge fair and consistent.
How do I verify which Bite rules apply?
Check your game system’s core rulebook, focusing on resource management, encounter design, or GM tools. Find out what Bite does, how you gain and spend it, and whether any timing rules apply.
If you’re tracking encounter progress, check whether success clocks, point trackers, or threshold markers control when you can spend Bite or when an effect triggers. The rules differ from system to system.
