Pathfinder Conditions and Status Effects

Conditions and status effects are the mechanical language Pathfinder uses to describe what happens when a fighter takes a sword hilt to the face, a wizard gets tangled in a web spell, or a rogue drinks something they probably shouldn't have. They sit at the intersection of narrative and ruleset, translating dramatic moments into precise game states that affect checks, actions, and survival. Understanding how conditions stack, interact, and expire is fundamental to both playing and running the game effectively — they appear in nearly every combat encounter and many out-of-combat situations across Pathfinder.

Definition and scope

A condition in Pathfinder 2nd Edition is a persistent game state that modifies a creature's capabilities, actions, or statistics in a defined way. The Pathfinder Second Edition Core Rulebook (Paizo Publishing) catalogues conditions in a dedicated appendix, defining each one with explicit mechanical effects rather than leaving interpretation to the table.

Conditions fall into two broad categories: simple conditions, which are binary (either you have them or you don't), and valued conditions, which exist on a numbered scale. Frightened, for example, is a valued condition — Frightened 1 imposes a -1 status penalty to all checks and DCs, while Frightened 4 is the kind of terror that makes a paladin reconsider their career choices. When a valued condition reaches 0, it ends. When multiple sources apply the same valued condition, a creature takes the highest value, not the sum — a mercy built directly into the rules.

Simple conditions include states like Blinded, Prone, or Paralyzed. Each has a fixed effect that doesn't scale.

How it works

Conditions impose one or more of three mechanical outcomes: they modify numbers (bonuses or penalties to checks and DCs), they restrict actions (limiting or eliminating what a creature can do on its turn), or they alter how a creature interacts with the environment and other creatures. Most conditions in the Core Rulebook stack only with conditions of different types — a status penalty and a circumstance penalty to the same roll both apply, but two status penalties don't stack; only the larger one counts.

Here is how a condition typically resolves:

1. Application — A spell, ability, or environmental effect states which condition is applied and, for valued conditions, at what value.
2. Duration tracking — Most conditions last until the end of a turn, for a set number of rounds, or until a specific triggering action (like succeeding on a saving throw).
3. Interaction check — The GM checks whether the new condition conflicts with an existing one. Grabbed and Restrained, for instance, cannot be applied simultaneously; Restrained supersedes Grabbed.
4. Effect resolution — The condition modifies any applicable rolls or actions for its duration.
5. Removal — Some conditions end automatically; others require a specific action, spell, or successful check to remove.

The Sickened condition illustrates the system's internal logic neatly: it imposes a -1 status penalty (or higher, if valued) to all checks and DCs, and the only way to remove it is to spend an action retching — which itself requires being able to act. A creature that is also Paralyzed cannot retch, so the Sickened condition persists until the Paralyzed condition is resolved first.

Common scenarios

Conditions appear with high frequency in the combat rules context, but they aren't exclusive to it. The most common encountered in play:

• Grabbed — Applied by successful Athletics checks (Grapple action); imposes the Immobilized condition and a -1 circumstance penalty to attack rolls.
• Frightened — Applied by fear effects; decreases by 1 at the end of each of the frightened creature's turns.
• Dazzled — Imposes the Concealed condition on all creatures; commonly applied by bright light effects or specific spells.
• Flat-Footed — One of the most frequently applied conditions in the game; removes the creature's Dexterity bonus to AC. Rogues deal sneak attack damage against flat-footed targets, making this condition central to the rogue's class mechanics.
• Wounded — Applied every time a creature is brought to 0 HP and then recovers; stacks numerically and increases the DC of the dying recovery checks, making repeated knockdowns increasingly dangerous.

The Wounded condition's stacking behavior is one of the few places in Pathfinder 2E where the same condition type accumulates additively, making it meaningfully different from most valued conditions.

Decision boundaries

Knowing when to prioritize removing a condition versus accepting it is one of the more consequential micro-decisions in Pathfinder play. A few structural guidelines clarify the boundaries:

Persist vs. remove: Conditions with immediate action-restriction effects (Stunned, Paralyzed, Unconscious) demand removal as fast as possible because they eliminate turns entirely. Conditions with numerical penalties (Frightened, Enfeebled) are often better tolerated while action-efficient options remain.

Stacking thresholds: Because most conditions don't stack with themselves, applying a second source of Frightened to a creature already at Frightened 3 only matters if the new source applies Frightened 4 or higher.

Valued vs. simple: Simple conditions like Blinded are binary and devastating — a blinded creature treats all targets as Concealed (20% miss chance) and is itself Concealed to others. Valued conditions often allow partial function at low values, making early-round application less critical than maintaining them at high values.

Removal methods: The spells and magic system includes direct condition-removal options — Restoration addresses drained and enfeebled; Remove Fear ends frightened and fleeing; Dispel Magic can end magically sustained conditions. Physical conditions like Grabbed or Prone are removed through actions (Escape, Stand), not spells.

The saving throws and checks system is tightly coupled to conditions — many conditions are applied on a failed save, and degrees of success (four possible outcomes: critical failure, failure, success, critical success) determine whether a condition is applied at full value, partial value, or not at all.