The Ghost in the Bestiary: The Pathfinder Monster That Doesn't Exist
If your Pathfinder 1e druid wants to summon a Black Bear, or your ranger wants one as an animal companion, your first instinct is to pull open the Pathfinder RPG Bestiary and flip to the "B" section.
Go ahead and try. You won't find it.
There is no entry for "Bear, Black" in the print book. There is no custom artwork for one, no standalone stat block, and no CR 3 beast entry.
Yet, if you search the web, databases like d20pfsrd or Archives of Nethys have full, beautifully formatted Black Bear pages. So how does a core monster that thousands of players run every week not actually exist in the official book?
We ran headfirst into this puzzle while building out the compendium database for our publishing imprint, Mithril Destiny. Solving it taught us a lot about how tabletop rules behave less like static tables and more like dynamic, open-source code.
The Grizzly Math: Rules-As-Code
In print, Paizo saved space by publishing rules instead of raw data.
If you look closely at page 31 of the Bestiary, under the entry for the Grizzly Bear (a CR 4, Large animal), you will find a small line of instructions:
"To generate stats for a smaller bear (like a black bear), you can apply the young simple template to the grizzly bear's stat block."
Tabletop RPGs are built on these kinds of transformation functions. Instead of printing a Black Bear, the Bestiary gives you a formula:
Black Bear = Grizzly Bear + Young Simple Template
Applying the Young simple template to a creature shifts its properties:
- Size: Decreases by one step (Large to Medium).
- Ability Scores: Strength drops by -4, Constitution by -2, Dexterity increases by +2.
- Defense: Natural armor drops by -2, and Armor Class recalculates for the smaller size.
- Combat: Damage dice scale down, and the Challenge Rating drops by 1 (from CR 4 to CR 3).
When d20pfsrd was built, the webmasters simply ran these calculations, formatted the resulting numbers into a standard monster template, and published the final pre-calculated "Black Bear" page as a convenience.
The OGL Puzzle: Who "Published" the Black Bear?
When my partner @ecoinstant and I were preparing our compendium database for publication, Eco raised a very real legal question:
"If we publish the pre-calculated Black Bear stat block on our site, are we the publishers? How can we be the publishers if d20pfsrd already has it, and Paizo never actually printed it?"
This is where understanding the mechanics of the Open Game License (OGL) 1.0a becomes essential.
To figure out who owns the "Black Bear," you have to trace its dependencies:
- The Math: Game mechanics and mathematical formulas cannot be copyrighted under US law. Even if they could, the Grizzly Bear stats and the Young Template are Open Game Content (OGC) owned by Paizo and shared under the OGL.
- The Flavor Text: If you read the description of the Black Bear on d20pfsrd, it talks about it being a "forest-dwelling omnivore" that is "rarely more than 5 feet long." Paizo didn't write that. It was copied verbatim from the D&D 3.5 System Reference Document (SRD).
Since Pathfinder 1e was built as a fork of D&D 3.5, the 3.5 SRD is an upstream dependency of the entire Pathfinder system. The d20pfsrd team simply grabbed the legacy 3.5 SRD description and merged it with the calculated Pathfinder 1e Young Grizzly stats.
Because every single component—the Grizzly base, the Young template, and the 3.5 description text—is Open Game Content, the resulting page is legally public domain (under the OGL). Nobody "owns" the Black Bear stat block. Anyone is free to distribute it, provided they attribute the upstream sources correctly.
Coding the Law: Automated Attribution
If you handle attribution manually, publishing even a simple beast companion becomes a nightmare of copying and pasting license agreements.
To solve this, we modeled OGL licensing as a resolver graph. In our database, the Black Bear is saved as core content, and its source field is linked to the Bestiary.
Behind the scenes, we built an attestation chain-walk. When the site generates its legal pages, the system automatically walks the reference chain. Because the bear is linked to the Bestiary, the platform automatically pulls the correct Section 15 copyright notices:
- Wizards of the Coast's System Reference Document (for the description).
- Paizo's Pathfinder RPG Bestiary (for the grizzly base and template math).
The code handles the compliance check, leaving the publisher free to focus on writing the game.
The Takeaway
The "bear incident" is a perfect example of why compiling a rules database isn't just a data-entry job. Tabletop RPG books are not flat spreadsheets; they are nested systems of rules, templates, and legacy codebases.
When your game rules are designed like code, your legal compliance has to be code too. By treating OGL licensing as a structured dependency graph, we can share classic fantasy beasts legally, cleanly, and automatically.
As always,
Michael Garcia a.k.a. TheCrazyGM
Mithril Destiny is our Pathfinder 1e publishing imprint. Emberbound is available at patreon.com/mithrildestiny, and the open layer of Gandurion surfaces free at thecrazygm.com.
Useful info - thank you ! So far I've mostly not had to worry because we're just playing 3.5 "in-house", which makes things much easier. But if I want to publish any D&D/Pathfinder content (or fiction even slightly based on it), this really helps.
Yes, an entire multi-verse lives inside google docs - unsure of how to tackle the legal minutia! We want any and all homebrew creators to be able to safely and confidently publish their content :)
!PIMP
El gran oso ...