Skip to content

Settings ​

You'll find the system's settings in Foundry under Game Settings → Configure Settings → Nimble. This page is a short, opinionated guide to the handful that shape how your table feels. The complete list, with defaults and who each setting affects, lives in the Settings Reference.

Automation ​

How much the system does on its own is controlled from one place: the Configure Automation button in the system settings tab (GM only). It opens a window with ten world toggles, all on by default, so a fresh world automates everything out of the box. Changes apply immediately; no reload is needed.

  • Apply Conditions and Effects from Rules. When a feature's rule triggers (say, an attack that frightens on a hit), the condition lands on the target automatically, targets are marked, and timed effects end on their own. When off, conditions still appear as one-click buttons on the chat card. Activating toggle effects and spending pool dice always work regardless of this toggle. See Conditions.
  • Derived Conditions. Conditions implied by other conditions are applied and removed automatically, such as Hampered while Dazed, Grappled, Prone, Slowed, or Restrained.
  • Resource Recovery. Charges and dice pools refill from their recovery triggers: turn start, rests, wounds, kills, and encounter end.
  • Resource Spending. Mana is deducted when casting, and charges are validated and consumed on use. When off, casting and item use no longer deduct or check costs, so they must be tracked by hand. The spell upcast dialog follows the same rule: with the toggle off it lets you upcast to your highest unlocked tier regardless of the mana on your sheet.
  • Action Tracking. Using an item during combat spends the combatant's actions.
  • Health-State Sync. Bloodied is applied at half hit points and removed on recovery.
  • Combat Convenience. Player characters roll initiative automatically when combat starts.
  • Movement Tracking. The system reports each finished token move to features and, during combat, keeps count of the spaces moved this turn, so features can react, in a started combat, when a creature finishes moving or moves adjacent to someone. It never moves a token and never blocks a drag. When off, the system counts nothing, and features that react to movement or let a creature move for free on their own post nothing. Foundry still keeps its own movement history. See Running Combat and Features that react to movement.
  • Forced Movement and Moves for Free. When a card pushes or pulls a creature, or lets it move for free, the creature's next drag counts as that movement: it never draws on the creature's own speed, and the ruler shows how far it can go. Nothing stops a longer drag, there is nothing to click, and the player still picks the path and the final space. It needs Movement Tracking, because only a recorded move can update the card. When either toggle is off, the card shows the distance as text, the token is dragged as usual, and a feature that lets a creature move for free on its own, for example when a creature gains dice in a pool, posts no card. Turning either toggle on or off stops the card from watching every waiting move, and its tag then shows only the distance. See Running Combat.
  • Chat Notifications. Informational messages such as initiative bonus reminders, pool gain notices, and toggle effect start and end announcements.

Some behaviors are deliberately not toggleable because removing them would break basic play rather than reduce bookkeeping: Last Stand handling, defeat syncing to the tracker, the dice pool spend prompt, toggle effect activation, combat mana grants, pool syncing, and hit point clamping are always on. The Moves on the ruler are always on too, because they only show distance. See Running Combat.

Flipping a toggle mid-combat

Toggles only stop future events. Effects that were already applied linger until removed by hand, and refills skipped while a toggle was off are not replayed when you turn it back on.

Worlds upgrading from an earlier version keep their old choice: the stored value of the legacy Auto-Apply Conditions from Rules setting seeds the initial state of Apply Conditions and Effects from Rules.

Custom conditions ​

The Manage Conditions button in the system settings tab (GM only) opens an editor for adding conditions the system doesn't ship with — useful when your table is running content that introduces its own statuses. Give each one a name, a description, and an icon from your Foundry files. The id fills in from the name, but you can type your own before the first save; after that it's locked, because every effect and rule using the condition stores that id. Descriptions are plain text: type them as you'd read them, and blank lines become paragraphs.

Saved conditions appear alongside the built-in ones in the token status panel, both Conditions tabs, and every rule that picks a condition. The token panel and any open conditions list pick up changes right away; sheets and rule dropdowns that are already open show them after you reopen them. Removing one that is still in use opens a confirmation listing the creatures carrying it and the items naming it, so you can strip it from them in the same step. Custom conditions carry no built-in mechanics — see Conditions for what that means.

Settings to decide before your first session ​

Hide Rolls by Default is off by default. When on, skill check and weapon roll windows start with the roll hidden from other players, instead of public. Each user sets this for themselves, so turning it on for yourself as GM keeps your monster rolls private without touching the players' rolls.

Auto-Expand Rolls is off by default. When on, chat cards show the dice breakdown inline under every roll instead of waiting for a hover. Per-user; players who like seeing the dice can turn it on without cluttering anyone else's chat.

Auto-Add Character To Combat On Initiative Roll is off by default. When on, a player rolling initiative from their character sheet is added to the current scene's combat automatically if they're not in it yet. Great for tables where "roll initiative!" is the announcement itself; leave it off if you prefer to build the tracker by hand. World setting.

Auto-Track Token Adjacency is off by default. When enabled, the system tracks how many enemies are adjacent to each combatant during fights, so features whose conditions (the Condition box) depend on adjacency work automatically. Leave it off unless your party has such features: it's extra bookkeeping the system only needs when something actually reads it. World setting, requires a reload. Details in Running Combat.

Whether a diagonal counts as adjacent is Foundry's own Grid Diagonals setting (under Core Settings). The rulebook offers three table options and each has a matching choice there: Equidistant means diagonals are adjacent (the default), Illegal means they are not, and either Alternating choice counts every other diagonal. With Alternating (1/2/1) the first diagonal costs 1 space, so a diagonal neighbour is 1 space away and is adjacent. With Alternating (2/1/2) the first diagonal costs 2 spaces, so a diagonal neighbour is 2 spaces away and is not adjacent. Along a path the cost alternates, so four diagonal steps count 6 spaces with either choice. Foundry also lists Exact, Approximate and Rectilinear, which the rulebook does not describe. Rectilinear counts every diagonal as 2 spaces. Exact and Approximate give a fractional distance, and the system rounds it to the nearest whole space (a half rounds up), so with Approximate a diagonal neighbour is 2 spaces away. The system reads the setting everywhere it measures spaces, for example adjacency and the spaces a token moves.

A high-automation table

Want the system to carry as much as possible? Leave every Automation toggle on (the default), then turn on Auto-Add Character To Combat On Initiative Roll and Auto-Expand Rolls (each player sets this last one themselves). Add Auto-Track Token Adjacency if anyone's features care about flanking-style positioning. Result: conditions land on their own, resources spend and refill themselves, the tracker fills itself, and every roll is fully readable at a glance.

A keep-it-manual table

Prefer to stay hands-on? Open Configure Automation and turn off Apply Conditions and Effects from Rules (conditions become one-click suggestions on chat cards instead), plus any other family you'd rather track yourself, such as Resource Spending or Action Tracking. Leave off Auto-Add Character To Combat On Initiative Roll and Auto-Track Token Adjacency. Consider turning on Hide Rolls by Default on your own client so GM rolls stay behind the screen. The system still rolls the dice and does the math. It just asks before changing anything.

3D dice ​

If your table uses the Dice So Nice module, the Configure 3D Dice button in the system settings tab opens a window where each player chooses how the primary die of their damage rolls looks. The primary die is drawn in its own colors so it reads apart from the rest of the pool, and the colors travel with the roll: everyone at the table sees the roller's choice, not their own.

  • Distinct Primary Die is on by default. Turn it off to have the primary die use your normal Dice So Nice theme.
  • Primary Die Color and Primary Die Number Color set the body and the numerals. Reset Colors puts both back to the crimson and gold defaults.

All three are per-user, so every player sets their own. Without Dice So Nice installed and enabled, the button is greyed out: these settings only change 3D dice, and there is nothing for them to affect.

The combat tracker has its own settings ​

The combat tracker at the top of the screen isn't configured from the settings menu. Instead, click the gear button on the tracker itself to open the Combat Tracker Settings window. Size, colors, hit point bar display, and what players are allowed to see all live there, and every option is listed in the Settings Reference.

Everything else ​

The remaining settings (the Combat System panel toggle, debug mode, and the rest) are documented in the Settings Reference, each with its default and whether it affects the whole world or just one user.

Released under the MIT License.