PF2e Remastered Checks and DCs Guide

Introduction

Checks and DCs are the spine of Pathfinder 2e Remastered. Attacks, saving throws, skill actions, Perception, Recall Knowledge, counteract checks, recovery checks, spell DCs, class DCs, and many item effects all point back to the same engine: roll a d20, add the relevant modifier, compare to a Difficulty Class, then apply the degree of success.

That sounds simple because it is. The hard part is choosing the correct kind of DC and knowing when not to roll at all. This guide connects the player-facing procedure from Player Core to the GM-facing DC guidance from GM Core, with examples for Player Core 2 classes, skill-heavy builds, spellcasters, combat turns, and campaign rulings.

The Core Check Loop

Use this every time the table is unsure what to roll.

Player Core's four-degree engine is the reason PF2e math feels sharper than many d20 games. A +1 is not just a tiny bump to success chance. It can also move failures into successes and successes into critical successes. That is why frightened, off-guard, Aid, Bless, weapon potency, skill investment, and circumstance bonuses matter so much.

Hot take: the d20 roll is the noisy part, but PF2e is secretly a DC game. The GM who sets fair DCs is doing more balance work than the player who bought the fanciest dice tower.

Which DC Should You Use?

GM Core's best advice is practical: separate the difficulty of the task from the drama of the moment. A cool stunt is not automatically legendary. A boring task is not automatically easy. Pick the DC from the obstacle, then let the story interpret what the result means.

Simple DCs

Simple DCs are for tasks defined by expected proficiency, not level. They are best when the obstacle does not have a level of its own.

Use simple DCs for Athletics, Crafting, Medicine, Survival, Society, and other everyday skill tasks when level is not the main point. If the challenge is a specific monster, hazard, item, ritual, affliction, or spell effect, switch to level-based DCs.

Level-Based DCs

Level-based DCs are for level-bound opposition. This is where PF2e's scaling math does its job.

Do not use level-based DCs to make ordinary reality level with the party. A ladder does not become a boss monster at 13th level. A normal rope is still a normal rope. High-level characters should be allowed to be casually good at low-level problems because that is part of advancement.

Opposed DCs

Opposed DCs are cleaner than opposed rolls. In PF2e, one side usually rolls against the other side's DC.

This keeps play fast. It also avoids the chaos of two d20s creating swingy results where nobody can tell whether the character was skilled or the opposition simply rolled like a chair with ambition.

Best links: Athletics, Deception, Intimidation, Stealth, detection and senses, and grapple and control actions.

Adjusted DCs

Adjusted DCs are where GM judgment belongs. Start with simple, level-based, or opposed DC logic, then adjust because the fictional task actually changed.

Do not punish clever play by raising the number because the player surprised you. If the plan uses tools, terrain, spells, scouting, or social leverage well, that should often make the check easier. The reward for preparation should not be "great idea, now roll the same DC."

Flat Checks

Flat checks are pure chance. You roll a d20 against a DC without modifiers. Bonuses and penalties do not apply unless a rule specifically says they affect flat checks.

Flat checks are not skill checks. A Rogue with absurd Stealth still rolls the flat check normally unless a rule changes it. A Wizard with a towering spell DC still does not add it to the flat check to target a hidden creature. The flat check is the game saying, "No, this part is just chance."

Best links: conditions, persistent damage, dying and death, and detection and senses.

Secret Checks

Secret checks protect uncertainty. They are strongest when knowing the die result would tell the player more than the character knows.

Secret checks should not become a wall between the players and the game. Give clear stakes when characters can perceive the risk. Hide the result when uncertainty is the point. There is a difference between mystery and "the GM has a spreadsheet and nobody else is allowed to have feelings."

Degrees Of Success

The four outcomes matter more than the pass/fail split.

Specific rules can change what each degree does. Spells, skill actions, afflictions, traps, saves, and class abilities often have their own result entries. Read those entries before improvising. In PF2e, the critical failure line is frequently where the rule hides the bear trap under a welcome mat.

Natural 20 and natural 1 adjust the degree by one step after comparing the total to the DC. That means a natural 20 is not always a critical success against an extreme DC, and a natural 1 is not always a critical failure if the character's total is high enough. The die shifts the result; it does not delete the math.

Player-Facing DCs

Players should know which numbers on their sheet turn into DCs.

This is why ability boosts and proficiency matter. A Kineticist, Alchemist, Inventor, or Commander may care about class DC in ways a pure weapon attacker does not. A Bard, Cleric, Druid, Oracle, Sorcerer, Witch, or Wizard lives and dies by spell DC targeting.

Player Core 2 Stress Tests

Player Core 2 does not change the check system. It gives the system more ways to matter.

The answer should come from the action or feature text first, not from whichever number on the sheet is highest. If a rule calls for a class DC, use class DC. If it calls for a spell DC, use spell DC. If it calls for a skill check against a target's Will DC, do that. "Can I use my better number?" is not a rules principle. It is a negotiation tactic wearing a tiny rules hat.

Skill Checks And DCs

Skill checks deserve their own deeper article because GM Core gives several useful ways to set DCs for them. Start here, then use skill check DCs when you need the table-facing version.

Skill DCs should reward investment. A character who became expert, master, or legendary in a skill should feel that choice at the table. If every task turns into the same hard DC for everyone, proficiency is being treated like decorative trim.

When Not To Roll

The most important DC decision is whether a roll should happen.

Do not roll when:

• The outcome is obvious.
• Failure would not change the scene.
• The character has enough time, tools, and safety to succeed.
• The task is beneath the character's established competence.
• The roll exists only because the GM feels nervous saying yes.

Roll when:

• Time pressure matters.
• Failure changes position, resources, information, safety, or reputation.
• The opposition has a meaningful defense.
• The action text calls for a check.
• The party has chosen a risky approach.

Failing forward matters here. If a failed check blocks the only path into the adventure, the DC is not the problem. The adventure structure is. Failure can cost time, make noise, damage gear, split the party's attention, reveal partial information, or force a harder route. It does not have to turn the session into a locked door appreciation society.

Common Mistakes

Combat Checks

Combat uses the same engine, but the cost of a bad ruling is higher because actions are scarce.

Best links: actions and activities, combat guide, conditions in combat, grapple and control actions, save progression, and spell guides.

GM Procedure For Fast Rulings

When the rules do not hand you a ready-made number, use this sequence.

1. Decide whether a roll is needed.
2. Decide whether the challenge is training-based, level-based, opposed, or pure chance.
3. Choose the relevant skill, save, attack, class DC, spell DC, item DC, or flat check.
4. Apply only the adjustments that the fiction supports.
5. Say the stakes clearly unless the check is secret for a reason.
6. Resolve all four degrees if the rule provides them.
7. On failure, move the scene forward with a cost when possible.

That sequence is faster than pausing to invent a custom subsystem. PF2e already has the procedure. Use it, then make the fictional result vivid.

Practical Examples

How To Talk About DCs At The Table

Players do not need every hidden number, but they do need enough context to make choices. "This is risky and failure will make noise" is useful. "Roll Thievery" with no stakes and a mysterious expression is less useful. Use secret checks when uncertainty is part of the fiction. Use open stakes when the character can reasonably judge the risk.

For GMs, the best habit is to name the category even when you do not reveal the number:

• "This is a trained-level task."
• "This is based on the hazard's level."
• "Roll against the guard's Perception DC."
• "This is a flat check, so no modifier."
• "This is secret because your character would not know whether the conclusion is correct."

That tiny bit of procedure makes rulings feel consistent instead of personal.

Related Guides

Best Links

Use skill check DCs, proficiency ranks, actions and activities, skills, GM skill check DCs, combat, and spell guides.

Hot Take

Most DC arguments are not math problems. They are expectation problems. Say what kind of DC you are using before the roll and half the friction disappears.

Second hot take: the worst DC is not the high one. It is the unprincipled one. Players can accept a brutal DC when the fiction supports it. What they hate is the sense that the number appeared because the GM needed the plot to win initiative.

Return to the PF2e rules guide.