Kingdom Building

GM Reference

Kingdom play changes the campaign scale. Once the table starts tracking a realm instead of a party, every decision takes longer, every project has political weight, and every turn can pull attention away from the adventure if the group is not aligned on what kind of campaign it wants to run.

Use this page for table guidance. If you want the full optional subsystem with build points, monthly turns, terrain improvements, buildings, events, and edicts, use Variant Rules → Kingdom Building.
Kingdom Play Usually Helps When…
  • The party explicitly wants to govern land, not just visit it
  • The campaign includes seasons, projects, and meaningful downtime
  • You want the realm itself to become a strategic resource and story engine
  • The table enjoys logistics, planning, and shared civic decisions
Handle Carefully When…
  • The group mainly wants fast-moving character-focused adventures
  • Only one player cares about ruling while the others tune out
  • The campaign lacks downtime windows to resolve kingdom turns cleanly
  • You have not agreed whether failure should hurt the kingdom, the PCs, or both

What the GM Should Decide Before Using It

  1. Campaign scope. Is the kingdom game the campaign spine, a periodic subsystem, or just a backdrop for adventure arcs?
  2. Turn cadence. Decide how often kingdom turns happen in real play and who is responsible for bookkeeping between sessions.
  3. Authority model. Clarify whether rulership decisions require unanimous party consent, delegated roles, or one primary ruler with table consultation.
  4. Failure pressure. Decide how hard the subsystem should bite. Some tables want real collapse risk; others want setbacks that generate quests instead of destroying the campaign.
  5. Adventure integration. Know in advance how kingdom events turn into scenes, missions, NPC conflicts, and domain-level consequences.

A Practical Table Stance

Treat kingdom turns as a structured campaign layer, not as the main performance unless the table explicitly signed up for that. Resolve routine bookkeeping quickly, surface only the decisions that matter, and turn the rest into consequences, rumors, opportunities, and crises that send the party back into active play.

  • Abstract the boring parts. If a choice does not create drama, summarize it and move on.
  • Spotlight the kingdom through people. Advisors, guild leaders, rivals, petitioners, and border threats keep the realm personal.
  • Let success change the map. New roads, stronger allies, safer trade, and bigger obligations should all be visible in play.
  • Convert systemic failures into adventures. A food shortage, unrest spike, or diplomatic break should produce scenes, not only penalties.

Suggested Workflow for Running It

1. Set the Domain Lens
Establish what the kingdom currently needs: safety, food, legitimacy, expansion, trade, or recovery.
2. Resolve the Turn Fast
Handle the subsystem cleanly and note only the pressures, gains, and open problems that actually matter.
3. Pull Out the Drama
Choose one or two turn results to become scenes, hooks, or consequences the players can engage directly.
4. Return to Adventure
End the domain pass with a clear next problem, mission, or political choice instead of more paperwork.

Best Supporting Pages

GM Guidance
Optional Mechanics
Best practice: decide up front whether kingdom play is a strategic minigame, a narrative frame, or a periodic administration layer. Most problems with domain play come from mismatched expectations, not from the rules themselves.