A twenty-level Adventure Path is a memory problem long before it is a rules problem
The honest version, same as our Daggerheart page: this product was built around D&D and two of its prompts say so in plain text. None of it reads a rulebook, so a Pathfinder session goes through the same pipeline and comes out the same shape. The part worth your attention is which proper nouns need protecting, because for a Golarion game it is not the ones you might expect.
The problem
An Adventure Path runs from level 1 to level 20 across a year or three of real time, and the book only holds half the canon — the other half is what your table did to it: the NPC they spared who was supposed to die, the name the alchemist made up for the tavern, the favour promised in book two that matters in book five. There is no page to check for any of that. By the time someone asks, the answer lives in a recording nobody is going to re-listen to, or nowhere.
Nothing in the pipeline is rules-aware
Worth stating exactly, because Pathfinder players are used to tooling that knows the rules. This does not. Transcription turns speech into text; extraction pulls out the people, places, items and factions that were mentioned; the recap summarises what happened. No step counts actions, tracks conditions, or knows a critical success from a failure. Degrees of success live in your VTT and at your table, not here.
The upside of that indifference is that nothing breaks either. A PF2e session transcribes, its NPCs and locations land in the wiki, the recap reads like a recap, and you can ask questions about your own campaign afterwards — exactly as for D&D, Daggerheart, Call of Cthulhu or homebrew.
What the product does not do is also unchanged by system: no character sheets, no dice, no maps, and no speaker labelling — the transcript does not say who spoke.
Two prompts say "D&D", and what that costs a Golarion game
In two places the AI is told, in so many words, that it is looking at a D&D game: the transcription prompt opens "A Dungeons and Dragons tabletop session", and entity extraction asks for entities from a "D&D session transcription" before categorising what it finds dynamically from context rather than against a fixed D&D list. We would rather show you that wording than have you find it later.
For a fantasy game the prefix mostly helps anyway — it tells the model to expect invented proper nouns rather than meeting vocabulary. And names that have been in print for two decades tend to survive transcription better than a name invented last Tuesday. The nouns that need protecting in a Pathfinder game are usually yours, not Golarion’s: the NPCs your table coined, the renamed terms your group uses, the way your players actually pronounce the ones from the book.
The glossary carries your table’s canon, not the book’s
Each campaign has a glossary you control, fed into transcription ahead of every session. Put the proper nouns your table actually says in it — your invented NPCs, the AP’s recurring cast, anything the transcription keeps mangling — and they come back spelled consistently instead of phonetically.
It takes pronunciation hints too, rendered like "Wendelbrie (WEN-del-bree)", which matters for a setting whose names people say six different ways at one table. There is a budget — roughly 850 characters reach the model, because the transcription API honours about the last 224 tokens of a prompt — so it is a list of your most-confused names, not a gazetteer. The Whisper guide has the underlying detail.
Adventure Paths are where the continuity tools earn their keep
A campaign that runs for years is exactly the case the rest of the pipeline was built for. The wiki accumulates every named person and place with the session they first appeared in; the timeline shows the whole run in order; and Ask Your Campaign answers "what did we promise the Lacunafex in book three" with a citation to the session where it happened.
The book knows what was supposed to happen. Your transcripts know what did. For a table that deviates from an AP — which is every table — the second record is the one you cannot buy a PDF of, and it is the one this builds (how the wiki assembles itself).
The numbers, with sources
| What | Value | Source |
|---|---|---|
| Pathfinder — publisher and edition | Paizo Inc.; the current edition is Pathfinder Second Edition | sourceas of 2026-09-07 |
| Pathfinder — how it describes itself | "a fantasy tabletop roleplaying game where you tell heroic tales in a world of quests, magic, monsters, and treasures" | sourceas of 2026-09-07 |
| Pathfinder — free rules reference | Paizo’s own page points players to the Archives of Nethys, a free official online rules reference | sourceas of 2026-09-07 |
| Pathfinder Society | Paizo runs an organized-play program of episodic scenarios under this name | sourceas of 2026-09-07 |
How we sourced this: The Pathfinder rows above come from Paizo’s own site and cover who publishes the game and what it is — nothing more. This page makes no claim about how PF2e’s mechanics work, because describing rules from a marketing page is how confidently wrong pages get written. Everything said about DM Scribe’s own behaviour — the two D&D-worded prompts, dynamic categorisation, the glossary, pronunciation hints and the 850-character budget — was read from this product’s source code.
This is not for you if…
Same test as every page in this cluster: what decides it is how your table plays, not which rules it uses.
- You want rules automation. Degrees of success, conditions, the action economy — that lives in your VTT, and this never will. It handles what was said, not what was rolled.
- Your Pathfinder is Society play. Episodic four-hour scenarios with rotating tables have little long-run continuity to lose; this earns its keep across a campaign.
- You do not record your sessions and do not want to start. Everything here is built on a recording.
- Your table is play-by-post. Every plan imports text transcripts (two a month free, ten on Dungeon Master, unlimited on Guild Master), but a text-first campaign is not what this is shaped around.
Other ways people use this
- Actual play and podcast crews
Actual play crews already have clean multitrack audio. Turn it into show notes, a searchable archive and accessibility transcripts.
- Professional and paid GMs
Running paid games for several tables means the worst continuity problem in the hobby — and a business reason to solve it. How the notes help.
- West Marches and open-table campaigns
Twenty players, rotating parties, one shared world — and nobody who was at every session. A shared record is the format’s missing piece.
- Daggerheart tables
Nothing in the pipeline is rules-aware, so Daggerheart transcribes and extracts like any other game. The prompts say D&D. Here is what to do about it.