Campaign Structure
AX.C.14.05 - Campaign Structure
This section covers the macro level of GM planning, how individual sessions nest into arcs, how arcs build into campaigns, and how the GM tracks and evolves the world across that full span. It is the complement to AX.C.15.04's session-level adventure design.
Sessions, Arcs, and Campaigns
Three planning scales, each nested inside the next:
A session is a single play period, typically one complete 5-stage adventure, or a substantial portion of a longer one. It has its own shape: an entry challenge, a contemplation beat, a twist, a climax, and a resolution that plants the next hook. Sessions are the unit of play. Everything else is built from them.
An arc is a sequence of sessions unified by a shared dramatic question. A faction is trying to seize control of something. An antagonist is pursuing a plan. A mystery is unfolding. The players are working toward or against a specific outcome. Arcs typically run 3–6 sessions, though neither bound is fixed. An arc ends when its dramatic question is resolved, answered, failed, or overtaken by events.
A campaign is a series of arcs with persistent characters, accumulating consequences, and a trajectory that spans the full run of play. Where a session has a structure and an arc has a shape, a campaign has a direction: the world the characters are moving through is changing, and they are part of what changes it.
The connection between scales is the Stage 5 hook mechanism from AX.C.15.04. Each session ends with a thread dropped into the next one. When those threads are consistently drawn from the same source, the same antagonist, the same faction tension, the same unresolved question, they become an arc. When arcs are linked by shared consequences and recurring forces, they become a campaign.
An arc should have a clear dramatic question established at its outset, even if the players don't know what it is yet. Will the faction consolidate control before the party can stop them? Will the characters uncover what actually happened to the expedition? The question gives the arc a destination. The sessions are the route.
XP Pacing and Advancement as a Campaign Rhythm Tool
Advancement is not just a reward; it is a pacing signal. The rate at which characters grow shapes how the campaign feels: fast advancement produces a game of expanding capability; slow advancement produces a game of working within limits. Neither is wrong. Both should be chosen deliberately.
The baseline rate is 3 XP per session. At this rate, the Profession Progression Track stages, which unlock at 10, 25, and 50 XP, fall at predictable intervals:
| Stage | XP Threshold | Sessions at Baseline | Campaign Phase |
|---|---|---|---|
| Stage 1 | 10 XP | ~3–4 sessions | Early arc |
| Stage 2 | 25 XP | ~8–9 sessions | Mid-campaign |
| Stage 3 | 50 XP | ~17 sessions | Late campaign |
These thresholds are natural arc break points. Characters who unlock a new Stage ability are measurably different from who they were when the arc started. Planning an arc to end near a Stage unlock, or to begin just after one, gives the character's growth a structural shape that mirrors the story's shape.
Adjusting the rate changes the campaign's timeline without changing its structure. Awarding 4–5 XP per session compresses full progression to 10–13 sessions, suitable for shorter campaigns or groups who prefer faster character growth. Awarding 2 XP per session extends it to 25 sessions or more, appropriate for long campaigns where each advancement should feel significant.
Major milestones, completing an arc, defeating a primary antagonist, resolving a long-running consequence, warrant an additional 2–5 XP beyond the session baseline. Use these sparingly. Milestone awards that are too frequent or too large disrupt the pacing signal; the Stage unlock should feel like the culmination of sustained effort, not an accidental byproduct of a big session.
Party synchronization keeps the group advancing together without mandating identical totals. The cleanest approach is flat per-session XP for all players, with individual accomplishment awards (1–2 XP) for specific moments of strong play. This naturally keeps the party within a session or two of each other. For players who miss a session, a partial award of 1–2 XP prevents widening drift without rewarding absence.
When the Deliberate Advancement option from AX.C.13.03 is in use, arc breaks are natural training windows. The downtime between arcs is when characters seek mentors, practice new Talents, and spend accumulated XP, giving advancement a narrative context rather than a mechanical abstraction.
Tracking Long-Term Consequences
The world accumulates the effects of player actions. Tracking those effects is the GM's tool for making the world feel inhabited and for delivering consequences that players can actually feel.
A minimal consequence tracking framework uses three fields per tracked event:
What changed: The concrete thing that is different as a result of player action. Not "the players helped the faction", "the faction now controls the southern checkpoint and has begun turning away unaffiliated travelers."
Who knows: Which forces in the world are aware of the change and have the capacity to respond. Information propagates at realistic rates. A consequence that happens in an isolated location may not reach relevant parties for sessions. A consequence that happens in front of witnesses spreads faster.
What response it is generating: What the aware parties are doing about it. A faction that lost ground is regrouping. An NPC the players antagonized is looking for leverage. An opportunity the players ignored is being pursued by someone else. The response is not a punishment; it is what a living world does.
Surfacing consequences is the GM's craft challenge. Delivering consequences as exposition ("you hear that the faction has taken the checkpoint") is less effective than showing them in play ("the guard at the bridge is wearing a faction insignia you recognize, and she's waving through faction-marked wagons while turning away everyone else"). Players should notice something has changed before they're told why. The consequence surfaces in the fiction first; explanation follows only when players seek it.
NPC tracking from AX.C.15.03 feeds directly into consequence tracking. The per-session update to a recurring NPC's record, what relevant event occurred, and how their disposition shifted as a result, is the granular level of what consequence tracking manages at scale. Faction-level tracking is the aggregate: if a genre catalog defines factions with competing interests, track their current positions, recent gains and losses, and what they're pursuing, in the same three-field format.
World Evolution
The setting is not static scenery. Antagonists are pursuing their goals. Factions are competing for resources and influence. Environmental and political processes are developing. Whether or not the players engage with any of these, they continue.
Maintain a small number of active world threads at any time, two to three is the practical maximum. More than that becomes difficult to track consistently; threads that aren't tracked consistently stop evolving and become dead ends that erode the world's credibility.
Each thread has four components:
Force: What is acting, a faction, an antagonist, an environmental process, an unresolved consequence from a prior arc.
Current action: What the force is doing right now, specifically. Not "the faction is expanding", "the faction is negotiating to acquire the eastern district's water access, which will complete by session's end if the players don't intervene."
Trajectory: Where the thread is heading if unchecked. This gives the GM something concrete to advance at the table when players engage with the thread, and something concrete to resolve in the background when they don't.
Intersection: When and how the thread surfaces into the players' awareness. Some threads surface through direct encounter. Others surface through NPC behavior shifts, environmental changes, or rumors. The intersection is the scene or moment where the thread becomes visible, not necessarily where it becomes urgent.
When the players resolve a thread, or when it resolves itself by running its trajectory to completion, introduce a new one. The count stays low, but the world's complexity accumulates. Players who were in the same city three arcs ago are in a meaningfully different version of it now.
Opportunities close. A contact who offered to help won't wait indefinitely. A faction advantage that could have been taken is eventually taken by someone else. A piece of information that was available for two sessions becomes buried or acted upon. This is not a punitive design; it is a consequence of the world having processes that don't pause. Players who learn that the world moves without them engage more actively with threads that are currently open.
Arc breaks are the natural moment to advance background threads visibly. When the campaign moves from one arc to the next, particularly if downtime is involved, the threads that have been developing in the background should surface in some observable form. The world the players return to should show the time that passed.