PF2e Monster Core 2 Guide: Dragons, Fiends, Undead, and High-Level Threats

Introduction

Monster Core 2 is the second Remastered monster book for Pathfinder 2e, and it is a GM toolbox first. It adds over 300 monsters: eight new dragon lines, a wide spread of outsiders and fiends, undead from a level -1 severed head to the level 21 ravener, troops and swarms, and campaign-ending titans and Spawn of Rovagug. It also carries an ability glossary, creature traits, rituals, languages, and indexes by type and level.

This guide does not copy stat blocks. It covers what the book adds, how each family changes your prep, which rules it tests, what players can do about it, and where it belongs in a campaign. The dragon, fiend, undead, and high-level sections below go deep; troops and swarms get their own rules page because their mechanics need more room.

Use this page with the main PF2e guide index, Monster Core hub, GM guide, encounter building, adjusting encounters, custom monsters, creature traits, stat blocks, creatures by level, summoned creatures, and rituals.

What This Guide Covers

Start with the book overview and the prep method, then jump to the family you need tonight:

• Dragons: the eight new lines, their magical traditions, lairs, negotiation, and counterplay.
• Fiends and pacts: seven fiend families, the four pact rituals, bargains, and combat pressure.
• Undead: the death story, vitality and void, scene templates, and tuning.
• Troops and swarms: a short summary here, with the full rules in the Monster Core 2 troops and swarms guide.
• High-level threats: titans, Spawn of Rovagug, ancient dragons, and how to earn a level 24 finale.

What Monster Core 2 Adds

Monster Core 2 is not power creep. It is a fix for boredom creep: more ways for the next fight to stop feeling like the last fight in a new hat.

How To Use The Book

Do not start at page one and try to memorize every monster. Start with the encounter job.

Prep notes should answer four questions. What does the monster want? What does the room do? What clue can players read before initiative? What happens if the party does not solve the problem with damage?

Monster Family Review

Family matters more than level for campaign feel. A level 8 hag encounter and a level 8 dinosaur encounter are not the same meal with different garnish.

Dragons

Monster Core 2's dragons are one of the most useful parts of the book because they are not reskins of familiar elemental dragons. Each line comes in young, adult, and ancient versions, and each points at a different kind of story. Treat them as campaign forces, not stat blocks with wings: pick a theme, build a lair and objective around its territory or motive, give the party clues, and decide whether the dragon fights, bargains, retreats, or comes back.

The Eight Dragon Lines

Blue marks a top pick for most campaigns; green marks a strong pick for the right campaign.

Dragons By Magical Tradition

Every Remastered dragon carries a tradition trait, and that trait answers prep questions a stat block cannot: what the dragon wants, what has changed around its lair, which clues reach the party first, and what a sensible retreat or bargain looks like. Monster Core 2 has two dragons per tradition, and Monster Core adds eight more you can mix in.

Do not turn traditions into personality cages. An individual dragon can be cruel, generous, petty, curious, or practical. Use the tradition as a scene engine, then give this dragon one concrete want the party can discover and affect.

Arcane dragons work best when magic changes how the party approaches the place. A phase dragon turns a chase, a missing traveler, or a broken teleport route into the mystery. A rune dragon turns wards, inscriptions, and a library into the dungeon. Give players a pattern they can learn, such as a ward that fires only near one threshold, and let that knowledge shape the final scene. A dragon with strange movement should have an escape route a careful party can anticipate.

Divine dragons gain weight from obligation. Requiem and resurrection dragons put death, recovery, and the line between them at the center of the campaign question. The prep question is not "Which side is this dragon on?" It is "What does it believe it must do?" A dragon may protect a guilty settlement from a worse threat, or demand the heroes decide who deserves a second chance. Social characters then have evidence to find, and every player keeps a decision that still matters if combat starts.

Occult dragons are excellent when the party meets the dragon's influence before its claws. A whisper dragon can make a city, manor, or archive feel watched. A false witness, a missing page, or an ally who knows too much does more work than an unexplained ambush. Keep the mystery fair: decide what the dragon knows, what it hides, and one clue a careful party can verify. Combat should resolve a situation the players already understand.

Primal dragons are strongest when the terrain stops being a painted backdrop. Start with a local change people can name: fishing boats do not return, ash ruins crops, a nesting ground is stripped. The final encounter now has an objective. The party may need to rescue people, stop a rival exploiting the disaster, cross the lair without wrecking it, or prove they are not the threat the dragon assumes.

For player-facing dragon options, see the Kobold guide, Sorcerer guide, spell guides, and archetype guides.

Dragon Level Bands

Monster Core 2 gives enough dragons to pace an arc without repeating the same fight three times.

The book notes that any dragon of at least level 13 can become a ravener. That makes a surviving adult villain a plausible late-campaign return.

Dragon Lairs By Theme

Dragons deserve rooms that think like they do. A blank square chamber turns an iconic creature into a large target.

Use hazards sparingly here. A dragon plus a full hazard suite is too much if the party has no information path. Use hazards as clues, not just punishment.

Negotiation Before Initiative

Dragons are usually intelligent enough to want things. Even predatory dragons can have territory, pride, offspring, tribute, grudges, magical projects, debts, or rivals.

Do not make every dragon reasonable. Do make every dragon legible. A dragon that refuses to bargain should still have a motive the party can understand.

Dragon Counterplay

Dragons are strongest when they make the party use the whole rules engine. PF2e dragons should make players ask, "Which defense are we attacking?" If the answer is always AC, the fight is leaving design space unused.

Player Core 2 adds clean story hooks. Dragonblood characters make lineage personal, and kobolds give the dragon cultural stakes. Sorcerers care about tradition and bloodline. Champions and Oracles care when the dragon's theme touches holy, unholy, oaths, or prophecy. Monks and Swashbucklers need maps with enough room for movement to matter.

Dragon Encounter Blueprints

Use encounter building for the math, then add dragon procedure. Put damage patterns, missing livestock, altered weather, or strange treasure in earlier scenes. Give the dragon a reason to fly, swim, hide, perch, phase, or retreat. Pace treasure with GM Core, because dragons pull wealth and magic items into the story. Elite and weak adjustments work for small shifts; use creature-building guidance when a big level change would alter the dragon's role.

If the party can solve a dragon fight only by standing still and trading Strikes, the encounter is underbuilt. Pull in three-action economy, flanking and positioning, conditions in combat, and runes when you build it.

Fiends And Pacts

The fiend coverage is a major campaign tool. Use it for cult arcs, planar bargains, cursed armies, corrupt courts, fear stories, torture horror, and enemies whose threat continues after initiative ends. The families do not all want the same thing, and treating every fiend as "evil thing attacks" is the fastest way to flatten the book.

Fiend Families

Monster Core 2 covers seven fiend families. Blue marks a top pick; green marks a strong pick for the right campaign.

Devils are not automatically the best fiends. They are the easiest to write badly, because "contract villain" can turn into a smug spreadsheet with claws.

Fiend Level Spread

Monster Core 2 supports fiends across the whole campaign, from level 1 dorus (divs), esipils (sahkils), augurs (velstracs), and ostovites up to level 20 eremites (velstracs), kimenhuls (sahkils), and bikkhasuras (asuras). Fiends can appear as signs, agents, patrons, bosses, and final consequences instead of waiting for one late planar chapter.

Do not list every stat block in your prep. Write the fiend's hold over people, what it wants, what it offers, and what it does if refused.

Fiend Encounter Roles

This is where encounter use matters. A fiend's role should change the choices on the table before anyone rolls damage.

Pact Rituals

Monster Core 2's rituals appendix includes four fiend pacts: daemonic, demonic, div, and diabolic. All four are uncommon and unholy, take a day to cast, and use Religion as the primary check. The key limit is the caster: each pact requires a fiend of that kind (the daemonic pact also allows urdefhans). A mortal cultist cannot just read one aloud.

That makes the pacts setting evidence rather than a player menu. A fiend calls in lesser fiends as a favor, and a cult led by a fiend can suddenly field more of them. The favors create debts between fiends that the party can learn about and exploit.

Contracts, Bargains, And Bad Deals

A fiend bargain should be playable, not just theatrical. The party needs enough information to make a bad choice knowingly.

Use social encounters, GM subsystems, and skill check DCs when a fiend plot needs more structure than one Diplomacy check. GM Core's influence, reputation, and research rules suit fiends better than a bare persuasion roll: a devil's bargain, a sahkil fear arc, or a div sabotage plot should have stages, pressure points, and fallout. The fiend's best attack is usually not in its stat block. It is the choice that makes a decent character consider doing something ugly.

Fiend Combat Pressure

Fiend fights should still be good fights. Let the family's theme shape the battle.

GM Core keeps fiends fair. Decide whether the fiend is the fight, the boss behind its support, or the patron behind the fight. Turn ritual circles, torture devices, cursed altars, and prison seals into interactive hazards. Let rewards include rescued people, broken contracts, purified sites, and safer roads, not only loot. Tie the pressure to conditions in combat, hazards, and adjusting encounters.

Fiend Counterplay And Class Hooks

Spellcasters should look at divine spells, occult spells, and rituals. Martial characters should care about runes, consumables, movement, and conditions. For cult structure, see secret societies and cults.

Undead

Monster Core 2 expands undead across mindless corpses, cursed warriors, ancient vampires, incorporeal hatred, draconic death, and void-born horrors. Not every undead scene needs to be a graveyard with three skeletons and the emotional range of a mop bucket. Run undead from the death story outward: who died, what remains unfinished, what the undead wants, and what the party can learn or release.

Undead Types In Play

Blue marks a top pick; green marks a strong pick for the right campaign.

Zombies are not boring. Boring rooms full of zombies are boring. Put the same zombies in a burning hospice, a flooded crypt, or a collapsing courtroom and everyone has opinions.

Undead Level Spread

Undead stop feeling thin when the GM knows what the corpse remembers.

Undead Scene Templates

Use social encounters, GM subsystems, and hazards when the scene needs more than a fight.

Vitality, Void, And Undead Counterplay

Player Core makes vitality and void central to how living and undead creatures interact. Explain that before it causes a table surprise. Holy and unholy sanctification makes undead scenes more specific than the "use radiant damage" habit from other games. Undead pressure is scarier, and fairer, when the party understands dying, doomed, drained, frightened, and recovery checks; see dying and recovery and conditions.

If the only counterplay is "hope the Cleric prepared the right answer," the encounter is too narrow.

Undead Class And Ancestry Hooks

Dhampirs need a healing conversation before the fight. They are living characters with undead-adjacent rules friction, so do not surprise a player mid-combat with how vitality and void work on them at your table. Duskwalkers make undead stories personal because their psychopomp connection pushes against unfinished death. Both heritages are in Player Core 2.

Undead GM Tuning

Before the session, answer five questions: who died, why they are still here, what releases them, what makes them worse, and what the party learns from the encounter. Then use the table below to set difficulty. Try adjusting encounters before changing monster math; undead already pressure healing, damage types, and conditions, so a small environmental shift is often enough.

Troops And Swarms

Troops and swarms are the book's reminder that not every combat should be a duel against a single stat block. They change target selection, damage types, movement, chokepoints, and party formation. A troop fills several 10-foot segments and loses segments as its Hit Points cross thresholds, and area abilities hit it far harder than single-target ones.

Troops and swarms are underused because they demand different player tools. That is the reason to use them. The full mechanics, rankings, and garrison scenes live in the Monster Core 2 troops and swarms guide, including troop and garrison jobs. Pair it with battle magic, combat spells, skirmish warfare, and war campaigns.

High-Level Threats

Monster Core 2 includes campaign-ending monsters: ancient dragons, the shoggoth, the ravener, titans, the green man, and Spawn of Rovagug. These are not "drop into room 7" monsters. Run them as campaign events: establish stakes and foreshadowing, give players usable clues, build terrain and several objectives into the finale, and plan the aftermath before initiative. At high levels the question is not "what number is printed?" It is "why has the campaign bent around this thing?"

High-Level Threat Types

Blue marks a top pick; green marks a strong pick for the right campaign.

High-level monsters are not harder because they have bigger numbers. They are harder because every wrong assumption should cost the party time, position, allies, or options.

High-Level Level Anchors

Use the levels to understand story scale, not to copy stat blocks.

If the party first hears about a level 24 monster when initiative starts, the GM skipped the good part.

Foreshadowing Clock

High-level threats need warning signs. Use a clock that escalates across sessions so the final encounter feels earned. Monster Core 2's own advice on Spawn of Rovagug points the same way: surviving one should be the culmination of several adventures spent researching it, gathering allies, and dealing with the disasters its approach sets off.

Build the arc backward from the finale. Decide what the threat already changed, such as an evacuated city or a broken army. Decide who knows the truth: scholars, envoys, survivors, or rival villains. Then pick the early clues and what makes the final fight playable, whether that is terrain, allies, rituals, weak points, or an evacuation. Use adventure hooks, subsystems, and skill check DCs to structure the research and approach.

Finale Shapes

Not every capstone is "kill it in its room." The Spawn of Rovagug entry itself notes that a Spawn can be banished, imprisoned, or transported away to save a region, which makes the alternatives below part of the design, not a GM workaround.

If the only win condition is "reduce the solo monster to zero," every non-damage character gets pushed to the edges. PF2e has too many tools to waste them that way.

Mythic Or Not?

War of Immortals and the mythic guide are optional. A Monster Core 2 high-level threat can be legendary without mythic rules. Use them when the story is about mythic callings, destinies, deeds, Mythic Points, and divine-scale escalation. Use normal high-level play when the story is about expert adventurers facing an extreme creature inside ordinary PF2e procedure.

High-Level Encounter Prep

High-level encounters punish vague prep. GM Core gives the structure, and severe and extreme encounters, hazards, subsystems, and victory conditions matter more because mistakes are bigger.

Elite and weak adjustments are fine for small changes, but ability-heavy high-level monsters can break if scaled casually. For a big level change, GM Core creature-building guidance is the cleaner tool. This is where encounter use, hazards, and custom monsters do real work.

Party Prep For The Endgame

A high-level monster should reward the preparation the party did, not ignore it.

Class texture helps. Champions and Oracles make divine stakes personal. Barbarians and Monks need terrain that lets commitment and movement matter. Investigators need clues before the final roll. Sorcerers and Witches need magical identity to matter. Battlecry! Commanders and Guardians can turn a high-level threat into a battlefield event instead of an isolated duel. Use consumables, runes, spell guides, and treasure by level for the party side.

Aftermath Design

If the aftermath is less interesting than the fight, the threat was too small for the campaign slot.

Player Counterplay

Players should not read Monster Core 2 for stat-block spoilers, but they can learn the system habits that keep monsters from being mysterious in the wrong way.

Best player links: conditions, conditions in combat, actions and activities, three-action economy, reactions, movement actions, battle magic, and utility spells.

Core Book Context

Monster Core 2 expects the rest of the Remaster rules to do their jobs.

Encounter Templates

What To Skip Or Delay

Copyright-Safer Coverage

This page summarizes purpose, family role, encounter design, campaign use, player counterplay, and related rules. It does not reproduce stat blocks, level tables, ability text, full creature lists, ritual text, or long lore passages, and creature levels appear only as broad review context. Keep Monster Core 2 at the table for the mechanics.

That is also better GM advice. A copied stat block tells you what a dragon can do. A guide should tell you why the dragon is in the story. The GM already bought the stat block; what they need is help making the monster matter.

Best Links

Start from the PF2e guide hub, then use Monster Core guides, monster families, encounter use, creatures by level, creature traits, the troops and swarms guide, encounter building, hazards, Religion, Occultism, equipment, and spell guides.

Hot Take: Monster Core 2 is best read sideways, by problem instead of A to Z. The best monster prep is motive, terrain, clue, complication, and exit condition, and a dragon that only waits in a square room, or a fiend whose only scary part is the damage number, has been demoted to furniture.