DISCUSSING
In the Shadow of the Spire – Session 35B: Letters of Mysterious Motive

Tor was deeply concerned by the missive from the Order of the Dawn.

“Could he suspect? But if he was going to kill me, why would he send me a note?” Tor shrugged. “Of course, the last time I tried to think my way through this sort of thing, I ended up over-thinking it.”

I use a campaign status document to keep track of the loose threads, NPC actions, faction agendas, backdrop events, and everything else that goes into bringing a reactive and dynamic campaign to life.

This session is a great example of how you can take material from your campaign status document and weave it together into a complex and compelling session for your players. To follow along, though, you’ll first need to understand the various materials I’ve prepped for the In the Shadow of the Spire campaign:

• Campaign Status Document, the details of which we’ll be diving into shortly.
• Scenarios, which are probably largely self-explanatory. The overall campaign structure is node-based (with a subset of megadungeon-structured scenarios), so I also have a Campaign Revelation List which shows how all of the scenarios are connected to each other via clues. (This campaign is old enough that this document is still referred to as the “Adventure Track.”) The scenario notes themselves are divided into the separate acts of the campaign, and Act II into three subsections: Banewarrens scenarios, Night of Dissolution scenarios, and Chaos Cult (I use this division when organizing scenario files on my hard drive. I also have separate three-ring binders for each scenario type — so I have a Banewarrens binder, a Chaos Cult binder, and a Night of Dissolution binder at the table, although I believe at this point in the campaign, the CC and NOD scenarios were still in the same binder.) These scenarios are further indicated by an alphanumeric code, so NOD3 is the Surgeon in the Shadows, for example, while BW05 is the Outer Vaults of the Banewarrens.
• Backdrop Files, which I discuss in the Smart Prep Each backdrop file provides a focused breakdown of ongoing background events that are related to each other. I maintain a number of these for the In the Shadow of the Spire campaign, but the two relevant for the current session are Backdrop 1: Balacazar vs. Killraven and Backdrop 2: Novarch in Exile. (At this point, the latter of these has begun transitioning out of being purely background material because the PCs keep getting involved with church politics.)
• Interludes, which are scenarios unconnected to the primary campaign structures. This is a mix of one-off events, scenarios created by the players pursuing agendas of their own creation, and other miscellanea.
• Subplots, which are long-running series of events which the PCs are interacting with (or expecting to interact with). A lot of these seem to end up being factions. (The distinction from Backdrops is that, due to their interactivity, the Subplots have either mini-scenarios or full scenarios. The distinction from Interludes is that Subplots aren’t one-shot adventures; they’re long-running sequences. Although, again, these distinctions get blurred in practice as PCs ignore subplots, get involved with events I thought were backdrops, or have long-term events spin off from an Interlude.)

It might be worth noting that I’m not super-invested in the Backdrop/Interludes/Subplots division; it’s just what I’ve found useful for organizing my notes for this specific campaign.

Okay, with this groundwork laid, let’s dig into Session 35.

IN THE CAMPAIGN STATUS DOCUMENT

The campaign date is 09/18/790 — the 18^th day of Kadal in the 790^th Year of the Seyrunian Dynasty. The PCs have spent most of the day — in sessions 32 thru 34 — engaged with the chaos cultists at, first, the apartment building where they’re conducting their venom-shaped thrall experiments and, later, in the ruins of the Old City below the apartment building.

The result is that a bunch of events scheduled for the 18^th have stacked up, particularly because the PCs spent most of the 17^th throwing a huge spanner into the schisming of the Imperial Church and getting themselves thoroughly tangled up in a city-wide political crisis.

The two most relevant sections of my campaign status document here are the Newssheets (summarizing backdrop events in the city) and Events (which are things more or less “aimed” at the PCs). These are the relevant entries from each section for the 18^th:

NEWSSHEETS

• 09/18/790: Blood in the Bathhouse. A flock of ravens bursts the doors on the Row Bathhouse and drives out the customers. When the ravens fly out again, the baths have been polluted with Blood. (Tavern Row War)
• 09/18/790: Vile Rites Performed in Oldtown! Report on what the City Watch discovered in the Oldtown apartment complex.

EVENTS

• 09/18/790: Ranthir receives a letter from Mahdoth’s. (BW03A)
• 09/18/790: Jevicca uses a sending to contact them. (Jevicca’s Sending)
• 09/18/790: Gemmell sends Tor a letter. (The orc prisoner has escaped with inside help; Sir Kabel was warned. Gemmell is worried that there are traitors in the ranks. But he trusts Tor because he gave him Kabel’s letter.)
• 09/18/790 (8 PM): Meeting with Sir Kabel at Pythoness House. (Meeting with Kabel)
• 09/18/790 (11 PM): GQT2 comes to Nibeck Street mansion. (BW Status)

The text in parentheses at the end of some of these entries indicate that they are pointers, either to a separate document (e.g, Tavern Row War refers to a section of Backdrop 1: Balacazar vs. Killraven) or to a later section of the campaign status document (e.g, BW Status and Jevicca’s Sending are both sections which appear later). This way, these sections of the campaign status document don’t become overwhelmed with so much information that they can no longer serve their essential function.

You can see in the case of “Gemmell sends Tor a letter,” however, that the supplementary info was short enough that I could just leave it in situ. Similarly, the specific details of “Vile Rites Performed in Oldtown!” are something I’m prepared to just improvise as necessary.

In addition to these regular sections of the campaign status document, I’ve also added a special section entitled Tavern Row Events. These are “random” encounters that I prepped several weeks before this session as part of Backdrop 1: Balacazar vs. Killraven. Since the PCs are boarding just around the corner from Tavern Row — and regularly walk up and down the street — I wanted them to experience some of the peripheral shrapnel of this gang war themselves. I’ve transferred the events from the Backdrop File to the campaign status document so that they’ll be right in my face when I’m running the session. (That way I won’t forget about them.)

Usually I would integrate events like this into the regular sections of the campaign status document, but in this case I decided it would be more useful to keep them grouped together. (Particularly because they weren’t keyed to specific dates or times.)

TAVERN ROW EVENTS

Raven Spies: While passing down Tavern Row, the PCs notice an unusual number of ravens roosting along the rooftops — peering eerily down into the streets below. Passersby keep glancing up nervously at them.

• These are Killraven spies.
• Just before the Showdown at the Onyx Spider, the number of ravens will multiply, roosting on seemingly every rooftop.

The Stink Man: The PCs are in position to spot Durant and a couple of Killraven thugs heading into the Old Goose tavern. They’re either there to intimidate Unos (before the 15^th), kill Unos (on the evening of the 15^th), or to threaten Unos’ heir Talia.

Tellith’s Problems: Tellith is harassed by Killraven enforcers: An ogre sorcerer named Fatok and three thugs. They’re demanding a monthly protection payment of 100 gp.

• “Don’t think your delver friends will help you.”

We can now see all the pieces that have been laid in place. These events have built up over time — either from long-term backdrop prep; time events; or consequences spinning off like free radicals from the actions of the over the last dozen sessions. All of these separate vectors have converged to seed the campaign status document with these specific mix of events for the 18^th, and then the PCs actions on the 18^th itself have further shaped how they’ll play out at the table.

RUNNING SESSION 35

You may want to pop open Session 35 in a separate browser tab so that you can follow along as we walk through the events that played out.

Having left the chaos temple in the Old City at the end of Session 34, the PCs kicked things off with some logistical play: Inventorying their loot, identifying magic items, etc. Standard stuff.

They had completed these chores as a matter of urgency and necessity, but now that the dinner hour was approaching, they realized they were still variously caked with sewer sludge, crusted blood, and other various foulnesses. And sothey headed toward the bathhouse on Tavern Row.

One of the reasons for keeping a campaign status document is that it can sit on the table right next to you during the whole session. Throughout the session, therefore, I’m consistently checking the campaign status document; sort of “touching base” to make sure I’m not forgetting anything and/or looking for stuff that I can opportunistically inject into the ongoing events.

Here my players are announcing their intention to visit a bathhouse on Tavern Row, and right at the top of my campaign status document I’m looking at the “Blood in the Bathhouse” event.

So this is pretty straightforward, right? It’s a no-brainer to have them arrive in the immediate aftermath of that event.

I then cross out this event, which obviously helps me keep track of what has and hasn’t happened. In addition, it also makes it easy for me to update my campaign status document between sessions by simply looking for and removing entries that have been crossed out.

With a shrug, Tor and Tee headed into the bathhouse. They found Derra, the proprietress of the bathhouse, being questioned by a watchman. Tee took the opportunity to sneak through the far door and into the baths themselves.

One consequence of having the PCs arrive in the immediate aftermath of the event — rather than hearing about it later through the rumor mill or by reading about it in a newssheet — is that they can choose to interact with it. “Derra” is just an improvised name, but I make a point of writing it down in my notes.

As they emerged from the door, they spotted a raven watching them from the roof on the opposite side of the Row. Seeing that it had been noticed, the raven took off and began to fly away to the south.

Since the PCs are on Tavern Row, it’s also time to trigger one of the Tavern Row Encounters. Here I’ve grabbed the “Raven Spies” encounters. It plays out a little differently than written because of the present circumstances. This is just fine, of course. But I also make the decision to NOT cross out the encounter. This is an encounter that could be easily repeated in any case.

Elestra flew in through the window of her room. The others followed on foot.

But when they opened the front door of the Ghostly Minstrel, they found Tellith being confronted by a large ogre and three thugs.

“—and don’t think your delver friends will help you,” the ogre growled.

“Delver friends like us?” Tee stabbed him in the back.

Elestra choosing to fly the Killraven spy straight back to their rooms (oh no!) has complicated this sequence of events more than I’d anticipated. (My thought behind the encounter was more along of the lines “look at those creepy ravens; they’re very creep.”)

Your thought might be to simplify it back down. Mine, on the other hand, is to seize the opportunity to add even more complexity to it. And since everyone is rushing back to the Ghostly Minstrel, I have an easy tool to do it: The “Tellith’s Troubles” encounter is not only apropos, but will also complicate the group’s desire to reach their rooms and join Elestra.

Tellith thanked them again for their help. While she was expressing her gratitude, she remembered that letters had come for “Master Ranthir and Master Tor, now where did they go? Ah! Here they are!”

Checking in with my campaign status document again, I can see that several letters were supposed to arrive for the PCs throughout the 18^th. Since they’ve been out all day, these have all stacked up.

And this, of course, is a perfect time for Tellith to deliver them.

You can begin to see how all of these separate elements, independently added to my campaign status document (often just one at a time!), begin weaving together during actual play into complex, multilayered scenes and sequences.

THE WEAVING OF TOR

“Nor is that the only treason in our midst. The orc woman you captured in the Banewarrens has escaped.”

“Escaped?” This time Tor was truly surprised. “How is that possible?”

“There must be a traitor within the Order,” Gemmell said. “The truth is that you’re the only one I can trust. You not only gave me Sir Kabel’s location, but you were also responsible for capturing the escaped prisoner.”

Tor valiantly stopped himself from gaping. “I’m honored that you would place your faith in me.”

This is one of my favorite moments in the entire campaign.

It started back in Session 31, when I set up a crucible choice for Sir Tor by having Sir Gemmell and Sir Kabel both send him a letter at the same time: Which letter would be he respond to? Which side would he choose in the schisming of the Church and the Order of the Dawn?

And then Tor blew my mind.

Believing that the arrival of both letters nearly simultaneously was too strange to be a coincidence, Tor concluded that Sir Kabel’s letter was a fake, sent by Sir Gemmell to test his loyalty. So he responded by showing Sir Gemmell the letter, unwittingly betraying Sir Kabel.

That alone was the stuff great game sessions are made of: Tor was going to be completely devastated when he realized what he’d done!

… except the player mulled it over, and realized that she may have made a mistake. So Tor took emergency action and managed to warn Sir Kabel in the nick of time! Sir Kabel escaped just before Sir Gemmell arrived to arrest him!

Meanwhile, in that same session, the PCs had captured an agent of the Pactlords in the Banewarrens. (This was unanticipated, as I’d expected them to kill all the Pactlords.) After attempting to interrogate her, they decided to turn her over to the Imperial Church for safekeeping.

This was even more unexpected!

What the PCs didn’t know is that the Pactlords had a highly placed agent in the Imperial Church, and so the logical outcome of this was that the Pactlord agent would escape from custody.

At this point, Session 31 came to an end and I had the luxury of sitting back and thinking things through at my leisure. I put myself in Sir Gemmell’s position. I thought about what he knew. I thought about what his goals were. I thought about what his fears were.

… and that’s when I realized that from Gemmell’s point of view Tor was the only person he could trust.

Completely and unequivocally.

And, therefore, there was only possible thing for Gemmell to do: Immediately knight Tor so that he would be in a position to help Gemmell root out the traitor in his midst!

I don’t know if this will blow your mind the way it blew mine. But of all the possible outcomes I could have possibly imagined when this sequence of events was set in motion, I literally could not have imagined any of this happening. That’s the amazing beauty and incredible power of a roleplaying game.

And, again, you can see all of these threads weaving together and becoming something greater than the sum of their parts.

Tor was ecstatic at the thought of being knighted. He was so excited, in fact, that he stopped to buy a couple bottles of wine on his way back to meet the others.

The other thing I’ll note is that I’d originally expected Tor to receive Sir Gemmell’s letter earlier in the day. So his meeting with Gemmell  happening at the same time the group was meeting with Kabel is actually another example of events unexpectedly weaving together.

They were glad to see him well, and surprised to see the giddy smile on his face. As Tor was explaining the situation to them, however, Agnarr’s eyes suddenly glazed over and he spoke aloud:

Jevicca requires a meeting. I request an update on your progress and have information for you.

… and we’ll go ahead and weave a little more by grabbing our last unresolved event for the 18^th that doesn’t have a specific time attached to it and drop it into this scene.

With that done, I’ve crossed out all the events on the 18^th except this one:

09/18/790 (11 PM): GQT2 comes to Nibeck Street mansion. (BW Status)

And this one is interesting because at this point I’m assuming that I know exactly how things are going to play out at 11 PM.

It turns out, though, that I’m very, very wrong.

But we’ll talk about that more next time.

Campaign Journal: Session 35C – Running the Campaign: Ambushing Your Timelines
In the Shadow of the Spire: Index

Tired of just reading from a script? USA Today Bestselling Author and ENnie Award-winning RPG designer Justin Alexander will help your reinvent your boxed text and bring your RPG adventures to life! Whether you’re using scripted boxed text, bullet points, or highlighters, learn how to describe an entire world!

Subscribe Now!

SPOILERS FOR DRAGON HEIST

Matu67 asks:

I’m running Waterdeep: Dragon Heist (Alexandrian remix), and I’m wondering: How do you improvise sources of information?

For example, a faction knows that character X did Y, but the DM hasn’t written down the reason why the faction knows this. When the players ask the faction, “How did you come across this piece of info?”, what do I say as the DM?

In Dragon Heist, for example, the Cassalanters know that Dalakhar was carrying the Stone of Golorr, and the DM is encouraged to give this information to the PCs if the PCs ally with them. Then the PCs ask, “Hey, Cassalanters, how do you know that?” And then I freeze up.

We can start here by getting down to the most basic ontology of the question:

How do we know things?

In this case, how does a faction in an RPG scenario — like the Cassalanters — know stuff? Where does that information come from?

Well, broadly speaking, they will have agents. (In an espionage campaign like Dragon Heist these might be literal secret agents, but generally we just mean anyone who’s a member of the faction or working with the faction.) For a faction to “know” something, it means that these agents will have either witnessed it directly or they’ll have learned the information from someone who did.

For example, “How do you know the Potenska Apocrypha can be found in the Ebon Library?”

Either someone saw the book in the Ebon Library themselves, or they’ve spoken to a scholar / read a reference to the Apocrypha in another book / cast a commune spell and been informed by the gods that the book is there.

To forge that connection, start with: Who definitely knows about the thing you’re trying to source?

For example, who knows that Dalakhar has the Stone of Golorr? Well, Dalakhar, obviously. But also, since he stole the Stone from Xanathar, members of Xanathar’s gang would know.

Who knows that the Potenska Papers are in the Ebon Library? Well… librarians, right? And probably other scholars who have seen it there? (To this general list, you could potentially also add any specific NPCs who you know have visited the Ebon Library.)

At this point, you have two options for creating the data trail.

First: If it’s possible the agents could have directly witnessed the information, then problem solved. You’re done. (e.g., “When I visited the Ebon Library, I saw the Potenska Papers in their collection.”)

You can flesh this out by providing an explanation for why they were there. (e.g., “When I was at the Ebon Library researching a summoning ritual for Demogorgon, I saw the Potenska Papers in their collection.”) The great thing is that, in an espionage scenario, you can almost always default to “…because they were spying on them” as the explanation. (e.g., “Our spy in Xanathar’s hideout was there because they were spying on Xanathar.”)

Second: If agents couldn’t have directly witnessed the information, then you just need to connect the agents to the people who do.

In some cases, it will be easier – or more fun! – if you imagine this happening in multiple steps. (For example, X talked to Y and the conversation was overheard by Z. Or the Iranian Ministry of Intelligence intercepted communication between a US Senator and the Lytekkas Corporation, which was scooped up from a vulnerable server during a Mossad operation, and we grabbed it from them because we’ve got a worm installed in their Tel Aviv data center.)

But you don’t usually need to over-complicate it. A single step is usually more than enough.

For example, “We have an informant in Xanathar’s gang, and he was sent out as part of a team to find Dalakhar and retrieve the Stone.” Or, “One of our agents intercepted written orders that were sent to Xanatharian agents to be on the look out for Dalakhar and to retrieve the Stone he carried.” Or, “I hired a Sage of Orthoria to research the Potenska Papers, and they found a reference to a copy that was given to the Ebon Library.”

If the players want to dig even deeper – e.g., “Who is this agent?” – an espionage campaign usually gives you the luxury of waving them off. (“Their identity is confidential. I’m sure you can understand that revealing it could potentially put them in danger.”)  On the other hand, there’s often no harm in satisfying their curiosity: If you know who the agent is, great If not, then it’s time to reach for your list of NPC names and spin somebody up.

This may also be a good point to figure out why the players are so insistent about digging into this data trail. (This is a slightly hidden case of making sure you know the intention of an action before resolving the action.) For example, maybe they want to question the Cassalanters’ informant; or maybe they just want to make sure they don’t accidentally kill them when they raid Xanathar’s hideout. Maybe the reason they want access to the original Tel Aviv intercept is because they want to run a data analysis and see if they can identify the location of the IP address the message was originally sent from.

Once you know what they’re actually looking for, it becomes a lot easier to aim your improv.

The way to do this, of course, is to simply ask them!

You might be able to do that in character – for example, the Cassalanters ask them why it’s so important for them to know the identity of their informant. But, as the GM, you can also just ask the players directly what their goal is.

Go to Ask the Alexandrian #13

DISCUSSING
In the Shadow of the Spire – Session 35A: Birds of Black Feather

Once they had emerged from the sewers, they sold the unclaimed items in various shops across Midtown and the North Market. Then they headed to the Cathedral and received divine healing, mystically purging their poison-wracked bodies. They also took the opportunity to stock up on a variety of portable curatives so that they would be able to deal with poison on site in the future. (“This probably won’t be the last time we’ll be dealing with the Brotherhood of Venom.”)

They had completed these tasks as a matter of urgency and necessity, but now that the dinner hour was approaching, they realized they were still variously caked with sewer sludge, crusted blood, and other various foulnesses. And so they headed toward the bathhouse on Tavern Row.

I’ve previously discussed expedition-based play, but the quick version is that:

1. The party gathers resources in order to…
2. Venture forth in pursuit of a goal, during which…
3. They will attempt to use their resources to best effect in order maximize the progress and/or payoff of their expedition.

The resources in question might be either practical supplies (e.g., rations or gasoline) or mechanical benefits (e.g., hit points and spell slots). The goal might be either specific (e.g., root out of the cultists) or general (e.g, loot as much treasure as possible).

The fun of expedition-based play comes from the challenge of maximizing the return on your investment. At some point, though, you’ll burn through your resources and be forced to return to your home base so that you can gather fresh resources for the next expedition.

This dynamic, however, can lead to expedition-based play being characterized as the PCs always losing and needing to run away with their tails tucked between their legs. When it’s perceived in this way, of course, expedition-based play can seem incredibly frustrating: “We failed again!”

As we can see at the end of the last session and the beginning of this one, however, the real secret to expedition-based play is figuring out when to beat a jubilant strategic withdrawal just BEFORE you hit the challenge that depletes your resources and leaves you fleeing in abject desperation. In fact, finding that moment of jubilant withdrawal is one of the great joys of dungeon exploration: You have fought the good fight. You have reaped your rewards. You have laid the groundwork for the even greater success of your next expedition!

That is, without a doubt, a triumph, and must be seen as such.

You won’t always find that perfect moment, of course. That’s OK. If there weren’t setbacks, the victories wouldn’t taste as sweet.

Finding the perfect moment, of course, is a matter of experience. And, honestly, I find it to be as much art as science.

Some may believe that they can outthink the problem by simply leaving long before their supplies run out. “If we never put ourselves at risk, then we can never fail!” goes the logic.

Such an overabundance of caution, however, is really just a different kind of failure. If nothing else, it’s a failure to realize your potential. On a more practical level, overly frequent retreats can be particularly devastating – ranging from the frustrating to the disastrous – if the GM is running a dynamic dungeon that responds to the PCs’ actions. In those circumstances, the overly-cautious group may find it incredibly difficult to make any real progress towards their goals, instead finding themselves fighting over the same dungeon rooms again and again and again, like some sort of subterranean reenactment of World War I trench warfare.

But when you find the sweet spot! That’s a glorious moment! You leave your foes broken behind you and emerge back into the warmth of the sun, looking around the table to see the grinning faces of your fellow adventures. And then you count your coins and gems, marvel at your new magic items, and tally your experience points.

You have reached the top of one pinnacle, and now it is time to prepare for the next!

Campaign Journal: Session 35B – Running the Campaign: Weaving the Background
In the Shadow of the Spire: Index