I think we need to start with a little disambiguation. This is NOT a review of Ptolus: City by the Spire, the incredible 700-page city supplement originally designed for D&D 3^rd Edition, recently adapted to both D&D 5^th Edition and the Cypher System, and the basis for my own In the Shadow of the Spire campaign.

This is a review of Ptolus: City of Adventure, an anthology of three adventures each sold separately as PDFs:

• The Doctrine of Ghul
• The Runeblood Blessing
• Return of the Ebon Hand

(Also not to be confused for Ptolus: City By the Spire, the graphic novel by Monte Cook and Caanan White. Although the odds of that error being made are probably significantly lower.)

The adventures are designed with the expectation that you’ll be using them in conjunction with the Ptolus sourcebook, but it wouldn’t be terribly difficult to adapt them to any urban D&D setting.

They are dual-statted for use with both 5^th Edition and the Cypher System. I usually find dual-statted books very awkward and frequently confusing, but Monte Cook Games cleverly uses sidebars and iconography to clearly delineate the two sets of stats. The result is easy to read and easy to use.

SPOILERS FOR THE ADVENTURES!

DOCTRINE OF GHUL

In Bruce R. Cordell’s Doctrine of Ghul, an incomplete manuscript purportedly written by Ghul the Skull-King (an evil overlord from the history of Ptolus) has surfaced and is being promulgated through the city. Those who read the manuscript, however, discover that (a) they are cursed to die unless they finish reading it and (b) it’s incomplete, so they can’t do that.

Whether it’s the PCs who get cursed by the incomplete doctrine, someone they care about, or someone who’s willing to pay them for help, they’ll have to journey into Ghul’s Labyrinth — the vast dungeons beneath Ptolus which once served as the barracks for Ghul’s legions and the laboratories for his arcanists — and visit three locations where the missing passages of the Doctrine can be found.

Truth be told, the metaphysics and background of this whole framing device is a dog’s breakfast. The “Doctrine” is actually a fake, created by a wizard named Alberek who wants to bring Ghul back from the dead. Alberek believes that each time someone finishes reading the full Doctrine there’s a chance that they’ll bring Ghul back from the dead… so, naturally, rather than just sending out full copies of the Doctrine, he’s hidden chunks of the text underground so that people have to go adventuring to read the full Doctrine. (Even though this isn’t necessary and, if you copy out the passages, you can bring them back to the surface and have people read them.) Also the Doctrine isn’t completely fake, it’s based on fragments of text which may have actually been written by Ghul. Also also, each time someone finishes reading the Doctrine and doesn’t miraculously resurrect Ghul, Alberek teleports to their location and kills them. For… reasons?

Bit of nonsense really.

But here’s the thing: This whole framing device is, ultimately, just a way to get the PCs to visit three locations within Ghul’s Labyrinth.

• The Frozen Crypt
• The Breeding Pits of Formless Hunger
• The Galchutt Cyst

Each of these locations is a completely independent mini-dungeon, and they’re all quite excellent. Incredibly creepy ambience, clever encounters, and cool lore make each one a delightful gem of dungeon design.

For example, in the Breeding Pits the PCs will encounter an airborne pathogen which subverts their immune systems and uses them to begin creating a grey goo. As they expectorate or vomit forth the strange substance, it becomes animate and begins joining together to form strange servitors seeking to continue the ancient work of the researchers who once labored here.

That’s the kind of idea which elevates a simple dungeon crawl into a truly memorable experience, and each of these locations are studded with stuff like this.

So here’s the bottom line for me: Jettison the wonky framing device and you’re left with three really great mini-dungeons that you can use to flesh out any journey into or through Ghul’s Labyrinth. That’s a fantastic tool for your toolkit! And makes it more than worthwhile to grab a copy of Doctrine of Ghul.

(Just make sure you read the whole thing.)

Grade: B-

THE RUNEBLOOD BLESSING

The Runeblood Blessing by Sean K. Reynolds is a brilliant example of how to prep and run urban adventures.

The concept is that a sorcerer named Vlenn has perfected a magical ritual that will grant people a blood-red rune that gives them a magical power (like blur or invisibility or feather fall). She offers the ritual for an extremely affordable price, and empowered runeblooders begin showing up throughout the city. It’s the democratization of magic and it upsets the existing structures of power in myriad ways.

There’s just one little problem: Some of the runeblooders are dropping dead.

So many published adventures would take this incredibly cool concept and immediately fail to realize its expansive, transformative potential by locking it into some form of linear structure. Reynolds’ skips right past this potential pitfall by instead providing an adventure toybox for the GM to actively play with.

The presentation of these toys can be a little sloppy in places, but it boils down to:

• A series of background events combined with incidental encounters that allow the runeblood blessing to become engrained into your campaign world.
• An investigation track that the PCs might choose to proactively look into the “runeblood sickness” as it begins to emerge through the background events.
• An investigation into various crimes being committed by runeblood-enabled gangs and cat burglars.
• An investigation into Vlenn’s operation, culminating in a location crawl or raid at her headquarters in the Warrens.
• An otherworldly dungeoncrawl in the Shadow of Ptolus (an evil demiplane) where the PCs explore the surreal umbral fortress from which the runeblood blessing’s power flows.
• A set of three Ptolus “side scenes” that further flesh out the life of the city.

The important thing to recognize is that these are all independent (yet overlapping) adventure elements. What makes The Runeblood Blessing so cool is that there’s not some specific moment at which The Adventure™ begins. There’s not one specific point where somebody shows up and says, “You should go on this adventure now.”

Instead, there is this vast, ongoing event that’s happening throughout the entire city. It’s not happening specifically to the PCs. It’s happening to the city. To everyone. And it’s up to the players to decide if, how, and when they’re going to choose to interact with these events: Do they buy a runeblood blessing? Blackmail Vlenn? Investigate the criminals?

The result will add a deeply rewarding layer to your Ptolus campaign, bringing the city to life and making it feel huge to your players. That scope and vibrancy, in turn, will make the PCs feel incredibly important once they get involved.

Highly recommended not only as an adventure in its own right, but also as a nearly perfect exemplar of how to create your own urban adventures.

Grade: A-

RETURN OF THE EBON HAND

The final adventure in the book — Return of the Ebon Hand by Monte Cook and Sean K. Reynolds — is another phenomenal example of how you can/should design adventures for your Ptolus campaign.

There are two things I love here.

First, Return of the Ebon Hand is a sequel. The adventure assumes that the PCs have already routed the Ebon Hand from their temple, which is presented as an adventure location in the core Ptolus sourcebook. Although it can’t be entirely sure how those events might have played out in your campaign, it offers several options and some guidance on how you can adapt the adventure to make it fit.

This is such a great example of how events in your campaign can/should spark additional adventures as events develop over time. (I might have a soft spot here because, in my own campaign, the PCs routed the Ebon Hand and then also had to deal with the legacy of their actions in a subsequent adventure.)

Note: I’ll also note that you don’t have to run this adventure as a sequel. The published adventure notes the possibility of assuming that NPC heroes or the City Watch had cleaned out the Temple of the Ebon Hand, and that perhaps those events could be used as background events in your campaign. But it would also be fairly easy to tweak things so that both the Temple of the Ebon Hand and the New Temple of the Ebon Hand are active at the same time. You could even put Fulton’s Journal, as described below, in the Temple of the Ebon Hand where the PCs can discover it.

The second thing I love about Return of the Ebon Hand is how it showcases using multiple scenario hooks that all point to the same scenario.

The background of the adventure sees the vestiges of the Ebon Hand flee from the destruction of their temple and eventually reorganize into a new temple built around a Pit of Insanity within Ghul’s Labyrinth. Harnessing this powerful artifact of chaos, the Ebon Hand once again begins experimenting with the human mutations which are the heart of their faith and through which they believe they will achieve transcendence.

Their use of the Pit kicks its chaotic power into high gear, and it begins manifesting strange effects in the city above and the dungeon nearby. This includes resurrecting various dead criminals in the crypts of the Prison.

As with The Runeblood Blessing, several background events are presented to integrate this background into your campaign. Then Cook and Reynolds present three scenario hooks:

• The PCs can investigate the chaotic manifestations, eventually tracking them back to the house that the cultists are using to access their underground temple.
• The PCs can investigate the resurrected criminals (who begin causing trouble throughout the city).
• The PCs can be come into possession of journal written by a delver named Fulton, whose adventuring party explored the area of Ghul’s Labyrinth where the Ebon Hand has now established its temple.

The cool thing is that you can deploy all three of these scenario hooks simultaneously. (The PCs might pursue one of them or they might want to pursue all three of them.) The even cooler thing is that it’s not immediately obvious that all three clues point to the same dungeon crawl!

Each hook not only points to a different problem/opportunity (chaos manifestations, resurrected criminals, an enigmatic journal), it also points to a completely different entrance to this section of Ghul’s Labyrinth. So, for example, the PCs might explore the prison crypts, follow the tunnels back to the lair of the resurrected criminals, and then realize, “Hey! I think these tunnels match those in Fulton’s journal!” And then they might explore a bit more and discover the Ebon Hand cultists that have been making headlines in the newssheets for the past several weeks!

In short, it’s a rich, multi-dimensional adventure environment that I think you’ll find really rewarding in actual play.

There are, unfortunately, a couple of flaws here that should be noted.

First, I found the cartography a little underwhelming. There’s some very nice xandering here (including, but not limited to the multiple entrances), but there’s a lot of “square rooms joined by long hallways.” I would have liked a few more geographically distinctive set pieces and perhaps a greater sense of the purpose for which these corridors were originally made. (This should not be interpreted as a knock on the key, which is studded with lots of interesting rooms.)

Second, Fulton’s journal is a really scenario hook and could be a really cool prop. But the adventure chooses to chop the journal up and print each entry directly next to the room which it’s describing. Expect to do some extra work stitching these together, and then even more work filling in the significant lacuna that you’ll immediately discover. (If you don’t do this, your players will find it virtually impossible to get any meaningful utility out of the journal.)

But these quibbles should be understood as exactly that: Quibbles.

Return of the Ebon Hand is a very, very good adventure that’s also a perfect bookend to The Doctrine of Ghul, nicely showcasing a different facet of Ghul’s Labyrinth.

Grade: B+

Style: 5
Substance: 4

Authors: Bruce R. Cordell, Sean K. Williams, Monte Cook
Publisher: Monte Cook Games
Cost: $29.95 (Physical) / $14.97 (PDF)
Page Count: 96

Buy Now!

DISCUSSING
In the Shadow of the Spire – Session 27A: The Midnight Meeting

“By coming here, you have already joined this Brotherhood,” Dilar continued. “Over the next few weeks you will be contacted. For many of you there will be training. You will be asked to do things. Many of these things will seem simple or even unimportant, but you should never doubt that in even the smallest service you are aiding the Brotherhood and all that we are attempting to accomplish.”

If you’re a long-time reader of the Alexandrian, you’re probably familiar with the Three Clue Rule: In a mystery scenario, for any conclusion that you want the PCs to make, you should include at least three clues.

This redundancy makes mystery scenarios robust, so that they don’t break down during play and leave either you scrabbling frantically, your players frustrated, or both. In my experience, the process of fleshing out a scenario to support the Three Clue Rule also usually results in a more dynamic and interesting scenario.

When I’m prepping a module, therefore, I make it a point to check each revelation and make sure that the Three Clue Rule is being observed. For published adventures, unfortunately, this often isn’t the case, and I’ll need to add clues. Session 27 of In the Shadow of the Spire is a good example of this.

Many of the events detailed in this session — the secret meeting and project site — are from Monte Cook’s Night of Dissolution mini-campaign. A key revelation is, in fact, the location of the project site. From the secret meeting, the published adventure includes one clue pointing to that revelation:

Dilar has a number of papers and notebooks with him. […] Among other things, the papers show the location of the Brothers of Venom’s secret project: an apartment build in Oldtown off Crossing Street. The documents refer to the building only as the “secret project” or the “joint project,” however. (The address can lead them to the Temple of Deep Chaos, found in Chapter 4.) The pages also discuss the cult’s new allies, the Ebon Hand cult, and mention that cult’s leader, Malleck, and their activities involving kidnapping young people and transforming them.

(You can also see here a secondary revelation — the alliance with the Ebon Hand — which is non-essential.)

Seeing this, the first thing I did was prep Dilar’s papers as a physical handout that I could give to the PCs.

You can see that this is not particularly elaborate, being a fairly simplistic example of the lore books technique we’ve discussed previously. The primary goal here is just to let the players “shuffle through the papers,” rather than listening to me narrate them. The map here also neatly correlates to the map of the city hanging on the wall during our sessions, so the players would’ve been able to take this handout over to the map and literally figure out where they needed to go.

As it turned out, however, the players never actually got this handout. Which is why the next thing I did was so essential: Adding additional clues to support the revelation.

To the adventure’s credit, it does discuss multiple paths by which the PCs might come into possession of Dilar’s papers: They might, for example, kill him and loot them. Or they might bloodlessly infiltrate the meeting, take the opportunity to surreptitiously peek at his papers, and then get out without the cult being any the wiser.

But these routes still all go through Dilar’s papers, creating a chokepoint that makes the scenario fragile. You can see that in actual play here: Because of how events played out, only one PC infiltrated the meeting, making the “kill all the cultists and loot their stuff” outcome basically impossible. Tee was also well aware of how vulnerable she was, meaning that she didn’t want to take any risky actions that might expose her (e.g., looking at papers she shouldn’t be looking at). If I’d run the adventure as written, it would have broken here.

What I needed to do was create additional vectors leading from the secret meeting to the project site. (Alternatively, I could have gone for a node-based approach, adding clues to the secret meeting pointing to cult-stuff other than the project site, and then seeded additional clues to the project site in those other nodes.) My thought process went something like this:

• Well… what is the actual purpose of this meeting?
• What if it’s to brief cult members on the project site? That would also explain why Dilar is bringing notes detailing the project site to the meeting.
• We know that this meeting includes new recruits. They’re not going to be fully read in on the project. (Which is convenient logic, because otherwise all of the scenario’s revelations would get frontloaded into this single scene instead of being slowly peeled back by the PCs over the course of their investigation.)
• What would the cult be asking new recruits to do that might be related to the project?
• They could be assigned as external security/lookouts!

This immediately gives me two new clues:

• The PCs can infiltrate the meeting and get briefed on the contents of Dilar’s notes.
• The PCs could question Iltumar about what he learned at the meeting.

And then, by having the cult members taken directly from the meeting to the project site, I can add another clue:

• Following cult members leaving the meeting will lead PCs to the project site.

While this took a little bit of thought, one thing to note here is how little prep was actually required. This is often the case. In my experience, it takes virtually no effort and a truly minuscule amount of time to add basic clues to a scenario. That’s because clues are just indicators. The meat of the scenario — the stuff you’ll spend the bulk of your prep time on — is what the clues point at.

(The most common exception to this is when you design a handout for the clue, like the lore book for Dilar’s notes. But this is usually not, strictly speaking, necessary, and the time you’re investing there is more in the value-add of the cool handout than it is in the clue itself.)

Despite the relative ease of adding these clues, also note how much depth we’ve added to this scenario. For example, the original adventure only told us:

The cultists are here to plan further murders, trade advice on poison use, and engage in perverted sexual acts.

But we now have a much more specific agenda for the meeting. The natural interrogation of the scenario that happens when we think about the vectors required for clues means that we now understand the what and why of the cultists here. So if the PCs were to eavesdrop on the meeting or, as it turned out, infiltrate the meeting, we have a much firmer foundation to stand on for improvising the scene.

As I say, this happens all the time when you apply the Three Clue Rule in your scenario design.

The other thing you’ll discover is that missed clues will no longer be something that you fear. This can feel weird, but it’s incredibly liberating. For example, if this scenario had still depended on Tee looking at Dilar’s notes, I would have felt the need to reassure her that it was OK to sneak a peek. I would have needed to find some direct or indirect way of letting her know that she didn’t really need to be afraid of exposing herself and getting caught.

But because I knew that I’d made the scenario robust, I didn’t need to do that. The result was a vastly better scene, in which the tension of discovery drove the stakes from beginning to end. It would have been a shame if I’d felt a need to deflate that tension in order to prevent the scenario from breaking.

And this is, again, something that happens all the time when you’ve got the Three Clue Rule backstopping you. Missed clues are no longer catastrophes; they are a vital part of the scenario’s flow.

If you haven’t experienced this firsthand, it can feel paradoxical. It might even feel like a violation of the principles of smart prep: You have this prepped content that you’re not using! It’s wasted! But, in practice, missing a clue isn’t a waste — it’s a consequence, a cost, or a choice. And even if you have a clue that is “wasted,” it’s not that big of a deal because, as we noted before, the clues are mostly ephemera. They aren’t the meat of the scenario.

NEXT:
Campaign Journal: Session 27B – Running the Campaign: Improvising Floorplans
In the Shadow of the Spire: Index

DISCUSSING
In the Shadow of the Spire – Session 26D: Elestra Digs Deep

Jamill slammed back the last of his amber-colored drink. “Okay, this is your last chance. Who sent you?”

Elestra suddenly became aware that two rather large men with short clubs strapped to their thighs had suddenly materialized out of the crowd behind her. She stammered, unable to find any kind of answer that would satisfy Jamill.

Jamill jerked his head and headed towards the back of the bar. The two thugs laid their hands on Elestra’s arms. She got the message and let them hustle her out through the back door of the tavern.

When you have factions in your game, those factions should react to the actions of the PCs.

But if factions act as if they know every action the PCs take – as if they were omniscient, all-knowing entities with an eavesdropping device planted under the gaming table — that becomes a frustrating experience for the players and stifles their ingenuity.

There are a number of methods you can use for handling this, but I’ve generally gotten good results taking the decision out of my hands and mechanically determining it.

For example, you might have a random faction encounter check, similar to a random encounter check. For example, roll 1d6 once per day and if you roll a 1, some faction is going to take action against the PCs (or, at least, based on what they know about the PCs’ actions). Increase this to a 2 in 6 chance if the PCs have been making a lot of “noise.”

Another option is to mechanically check whether specific PC actions are detected by relevant factions (e.g., the faction they’re taking the action against or a faction that has them under surveillance). You can think of this as a stealth-type resolution, but at a more abstract level (and possibly using different skills).

Note: This is different than a situation where a faction DEFINITELY knows what the PCs are doing. For example, if the PCs break into a Renraku facility and get spotted by surveillance cameras or fight NPCs who escape and can identify them, you can just actively play Renraku’s response.

A key thing I recommend here is that the PCs should be able to influence the outcome of these mechanics, ideally in a way that involves meaningful choices by the players and is more than just an all-or-nothing decision to take or not take the risky action.

For example, the events in this session use the counter-intelligence system I shared here on the Alexandrian back in 2010. (When I originally mentioned them in this article and talked about the gameplay they made possible that otherwise would never have arisen, it was specifically this Ptolus campaign I was talking about.)

The other thing to note about these counter-intelligence mechanics is that they aren’t uni-directional: The players can also use them to figure out if people are asking questions about them.

In the case of this session, the impact on play was pretty straightforward:

• Elestra succeeded on her Gather Information check to gain information about the cult Iltumar was involved with.
• But the cult also succeeded on their counter-intelligence check to detect that Elestra had been asking questions about them, resulting in the ambush at the Onyx Spider.

Elestra really had dug a deep hole for herself here, and I thought it quite likely that the scenario was now going to turn into a rescue op by the other PCs. (Or possibly even somebody finding Elestra’s body in an alley. The decision not to tell anyone else in the group what she was doing was incredibly risky.) But she managed to turn the tables quite nicely.

Taking Jamill back to their rooms, on the other hand, was a potentially disastrous decision from a counter-intelligence standpoint: The bad guys didn’t know who Elestra was, but if they knew where she lived they’d be able to figure it out pretty quick.

Tee recognized the risk and took some very smart actions to blunt the counter-intelligence vectors that had been established. Just dumping Jamill somewhere would have left him free to continue trying to figure out who Elestra was and why she’d been asking questions. Running him out of town under the guise of the cult itself AND planting the idea that Elestra had been “dealt with” even if she decided to stay in town was both a plan and a contingency plan.

The follow-up decision to then use Jamill’s identity to infiltrate the cult itself was also smart play, and would shape how the entire scenario would play out.

NEXT:
Campaign Journal: Session 27A – Running the Campaign: Missing Clues
In the Shadow of the Spire: Index