Core Philosophy
The Fundamental Principle
Content is generated responsively when players declare intent, not pre-generated in advance. Once established, it “always existed”—common knowledge available to all guild members.
Five Pillars of Western Horizon
1. Goal-Driven Play
Players bring goals, not reactions to GM hooks. Each character has concrete objectives they’re actively pursuing. The GM’s job shifts from “create interesting hooks” to “create interesting obstacles to what players already want.”
Why this works:
- Players are invested because they authored their own direction
- Eliminates “what do we do?” paralysis at session start
- Provides clear criteria for content generation
- Creates natural story through goal collision between PCs and factions
Goals vs. Hooks
Traditional play: GM creates hooks, players choose which to pursue. WH play: Players declare goals, GM creates obstacles to those goals.
2. Responsive Generation
Content is created when needed, not before. When a player posts “I want to investigate the ruins in the Thornwood,” that’s when you generate the dungeon. When they reach a new tier and need a larger settlement, that’s when you build the town.
Why this works:
- Eliminates wasted prep on content players never engage
- Reduces DM burnout from pre-building an entire world
- Ensures content is responsive to actual player interest
- Allows the campaign to grow organically in unexpected directions
When Does "Responsive" Happen?
Not during the session. Responsive generation happens between sessions during prep. Player posts intent → GM generates content before session → Session runs with established content → Discoveries logged after session.
3. Collaborative Authorship
The GM doesn’t create the world alone. Players participate in worldbuilding at multiple stages:
- Session Zero: Everyone builds history, sets tone, establishes the Guild
- Settlement Building: Players help create towns, detail landmarks, define factions
- Dungeon Rumors: Player speculation about dungeons informs their actual contents
- Discovery: When players find something, they help name it, describe it, define it
The GM’s Specialized Role
In collaborative authorship, the GM is still a storyteller—just no longer the primary author. Instead, the GM specializes in adjudication and simulation.
| Traditional GM | WH GM |
|---|---|
| Primary author of world and story | Co-author alongside players |
| Creates content proactively | Creates content responsively to player goals |
| Guides players through planned narrative | Adjudicates player interaction with established world |
| Reacts to player choices during session | Reacts to player declarations between sessions |
The GM’s authorship happens in three distinct modes:
-
Collaborative Creation (Between Sessions) — With players: running worldbuilding games. Alone: using generation systems to build content responsive to declared goals. This is where “what exists” gets authored.
-
Active Adjudication (During Session) — Making rulings on player actions within the established world. This is where “what happens” gets authored.
-
World Simulation (After Session) — Advancing faction clocks, simulating consequences, updating the state of the world. This is where “what changes” gets authored.
Two Types of "Reactive"
Content Reaction (Between Sessions): Players declare “We’re going to the Thornwood Swamp” → GM preps that location. Asynchronous.
Adjudication Reaction (During Session): Players act “I want to swing from that chandelier” → GM rules whether/how that works. Synchronous.
Most traditional GMing advice addresses content reaction during play (“what if they go somewhere I didn’t prep?”). WH eliminates that problem through self-contained expeditions. The GM still needs adjudication skills, but not improvised content generation.
The Self-Contained Expedition Structure
| Phase | What Happens | GM’s Authorship Mode |
|---|---|---|
| Planning (Between Sessions) | Players discuss goals and post: “We’re going to [location] to [goal]“ | Collaborative Creation: Prep the declared location with obstacles relevant to the goal |
| Expedition (During Session) | Session starts in medias res. Players execute their declared plan. | Active Adjudication: Rule on player actions, simulate consequences |
| Resolution (After Session) | Return to settlement. Log discoveries. Discuss next goals. | World Simulation: Advance faction clocks, update world state, seed new rumors |
Why "Self-Contained" Matters
Traditional sessions often start with “What do you do?” and can go anywhere. The GM must constantly react to unknown player direction.
WH sessions are different: They’re going to the swamp. You prepped the swamp because they told you. During the session, you’re not surprised about where they are—only what they do when they get there.
This is why “stalling tactics” or “back-pocket encounters” don’t apply to WH.
4. Canon Integration: “It Always Existed”
Once content is generated and played, it becomes permanent canon known to all guild members. The temple in the Thornwood? It always existed. The merchant prince who runs the harbor? Everyone knows about them.
How this works in practice:
- Content is added to the Guild Wiki (Obsidian or similar)
- Other players can reference it: “I heard there’s a temple in the Thornwood…”
- Future generation must not contradict established canon
- New content builds on rather than replaces old content
What "Always Existed" Means
It doesn’t mean the DM secretly planned everything in advance. It means once something appears in play, we treat it as if it was always part of the world. The generation method is invisible to players—they just see a coherent, persistent world.
5. Scale & Scope
A living world operates at multiple scales simultaneously. WH needs generation procedures for each scale:
| Scale | Generation Need | Key Outputs |
|---|---|---|
| History | Shared past, defining moments, cultural touchstones | Eras, events, legends, conflicts |
| Settlement | Living towns with factions pursuing goals | Districts, power structures, development timeline |
| Locations | Specific places with sensory details and NPCs | Landmarks, residents, relationships, atmosphere |
| Wilderness | Travel between sites with emergent complications | Terrain, discoveries, dangers, waypoints |
| Dungeons | Dangerous sites with internal logic and threats | Layouts, denizens, treasures, ecology |
Problem-First, Not System-First
Each scale has specific problems to solve. The Western Horizon defines what makes a good solution rather than mandating specific systems. See 00d - Proven Solutions for battle-tested procedures that align with these principles.
Guiding Principles for Collaborative Creation
These principles inform how we generate content at every scale:
- Everyone is equal. One person might facilitate, but they don’t have more control than others during collaborative creation.
- Don’t contradict what’s already established. New content builds on the foundation—it doesn’t erase it.
- Don’t coach or suggest on someone else’s turn. Let each person contribute their own ideas so we can be surprised.
- Paint a clear picture everyone can visualize. Vague content is hard to build on—be specific and evocative.
- Players are more important than the game. If something makes someone uncomfortable, address it immediately. Safety tools override all other rules.
What This Framework Provides
- Philosophy: The “why” behind goal-driven, responsive, collaborative play
- Problem definitions: Clear articulation of what needs solving at each scale
- Solution criteria: What makes a good generation procedure for WH
- Workflows: Player intent → content generation → session play → wiki documentation
- Proven systems: Battle-tested procedures that align with WH principles
- Integration points: How different scales hand off to each other
- Goal and faction frameworks: Practical tools for proactive play
- Templates: For wiki pages, session prep, and quick reference
It does not prescribe mandatory systems. Think of this as design principles with proven examples, not a rigid playbook.