Your Complete Guide to Tracking Pathfinder 2E Rulings, Errata, and Official Sources

Stealth errata is the silent killer of prepared game sessions. You've spent an hour building an encounter around a creature's resistance, prepped your action economy around a feat interaction, or patiently answered a player's question mid-session, only to discover the underlying rule changed two weeks ago in a seasonal update you missed. The fix isn't obsessive forum-checking. It's a five-step workflow backed by a clear source hierarchy, bookmarked once and maintained as a simple habit.

Paizo's Spring 2026 errata is a perfect illustration of why this matters. A single blog post updated Player Core, GM Core, Player Core 2, and Guns & Gears (Remastered), while also carrying forward one retroactive Spellstrike change that originated in the Fall 2024 Secrets of Magic errata. GM Core changes included updated language for alchemical bomb rules and a corrected item price for 5th-rank wands. Guns & Gears (Remastered) changed how long the inventor's Overdrive failure lasts. That's four books touched in one post, with a fifth pulled in retroactively. There is no secondhand summary that reliably captures all of that. The only way to catch it is to go to the source.

Tier 1: Authoritative Sources — Start and Stop Here When You Can

Everything verifiable begins at paizo.com. Paizo's official FAQ and errata page (paizo.com/pathfinder/faq) is the canonical document for all rules changes. Published errata apply to the core rules unless the post explicitly limits its scope. When you land on the FAQ page, look for the tagged entries first: Paizo formats them by book and printing, for example "Rival Academies (Spring 2025, 1st Printing)," which tells you exactly which physical copy is affected and when the change took effect.

The Paizo blog (paizo.com/blog) is your second mandatory bookmark, specifically the errata tag. Seasonal posts go live here before anywhere else, and unlike the FAQ page's dry amended text, the blog posts include the design reasoning behind each change, with walkthrough examples for rulings that generated community confusion. Bookmark the errata tag directly rather than the blog homepage so every seasonal drop surfaces immediately.

The Spring 2026 errata post covers Player Core, GM Core, Player Core 2, and Guns & Gears (Remastered), and also includes one Spellstrike change from the Pathfinder Secrets of Magic errata that dates to Fall 2024. That kind of reach across multiple books in a single post is exactly why checking the errata tag regularly matters more than any secondhand summary.

Tier 2: Corroborating Sources — Cross-Check Here

Archives of Nethys (2e.aonprd.com) is the community's canonical compendium for searchable rules content and quickly indexes official errata and new releases. It mirrors Paizo's official entries for spells, feats, creature stat blocks, and class features, and adds the navigation infrastructure the PDFs lack: full-text search, printer-friendly formats, and version timestamps on updated entries. For most tables, it's the fastest path from "I need to look this up right now" to a usable answer.

The practical workflow is simple: errata drops on paizo.com, you read the summary blog post for context, then you immediately cross-check the specific affected entries on Archives of Nethys for the clean updated text. If both sources agree, you have your ruling.

Paizo sometimes follows errata with clarifying blog posts or Paizo Live segments when a change requires further discussion. If an errata stirs community questions, particularly around rulings on damage, weakness, and resistance, Paizo may publish follow-ups or highlight the change in a Paizo Live. These recordings don't generate binding errata on their own, but they provide designer intent that resolves ambiguity when the official text alone still leaves a gap.

The Five-Step Table Workflow

When a rules question lands mid-session or a new errata post drops, run this sequence in order:

5. For sanctioned events, check organized play guidance separately. This step has its own dedicated resource (below) and should never be skipped for Pathfinder Society or convention games.

Stop-point rule: If steps 1 and 2 give you matching, unambiguous text, stop. You have your ruling. Only continue down the list when the official text is still unclear or when event legality is in question. The goal at the table is a fast, confident call — not a research session.

Tier 3: Community-Only Sources — Useful, Not Binding

Discord servers, forum threads, optimizer guides, and Reddit discussion belong in this tier. They're rich with practical insight and often catch edge cases before official errata addresses them. But community consensus is not a ruling. When a forum thread and an errata post conflict, the errata post wins. Use Tier 3 to generate options and find likely interpretations; verify anything you plan to carry into an event against Tier 1.

Organized Play: Lorespire Is a Separate Bookmark

If you run or play Pathfinder Society, Paizo's Lorespire site now serves as the definitive, continuously updated resource for Pathfinder Society organized play, consolidating the Guide to Organized Play, character creation rules, GM tools, welcome kits, conversion guidance, and an up-to-date changelog. Lorespire is the place to confirm what is legal in organized play, download registration and reporting tools, and find onboarding materials for new participants.

The site contains the Complete Guide to Organized Play with the Core Guide, Player Options, GM Options, and Supplemental Materials all available in one place. The guide's version changelog is essential reading for active GMs: the guide moved from version 6.04 to 7.00 on October 5, 2025, then to 7.01 on October 6, then to 7.02 on February 22, 2026. Each changelog entry specifies exactly what changed, so you can audit the delta rather than re-reading the whole guide.

The Pathfinder Roleplaying Game is a living game, meaning sometimes game elements change over the course of a PC's career. However, if you begin playing an adventure before the effective date of a rule change, you are not required to use the updated rules for that play of the adventure. That protection requires you to know when you started, which means dating your session notes carries more practical weight than most GMs realize.

VTT Platforms and the Update Lag Problem

Demiplane Nexus, the Foundry VTT community PF2e system, and Roll20 all update on different cadences than Paizo's errata calendar. When Paizo publishes a seasonal post, these platforms take variable amounts of time to reflect the changes. Assuming your VTT's stat block is current because the errata is live is one of the most common ways tables end up running outdated rules.

After any Paizo errata drop, check your platform's own changelog or patch notes before running sessions that involve the changed rules. Demiplane publishes platform-specific rule update notes through its patch note blog. The Foundry community PF2e system maintains its own version log updated by its maintainers. Neither updates instantly, but both give you a verification path. For events specifically, keep a versioned local copy of the rules text referenced in your event listing, and flag any version discrepancy for players in advance.

Building Your Update Stack

The goal is passive monitoring, not manual daily surveillance. A minimal stack covers three habits:

• Subscribe to Paizo's blog RSS or JSON feed and filter for "errata" and "organized play." Feed readers like Feedly or NetNewsWire push new posts the moment they go live, so seasonal drops land in your inbox without any manual checking.
• Bookmark paizo.com/blog/tags with separate saved links for the Spring Errata and Fall Errata tags. Paizo's social accounts (and the PF2e community Discord servers) will surface major drops quickly, but the tag bookmark is your verification layer.
• When an errata post lands, immediately save an offline snapshot or export a PDF copy of the relevant FAQ text. Access problems mid-session are common enough that a local backup eliminates real-table delays.

One session lost to a rules dispute you could have resolved in two minutes is one too many. The Spring 2026 errata cycle reached across four books and pulled in a fifth retroactively; the next cycle will do something similar. The tables that stay current are the ones that built this system before they needed it, not after.