Monster of the Week

AX.GHW.14.02.01

Best for: New groups, one-shots and short arcs, players who prefer episodic play, introducing the setting gradually

Power level fit: Street Level (6D) through Regional (9D)

Session count: Open-ended; typically 3–20 sessions before natural conclusion or transition

How It Works

Each session (or 2-session pair) presents a discrete supernatural threat. The characters investigate, identify, and address the threat. The scenario resolves. The next session brings a new threat.

This structure is the genre's default; it is how Buffy and Supernatural run in their early seasons. It allows new players to learn the setting without needing to track complex ongoing threads, and it lets the GM test different threat categories and tones before committing to a longer arc.

The hidden world in Monster of the Week is a populated environment, not a sandbox. The threats don't appear in isolation; they exist in a setting with organizations, lineage communities, and ongoing pressures. Even in an episodic structure, those elements should be present in the background. The BUA shows up at scenes. The Network passes along information. Organization relationships build session to session even if the threats are unconnected.

Session Structure

Session opening: Establish the inciting event. The characters receive the situation through one of three channels: - Direct involvement (they witness something, someone they know is affected) - Professional contact (an organization employer provides a case) - Network call (a contact flags something that matches the characters' pattern)

Investigation phase (1–2 scenes): Follow the three-clue rule. Every key piece of information is available through at least three routes. The investigation ends when the characters have identified the threat and know enough to engage it.

Engagement phase (1 scene): The confrontation. The threat is active and the outcome is not certain. The engagement should test something, tactical creativity, moral choice, resource management, not just attack rolls.

Resolution phase (brief): Evidence management, organizational aftermath, any consequences that carry forward. Even in an episodic structure, consequences accumulate. A contact who helped this week remembers it next week.

Building Episodic Sessions

Vary the threat categories. A campaign that runs six consecutive undead scenarios stops being a horror game and becomes a tactical challenge. Rotate: one undead scenario, one cryptid scenario, one Shadow entity scenario. Each category creates different investigation tools, different evidence signatures, different engagement approaches. The variety keeps the setting from feeling like a single-threat sandbox.

Connect episodes through recurring elements. Monster of the Week does not mean nothing connects. The BUA Agent who showed up in Session 2 shows up again in Session 5, now with a reason to be wary of the characters. The Lore Keeper who provided research in Session 3 contacts the characters in Session 7 because they found something relevant to an earlier case. These connections build the world without requiring the GM to plan a conspiracy.

Give the threat a face. The most memorable Monster of the Week scenarios are about a specific threat with a specific history. Not "there's a Revenant in the warehouse district", "there's a Revenant in the warehouse district, and preliminary research suggests she was murdered by someone connected to a construction project that broke ground six months ago, and one of the characters' contacts works for the development company." The face makes it worth caring about.

Transitioning Out of Monster of the Week

Monster of the Week campaigns often find a natural through-line that wasn't planned. The recurring BUA Agent starts appearing too regularly to be coincidental. The same shadow compact broker's name shows up in three unconnected scenarios. A specific threat category appears with unusual frequency in the same geographic area. When patterns like this emerge organically, follow them, the campaign is finding its conspiracy arc. Transition by:

Acknowledging the pattern in-fiction: a Network contact notices it, a piece of research connects dots, an NPC asks if the characters have noticed
Providing a choice: the characters can pull on the thread or leave it alone
Pulling the thread creates the Conspiracy Arc's opening act