Pathfinder Conditions: What They Do and How They Interact

Pathfinder Second Edition uses a structured condition system to track the mechanical states that affect characters, creatures, and objects during play. Conditions are not informal narrative descriptors — they are defined game states with precise mechanical penalties, durations, and interactions codified in the Pathfinder Second Edition rules published by Paizo Inc. Understanding how conditions stack, override, and terminate one another is essential for accurate adjudication at the table, particularly in combat where 2 or more overlapping conditions can significantly alter action economy and survivability.

Definition and scope

A condition in Pathfinder Second Edition is a named game state applied to a creature or object that modifies its mechanical capabilities in a defined way. Conditions are listed and defined in the Pathfinder Second Edition Core Rulebook (2019) and updated in the 2023 Remaster texts — Player Core and GM Core — published by Paizo Inc. The Remaster editions serve as the current canonical source for condition definitions.

Conditions fall into two structural categories:

The full conditions and effects reference on this site catalogs every named condition in the core system. Within the broader Pathfinder RPG conceptual overview, conditions are one of the primary output mechanisms of the resolution system — the d20 roll determines an outcome, and conditions are often that outcome's mechanical consequence.

Scope matters here: conditions are distinct from effects (which are persistent magical or physical states attached to a spell or ability), from afflictions (poisons, diseases, and curses that progress through stages), and from permanent ability penalties. A condition ends when its removal criteria are met; an affliction requires active treatment or saving throws to progress.

How it works

Valued conditions operate on a numeric scale, typically from 1 to 4, though some extend higher. When a source would apply a valued condition that a creature already has, the higher value takes precedence — the values do not add together unless a specific rule states otherwise. For example, if a creature already has Frightened 2 and a new effect would apply Frightened 1, the condition remains at Frightened 2.

The primary mechanics governing valued conditions:

  1. Application — A spell, ability, or hazard specifies the condition and its value (e.g., "the target is Sickened 2")
  2. Effect — The condition modifies relevant checks, defenses, or actions as defined in the rulebook (Frightened, for instance, applies a status penalty to all checks and DCs equal to its value)
  3. Reduction — Most valued conditions decrease by 1 at the end of the affected creature's turn unless the condition specifies otherwise
  4. Removal — The condition ends when its value reaches 0, or when a specific removal action (such as the Escape action for Grabbed) is taken

Flat conditions operate without a value. They are either present or absent. Blinded, for example, prevents a creature from seeing, causes it to be Flat-Footed to all opponents, and imposes a –2 circumstance penalty to Perception checks based on sight — all simultaneously and without gradation.

The saving throws and defenses reference explains how critical failures on saves commonly trigger more severe condition applications, a mechanic detailed under the critical hits and success degrees system.

Common scenarios

Condition stacking in combat: A fighter who is both Encumbered and Enfeebled 2 faces compounding penalties. Encumbered applies a –1 circumstance penalty to attack rolls and a –5-foot penalty to Speed; Enfeebled applies a –2 status penalty to Strength-based rolls and DCs. Because these are different penalty types (circumstance vs. status), both apply simultaneously. Pathfinder 2E's typed penalty system — distinguishing circumstance, status, and item penalties — means only the highest penalty of the same type applies, but penalties of different types always stack.

Grabbed vs. Restrained: These two conditions are commonly conflated. Grabbed renders a creature Flat-Footed and immobile (Speed 0), and ends if the creature successfully uses the Escape action or the grabber releases it. Restrained is more severe — it also prevents the creature from taking most physical actions and applies the Flat-Footed condition — and typically requires a higher-tier ability or spell to impose. The flanking and positioning rules are directly affected by Flat-Footed, making the Grabbed condition tactically significant beyond simple immobilization.

Dying and Wounded: These two conditions interact in a specific sequenced relationship. A creature reduced to 0 Hit Points gains the Dying condition, starting at Dying 1. The Wounded condition — acquired when a creature is restored from Dying — increases the Dying value by 1 each time the creature falls unconscious again. A creature at Wounded 2 that drops to 0 HP begins at Dying 3 rather than Dying 1, accelerating the path to Dying 4 (which means death). The dying and recovery rules page covers the full recovery stabilization sequence.

Decision boundaries

The primary adjudication questions that arise from the condition system involve three boundary types:

Same-type penalty stacking: Only the highest penalty of a given type applies. Two sources of Frightened do not compound — the higher value supersedes. Two sources of a –2 status penalty to attack rolls produce a –2 penalty, not –4. However, a –2 status penalty and a –2 circumstance penalty both apply, producing a –4 total.

Condition immunity vs. condition removal: Immunity to a condition (typically granted by a spell or ability) prevents the condition from being applied. It does not retroactively remove a condition already present. A creature that gains immunity to Paralyzed while already Paralyzed remains Paralyzed until the condition ends through its normal termination criteria.

Condition vs. affliction classification: A Game Master adjudicating whether a poison's "Sickened" application counts as a condition (and therefore subject to removal via the Treat Poison action) or as a stage-locked affliction effect must reference the specific ability's rules text. The crafting and alchemy rules include the affliction framework for alchemical items, which clarifies this boundary for the most commonly encountered cases.

The action economy system determines when and how condition-removal actions — Escape, Recover, Treat Condition — can be taken within a turn structure. Conditions that impose the Stunned state consume actions directly (Stunned 2 costs 2 actions at the start of the next turn), making Stunned one of the most action-economically punishing conditions in the system. The hero points system provides one of the limited mechanisms for forcing a reroll on the saving throw that originally imposed a severe condition.

Proficiency in the relevant skills affects the success rate of condition removal attempts. The proficiency rank system governs whether a character's Medicine checks — used for actions like Treat Wounds or Treat Poison — are competitive against the DC thresholds set by the conditions being treated.

References

Explore This Site

Tools & Calculators Chinese Zodiac Calculator FAQ Pathfinder RPG: Frequently Asked Questions Overview Pathfinder RPG: What It Is and Why It Matters