Running a 10-Level Dungeon in DCC Without Losing Your Mind
Most people buy Temple of the Dragon Cult because the page count looks intimidating and promise themselves they will be organized. Ten levels is a lot of content to track, and without a system you will drown in notes within the first two sessions. The module itself is well written. Scott Greene packed enough into those pages that it took me three separate campaigns before I felt like I had actually seen the whole thing. Even then I missed half the side rooms in the lower levels on the first pass. Here is the practical breakdown of how this thing actually plays out at the table and what I have learned the hard way about running it. The core loop is straightforward. You take a band of low-level characters into the temple and fight your way down level by level. Each level contains combat encounters, traps, skill challenges, and NPCs. The dragons of the cult operate on a hierarchy, and the deeper you go the more dangerous the patron creatures become. That is the surface reading. The real structure is about resource attrition. DCC does not hide this from you. Every encounter drains hit points, spell slots, ammunition, and sanity. The module is built so that a party that conserves resources can survive well past the point where a reckless party dies.
I learned this the slow way. My first run, the players charged into level four thinking they could fight through everything. They wiped. Third level rest spots are sparse, and the monsters on levels five and six scale up fast if you do not control engagement. I rewrote my approach for the second run and started tracking every arrow and rations explicitly. It changed the tone of the game entirely. Combat became a negotiation instead of a sprint.
Preparation Before You Roll Dice
Do not skip the prep work. The module assumes the GM has done some mapping and encounter selection before play starts. Several encounters reference conditions that only make sense if you know which doors are locked, which rooms contain loot, and which NPCs are actually hostile versus merely suspicious. I keep a master grid for this module. Not a formal one. Just a spreadsheet with columns for level, encounter number, difficulty, and notes about what happens if characters bypass it. When a player decides to sneak past the kobold shrine on level two instead of fighting, I flip to that row and read the bypass condition. This saves about twenty minutes per session compared to hunting through the book mid game. The dragon cult priests are a recurring element. They show up across multiple levels and their presence changes encounter dynamics. If the players manage to turn one against another, entire sections become easier. If they ignore them, those same sections get harder over time as the cult coordinates its defenses. I track cultist alert status on a small section of my GM screen. It takes about thirty seconds to update and it keeps the story coherent.
Get the Full Details
Running the Early Levels Without Killing the Party Prematurely
Levels one through three are the tutorial zone. The enemies here are mostly kobolds, cultists, and minor undead. The intention is to let the party learn the mechanics while building confidence. What actually happens in most tables is that players treat these levels as warm-ups and walk into level four with false confidence. This is where people die. I have found that inserting one genuinely scary encounter on level two or three resets expectations. The module includes several options. I usually pick the ones that involve a trapped corridor rather than open combat. A single failed saving throw against a poison trap makes players pay attention to everything they touch for the rest of the session. That shift in attitude carries forward into the later levels where it matters. Traps in this module are not filler. They are deliberate resource sinks. Every trap bypassed costs time, tools, or spells. Every trap triggered costs hit points or worse. The skill challenge on level two that involves disarming a pressure plate sequence is exactly forty-five minutes of real table time if you are doing it properly. Some groups rush through it in ten minutes because they are impatient. The rushed group usually misses a reward hidden in the third mechanism. This is a repeated pattern I have seen across six different runs.
The Middle Levels Are Where Most Games Stall
Levels four through six contain the densest encounter cluster in the entire module. This is also where resource management breaks down for most groups. The dungeon layout forces movement between sections, and those movement costs add up faster than people realize. One issue I ran into repeatedly involves resting. The module does not give clean safe zones until level seven. Players who attempt to rest after every encounter burn through rations and supply in roughly two sessions. I stopped telling them the exact ration count and let them ask. When they inevitably ask, I give them the math in real time. This alone reduces unnecessary combat encounters by about thirty percent because players stop engaging when they know they cannot afford to heal afterward. The dragon wyrmlings appear more frequently in the middle levels than first-time GMs expect. They are not the most dangerous monsters in the module, but they have area attacks that punish clustered formations. If your party stays tightly packed during those fights, the wyrmling breath weapons will erase front line fighters in one round. Spreading out is a simple positional choice that changes the difficulty curve dramatically. I do not enforce this rule. I describe the wyrmling breathing down the corridor and let the players react.
Navigating the Lower Levels
Levels seven through ten are where the cult's leadership becomes visible. The encounters shift from random monster placement to scripted boss fights and narrative decisions. This is also where the module tests whether the party has been paying attention to the earlier content. Several lower level encounters reference information discovered on levels two through five. If the players read the cultist manifest on level three but never acted on it, they miss a major advantage on level eight. I have watched this happen twice. Both times the party died to a boss they could have weakened significantly if they had connected the dots earlier. I do not hold this against the module. I hold it against my own habit of assuming players will remember details they barely noticed. My workaround for the memory problem is simple. After each session I send a one paragraph recap to the table. It includes one specific detail they should notice and one consequence they should remember for later. This has increased player recall by a noticeable amount without feeling like I am handing out answer keys. The recap takes me about five minutes to write and it replaces hours of in-game frustration.
The final level contains the cult leader and a dragon that functions as the climactic encounter. This fight is brutal if the party arrives at full strength and survivable if they have been managing resources carefully. The design intent is clear. The module rewards patience. It punishes aggression unless that aggression is backed by preparation.
What This Module Does Poorly
Every product has weaknesses. Temple of the Dragon Cult struggles most with pacing on the upper levels. There are stretches where encounters feel interchangeable. The kobold lairs repeat the same structural formula three or four times across different levels. This is not fatal. It is just noticeable if you have run the module more than twice. Another weakness is the lack of non-combat resolution paths for several key obstacles. Players who specialize in social skills or arcane knowledge sometimes hit walls where the only option presented is fight or flee. I have house ruled some of these sections to allow skill checks, but the module itself does not support that extensively. If your table favors negotiation over combat, you will need to adapt. The random encounter tables on levels four through six are also denser than most parties can handle in a single session. I recommend cutting them in half for games that run longer than four hours. The encounters themselves are fine. The frequency is not. Running every random encounter slows the game to a crawl and burns through character resources faster than the module intends.
How I Actually Run This Now
My current approach for Temple of the Dragon Cult involves three changes from the default expectations. First, I trim the random encounter rate on middle levels. Second, I emphasize the tracking spreadsheet I mentioned earlier and use it actively during play. Third, I send session recaps that highlight specific details players should remember. These changes have turned what was originally a frustrating experience into something consistently enjoyable. The module still demands attention. It still punishes carelessness. But it does not punish preparation the way it used to. That distinction matters a lot over a ten level campaign. If you are new to this module, start with a party that has at least one character skilled in perception and one with access to healing magic. Neither class is mandatory. Both make the early levels significantly less stressful, and the stress accumulation from those early levels determines whether you survive the later ones.
