PF2e Top 100 Table Rules Quickref

Purpose: fast, spoiler-safe at-table rulings and decision support. Scope: practical reminders, not full legal text. If disputed, confirm via core index.

---

0) 15-Second Ruling Protocol

1. Keep game moving with a provisional ruling.
2. Prefer the interpretation that preserves action economy clarity.
3. Log the dispute, verify after session, then standardize.

---

1) Action Economy (1–10)

1. You usually get 3 actions + 1 reaction each turn cycle.
2. MAP applies to attacks in same turn; 3rd attack is often poor value.
3. Activities consume listed actions and can trigger MAP if they include attacks.
4. Stand/Interact/Step taxes are huge tempo levers.
5. Trading your 2 actions for enemy 2+ actions is a win.
6. Delaying can improve team sequencing; don’t lose track of initiative order change.
7. Ready costs 2 actions and uses your reaction later.
8. Stride + Strike + setup often beats Strike x3.
9. Force enemy movement to burn actions.
10. Protect your reaction economy (AoO-like threats, shield/defensive reactions).

2) Degrees of Success (11–18)

11. Beat DC by 10 = critical success.
12. Miss DC by 10 = critical failure.
13. Nat 20 bumps degree up one step.
14. Nat 1 bumps degree down one step.
15. Most strong effects are balanced around partial results.
16. Favor spells/effects that do something on success.
17. Confirm whether effect uses spell DC vs class DC vs skill DC.
18. “Basic save” means standardized crit success/success/failure/crit failure scaling.

3) Vision, Detection, Stealth (19–30)

19. Hidden vs undetected vs unnoticed are different states.
20. Concealed imposes flat-check risk before hit resolves.
21. Hidden/undetected generally involve stronger targeting uncertainty.
22. Seek is your friend when targeting is unclear.
23. Step avoids many reactive movement punishers.
24. Cover matters constantly; call it early each encounter.
25. Standardize table callouts: “seen / hidden / undetected.”
26. Don’t stack assumptions—confirm line of effect and line of sight separately.
27. Invisibility does not equal invulnerability; detection still possible.
28. Bright/dim/dark context changes value of stealth plays.
29. If uncertain, rule for clarity and consistency this encounter.
30. Log stealth edge cases for post-session rules check.

4) Conditions That Swing Fights (31–45)

31. Off-guard is often best team DPR enabler.
32. Frightened is premium because it pressures many checks/DCs.
33. Stupefied is high-value vs casters.
34. Slowed/stunned-like effects crush enemy action economy.
35. Grabbed/restrained can force escape taxes.
36. Prone manipulates both offense and defense geometry.
37. Sickened taxes actions and can reduce output.
38. Persistent damage is tempo pressure, not just HP loss.
39. Dying/wounded management is priority over greedy damage lines.
40. Doomed + dying interactions can snowball danger quickly.
41. Enfeebled/clumsy/drained target different stat ecosystems.
42. Don’t forget duration and end conditions.
43. Reapplying short debuffs at key initiative points is often correct.
44. Condition immunity checks save wasted turns.
45. Clarify whether penalties are status/circumstance/item before stacking.

5) Triggers, Reactions, Interrupts (46–55)

46. Ask “what triggers right now?” before resolving big actions.
47. Reactions can invalidate greedy lines—bait them early.
48. Ready interacts with trigger timing; define trigger text clearly.
49. Counterplay windows matter (movement, manipulate, concentrate).
50. Trigger ambiguity: GM picks cleanest timing interpretation and moves on.
51. Don’t retroactively rewind too far unless outcome-critical.
52. Call out reaction availability openly for table clarity.
53. Save one reaction for survival when fight is volatile.
54. Team plan should account for ally reactions too.
55. If multiple reactions compete, prioritize life-saving/control value.

6) Counteract, Resistances, Immunities (56–65)

56. Counteract is level/rank-sensitive—great when matched, weak when outscaled.
57. Don’t toss premium counteract blindly; identify threat first.
58. Resistances chip multi-hit lines harder than single big hits.
59. Weaknesses reward right damage typing over raw damage size.
60. Immunities can hard-stop whole strategies—check traits first.
61. Precision/mental/poison edge cases come up often; verify quickly.
62. Swapping damage type can outperform upcasting in some fights.
63. Persistent damage type matters for bypassing defenses.
64. “Magical” and “spirit/align-like” distinctions can matter in specific matchups.
65. When unknown, probe with low-cost action first.

7) Movement & Positioning (66–74)

66. Position to force enemy Strides through bad lanes.
67. Flanks/off-guard setups are team resources, not personal perks.
68. Step for precision positioning under reactive threat.
69. Verticality and choke points create action taxes.
70. Retreating one square can blank enemy 3-action plans.
71. Protect backline by controlling approach vectors.
72. Don’t over-extend for one hit unless it wins tempo.
73. Use terrain to trade your action for enemy two.
74. End turn where healer/defender coverage exists.

8) Spellcasting Practicals (75–84)

75. Pick save targets by enemy archetype (brute/reflex, skirmisher/fort, caster/will pressure).
76. AoE is best when it also distorts enemy decisions/position.
77. Sustain cost must justify itself every turn.
78. Pre-buff only when expected value beats immediate impact.
79. Keep one emergency defensive spell/line online.
80. Don’t chase perfect turns—take reliable value.
81. If target likely saves, choose effects with meaningful success text.
82. Sequence debuffs before ally burst windows.
83. Preserve top slots for tempo flips, not vanity damage.
84. Track your overperformers/underperformers after each session.

9) Aid, Recall, and Team Utility (85–92)

85. Aid can be huge if set up intentionally.
86. Recall-like info is best when it changes this-round choices.
87. If info won’t alter decisions, skip it and act.
88. Help actions that create off-guard/opening often outvalue chip damage.
89. Communicate intent before turn starts for sequencing.
90. Shared target priority wins more fights than isolated optimization.
91. Stabilize allies early in swingy encounters.
92. Resource spend should match encounter danger, not panic.

10) Dying, Recovery, and Risk Control (93–100)

93. Preventing a drop is better than recovering from one.
94. When ally drops, reassess objective: survival vs finish.
95. Minimize exposed turns while wounded.
96. Confirm who can administer recovery now vs next initiative.
97. Don’t chain risky plays when party HP state is unstable.
98. Preserve one clean exit/reset option.
99. If table is unsure, choose the ruling that avoids accidental lethality spikes.
100. After session, codify rulings to prevent repeat friction.

---

Kane-Specific Fast Defaults

• Open unknown fights with conservative control/info line.
• Against elites: debuff/control first, then feed striker windows.
• Against mobs: prioritize action-tax and positioning disruption.
• Keep one emergency defensive answer unspent until tempo is secure.

Dispute Escalation Path

1. PF2e_Core_Search_Index.md for quick locate.
2. Search raw index (.jsonl) by keyword.
3. Pull exact text from book if still contested.
4. Record final ruling in 03_Rules_Quickrefs/Session_Rulings_Log.md.