Paizo Events Pages Serve as Canonical Hub for Pathfinder Sessions Jan 17-24

Paizo's public Events pages are serving as the canonical hub for Pathfinder Society (PFS) organized play listings during the Jan 17-24, 2026 week. The pages list numerous Paizo-run and store-organized sessions, and the Athoria Tempe OP event page, for example, shows session slots with games scheduled for Saturday, Jan 24, 2026. That centralization matters because it puts event numbers, scenario codes, session times, and venue locations in one place where GMs and players can plan tables and sign up.

Each event entry includes the core metadata gamemasters and players need to run or join a session: event number, scenario code, start and end times, and the location. Organizers are using the pages to publish which scenarios are running in each slot, so players checking for specific adventures or chronicle opportunities can quickly find matching tables. Convention organizers and local stores are also reflected alongside Paizo-run listings, which helps players track convention-run tables without hopping between different community calendars.

For players looking to book a seat or for GMs scheduling runs, the Events pages remove ambiguity. Players can confirm the exact scenario code and session time before arriving, which makes pregame prep and chronicle tracking smoother. GMs can rely on the public listing to advertise table details and avoid conflicts with other local events. That practical value is especially relevant on days like today, Jan 24, when multiple sessions are live and availability can shift rapidly.

Community workflows benefit as well. Players hunting for a particular scenario or trying to hit a chronicle milestone can search event pages for matching session codes rather than relying on word of mouth. Stores and convention organizers can publish full slot details to guide badgeed players and walk-ups. The centralized listings also help maintain transparency about which tables are official PFS runs, which is important for rewards, chronicle entries, and play tracking.

What this means now is straightforward: verify the event number and scenario code on Paizo Events before committing to a table, check session times to avoid double-booking, and use the event listings as the primary source for whether a run is Paizo-run or store-run. Expect organizers to update listings as seats fill or scenarios change, and treat the Events pages as the first stop when planning play for the coming week.