Skip to content

Rules Reference: Resources ​

Resource rules give an item (or the character) a pool to spend: charges, dice, or combat-only mana. Pools can be consumed by item activations and refilled on rests or other events.

Shared fields

Every rule also has a Label, Identifier, Condition, Priority, a Disabled toggle, and a Suppress activation card setting. Those are explained once in Rules Builder Basics.

Action Adjustment ​

Grant or remove raw actions when this item is used: immediately or at the recipient's next turn. Can also borrow: gain actions now and start the next turn with that many fewer. Applies to character combatants only.

FieldWhat it doesOptionsDefault
ActionsHow many actions to grant. A flat number or formula (e.g. @level). Negative values remove actions.Number or formula1
Timingnow: adjust the current action pool immediately (may exceed the usual maximum). nextTurn: apply when the recipient's actions next refill.now, nextTurnnow
Targetself: the actor using the item. targeted: the currently targeted tokens. allAllies: every allied hero in the combat.self, targeted, allAlliesself
Borrow from next turnAlso start the next turn with that many fewer actions, applied together with the immediate gain as a single adjustment. (Only shown when relevant.)On/off toggleOff

Action Cost ​

Change how many actions it costs to activate matching items or use heroic reactions. Adjust adds to the base cost (use a negative value to reduce it); Set replaces it. The final cost never drops below 0. Cost only: a free reaction is still limited to once per round.

FieldWhat it doesOptionsDefault
Applies toitem: price matching item activations. heroicReaction: price the selected heroic reactions instead.item, heroicReactionitem
How to applyAdjust: add the value to the base action cost (negative values reduce it). Set: replace the action cost with the value.delta, setdelta
ValueA flat number or formula (e.g. @level). Combined per the mode above.Number or formula1
Item typesOnly activations of these item types are affected. Leave empty to affect every item type. (Only shown when relevant.)ListNone
Item identifierOnly affect the item whose identifier matches this. Leave blank to affect all matching items. (Only shown when relevant.)TextNone
Heroic reactionsOnly these heroic reactions are affected. Leave empty to affect every heroic reaction. (Only shown when relevant.)ListNone

Charge Consumer ​

Spend charges from an item or actor pool when this rule’s owner is activated.

FieldWhat it doesOptionsDefault
poolIdentifierCharge pool pickerCharge pool pickerNone
poolScopeTextitem, actoritem
Cost modeFixed spends the cost every activation. Variable asks the player how much to spend, from the cost up to the maximum, and the item’s effect formulas read the chosen amount as @spent.Fixed, Variablefixed
CostCharges spent per activation. In variable mode this is the smallest amount the player may choose.Number or formula1
Maximum costVariable mode only. Ceiling formula for the player’s choice. Leave blank to allow the pool’s remaining charges. (Only shown when relevant.)Number or formulaNone

Example: Wand of Scorching Rays. Spend one of the wand's charges every time it is used.

  • Pool → wand-charges
  • Pool scope → item
  • Cost mode → fixed
  • Cost → 1

The consumer goes on the item that spends the charges. It does not have to be the item that holds the pool: point Pool at any Charge Pool rule on the character. If too few charges are left, the item cannot be used. The chat card reports what the use cost.

Example: a pool you spend any amount of. Set Cost mode to variable and the item asks the player how many charges to spend. Cost is the smallest amount they can pick, Maximum cost the largest. Leave Maximum cost blank to let them spend whatever the pool has.

The item's own damage and healing formulas read that amount as @spent, so a healing effect of @spent heals what was spent. Lay on Hands works this way: a pool of 5 * @level that refills on a safe rest, and a variable consumer that heals what it spends.

An item with a variable consumer always opens its roll window, even when it is set to skip it.

An item can have a fixed cost and a variable one on the same pool. The fixed cost comes out first and the player picks from what is left, so a pool of 10 with a fixed cost of 3 offers up to 7. If the pool cannot cover both, the item cannot be used.

A variable consumer will not work in these cases. The item cannot be used, and the message names the pool.

  • Two variable consumers on one pool. The item asks once per pool, so the second has no answer of its own. Give it another pool, or make it a fixed cost.
  • Maximum cost below Cost. Nothing is left to pick.
  • A hidden pool. It has no control on the sheet, so there is nowhere to enter an amount.
  • A variable consumer on a spell. Casting opens the upcast window, which asks for a tier. Put it on a feature or an item instead.

Charge Pool ​

Define a refillable pool of charges (per item or actor) with one or more recovery triggers.

FieldWhat it doesOptionsDefault
ScopeWhere the pool lives. "Item" pools live on this item; "Actor" pools live on the actor and can be shared by features that reference the same identifier.item, actoritem
Max chargesCapacity formula. Flat (3), formula (@key), or actor data (@strength).Number or formula1
Die sizeOptional. Set when charges are spent by rolling a die (e.g. Combat Dice). Leave blank for plain counters.d4, d6, d8, d10, d12, d20None
InitialWhether the pool starts full or empty when first granted.max, zeromax
Hide from sheetTrack and enforce the pool without showing it. Use this for a pool that only rate-limits or gates the feature, so it does not read as a second budget next to the pool the player actually spends.On/off toggleOff
Show as a resourceAlso show the pool in the sheet header, alongside mana and the other standing resources. Use this for a pool the player spends and plans around. A pool hidden from the sheet is never shown here.On/off toggleOff
Recoveries → TriggerEvent that drives this recovery (rest type, encounter event, hit, etc.).safeRest, fieldRest, onHit, onCriticalHit, encounterStart, encounterEnd, onWound, onTurnStart, onTurnEnd, onKill, onBloodied, onInitiativeRolledsafeRest
Recoveries → ModeHow the value applies: "add" (gain N), "set" (set to N), or "refresh" (fill to max).add, set, refreshadd
Recoveries → ValueAmount used by the mode. Flat or formula. Ignored when mode is "refresh".Number or formula1

Example: Wand of Scorching Rays. A wand with 3 charges that refills on a safe rest.

  • Label → Wand Charges
  • Scope → item
  • Max charges → 3
  • Initial → max
  • Recoveries → one entry: Trigger → safeRest, Mode → refresh

Hide from sheet covers the other kind of pool: one that exists to gate a feature rather than to be managed. A feature limited to once per round and a few times per rest needs two pools, but only the second is a budget the player spends down. Hiding the round limiter keeps it enforced (it is still tracked, spent, refilled, and it still blocks the feature when empty) while leaving a single charge badge on the card, so the two limits are not read as one larger allowance. Chat cards still report the hidden pool when a use spends it.

Show as a resource promotes the pool to the sheet header, next to mana, as well as its badge on the granting item. Use it for a pool the player spends and plans around, like the Shadowmancer's Pilfered Power, and leave it off for one they only glance at when using the feature it belongs to. Hidden wins: a pool hidden from the sheet never reaches the header.

The Label names the pool wherever it is shown. A pool by itself never spends charges automatically; pair it with a Charge Consumer rule (or a Pool effect on the item's activation) to spend charges when the wand is used. Max charges takes formulas too: @key + 1 scales with the character's key stat.

Combat Mana ​

Grant a mana resource on a combat trigger and clear it on a configurable event.

FieldWhat it doesOptionsDefault
formulaNumber or formulaNumber or formula0
resourceTextTextmana
triggerTextTextinitiativeRoll
clearOnTextTextcombatEnd

Dice Consumer ​

Spend or auto-apply dice from an item or actor dice pool. "Manual" mode prompts the player at activation; "Auto-bonus" adds every rolled die face to qualifying attacks without consuming the pool.

FieldWhat it doesOptionsDefault
poolIdentifierDice pool pickerDice pool pickerNone
poolScopeTextitem, actoritem
modeTextmanual, autoBonusmanual
costNumber or formulaNumber or formula1
Attack deliveryRestrict this consumer to melee or ranged attacks. Applies to both an auto-bonus pool and a card offer. Leave empty (or pick "any") for no restriction. Beware: an activation with no attack type set counts as neither melee nor ranged, so most spells and utility features are excluded by any restriction here, with nothing shown to explain why.melee, ranged, anyNone
effectFormulaNumber or formulaNumber or formulaNone
Effect typeWhat a manual spend's effect roll produces. "Generic" posts the total to chat; "Damage Reduction" also banks the total as a one-shot reduction applied to the next damage taken.generic, damageReductiongeneric
Bonus damage typeThe damage type a card offer's bonus deals. Leave empty to inherit the attack's own type, which folds the bonus into the attack's damage total. Setting a type adds the bonus as a separate damage packet with its own Apply Damage button, so the target's flat reduction and resistance resolve against it on their own. Ignored unless the spend is offered on an attack card.Inherit the attack's type, Acid, Bludgeoning, Cold, Fire, Force, Lightning, Necrotic, Piercing, Poison, Psychic, Radiant, Slashing, ThunderNone
Selection outcomeWhat happens to the dice the player picks. "Consume" removes them from the pool; "Maximize" leaves them in place and raises each to the die's highest face, limited to the cost.consume, maximizeconsume
Offer on attack cardAlso offer this spend as a button on the owner's own attack cards, adding the result to that card's damage instead of posting a separate roll. "Hit" offers it on any hit, "Critical Hit" only on a crit. Leave empty to offer the spend through the sheet's dice pool panel only. Requires a manual spend that consumes dice for a generic effect.hit, criticalHitNone

Example: That all you got?! A reaction that spends Fury Dice to soak damage.

  • Label → That all you got?!
  • Pool identifier → fury
  • Mode → manual
  • Cost → 1
  • Effect formula → (@strength + @dexterity) * @n
  • Effect type → damageReduction
  • Selection outcome → consume

A consumer is what makes a dice pool do something. The pool stores the dice; the consumer decides how they are used.

Mode picks between the two shapes:

  • manual puts the player in charge. Activating the item opens the dice panel on their sheet with this feature already selected, they pick which dice to use, and confirming applies the result. Use this for anything the rules text describes as a choice.
  • autoBonus is passive: every face in the pool is added to qualifying attacks automatically and nothing is spent. This is how a pool that snowballs damage works.

Several consumers can share one pool. A Berserker's Fury Dice carry an autoBonus consumer for melee damage and separate manual consumers for the features that spend them, all pointing at the same fury identifier.

Attack delivery narrows a consumer to melee or ranged attacks and governs both shapes: an autoBonus pool only adds its faces to attacks of that kind, and a card offer only appears on them. Leave it empty (or pick any) for no restriction.

Two things to watch for. An activation with no attack type set counts as neither melee nor ranged, so most spells and utility features are excluded by any restriction here, with nothing on screen to explain the absence. And the unarmed strike, opportunity strike and heroic-action buttons build their attack outside the normal activation flow: a card offer reads them as melee, but an autoBonus pool does not reach them at all, filtered or otherwise.

Effect formula is evaluated when the player confirms, with two references filled in from their picks: @n is how many dice they chose and @sum is the total of those dice faces. Both combine with the usual sheet references, so a spend can scale with the character as well as the dice. See Formulas & References for the full vocabulary. Effect type decides what the result does: generic posts the total to chat and leaves the rest to the table, while damageReduction also banks the total so it is subtracted from the next damage the character takes.

Offer on attack card moves the spend out of the sheet panel and onto the attack card it modifies, for features the rules tie to how an attack landed. Set it to criticalHit for a feature that only works on a crit (the Berserker's Death Blow), or hit for one that works on any hit. Leave it empty and the spend stays on the sheet, which is the right choice for anything that is not about a specific attack, such as a reaction that soaks damage.

Example: Death Blow. Spends any number of Fury Dice after a crit and deals double their total.

  • Label → Death Blow: bonus damage
  • Pool identifier → fury
  • Mode → manual
  • Effect formula → 2 * @sum
  • Effect type → generic
  • Offer on attack card → criticalHit

With Bonus damage type left empty the result is added to that attack's own damage total, so the GM applies damage once and the target's armor, resistances and reductions are counted once. Posting it as a separate roll would count them twice.

A consumer that opts in gives up its sheet flow entirely: it no longer opens the panel when the item is activated, and it is hidden from the pool panel's feature list. The panel cannot see how the attack turned out, so leaving it there would offer a crit-only spend on any activation.

Opting in needs the rest of the rule to line up. It has to be a manual spend with consume as its outcome, a generic effect type, and an effect formula, on a player character. A damageReduction spend is banked against incoming damage rather than added to an attack, so it is not eligible.

Bonus damage type covers the features whose extra damage is a specific type (radiant, fire) rather than more of what the weapon deals. A damage node carries exactly one type, so a typed bonus cannot fold into the attack's roll: it lands on the card as its own damage packet. Leave it empty and the bonus deals whatever the attack deals, which is the simpler path.

The GM still applies the card with one click and the target's flat damage reduction still comes off once. Two things do change. Resistance is judged per packet, so a target resistant to the bonus type takes half of it and full damage from the attack itself: the reasonable reading of "take half as much damage" for an attack dealing two types, though the rulebooks never address one. And a monster in heavy armor halves each packet separately and rounds each up, so a typed bonus gets slightly better through heavy armor than the same amount folded in would.

Selection outcome decides what happens to the dice the player picked:

  • consume removes them from the pool. This is the normal case, and it needs an effect formula to be worth showing.
  • maximize leaves them in the pool and raises each one to the die's highest face. Use it for a feature that changes a die rather than spending it. No effect formula is needed, dice already showing their highest face are not offered, and the number of picks is limited by Cost, so a cost of 1 gives the player exactly one choice.

Dice Pool ​

Define a refillable pool of rolled dice (each die stores its rolled face). Used for snowballing damage pools (Fury Dice) and rolled resources (Judgment Dice).

FieldWhat it doesOptionsDefault
ScopeWhere the pool lives. "Item" pools live on this item; "Actor" pools live on the actor and can be shared by features that reference the same identifier.item, actoritem
Die sizeSize of each die stored in the pool.d4, d6, d8, d10, d12, d20d4
Max diceMaximum number of dice the pool can hold. Flat (3), formula (@key), or actor data (@strength).Number or formula1
InitialWhether the pool starts full (pre-rolled to max) or empty when first granted.max, zeromax
Refills → TriggerEvent that drives this refill (rest type, encounter event, taken damage, etc.).safeRest, fieldRest, onHit, onCriticalHit, encounterStart, encounterEnd, onWound, onTurnStart, onTurnEnd, onKill, onBloodied, onAttacked, onCritReceivedsafeRest
Refills → ModeHow the value applies: "add" (roll N new dice), "set" (rebuild pool to N), or "refresh" (fill to max).add, set, refresh, setIfEmpty, clearadd
Refills → ValueAmount used by the mode. Flat or formula. Ignored when mode is "refresh".Number or formula1
Refills → ConditionOptional condition tested when the trigger fires (e.g. self: raging). Leave empty to always apply.ConditionNone

Example: Fury Dice. The pool a Berserker builds up while Raging.

  • Label → Fury Dice
  • Scope → item
  • Die size → d4
  • Max dice → @key
  • Initial → zero
  • Refills → one entry: Trigger → onTurnStart, Mode → add, Value → 1, Condition → { "self": "raging" }

A dice pool holds rolled die faces, not a count: each die keeps the number it came up with, and features read those numbers. Max dice takes formulas, so @key grows the pool as the character's key stat does.

Initial decides what the pool looks like the moment the feature is granted: max pre-rolls a full pool, zero starts it empty and waits for a refill or an activation to put dice in.

Each Refill entry says when dice come back and how many:

  • Mode add rolls new dice up to the maximum, set rebuilds the pool to exactly that many, refresh tops it up to full, setIfEmpty only acts when the pool is empty, and clear empties it.
  • Value accepts formulas plus two pool-specific references: @poolMax and @poolCurrent. See Formulas & References.
  • Condition is optional and is checked at the moment the trigger fires, so state that changes mid-combat works correctly. { "self": "raging" } on an onTurnStart refill means the die only arrives on turns where the character is actually Raging.

Not every trigger in the list is wired up yet. The ones that fire today are onTurnStart, onTurnEnd, onAttacked, onCritReceived, and encounterEnd. The others are accepted but never fire, so avoid building a feature that depends on them.

A pool by itself is only storage; it never spends or grants anything. Pair it with a Dice Consumer rule to spend from it or add its faces to attacks, and use Modify Pool on a later feature to grow the die size, raise the maximum, or add more refill triggers.

Grant Activation ​

Offer the currently targeted tokens an immediate activation (e.g. a weapon attack) via a button on this item's chat card. Any action cost for the recipient is governed by other rules, such as an Action Cost or Action Adjustment rule.

FieldWhat it doesOptionsDefault
Granted activationWhat the recipient is offered. Weapon attack: the recipient picks one of their weapons and makes a normal attack.weaponAttackweaponAttack

Modify Consumer ​

Augment the effect formula of dice-spend consumers targeting a pool (by identifier). Typically attached to a feature that improves how another feature spends its dice.

FieldWhat it doesOptionsDefault
Pool identifierThe identifier of the pool whose consumers to modify (e.g. fury).Dice pool pickerNone
Pool scopeThe scope of the pool whose consumers to modify. Must match the pool: identifiers are only unique within a scope.item, actoritem
Effect type filterOnly modify consumers with this effect type. Leave blank to modify every consumer on the pool., generic, damageReductionNone
Append formulaAppended to matching consumers' effect formula as "+ (...)". Spend tokens @n (dice spent) and @sum (sum of spent faces) are available.Number or formulaNone

Example: Stone's Resilience. A subclass feature that improves how another feature spends Fury Dice.

  • Label → Stone's Resilience
  • Pool identifier → fury
  • Pool scope → item
  • Effect type filter → damageReduction
  • Append formula → @sum

Modify Consumer edits the effect formula of Dice Consumer rules that target a pool, without touching the feature those consumers live on. It is the consumer counterpart of Modify Pool: use it when a later feature makes an earlier spend better.

Pool scope must match the pool you are aiming at, the same way a Dice Consumer's does. Identifiers are only unique within a scope, so an item-scoped fury and an actor-scoped fury are different pools, and a modifier set to the wrong scope simply does nothing.

The append is added to the matching formula as a sum, so a consumer reducing damage by (@strength + @dexterity) * @n becomes (@strength + @dexterity) * @n + (@sum). The same references are available as in the consumer itself: @n for the number of dice spent and @sum for their total.

Effect type filter narrows which consumers are touched. Left blank it modifies every consumer on the pool; set to damageReduction it only improves spends that soak damage, leaving other features that spend from the same pool alone. That distinction matters on a shared pool, where one feature spends for damage reduction and another for movement.

If several Modify Consumer rules match, each one appends in rule Priority order. The rule's Predicate gates it in the usual way.

Modify Pool ​

Override or scale an existing dice or charge pool (by identifier): typically attached to a level-up feature to upgrade die size or expand max.

FieldWhat it doesOptionsDefault
Pool typeWhich subsystem to target: dice pools (rolled faces) or charge pools (counters).dice, chargedice
Pool identifierThe identifier of the pool to modify (e.g. fury, judgment, combat-dice). (The input changes with the other field values.)Dice pool pickerNone
Die size overrideReplace the target pool's die size. Leave blank to keep it unchanged.d4, d6, d8, d10, d12, d20None
Max deltaSigned amount added to the target pool's max (e.g. "+1", "-1", "+@level"). Leave blank to keep max unchanged.Number or formulaNone
Minimum faceDice rolled into the target pool below this value are raised to it. Leave blank for no floor. Ignored for charge pools.NumberNone
Additional refills → TriggerEvent that drives this refill (rest type, encounter event, taken damage, etc.).safeRest, fieldRest, onHit, onCriticalHit, encounterStart, encounterEnd, onWound, onTurnStart, onTurnEnd, onKill, onBloodied, onAttacked, onCritReceived, onInitiativeRolledsafeRest
Additional refills → ModeHow the value applies: "add" (roll N new dice), "set" (rebuild pool to N), or "refresh" (fill to max).add, set, refresh, setIfEmpty, clearadd
Additional refills → ValueAmount used by the mode. Flat or formula. Ignored when mode is "refresh".Number or formula1
Additional refills → ConditionOptional condition tested when the trigger fires (e.g. self: raging). Leave empty to always apply.ConditionNone

Example: Intensifying Fury. A level-up feature that upgrades the Berserker's existing Fury Dice.

  • Label → Fury Dice to d6
  • Pool type → dice
  • Pool identifier → fury
  • Die size override → d6
  • Predicate → { "level": { "min": 6 } }

Modify Pool changes a pool that some other feature created, matched by its identifier. This is how progression works without editing the original feature: the level 1 item defines the pool, and each later item carries a modifier that upgrades it. Put one modifier per breakpoint on the same feature, each with its own level predicate, and give the later ones a higher Priority so they win.

The fields are all optional; leave blank the ones you are not changing.

  • Die size override replaces the pool's die (d4 to d6 and so on). Dice already sitting in the pool keep the number they rolled.
  • Max delta is a signed formula added to the maximum: +1, -1, +@level.
  • Minimum face raises any die rolled into the pool that comes up below it. A value of 6 on a d12 pool means every new die is at least a 6. It applies to refills, activation rolls, and the initial fill, but not to a value typed in by hand on the sheet. When several modifiers set one, the highest wins.
  • Additional refills contributes refill entries to the target pool, in the same shape the pool's own refills use. This lets the feature that grants a new trigger carry it, instead of the original pool rule having to know about every later feature.

The rule's own Predicate gates whether the modifier applies at all, so it is the right place for level gates. A condition that flips during play (like being Raging) belongs on the refill entry's own Condition instead, because that is checked when the trigger fires rather than when the pool is built.

Pool Max Bonus ​

Raise the maximum of a charge pool by a flat amount. The bonus lives on this item, so taking the same option twice grants two items and twice the bonus, and removing an item removes its share.

FieldWhat it doesOptionsDefault
Pool identifierThe identifier of the charge pool whose maximum is raised (e.g. combat-dice).Charge pool pickerNone
AmountHow much this item adds to the pool maximum.Number1

Example: +1 Max Combat Die. The Commander's Fit for Any Battlefield offers, at several levels, either another Combat Ability or one more maximum Combat Die. The die is granted as an item carrying this rule.

  • Pool identifier → combat-dice
  • Amount → 1

The bonus lives on the item, so a Commander who takes the option three times holds three items and has three more maximum Combat Dice. Removing one item removes exactly its share.

This is why the bonus is an item rather than a number on the character: it makes the pick behave like every other granted item. The level-up dialog grants it through the same path as any other option, levelling down removes it with the level that granted it, and the option swap and the level choices audit count it by holding it.

The die is part of the same option pool as the Combat Abilities it is offered beside, so Option Swap can trade a held die for an ability, or an ability for a die. Each die item on the sheet is its own pick: a Commander who holds two of them sees one die card marked x2, and can give up one while keeping the other. Because the die's grant rule allows duplicates, the swap keeps offering it while a copy is held, so a Commander with one die can trade an ability for a second. Trading one die away removes one item and one point of the bonus.

The pool identifier must match the identifier of a Charge Pool rule somewhere on the character. A bonus naming a pool that does not exist does nothing. To change a pool's die size or its current value rather than its maximum, use Modify Pool.

Released under the MIT License.