Domain Play and the Quest for Meaningful High-Level Gaming

TTRPG Design Discourse: Article 10 of 14

From hexcrawling’s exploration of wilderness, we ascend to kingdom-scale play. Most campaigns die at mid-level because designers don’t know what to do with demigod-level characters. Domain play—transitioning from adventurers to rulers—represents the lost endgame. We examine why it disappeared, why it matters, and how modern designs are reclaiming it. This synthesis draws on everything we’ve discussed: player agency at institutional scale, tactical complexity in mass combat, and magic systems that reshape nations.

In the vast majority of tabletop RPG campaigns, there exists an invisible ceiling—a level, usually somewhere between 8 and 12, where campaigns quietly end. Characters retire, groups disband, or the campaign simply fades into “we should really get back to that someday” limbo. Industry surveys consistently show that while games like Dungeons & Dragons provide rules for characters reaching level 20, fewer than 5% of campaigns ever reach double-digit levels, and virtually none play through to the mechanical endpoint.

This isn’t an accident, and it isn’t simply a matter of campaigns naturally concluding their stories. It’s a fundamental design failure that has plagued the hobby since its inception: most RPG systems have no idea what to do with high-level characters.

The problem is straightforward: RPGs are extraordinarily good at modeling personal adventure—a band of scrappy heroes delving into dungeons, fighting monsters, and claiming treasure. But as characters grow in power, this paradigm breaks. A 15th-level wizard who can teleport across continents, reshape reality, and level armies isn’t having “adventures” in any traditional sense. They’ve transcended the scale that dungeon-crawling rules were designed to handle.

Enter domain play—the concept that high-level characters should transition from adventurers to rulers, kingdom-builders, military commanders, and shapers of nations. Instead of looting dungeons, they’re founding dynasties. Instead of fighting individual monsters, they’re managing armies, economies, and political intrigue. The game shifts from tactical to strategic, from personal to institutional.

When executed well, domain play provides campaigns with a satisfying endgame where characters’ accumulated power finds meaningful expression. Players experience genuine progression—not just bigger numbers, but qualitatively different challenges appropriate to their godlike abilities. The campaign achieves narrative closure as murder-hobos become the makers of history.

When executed poorly—or more commonly, when not attempted at all—high-level play becomes an exercise in absurdity. Twentieth-level characters still raiding dungeons for gold pieces, still threatened by random encounters, still operating within frameworks designed for 1st-level nobodies. The mechanical power curve has outpaced the fiction, creating tonal dissonance that drives campaigns to their premature deaths.

This essay examines the history, mechanics, successes, and failures of domain play across five decades of RPG design. From its origins in wargaming through its abandonment in the modern era to its current renaissance in the OSR movement, domain play represents both the ultimate expression of character progression and one of design’s most persistent unsolved problems.

The Historical Context: D&D’s Lost Endgame

Domain play isn’t a modern innovation—it’s baked into the hobby’s foundational DNA. Understanding this requires examining the assumptions of early Dungeons & Dragons design.

The Wargaming Roots (1974-1981)

Gary Gygax and Dave Arneson didn’t create D&D as a standalone game. They created it as an expansion to existing miniatures wargaming. The original 1974 D&D rules existed in dialogue with Chainmail, a medieval miniatures combat system. The assumption was clear: players would start with individual character-scale adventure (the “game” part of D&D), but would naturally graduate to mass combat, kingdom management, and large-scale warfare (the “wargame” part).

This is explicit in early materials:

Men & Magic (1974): “As he [the player character] rises in levels he will probably be anxious to increase his status by obtaining a ‘castle’ and men-at-arms.”

Greyhawk Supplement (1975): Introduced rules for character followers, stronghold construction costs, and territorial control.

Expert Set (1981, edited by Tom Moldvay): Formalized domain play with extensive rules for:

  • Stronghold construction (castles, towers, keeps)
  • Clearing wilderness hexes of monsters
  • Attracting settlers and establishing domains
  • Taxation and economic management
  • Hiring and maintaining military forces
  • Mass combat using the War Machine system

The progression arc was assumed to be:

  • Levels 1-3: Novice adventurers exploring dungeons
  • Levels 4-6: Experienced adventurers tackling greater challenges
  • Levels 7-9: Heroes establishing reputations, acquiring followers
  • Levels 10+: Lords establishing domains, managing territories, waging wars

The game was designed to transition scales. A 10th-level fighter wasn’t supposed to keep crawling through dungeons—they were supposed to build a castle, clear the surrounding wilderness, attract settlers, defend against invasions, and expand their territory.

The Companion and Masters Sets: Apotheosis of Domain Play

Frank Mentzer’s BECMI (Basic, Expert, Companion, Master, Immortals) D&D line (1983-1986) represented the most ambitious attempt to systematize progression from zero to godhood:

Companion Set (levels 15-25):

  • Detailed domain management rules
  • War Machine mass combat system
  • Siege warfare
  • Naval combat
  • Economic systems (trade routes, taxation, construction)
  • Dominion morale and loyalty mechanics
  • Kingdom events and disasters

Masters Set (levels 26-36):

  • National-scale play
  • Planar travel and extraplanar domains
  • Artifact creation
  • Building and ruling entire civilizations
  • Transitioning from mortal ruler to immortal sponsor

Immortals Set:

  • Ascension to godhood
  • Divine politics and cosmic warfare
  • Creating and managing entire worlds
  • Abstract resource management at universal scale

This was comprehensive. The Companion Set alone provided more detailed domain management rules than most modern games offer for anything. Players had procedures for:

  • Determining population growth rates
  • Calculating tax revenues based on terrain type and development level
  • Managing seasonal agriculture cycles
  • Recruiting and maintaining different troop types (cavalry, infantry, artillery)
  • Resolving sieges with siege engines and magical support
  • Handling diplomatic relations with neighboring domains
  • Dealing with internal revolts, economic downturns, and natural disasters

The systems were procedural—not narrative hand-waving, but mechanical simulation of running a kingdom. This created gameplay at a different scale but with the same concrete decision-making as dungeon exploration.

The Abandonment: Why Domain Play Disappeared

Despite these robust systems, domain play largely vanished from mainstream RPG design by the 1990s. Several factors contributed:

Time Scale Mismatch: Domain management operates on monthly or seasonal timescales. Traditional adventuring operates on daily or hourly timescales. Switching between them created awkward pacing.

System Complexity: Learning an entirely new subsystem (economics, mass combat, realm management) when characters hit high level was daunting. Many groups never reached that point, so the complexity went unused.

Campaign Length: Most campaigns didn’t last long enough to reach domain levels organically. Why invest design resources in content 95% of players would never use?

Narrative Preferences: The 1990s saw a shift toward character-driven storytelling (influenced by Vampire: The Masquerade and similar games). Building spreadsheets of tax revenue felt antithetical to dramatic character arcs.

Preparation Burden: GMs already struggled with adventure prep. Adding kingdom management, economic tracking, and mass combat was overwhelming.

Market Fragmentation: As RPGs diversified beyond fantasy, many genres (cyberpunk, horror, superheroes) didn’t have obvious domain play equivalents.

By the time D&D 3rd Edition (2000) arrived, domain play had been relegated to a sidebar. The DMG included optional rules for followers, strongholds, and organizations, but these were vestigial—vague suggestions rather than functional systems. The game’s mechanical focus was squarely on tactical combat from levels 1-20 using the same frameworks.

D&D 4th Edition (2008) went further, essentially eliminating domain play entirely. Character power scaled vertically (bigger numbers, flashier abilities) but never horizontally (broader scope of influence).

D&D 5th Edition (2014) provides almost nothing. The DMG has a few pages on “running a business” or “building a stronghold,” but these are narrative suggestions without mechanical weight. There’s no economic system, no mass combat rules, no procedures for managing territories. High-level play in 5E is simply mid-level play with larger hit point pools and save-or-suck spells.

The Design Challenge: Why High-Level Play Breaks

To understand why domain play matters, we must understand why high-level play without domain systems fails. The problems are both mechanical and conceptual.

The Power Curve Problem

RPGs use numerical progression to represent character growth. This creates an exponential power curve that breaks verisimilitude:

Level 1 Fighter: 10 HP, +3 to hit, 1d8+2 damage (avg 6.5) Level 20 Fighter: 200+ HP, +11 to hit, 4d8+20 damage (avg 38)

The level 20 fighter is approximately six times more lethal and twenty times more durable than their starting self. But they’re still resolving challenges using the same mechanics—rolling to hit individual enemies, tracking individual hit points.

This creates absurdities:

  • A high-level fighter can survive being hit by dozens of arrows that would kill normal humans, but still takes the same action time to kill a single enemy
  • High-level characters accumulate wealth that could buy kingdoms but have nothing meaningful to spend it on
  • Characters who can fly, teleport, and reshape matter still spend sessions searching rooms for secret doors

The mechanics haven’t evolved to match the power level. The scale is wrong.

The Challenge Escalation Treadmill

The standard solution is enemy inflation: higher-level enemies with proportionally higher numbers. This creates several problems:

Treadmill Effect: A 20th-level character fighting 20th-level enemies feels mechanically identical to a 1st-level character fighting 1st-level enemies. The numbers are bigger, but the challenge ratios are the same. There’s no sense of progression.

Narrative Nonsense: The world must be populated with increasingly improbable threats. Why do ancient dragons conveniently exist at exactly the CR to challenge the party? Why are there so many godlike threats just waiting to be discovered?

Combat Slog: High HP pools + high damage = very long combats with predictable outcomes. A level 15+ D&D 5E combat can easily take 2-3 hours of real time to resolve 30 seconds of in-game action.

Diminishing Threat: When characters can teleport, scry, resurrect the dead, and reshape reality, most traditional threats become trivial. GMs must constantly invent new gimmicks to challenge abilities the game explicitly gives players.

The Superhero Problem

At high levels, PCs become superheroes—they’re no longer part of the world’s power structure but above it. A 15th-level wizard can:

  • Teleport anywhere on the planet instantly
  • Become invisible at will
  • Read minds and detect lies
  • Summon elemental servants
  • Reshape terrain
  • Raise the dead
  • Stop time

How do you threaten someone with these abilities using dungeon-crawling frameworks? The answer: you don’t. You either:

  1. Inflate opposition to absurd levels (every enemy is also a reality-warping superhero)
  2. Arbitrary negation (“this dungeon blocks teleportation because reasons”)
  3. Change the game to challenges appropriate to godlike beings

Domain play represents option 3.

Systems That Succeed: Case Studies in Domain Play

Some RPG systems have successfully implemented high-level play through domain mechanics. Examining their approaches reveals design principles that work.

ACKS (Adventurer Conqueror King System): The Gold Standard

ACKS (2012, designed by Alexander Macris) is explicitly built around the domain play progression. It’s considered by many OSR enthusiasts as the definitive solution to the endgame problem.

What ACKS Does Right:

Economic Simulation: The game includes a full economic system:

  • Markets have limited capacity (you can’t just sell unlimited gold in a small town)
  • Prices vary based on supply and demand
  • Trade routes provide ongoing income
  • Economic development can be player-driven (building mills, markets, workshops)
  • Taxation rates affect peasant morale and productivity

This makes wealth meaningful beyond number-go-up. Gold becomes a resource for building economic infrastructure.

Domain Management Procedures:

  • Monthly domain turns resolving seasonal events
  • Peasant morale system (overtaxation causes revolts)
  • Construction times and costs for infrastructure
  • Monster population dynamics (cleared dungeons refill over time unless domain controls the area)
  • Military unit recruitment, training, and maintenance costs

Mass Combat: The Domains at War expansion provides:

  • Strategic warfare (army movement on campaign maps)
  • Tactical battles (using miniatures with streamlined rules)
  • Siege warfare (with siege engines, sappers, and starvation)
  • Heroic forays (individual PCs can influence battles through targeted actions)

Integration: Crucially, domain play isn’t a separate game. It’s the natural continuation of adventuring:

  • Clearing dungeons makes surrounding hexes safe for settlement
  • Treasure from adventures funds domain development
  • High-level character abilities (magic, leadership) provide advantages in domain management
  • Domain positions (ruler, general, spymaster) align with character classes

Example Play Loop:

  1. Adventure: Party clears a dungeon, defeating the orc chieftain and claiming treasure
  2. Domain Impact: The surrounding hex is now safer; the domain can expand settlement
  3. Economic Development: Treasure funds building a fortified village in the cleared hex
  4. Population Growth: Settlers arrive, increasing tax base and providing recruits
  5. Military Expansion: New recruits allow fielding a larger army
  6. Strategic Conflict: Neighboring domain sees expansion as threat; war begins
  7. Battlefield Heroics: PCs lead armies in mass combat, using adventuring abilities strategically
  8. New Adventures: Victory brings new territory with undiscovered dungeons to clear

The loop is self-reinforcing and provides clear strategic goals beyond “find next dungeon”.

Why It Works:

  • Concrete procedures prevent GM paralysis (clear rules for domain actions)
  • Meaningful choices (invest in military vs economy vs infrastructure)
  • Risk and reward (expansion brings conflict; development takes time and resources)
  • Power scaling (personal abilities translate to strategic advantages)
  • Emergent stories (faction conflicts, economic competition, territorial wars)

Birthright (AD&D 2nd Edition Setting): Rulership as Core Gameplay

Birthright (1995) took a different approach: rather than domain play being the endgame, it’s the entire game from the start. Player characters are rulers of nations from 1st level.

Unique Mechanics:

Bloodline System: PCs descend from gods, granting supernatural abilities and the right to rule. This justifies why adventurers can be kings—they’re literally divinely ordained.

Domain Turns: The game uses seasonal domain turns separate from adventure time:

  • Spring: Planting season, military recruitment
  • Summer: Campaigning season, construction
  • Fall: Harvest, tax collection
  • Winter: Court intrigue, planning

Each season, rulers take domain actions:

  • Rule (manage holdings, adjust taxation)
  • Create (build temples, guilds, fortifications)
  • Contest (challenge rival’s control of provinces)
  • Diplomacy (forge alliances, trade agreements)
  • Espionage (spy networks, sabotage)
  • Research (magical research, artifact creation)
  • Muster (raise armies)

Regency: A resource representing divine mandate and political capital. Rulers spend Regency to take domain actions. Regency is earned through:

  • Controlling provinces aligned with your bloodline
  • Successfully managing your realm
  • Heroic adventuring (personal actions still matter)

Holdings System: Provinces contain different holding types:

  • Law (courts, guards, administration)
  • Temples (religious influence)
  • Guilds (economic control)
  • Sources (magical ley lines)

Multiple rulers can control different holdings in the same province, creating intricate political webs. The law holder might be opposed by the guild master, while the temple competes with a rival faith.

Integration of Adventure and Domain:

  • Adventuring earns Regency (needed for domain actions)
  • Domain conflicts create adventure hooks (investigate rival’s spy network, quest for artifact to break curse on realm)
  • Personal power augments domain (high-level wizard creates magical defenses for capital)

Why It Works:

  • Political complexity without overwhelming mechanics (holding system is elegant)
  • Player vs. player potential (PCs can rule rival nations with competing interests)
  • Multiple victory conditions (military conquest, economic dominance, religious conversion, magical ascension)
  • Integration of scales (personal adventures affect strategic position)

Why It Also Failed: Birthright had significant weaknesses:

  • Setting-specific: Mechanics tied to Cerilia setting; hard to export to other campaigns
  • Complexity frontload: New players had to learn domain rules from level 1
  • Balance issues: Some bloodlines and domain positions were vastly more powerful than others
  • Realm size disparities: PCs ruling empires vs. single provinces created power imbalances

Pendragon: The Generational Campaign

Pendragon (1985, designed by Greg Stafford) offers a radical solution: campaigns span generations. Characters age, marry, have children, and eventually die. Their heirs continue the campaign.

Domain Mechanics:

Manor Management: Every knight has a manor providing income. The winter phase involves:

  • Calculating annual income from lands
  • Paying expenses (equipment, servants, taxes)
  • Determining family events (births, deaths, marriages)
  • Making economic investments (building improvements)
  • Training and education

Glory and Renown: Instead of experience points, characters earn Glory through heroic deeds. Glory determines social status, marriage prospects, and political influence.

The Passion and Trait System: Characters have mechanical stats for virtues (Chaste/Lustful, Energetic/Lazy, etc.) and passions (Love of Family, Loyalty to Lord, Hatred of Saxons). These affect decision-making and create emergent character drama.

Generational Play:

  • Characters age in real-time (one game year per session is common)
  • At ~40-50, knights become too old for adventuring
  • Players create the heir (son, daughter, or other family member)
  • Heir inherits estate, Glory modifiers, and family reputation
  • Campaign continues across generations

Why It Works:

  • Time scale matches domain scope (managing estates happens across years/decades)
  • Natural retirement (characters age out rather than arbitrarily stopping play)
  • Legacy creation (your actions affect your heirs)
  • Historical scope (campaigns can cover the entire Arthurian period, 485-565 AD)
  • Emergent dynasties (family trees, inter-family marriages, inherited feuds)

Example: A campaign might begin with Sir Cadwallon in 485 AD fighting Saxons. By 510, he’s an aging lord with grown children. His son Sir Cadfael inherits the manor and fights in different wars. Cadfael’s daughter marries into another player’s family, creating alliances. By 540, the campaign features third-generation characters, with family histories affecting current play.

Domain as Character Sheet: The manor itself becomes part of character identity:

  • Manor improvements provide mechanical benefits
  • Estate reputation affects social encounters
  • Family members become NPCs who can assist or complicate
  • Library, chapel, and other buildings provide training bonuses

Legend of the Five Rings: Courtly Domain Play

L5R (1997) demonstrates that domain play doesn’t require vast territories—it works at the scale of clan politics and courtly intrigue.

Clan Allegiance: Characters serve Great Clans, each with territories, armies, and political agendas. Even low-level characters participate in clan politics.

Honor, Glory, and Status: Three separate social metrics:

  • Honor: Personal integrity and adherence to Bushido
  • Glory: Reputation and fame
  • Status: Political rank and authority

These create mechanical effects:

  • Status determines who you can socially influence
  • Glory affects first impressions and public perception
  • Honor affects dice rolls and supernatural protection

Court Conflict: Instead of dungeons, many sessions occur in Winter Court—months-long political gatherings where clans negotiate, scheme, and position themselves. Mechanics include:

  • Contested social rolls (persuasion, etiquette, manipulation)
  • Scandal and blackmail (discovering and exploiting secrets)
  • Gift-giving economics (building obligations and alliances)
  • Poetry contests and artistic displays (demonstrating culture and refinement)

Military Position: High-status characters command armies:

  • Mass battle system using character abilities to influence large-scale combat
  • Strategic deployment on campaign maps
  • Tactical duels (individual combats that determine battle outcomes)

Why It Works:

  • Domain play at personal scale (you’re influencing clan politics, not managing tax rolls)
  • Social systems with teeth (honor loss can force seppuku; status determines access)
  • Multiple challenge types (courtly intrigue, military command, spiritual quests, dueling)
  • Cultural resonance (samurai fiction naturally involves service to lords and clan warfare)

Systems That Fail: When High-Level Play Collapses

Understanding failure modes is as instructive as examining successes. Several major systems demonstrate how not to handle high-level play.

D&D 5th Edition: The Endgame Void

5E is phenomenally successful at levels 1-10. Beyond that, it falls apart.

The Problems:

No Domain Systems: The DMG provides a few paragraphs on “running a business” suggesting 2d20 × 5 gold per month profit. That’s it. No mechanics for:

  • Territorial control
  • Economic management
  • Mass combat
  • Political influence
  • Kingdom building

Vertical Scaling Only: Characters get numerically stronger but never shift in scope:

  • 20th-level fighters still swing swords at individual enemies
  • 20th-level wizards still track spell slots for personal-scale magic
  • Wealth accumulates with nothing meaningful to purchase (a +3 sword costs less than maintaining an army for a month)

Challenge Void: By level 15+, characters can:

  • Teleport anywhere
  • Resurrect the dead
  • True Polymorph into ancient dragons
  • Plane Shift to other realities
  • Wish for almost anything

What challenges these abilities without domain-scale stakes? The answer: none, really. DMs resort to:

  • Arbitrary magic negation (“teleportation doesn’t work here”)
  • Endless enemy inflation (every enemy also has reality-warping magic)
  • Abandoning the campaign

The Math Breaks: At high levels:

  • Attack bonuses exceed AC to the point where missing is rare
  • Saving throws become binary (make or fail, no middle ground)
  • HP pools create combat slogs
  • Action economy dominance (more attacks = auto-win)

Documented Failure: Surveys show:

  • ~70% of 5E campaigns end by level 10
  • ~5% reach level 15+
  • ~1-2% actually play to level 20

This isn’t players choosing to end campaigns—it’s campaigns collapsing because the game stops functioning.

What 5E Should Have Done: The Strongholds & Followers and Kingdoms & Warfare supplements by Matt Colville (third-party) demonstrate what 5E needed:

  • Stronghold management systems
  • Organization building (thieves’ guilds, wizard towers, mercenary companies)
  • Warfare rules using units (not individual combatants)
  • Economic systems for maintaining domains

These filled a gaping hole in the core design, selling hundreds of thousands of copies despite being unofficial content.

Pathfinder 1st Edition: Complexity Without Payoff

Pathfinder 1E inherits 3.5’s high-level problems and amplifies them.

The Issues:

Option Bloat: By high level, the sheer number of options becomes paralyzing:

  • Thousands of feats, spells, items, class features
  • Interacting subsystems (grapple, combat maneuvers, spell resistance, damage reduction)
  • Optimization traps (many builds become non-viable at high level)

Linear Fighters, Quadratic Wizards: The power disparity between classes grows exponentially:

  • Fighters gain more attacks and better numbers
  • Wizards gain reality-warping magic (Gate, Wish, Time Stop)
  • By level 15, martials are irrelevant in many scenarios

Kingdom Building: Pathfinder’s Ultimate Campaign includes kingdom building rules, but they’re:

  • Overcomplicated: Tracking dozens of stats (Economy, Loyalty, Stability, Unrest, Fame, Infamy)
  • Monthly spreadsheet management: Every month requires calculating 10+ modifiers
  • Disconnected from play: Kingdom turns happen “off-screen” in downtime
  • Balance issues: Certain buildings/choices are clearly optimal; others are traps

Cognitive Overload: High-level Pathfinder requires:

  • Tracking 30+ buffs and debuffs simultaneously
  • Consulting multiple rulebooks for edge cases
  • Calculating stacking modifiers from 5+ sources
  • Remembering complex spell interactions

Sessions become mechanical exercises rather than narrative experiences.

Combat Slog: A high-level Pathfinder combat can take:

  • 30-45 minutes real-time per round
  • 3-4 hours for a “normal” encounter
  • 6-8 hours for a “boss fight”

Most of this time is spent calculating modifiers, looking up rules, and resolving spell effects.

Exalted: When Mechanical Complexity Implodes

Exalted (White Wolf, 2001) presents an interesting case: it’s designed for high-power play from the start. Characters are demigods reshaping reality. Yet it fails spectacularly.

The Design Philosophy: Characters should be able to:

  • Command armies
  • Rule kingdoms
  • Perform legendary crafting
  • Shape societies
  • Battle evil gods

Why It Fails:

Charm Bloat: Character abilities (“Charms”) number in the hundreds per character type:

  • Determining which Charms counter which becomes a metagame
  • “Charm trees” require planning 10+ sessions in advance
  • Combat becomes “I use Perfect Defense Charm, you use Defense-Piercing Charm, I use Defense Against Defense-Piercing Charm…”

Social Combat: The game attempts to mechanize social influence:

  • Social “health tracks” (Intimacies)
  • Social attack rolls
  • Social defense values

In practice, players feel agency is mechanically removed (“I lost the social combat, so my character changes their mind”).

Mass Combat: Rules exist but are:

  • So complex they require dedicated study
  • Poorly integrated with personal-scale combat
  • Often ignored in favor of “main characters fight while armies are backdrop”

Crafting Systems: Creating magical artifacts requires:

  • Weeks of game time
  • Resource expenditure (including permanent stat loss)
  • Multiple subsystems (research, gathering materials, construction)
  • Can break campaigns (over-powered artifacts)

The Collapse: High-level Exalted play typically devolves into:

  • Rules arguments about Charm interactions
  • Combat taking entire sessions
  • GM frustration at mechanical complexity
  • Abandonment

The game wants to support demigod-level play but lacks the procedural clarity and mechanical elegance to function at that scale.

Design Principles: What Makes Domain Play Work

Examining successes and failures reveals consistent principles for functional high-level play.

Principle 1: Shift Scale, Don’t Just Inflate Numbers

Bad: Level 20 character fights enemies with 500 HP instead of 50 HP Good: Level 20 character commands armies; personal combat becomes strategic resource

Successful domain systems change the unit of resolution:

  • Personal scale: Individual attacks and hit points
  • Domain scale: Unit strength, army morale, economic output

The character’s personal power becomes a modifier to strategic actions, not the resolution mechanic itself.

Example: In ACKS mass combat, a high-level fighter doesn’t personally kill 100 soldiers. Instead, their leadership provides:

  • Morale bonuses to friendly units
  • Ability to execute tactical maneuvers
  • Heroic charges that can break enemy formations
  • Prevention of friendly routs through personal inspiration

Their power is expressed through strategic effect, not literal individual actions.

Principle 2: Provide Concrete Procedures

Domain play fails when it’s narrative handwaving (“you manage your kingdom” with no mechanical support).

Successful systems provide clear procedures:

ACKS Domain Turns:

  1. Check for threats (invasion, monster incursion, revolt)
  2. Collect taxes (calculated from population and development)
  3. Pay expenses (garrison, court, infrastructure maintenance)
  4. Resolve construction (ongoing projects progress)
  5. Take domain actions (limited number per turn)
  6. Check for random events (natural disasters, discoveries, diplomatic opportunities)

This creates structure that:

  • Prevents GM paralysis (“what happens?”)
  • Provides clear decision points for players
  • Generates emergent situations
  • Maintains forward momentum

Without procedures, domain play becomes: GM: “You manage your kingdom. What do you do?” Player: “Um… make sure everything’s running okay?” GM: “Okay, it is.” [awkward silence]

Principle 3: Integrate Scales Rather Than Segregating Them

Failed domain systems create separate minigames that don’t interact with core play.

Pathfinder’s Kingdom Building: Happens in downtime, uses completely different stats (Economy, Loyalty, etc.) than character stats, provides minor narrative framing for adventure selection.

Successful integration means:

  • Adventuring affects domain position
  • Domain resources fund adventuring
  • Personal abilities provide domain advantages
  • Domain threats create adventure hooks

Pendragon Example:

  • Winter phase (domain management) determines available funds for equipment
  • Equipment quality affects summer adventuring success
  • Adventuring Glory affects social status
  • Social status determines marriage prospects
  • Marriage brings allies, lands, and political connections
  • Political connections create new adventure opportunities

Each scale feeds the other in a virtuous cycle.

Principle 4: Make Wealth Meaningful

Most RPGs break because wealth becomes meaningless at high level. Characters accumulate millions in gold with nothing to buy.

Successful approaches:

Limited Markets: ACKS assumes villages can’t absorb unlimited wealth. Selling massive treasure requires:

  • Finding appropriate markets (cities, wealthy patrons)
  • Time to locate buyers
  • Potential price negotiation or bulk discounts

Massive Expenses: Domain play creates wealth sinks:

  • Castle construction: 75,000-250,000 gold
  • Army maintenance: 1,000-10,000 gold per month
  • Infrastructure development: 5,000-50,000 per project
  • Magical research: 10,000+ per major work

Suddenly that 50,000 gold dragon hoard isn’t “retirement money”—it’s one season’s military expenses or partial payment for a castle tower.

Economic Warfare: Wealth becomes a weapon:

  • Funding rival’s enemies
  • Economic blockades
  • Bribing enemy commanders
  • Subsidizing rebellion

Gold becomes strategic resource rather than personal enrichment.

Principle 5: Create Strategic Dilemmas, Not Optimization Puzzles

Bad domain systems have correct answers: Build X, then Y, then Z for optimal outcome.

Good domain systems create meaningful tradeoffs:

ACKS Example: Your domain is threatened by neighboring orcs. Do you:

Option A – Military Buildup:

  • Costs: 5,000 gold, 2 months construction, ongoing maintenance
  • Benefits: Defense against invasion
  • Risks: Economic slowdown (resources diverted from development), neighboring human kingdoms see this as aggressive posturing
  • Opportunity cost: Can’t invest in market that would boost long-term economy

Option B – Diplomatic Alliance:

  • Costs: Political obligations, sharing future conquests
  • Benefits: Allied forces assist in defense
  • Risks: Ally might demand unpopular actions, may betray if offered better deal
  • Opportunity cost: Less autonomous decision-making

Option C – Preemptive Strike:

  • Costs: Military campaign expenses, potential casualties
  • Benefits: Eliminate threat entirely, claim orcish territory
  • Risks: Failure leads to exposed position, other neighbors might see expansion as threat
  • Opportunity cost: Extended campaign prevents other activities

None of these is objectively correct. The best choice depends on:

  • Current economic state
  • Relationships with neighbors
  • Player risk tolerance
  • Long-term strategic goals
  • Character abilities (high-level fighter might make Option C more attractive)

This creates strategic depth through genuine dilemmas.

Principle 6: Embrace Emergence Over Scripted Narrative

The best domain play is emergent—stories arise from mechanical interaction rather than GM planning.

Bad Approach: GM pre-writes “invasion storyline” that triggers regardless of player actions

Good Approach:

  • Domain has orc population in nearby hexes
  • Orcs have goals (expand territory)
  • Orcs take actions during domain turns
  • Player domain actions affect orc success/failure
  • Conflict emerges organically from competing goals

Birthright Example: GM doesn’t plan “Player A invades Player B.” Instead:

  • Player A’s domain has Law 4 in Province X
  • Player B also has Law 2 in Province X (competing jurisdiction)
  • Player B takes Contest action to increase Law holding
  • Player A can: Accept reduction, Contest back, or Agitate (create unrest)
  • Escalation emerges from mechanical conflict
  • War might result, or diplomatic solution, or economic warfare

The story emerges from the domain systems rather than being imposed on them.

Modern Innovations: The Domain Play Renaissance

The OSR movement and indie designers are reviving domain play with modern sensibilities.

Worlds Without Number (Kevin Crawford, 2020)

Provides faction turn mechanics:

Faction Turns occur between sessions:

  1. Each faction has assets (military units, spy networks, economic enterprises)
  2. Factions take actions (Attack, Expand, Coerce, Defend)
  3. Assets contest each other using simple opposed rolls
  4. Successful actions shift territorial control or damage rival assets

Integration with Adventure:

  • PCs can acquire or create faction assets
  • Adventures can target rival faction assets
  • Faction conflicts create adventure hooks
  • PC reputations affect faction interactions

Elegant Simplicity:

  • Single page of faction rules
  • Minimal bookkeeping (track ~5 assets per faction)
  • Generates emergent geopolitics
  • Scales from city-state to interstellar empire

An Echo, Resounding (Kevin Crawford, 2012)

Crawford’s earlier domain supplement for old-school games provides:

Project System: Abstract domain actions as “projects” with:

  • Cost (money, time, resources)
  • Difficulty (opposed by circumstances or rivals)
  • Completion conditions
  • Benefits when complete

Examples:

  • “Build Castle” = Construction project
  • “Train Army” = Military project
  • “Establish Trade Route” = Economic project
  • “Suppress Rebellion” = Social project

Each project type has templates, but system is flexible—GM can create custom projects.

Why It Works:

  • GM-facing (provides tools for GM to manage world)
  • Abstracted (doesn’t require tracking every copper piece)
  • Scalable (works for single stronghold or vast empire)
  • Hackable (easy to modify for different settings)

The Nightmares Underneath (Johnstone Metzger, 2015)

Focuses on creating incursions (dungeons) as domain-level activity.

The Premise: High-level characters don’t just explore dungeons—they create them. Nightmares seep into reality, manifesting as dungeons. Powerful ritualists can harness this for:

  • Creating magical infrastructure (permanent teleportation circles)
  • Manufacturing enchanted items at scale
  • Establishing power bases in nightmare space
  • Controlling incursion points for strategic advantage

Mechanical Support:

  • Incursion creation rules (cost, time, effects)
  • Infrastructure benefits (what different incursion types provide)
  • Strategic value (controlling incursion points affects territorial power)
  • Economic integration (incursions generate resources)

Why It’s Innovative:

  • Flips script (PCs become dungeon creators, not just explorers)
  • Provides concrete domain benefit from weird magic
  • Creates strategic layer (location of incursions matters)
  • Maintains dungeon-crawling identity while shifting scale

Stars Without Number Revised (Kevin Crawford, 2018)

Applies domain principles to space opera:

Faction System (as in Worlds Without Number but space-themed):

  • Megacorporations, planetary governments, pirate fleets, psychic cults
  • Assets: Stealth, Wealth, Force (replacing medieval equivalents)
  • Cyberware, orbital stations, and starships as assets
  • Interstellar conflict through faction turns

PC Factions:

  • Players can create factions (mercenary company, trade consortium, colonial government)
  • Faction grows as PCs gain experience
  • Faction actions happen between adventures
  • Adventure and faction play interweave

Integration:

  • Adventures might be: Destroy rival faction asset, acquire new technology, establish colony, negotiate treaty
  • Faction conflicts create adventure opportunities
  • PC skills translate to faction bonuses (pilot skill helps Fleet Asset, leadership helps Cunning Asset)

Why It Works in Sci-Fi:

  • Space opera naturally involves empires, corporations, and interstellar politics
  • Strategic scale fits genre (colonies, trade routes, fleet movements)
  • Maintains personal adventure (boarding actions, espionage, exploration) while adding strategic layer

The Player Psychology: Why Domain Play Appeals

Domain play isn’t for everyone, but it appeals to specific player motivations:

The Builder Archetype

Some players derive satisfaction from construction and development:

  • Watching settlements grow
  • Seeing economic output increase
  • Completing long-term projects
  • Creating lasting legacy

These players often find murder-hobo adventuring hollow. “We killed the dragon and took its hoard. Now what?” Domain play provides the “now what”—apply resources to create something enduring.

The Strategist

Players who love tactical depth often find high-level adventuring boring (combat becomes too predictable). Domain play provides:

  • Strategic decision-making (resource allocation, risk assessment)
  • Long-term planning (multi-season strategies)
  • Complex webs of cause-and-effect
  • Emergent challenges (no two domain situations identical)

For these players, managing a kingdom under threat is more engaging than another dragon fight.

The Monarch Fantasy

Some players explicitly want power fantasy at institutional scale:

  • Ruling kingdoms
  • Commanding armies
  • Shaping history
  • Building dynasties

For them, the ultimate character progression is from nobody to ruler of nations.

The Legacy Creator

Related to builders, some players want permanence:

  • Their character’s name on maps (“Fort Alaric,” “The Duchy of Kendra”)
  • NPCs referencing their deeds decades later
  • Institutions they founded outliving them
  • Generational play (Pendragon-style)

Domain play provides concrete legacy—the kingdom you built continues after your character dies.

The Collaborative World-Builder

For some groups, domain play becomes group worldbuilding exercise:

  • Multiple PCs ruling neighboring domains
  • Alliances, trade agreements, conflicts between PC nations
  • Shared investment in regional development
  • Emergent geopolitics from player decisions

This creates table dynamics impossible in traditional adventuring.

The Future: Digital Assistance and Procedural Domain Play

Technology is making domain play more accessible:

Automated Bookkeeping

Digital tools can handle calculation-heavy aspects:

  • Tax revenue calculation
  • Resource tracking
  • Construction timers
  • Army maintenance costs
  • Population growth

This reduces cognitive load while preserving strategic decision-making.

Simulated Factions

AI-assisted faction systems could:

  • Simulate rival domain decisions
  • Create emergent geopolitical situations
  • Respond intelligently to player actions
  • Generate contextually appropriate challenges

Rather than GM managing 5+ rival domains manually, software handles faction turns, presenting results to GM for interpretation.

Procedural Event Generation

Random event tables enhanced by context:

  • Events appropriate to current domain state
  • Callbacks to previous events
  • Faction-specific complications
  • Seasonal/economic context

This maintains emergence while reducing GM prep burden.

Virtual Tabletops

VTTs are beginning to support domain play:

  • Hex ownership overlays on campaign maps
  • Automated domain turn processing
  • Economic calculators
  • Army unit tracking
  • Construction project timers

Foundry VTT has modules for ACKS domain management, automating most calculations while keeping strategic decisions player-facing.

Conclusion: Reclaiming the Endgame

The abandonment of domain play represents one of the hobby’s great missed opportunities. For decades, the industry designed elaborate progression systems (20 levels, dozens of abilities, exponential power growth) while providing no meaningful outlet for that power at high level.

The result: campaigns that peter out at mid-level, players who never see the upper tier abilities they theorycrafted, GMs forced to house-rule entire gameplay paradigms, and a persistent sense that high-level play is “broken.”

But it doesn’t have to be this way. The OSR revival, modern indie design, and third-party supplements demonstrate that domain play can work when approached with:

  • Procedural clarity (concrete systems, not narrative handwaving)
  • Scale shifting (strategic rather than tactical resolution)
  • Integration (domain and adventure scales feeding each other)
  • Meaningful choices (strategic dilemmas, not optimization puzzles)
  • Emergent complexity (systems generating stories rather than pre-scripted plots)

Domain play isn’t a niche preference or obsolete relic of wargaming roots. It’s the natural culmination of character progression from zero to hero to ruler to legend. It provides:

  • Satisfying endgames (campaigns that feel complete)
  • Power expression (godlike abilities finding appropriate challenges)
  • Strategic depth (new gameplay paradigms at high level)
  • Legacy creation (permanent impact on game world)
  • Emergent narrative (stories arising from mechanical interaction)

The systems exist. The player appetite exists. What’s needed is industry recognition that high-level play deserves the same design attention as low-level play, that the endgame is not disposable content for the 5% who reach it, but the payoff that makes the entire progression meaningful.

Whether through ACKS’s economic simulation, Birthright’s political intrigue, Pendragon’s generational dynasties, or modern innovations like Worlds Without Number’s faction systems, domain play represents tabletop gaming’s final frontier—the space where characters transcend personal adventure to become the forces that shape worlds.

For those willing to engage with these systems, high-level play isn’t where campaigns go to die. It’s where they truly begin.

The question isn’t whether domain play is worthwhile. The question is: why would you design a progression system from level 1 to 20 and not provide meaningful gameplay for the upper half?

The endgame beckons. It’s time to reclaim it.

Continue Reading

Next in Series: The Party of One: Solo Play as the New Frontier – From ruling kingdoms with groups, we turn to an increasingly important alternative: playing alone.

Related and Upcoming Articles:

  • Hexcrawling – Procedural exploration that feeds into domain building
  • Tactical Design – Mass combat and strategic warfare
  • The Quadratic Wizard Problem – High-level balance issues