Conditions
Conditions are status markers (Prone, Frightened, Grappled, and friends) that sit on a character or monster and show as icons on its token. The system ships with the full set of Nimble conditions; for what each one does, see the Conditions Reference (and the Nimble rulebook for the underlying rules). GMs can also add conditions of their own.
Three ways to apply and remove them
- The token. Select a token and open its overhead controls (right-click the token). The status panel lists every condition by name. Click one to toggle it on or off, and use the clear-all button to wipe them.
- The sheet's Conditions tab. Both the character sheet and the NPC sheet have a Conditions tab listing every condition with a search box and an "active only" filter. Toggle a condition there to apply or remove it. Other temporary and passive effects on the actor are listed on the same tab.
- Chat card buttons. When an attack, spell, or feature inflicts a condition, the condition appears as a button on its chat card. Select the affected tokens and click the button to apply the condition to all of them. Hover the button for the condition's description.

Linked conditions
Some conditions come bundled together, and the system tracks the relationships for you:
- Counts as. Some conditions imply others: Grappled also counts as Restrained (and the reverse), and Stunned counts as Incapacitated, Restrained, Paralyzed, and Unconscious for anything that checks those. You'll only see the icon you applied, but rules that look for the implied condition will find it.
- Applied together. Petrified automatically carries Incapacitated with it.
- Automatic Hampered. Applying Dazed, Grappled, Prone, Slowed, or Restrained automatically applies Hampered as well. When the last of those trigger conditions is removed, Hampered goes away on its own.
- Wounded stacks. Unlike other conditions, Wounded can be applied multiple times, one stack per wound.
Concentration
Concentration applies itself. Casting a spell whose Concentration property is ticked puts the Concentration condition on the caster as the chat card posts, and the card says Concentration Applied so the player can see it took. No GM click is involved, and it happens whether the spell targets an ally, several creatures, or nobody at all. The condition always lands on the caster, never on the targets. If the condition cannot be applied, the card says nothing and the caster gets a warning instead.
A caster holds one concentration at a time. Casting a second concentration spell ends the first: the old condition is removed and a new one applied, credited to the new spell. If the new one is refused, the first is left where it was.
The rulebook says a character can only concentrate on one activity at a time, but it does not say what happens when they start a second. Replacing the first is the system's reading of that, not printed text.
Casters who concentrate on more than one thing. A feature can give a spell school a concentration of its own. Stormshifter's Master of Storm does this for Lightning and Wind, so casting a Wind spell leaves a Lightning concentration alone and the other way round.
Master of Storm names two schools and grants two concentrations. What it does not say is what happens when that caster concentrates on a third school, so the system reads the naming as splitting their single concentration rather than adding to it: casting in a school the feature does not name ends every concentration they hold, and casting in a named school ends that school's concentration along with anything held in an unnamed school. That reading keeps them at the two the feature grants. It is the system's reading of the printed line plus the one-at-a-time rule, not printed text. Homebrewers get the same through the Concentration Track rule.
Tracks follow a spell's school, and a magic item carries no school. So a Wand of Fly or a Cloak of Lesser Windform concentrates on the default track, and using one ends a tracked concentration the caster is holding.
Ending one of two held concentrations is a choice rather than bookkeeping, so removing Concentration from the token panel or the Conditions tab asks which one should end. A caster holding only one is ended without a prompt.
This is driven by the property, not by anything authored on the spell, so a homebrew spell that ticks Concentration behaves exactly like one the system ships. The same goes for a spell scroll, which carries the inscribed spell's Concentration property.
What the system does not do is break concentration for you. Losing it when crit (a DC 10 STR save), at 0 HP, or when Incapacitated is still yours to track. Remove the condition by hand when it ends. Ending concentration deliberately is a free action, and a hero gets one free action per turn, which the system does not spend for you either.
Only spells and objects carry the Concentration property, so a feature that holds concentration in its text, such as Shadowmancer's Gaze of Two Minds, is not covered. Apply and remove the condition by hand for those.
Turning off Apply Conditions and Effects from Rules in the Automation settings turns this off with it: casting then applies nothing and ends nothing, and Concentration is yours to place by hand.
Custom conditions
A GM can add conditions of their own from Game Settings → Configure Settings → Nimble → Manage Conditions — handy for statuses from content the system doesn't ship with. Each one takes a name, an id, a plain-text description, and an icon, and from then on it behaves like any other condition in the token panel, the Conditions tab, and the Rules Builder's condition lists.
Custom conditions are markers only: none of the linked-condition behavior above applies to them, they never stack, and they aren't listed in the generated Conditions Reference, which is built from the conditions that ship with the system.
Removing a custom condition that something still uses opens a confirmation listing what would be left behind: the creatures currently carrying it, and the items whose rules or activation effects name it. From there you can Remove Everywhere, which deletes those effects and strips the condition out of those items, or Remove Only, which drops the definition and leaves the references in place. Either way nothing changes until you save the conditions list, so closing the editor cancels it.
Remove Only leaves markers and rules pointing at an id nothing resolves. Rules in that state stop running and say why on their card in the Rules Builder; leftover markers drop out of the Conditions tab's condition list, so remove them from the same tab's Temporary Effects or Passive Effects section, or from the token conditions panel on the canvas. Items inside compendiums are not searched or rewritten, since packs can be locked or owned by a module.
Condition immunity
Items can make a character immune to specific conditions through a condition immunity rule (see the Rules Builder pages). Attempts to apply a condition the actor is immune to are blocked, including the automatic applications described above.
The condition automation toggles
Two toggles in the GM's Automation settings govern conditions. Both are world settings, both default to on, and changes take effect immediately without a reload.
Apply Conditions and Effects from Rules controls what happens when a feature's rules say "on X, apply condition Y" (for example, a weapon that poisons on a hit):
- On (the default): when the trigger fires (damage is applied, a save is failed, a turn starts), the condition is applied to the target automatically.
- Off: nothing happens automatically, but the condition still appears as a button on the chat card so the GM can apply it manually.
Derived Conditions controls the automatic Hampered behavior described above: whether applying Dazed, Grappled, Prone, Slowed, or Restrained automatically brings Hampered along, and whether Hampered leaves when they do. The counts-as implications, Petrified carrying Incapacitated, and Wounded stacking are always active regardless of these toggles.