Recommendations – Page 2

Blades in the Dark Player Best Practices

At this point, I’ve dealt, at length, with the GM advice, but what about the players? Surely they deserve a little guidance too!

Yep, they have not been forgotten.

Progress Clock

We started our Blades in the Dark campaign last Wednesday with a character creation session. I had hoped that we’d be able to get down to the first score as well, but it was not to be. Honestly, character creation, although pretty straight-forward, was rather time-consuming. When you have three or four people around a table making decisions on their own characters as they try to form a coherent picture of them in their minds, it can take a while. Add on the collaborative decisions required of them for Crew creation, and you can comfortably double the time required.

Anyway, current progress looks like this:

Three of four characters created, an Akorosi Cutter, an Akorosi Hound and a Whisper from the Dagger Isles
Crew created: It was a toss-up between Bravos and Smugglers but, with the general vibe of the crew so far, Bravos won out in the end.
Decided that their main sponsor faction will be the Crows of Crows Foot.

I’ll get a character creation session with our last player in the next week or so and then we’ll be ready to launch into the first score.

Creating Opportunities

That’s what this game is all about, right? Taking chances, building relationships, gathering information, making your own opportunities. Well, that’s what I’m doing today. Instead of the recap of the first score, I’m using this opportunity to discuss the advice levelled at the players in a Blades in the Dark campaign. At this point, I’ve dealt, at length, with the GM advice, but what about the players? Surely they deserve a little guidance too!

Yep, they have not been forgotten.

Starting on page 182 of the Blades in the Dark book, at the end of the How to Play chapter, we have the section entitled…

Player Best Practices

The Lurk, a light-skinned, femme character dressed in a dark hood. — The Lurk, by J Harper

We have a total of eight of these listed here. Not as many as for the GM, but there’s a lot in each one. Here’s what we’ve got:

Embrace the Scoundrel’s Life
Go into Danger, Fall in Love with Trouble
Don’t Be a Weasel
Take Responsibility
Use Your Stress
Don’t Talk Yourself out of Fun
Build Your Character through Play
Act Now, Plan Later

As usual, I’m not going to go into detail on all of these. This time, I’m going to group them.

Embrace the Scoundrel’s Life + Go into Danger, Fall in Love with Trouble + Don’t Talk Yourself out of Fun

These three best practices all relate generally to the same issue. You, as a player of Blades in the Dark, are not there to play it safe. You are not at the table to make optimised choices. Your character lives in a brutally unfair world and they have become adept at surviving it and even profiting from it. Lean into that! Will they have to make difficult choices that might lead them or their crew to harm? Yes! Will they have to take wildly risky actions to achieve their goals or create those opportunities? Yes! Will they have accept the consequences of their actions, which might include conflict with the highest powers int he city, imprisonment and death? Yes! This is the good stuff, in fact, not the downside. These are the parts of the game that keep it moving forward and allow you to craft scenes of kick-ass action, ice-cold espionage and even heart-breaking tragedy. This is why you want to play. If you’re playing to win, instead of to find out what happens, you won’t get the most out of this game.

Don’t Be a Weasel + Use Your Stress + Act Now, Plan Later

You know, there’s a common thread running through all the best practices for players, to be honest. I think it can best be described as “let go.” You have a say in what happens in the story, of course, but you should not be precious about your character. Push them as far and as fast as you can, drive them like that proverbial stolen car. These three practices are about doing that within the rules of the game. You do stuff by rolling with Actions, not skills. It’s important to choose the right action for the job, even if it’s not your best. That’s where stress comes in! One of your companions can spend stress to help your actions succeed with an assist, or you can spend it to push yourself. It’s invaluable for resisting consequences that would be otherwise inevitable. You can even use it to work in a flashback and do a setup action to get you out of a particularly sticky spot. You will build up the stress, of course. You’re going to have to indulge your vices to shed it or you’re going to find yourself traumatised. That’s where these stories end up sometimes. Your PC might build up a weakness or two, they might be brought to the end of their tale through the extremities of stress. But what a tale it will have been!

Take Responsibility + Build Your Character through Play

Blades in the Dark is a story game. You are telling a story at the table with your friends and you want it to be the best it can be. You want it to have ups and downs, ins, outs and what-have-yous. Dark, tragic, thrilling, horrific comedic, action-packed, whatever you want it to be, you can contribute to it. You have the option to add as much or as little as you like. Some players are going to invent new NPCs, locales, factions, street-vendors, family-members, ghosts, you get the idea. This is all good. But a player’s greatest power to contribute to the story is through their own character. The actions they take, the things they say, these things can add as much to a session as the NPCs invented by the GM, probably far more. Maybe you are already delighted with the general atmosphere and vibe the rest of the table is bringing, so you don’t feel like you need to add too much, you still have a responsibility to your own character, to have them grow from their beginnings into fuller, more alive beings. You start with a “sketch” but, through the actions you choose for your PC, how they comport themselves in various situations, the risks they are willing to take, you’ll make an unforgettable character and story.

Conclusion

The Shade. A floppy-haired dandy in a Victorian gentleman’s clothing. — The Shade, by J Harper

Like I stated above, there is a strong theme across all of these best practices: don’t be boring. In a game like this where the story evolves collaboratively at the table and is not even slightly left up to a published campaign frame or the GM, the choices you make as a player will dictate the sort of experience you have. Be bold, don’t behave.

Blades in the Dark GM Tools

I’ll be honest, I don’t usually think about the games I run in terms of goals, beyond a vague desire to do my best to GM competently, engage the players and make them entertaining.

Good Advice

So, like I said in my last Blades in the Dark preview post, this book is full of great advice. Today, I’m going to take a closer look at some of the advice for GMs that is not directly related to the first session or two. This is the sort of thing that will help you create the best version of your game at the table every session.

GM Goals

I’ll be honest, I don’t usually think about the games I run in terms of goals, beyond a vague desire to do my best to GM competently, engage the players and make them entertaining. Many of the other games I’ve played don’t deal in these terms at all, but I find I appreciate the project-like manner Blades employs here. It’s good to state your goals before embarking on any sort of initiative, otherwise, how do you know if you manage to achieve them? What do you use to steer your efforts?

Here are the GM Goals as stated in Chapter 7, Running the Game:

“Play to find out what happens.” This is the primary guiding principle. A concept that was introduced by D. Vincent and Maguey Baker in Apocalypse World, “play to find out” is central to Blades in the Dark. The idea here is that you have no set narrative in mind, no list of occurrences that you’re waiting to introduce to outfox or defeat the PCs, no plan at all. Instead, you let the PCs lead the way. Their own plans, desires, vices, mistakes etc. will drive the story forward in a way you could never have imagined beforehand. The GM here is just as “in the dark” as the players are about what’s coming.
“Convey the fictional world honestly.” Honestly, I am struggling with this one. The advice here is to “make the world seem real, not contrived.” Of course, this is a reasonable suggestion, but much more difficult in practice, I imagine. It pre-supposes this “vision of Duskwall in your head.” But, in a game where the GM is largely just reacting to things the players invent or decide, the vision is probably changing constantly. You’re told here, though, “don’t play favourites,” as well, so I begin to see the purpose a little clearer. The idea is that, as GM, you should not be inventing elements of the world that exclusively benefit just your NPCs, or explicitly disadvantage the PCs in ways that seem unfair. I suppose it could also refer to a tendency some GMs might have to treat certain PCs better than others. Resist that urge! Play fair!
“Bring Doskvol to life. Give each location a specific aspect (crowded, cold, wet, dim, etc.). Give each important NPC a name, detail and a preferred method of problem solving (threats, bargaining, violence, charm, etc.). Give each action context—the knife fight is on rickety wooden stairs; the informant huddles among the wreckage of the statue of the Weeping Lady; the Lampblacks’ lair stinks of coal dust.” I wanted to quote this whole paragraph because it is filled with practical, actionable advice that I would struggle to paraphrase. I have to say that this is a reasonable goal for any RPG, not just this one.

GM Actions

Two dark silhouettes having a knife fight. The dark city streets are portrayed within their shadows. — Knife-fight City – J Harper

So this is one of the ways in which you, as the GM of Blades in the Dark, can endeavour to achieve your goals. I guess these are the story-game equivalent of an OSR GM’s Random Encounter tables, weather and misfortune tables and hex maps. Essentially, when it’s your turn, you can look at the list of GM actions and choose one to keep things interesting.

Ask questions
Provide opportunities & follow the player’s lead
Cut to the action
Telegraph trouble before it strikes
Follow through
Initiate action with an NPC
Tell them the consequences and ask
Tick a clock
Offer a Devil’s Bargain
Think off-screen

I like that these are presented as moves. These are all the types of things you might do a GM in any game to spice things up, to introduce complications if its all going a little too well, if the game is getting stale. But, in other types of RPGs, they aren’t treated like the action you get to do on your turn, in fact, they are rarely dealt with at all.

Now, I’m not going to deal with each and every action here. Some of them speak for themselves and their purpose is obvious. For instance, “Ask Questions,” is very broad, but I think its fairly clear that it can be used in almost any situation to gather information, provoke actions, or even get the players involved in creating situations and the world. “Cut to the action,” is a great way to take the reins briefly to prevent plan-spiralling or similar. But I do want to look at a couple of these a bit closer:

Provide opportunities, follow their lead

This is how “play to find out” works in practice. You can’t simply allow the players to create their characters, tell them a bit about the city and ask them what they want to do. I mean, you could, but they will proceed to have a million questions. The starting situation is designed in such a way as to provide the opportunities ready-made for them, but from that point on, it’s up to the players to find them. It’s the GM’s job to present them according to how the PCs went about it. So you follow their lead. If they go scouring the underworld for leads, they might hear of a secret cache of electroplasm in a poorly guarded warehouse near the docks, but it might be inferior quality information. Or, they might read about a prestigious visitor from the Iruvian embassy with a price on their head attending the opera form a report in the newspaper. They might take very different approaches to find these opportunities and it’s up to the GM to provide what’s appropriate.

Sometimes, though, the players will come up with an opportunity all of their own. Maybe their efforts were stymied by a rival crew during their last score and they’re looking for revenge. Maybe they want to expand their criminal empire and have an idea for a score against a gang in another district. Same thing, in this case, it just saves you the trouble of inventing the opportunity yourself.

This section also provides practical tips on how the players might handle these things mechanically, what difference the crew’s heat and resources make to this process and even a step by step guide to what constitutes an opportunity.

Think offscreen

This action makes you spin some more plates than you already are as GM, but it is useful to think about. Basically, the idea is to bear in mind what is happening elsewhere that might have consequences for the action of the current scene. Maybe there is a riot happening nearby and it’s getting closer, maybe the Bluecoats are out in force on patrol tonight, maybe there are some errant ghosts in the area that might want to get involved. This is the sort of thing I do tend to forget about when GMing normally. It generally feels too much to introduce another element to an encounter in a lot of games. But in a story game like this, you want complications, and, more importantly, you want to see how the PCs deal with them. In all likelihood, they’ll have to do something that drives the story forward even more!

GM Principles

A man in a high collar holding a skull in black and white — “I knew him, Horatio” – J Harper

This is the second set of tools for you to use to achieve those GM goals. If you play with these principles in mind at all times, you should get the most out of your experience GMing Blades in the Dark:

Be a fan of the PCs
Let everything flow from the fiction
Paint the world with a haunted brush
Surround them with industrial sprawl
Address the characters
Address the players
Consider the risk
Hold on lightly

“Paint the world with a haunted brush” and “surround them with industrial sprawl” are specific to Blades, in that they are concerned with describing the city and the situation in the appropriate vibe and tone. “Be a fan of the PCs” has become a standard piece of RPG advice but it is important, for sure. I’d like to go into more detail on two of these:

Let everything flow from the fiction

You don’t need to “manage” the game.

It can be hard to let go. Especially when you have been raised on a strict diet of stat blocks, challenge ratings, 6 second rounds and proscribed consequences. But much of the advice in this chapter is encouraging you to do exactly that. Stop planning. Nothing good can come of it. You have to let the story flow naturally from the actions of the players and the reactions of the world. In Blades, after the briefly described starting situation and opening scene, every element of the campaign should cascade down from there.

Hold on Lightly

This is not a “no take backs” kind of game.

When thinking about the PCs approach to a situation, remember that goal of portraying the fictional world honestly. If you do that and are forced to rethink how you described a scene, that’s fine, you can go back and retcon it. Maybe you first introduced them to a room crowded with ghosts, but, on reflection, considering how the players told you they spent time staking out the room as an entrance to a hideout, beforehand, you decide there is just one, lonely spirit, there. Not only that, you should not be afraid to allow the players the same sort of leeway when describing their actions.

Next time

In the next preview post, I want to write about the GM best practices and bad habits as presented by Mr Harper in the book. Till then, dear reader!

Beginnings in the Dark

I want to start by acknowledging that I think this entire section is fantastic. It’s full of gold. The advice presented here is the kind of thing I would love to see in every game.

My Own Advice

In my post on beginnings I suggested a few things. It’s a good idea to start in media res. Starting in the middle helps to introduce the world to your players and helps them to introduce their characters to the world, assuming you give them enough narrative freedom to do so. I suggested using flashbacks to fill in blanks as necessary. But I also suggested that, for a longer game, you might want to begin with some in-depth scenes of the PCs’ personal lives to give everyone a good idea of what drives them.

So, how does this hold up to the advice provided by John Harper in Blades in the Dark?

Starting the Game

A leaping scoundrel in black and white. — A leaping scoundrel in black and white by J Harper.

That’s the name of the section under the Running the Game chapter in the book. No confusion. I want to start by acknowledging that I think this entire section is fantastic. It’s full of gold. The advice presented here is the kind of thing I would love to see in every game. It was definitely the kind of thing I wanted from Spire before beginning it. I was so anxious about starting that game because I really was flying by the seat of my pants. Why? Well, because I had never played anything like it before. And in Blades in the Dark, Harper is perfectly aware that you’ve probably never played anything like this game before. So he takes your little hand and leads you gently into Duskwall, nodding reassuringly and telling you it’ll be alright.

Preparing for the First Session

A map of the coastal city of Doskvol which includes the names of each of the districts. — A map of the coastal city of Doskvol

Under the sub-heading, Preparing for the First Session, you get the advice to read through the character and crew creation sections again, assuming, I suppose, that you read them already. Here, it’s recognised that the GM is going to be the one leading on this and advising the players on how to create those scoundrels they’ve got in mind. Of course, this is good advice for any GM-led game but it’s good to have it in black and white here. Related to this is the fact that during these processes, the players are going to need answers about certain factions that will be relevant to their characters and the starting state of the city. So, you’re advised to pick a few factions you’re interested in or brush up on the ones mentioned in the starting situation, “War in Crow’s Foot.” To add to this, personally, I think you want to brush up on some of the factions, personalities and organisations that affect the entire city, like the Bluecoats, the Sparkwrights and the Spirit Wardens. You don’t need an exhaustive knowledge, but the basics will be helpful to allow you to answer some world-building questions, even if they’re not directly related to their characters or crew.

Harper states here that you should get through character and crew creation and, at least start the first score in your first session. This sets an expectation and, trusting that he has play-tested this a lot, its one that you have to assume is realistic. I also like the idea of taking these freshly minted scoundrels and throwing them straight into the action. I guess my in media res advice remains solid here.

There’s a short paragraph about what you can do to get yourself in the dark industrial fantasy mood of the game. Watch some Peaky Blinders, play some Dishonoured or read some Fafhrd and the Grey Mouser. I like this idea and it is something I do regularly to get me thinking the right way for an upcoming game with a very specific vibe.

Lastly, print out the character sheets and other reference sheets and get the gang together.

The First Session

A dark black and white illustration of several scoundrels on the canal, lit by a giant moon above. — Midnight on the Water, J Harper

The next section is entitled, “At the First Session: Setting Expectations.” This is always important. There are some formalised techniques to achieve this, of course. One of these is C.A.T.S. (Concept, Aim, Tone, Subject matter.) You can describe the type of game you’re going to play using CATS and, hopefully, that should help potential players to decide if they want to play it or not. Honestly, by the time you gather at the table, players should already be familiar with this stuff and know what to expect from your game. So this is not really what Harper is trying to achieve here. Instead, he’s trying to get you into, as he calls it, “let’s play mode.” He suggests a “punchy synopsis of the game” like this:

Okay, so you’re all daring scoundrels on the haunted streets of Duskwall, seeking your fortunes in the criminal underworld.

This is something I also love to do when starting a new game. I often take the blurb from the back of a book, or the summary from the first page and read it aloud, or paraphrase it to get the players in the right frame of mind so I would go further and remind them about what sort of dark, broken, victorian world this is, what the stakes are and the types of things they might be called upon to do.

Then continue:

Let’s make some characters and form a crew! Here are the playbooks. They’re the different types of scoundrels you can play. I’ll summarize them and then you can choose…

Harper goes on that the advise you to keep your explanations and rules-talk to a minimum at this stage. Introduce the players to concepts and answer questions but don’t get lost in the darkened alleys of Doskvol just yet. Instead, give a loose outline of the various playbooks and crew types, just enough to pique your players’ interests while they look through the options.

He then suggests saying something more like a sales-pitch at this point. The speech he includes in the book is real hearts-and-minds stuff,

This is a game, but it’s also something else—something really cool and unique. We’re gonna collaboratively create fiction together, by having a conversation about these characters and situations, without anyone having to plan it out or create a plot ahead of time. It’s like our very own TV series that we produce but we also get to watch it as a viewer and be surprised by what happens. You’ll say what your characters care about and what they do, and I’ll say how the world responds and just like that, a story will happen. It’s crazy. And fun.

I like this but I think I’d definitely come up with my own spiel. It’s just not me. I would definitely use this though:

play your character like you’re driving a stolen car.

Creating Characters and Crew

An Eldritch ball of light being released or cpatured by a crouching person in the foreground. Several scoundrels with a lantern in the background. — Eldritch light. J Harper

While the players work on their PCs, this section provides a set of questions to ask them. The text here does not suggest you ask all of the questions or that you ask everyone the same questions, or even that they should answer them out loud. Although I think I would try to get answers for at least a few of these to help me in making decisions as the game builds.

Here is a selection:

Why did you become a scoundrel?
The two of you have the same heritage. Do you want to be blood relatives? Do you know each other’s families?
When was the last time you used your blade? Why?
Who do you trust the most on the crew? Who do you trust the least? What’s that about? Or will we find out in play?

Harper points out here that we don’t need or really want to know everything about the characters before starting. A lot of the fun of playing a character is discovering them as you play, of course. The dynamic nature of Blades in the Dark and the degree of influence PCs can have over the world and, more importantly, the story, makes this particularly true of this game, from my experience.

You want the players to want to play their characters and to be excited about it. So Harper asks you to make sure, if anyone is not that enthused or is maybe frustrated by the process or any lack of detail that you spend a little time getting to the bottom of their dissatisfaction, providing more info if they need it, until they’re happy. You can also remind them that, if any of them find, after a few sessions that they wished they’d made a different choice here or there in character creation, then they can make the change, “no big deal.” An enlightened and realistic approach, I think, to what is, after all, just a game.

Once they reach the crew creation stage, they’ll have questions for you about the factions I mentioned earlier.

who gave them their hunting grounds, who helped with their upgrades, and who’s connected to their contact.

So, you’ll be happy at this point that you did that reading earlier. The advice here is, again, to use the factions in the starting situation to save yourself some work and associate the crew with the occurrences. This section ties things up by suggesting you skip crew creation for a one-shot, allowing the crew to develop organically during play instead.

Introduce Characters & Crew

Finally, it comes to the point the players will have been waiting for. They get to show off their cool new guys, their wee scoundrels! You get to use this to ask each player a few more questions to help clarify things or to get them thinking about how their PC might develop in play.

Some good advice here on how they should come up with their crew name. Even though they just put in a lot of work on crew type, upgrades, special abilities etc, the name can be elusive. So Harper suggests they leave that until after their first score at least. A suitable moniker is likely to come out of that.

The Starting Situation

A cityscape type view of Crow's Foot — A cityscape type view of Crow’s Foot

I love this bit the most. You could potentially run Blades in the Dark games over and over again for years, one campaign after another, and use this same formula for your starting situation, and it would never get old:

Set two factions directly at odds, with opposing goals. They’re already in conflict when the game begins. Both factions are eager to recruit help, and to hurt anyone who helps their foe.
Set a third faction poised to profit from this conflict or to be ruined by its continuation. This faction is eager to recruit help.

And that’s it. It’s not overly convoluted. Three factions and their goals shouldn’t be too much to burden the players with and there should be plenty of potential in the situation. “Keep
it simple at first—things will snowball from here.”

The main thing is to give them something to do right off the bat, rather than asking “more creative work” of them. Once again, I love this. This is the sort of advice I wanted when I first ran Spire. Instead, I think I left my players floundering right at the beginning, without a clear idea of what they should pursue straight away. We ended up really enjoying that campaign but it always involved an awful lot of talking about what they were going to do next, planning that thing and then changing minds and starting over. And I think that’s because it never recovered from that first session, and its lack of direction.

The Opening Scene

Now you get into the nitty-gritty. This is practical advice that I really wanted. What should that first scene look like? What should you give the players here? What kind of thing is being asked of them? What if they don’t want the jobs that are being asked or demanded of them?

The most important lesson I am getting from this section is that the ball is in the PCs’ court. You need to give them a decision to make and they need to make it right now! Whatever happens, they are going into their very first score right away. No hanging about, no ifs, ands or buts. Love it.

Conclusion

The section ends with an example starting situation, “War in Crow’s Foot.” I’m not going to go into it because I might just use it. But I can tell you that its exactly what I’m looking for here. It’s a concrete example of the way the GM gets things started and how you can hand it over to the players. It’s got sample scores from different NPCs and advice on how to play those NPCs too.

Having read this whole section and followed some or all of its advice, you should be more than prepared for the crew’s first big score.

Throwback Wednesday: Beginnings

Instead of a new post, please enjoy this one from last August. It deals with beginnings and how to manage them in RPGs. Its got some advice I must take into account as I embark on my recently decided upon campaign of Blades in the Dark.

A Short Rest

Once again, dear reader, I find myself a little under the weather. Maybe I just overindulged at the weekend, maybe I have been working too hard, maybe it’s the current wave of ‘rona. Whatever it is, I feel like I’ve been struck by a nasty disease and I failed my resistance check/saving throw etc. etc. So, I’m taking a break today.

Beginnings

See you with a new post soon!

Troika! Whalgravaak’s Warehouse Review

Here’s the story: hundreds of years ago, the city’s premier logistics wizard, Whalgravaak, abandoned his warehouse, having shredded the Manual of Operations for his Sphere Pool (a mechanism used to import and export goods across the cosmos) so that his rivals could never figure it out.

One-shot fun-shot to campaign of terror

You know what it’s like, dear reader: you want to introduce some noobs to RPGs or just to your group of players, you want to make a good impression but you don’t want to scare them off by plunging them into a multi-session campaign with a complicated, crunchy system. So you pick up a location-based adventure, thinking you can just use a small portion of it, just what you need, just enough for one session, one single shot. But, after that session, the curiosity gets the better of you all. That was a weird, but enjoyable experience, you tell each-other. I bet we could have fun exploring the rest of that odd locale, you tell the players, why not have some more sessions and see how it goes? So you do that. And then the bloodbath begins.

Whalgravaak’s Warehouse

SPOLIERS BELOW! If you are interested in being a player in Whalgravaak’s Warehouse, turn back now!

Whalgravaak’s Warehouse is a Location based adventure by Andrew Walter for Troika! The design is by Shuyi Zhang. It came out in 2023 and was the first of the Melsonian Arts Council’s 1:5, an ongoing series of location-based adventures for Troika! There are a couple more available now and another out very soon. You can find them all here. My somewhat rotating group of Tables and Tales members just had our last session in Whalgravaak’s Warehouse on Monday night, after spending a total of eight sessions there.

Since then, the strange nature of the warehouse, staffed by giants and stocked with oddities, has only grown stranger, and more dangerous. It houses a handful of physics defying, Tardis-like chambers, not least of which is the terrifying Deep Storage, a swirling mass containing several pocket dimensions and a wraith-like being who wants nothing more than to consume intruders. At least one cult has taken up residence, and they are often mutated into horrific Chaotic Spawnlets by the effects of the radiation still spilling from the Sphere Pool. The warehouse is sandwiched by a vast desert of dust occupying the roof, which is peopled by the descendants of Whalgravaak’s former employees and, underneath, the tunnels of a pack of unpredictable Worm-headed Hounds.

But entrance has been forbidden by the Autarch for centuries and, even if you were foolhardy enough to ignore a diktat like that, you would still need to be brave enough to face the unknown dangers within.

The Hook and the Party

The book suggests a few potential hooks for your PCs. Since my game started off as a one-shot, with brand new characters and no existing campaign to work it into, I went for one that seemed like the object might be achieved in one session. They, along with many other groups of mercenaries were contracted to return with the head of a Cacogen, known only as the Opportunist, to their patron, an Exultant of the Autarch’s court. But we dealt with that in flashback as they all sat in the weed-choked yard of the warehouse, dotted now with small encampments of adventurers and brigands all gathering their courage to gain entry. The PCs’ band consisted of a Monkey Monger (and monkeys), a Gremlin Catcher (and dog), a Wizard Hunter and a Landsknecht. They were, to put it bluntly, a motley crew.

That first session was all fun and games. Every encounter, except for the last one with the Cacogen, was resolved peacefully. This happened mainly due to the rolls I made on the Mien table for each encounter. The worm-headed Hounds they encountered wanted to play with the Monkey Mongers monkeys, they did not want to eat them. The Flat Serviceman was happy to follow the party around and clean up after them. The Segmented Crippler in the Pigeonholery, didn’t want to wake up, so they skipped that one entirely. This is a pretty standard mechanic in Troika but I think it gave the players a false sense of security. The session ended with this motley crew finding and defeating the Opportunist quite handily. And, at that point, we thought that would be it.

But a few months later we decided to continue with their explorations of the warehouse. Obviously, their original motivation to explore was gone. They had achieved their objective, but the players were all good sports. They decided between them that the motivation was purely one of curiosity and greed. They had spotted, through a bubble like window in one of the rooms they had traversed, a vast and terrifying pool of chaos and wonder in a room far too big to exist within the confines of the building. This was enough for them. Essentially, they went in search of adventure. Although, through the sessions that followed, I did introduce the idea that they might want to find that cult I mentioned earlier and that they should seek out the incredibly valuable Tome of the Sable Fields that was reported to be stored in the warehouse, somewhere. This gave them a little direction when I thought they might need it, but, honestly, I think my players just wanted to see what new wonder/horror the dungeon had in store in the next room.

The Dungeoncrawl

It was only from this point that I started to really treat this adventure like the dungeoncrawl it is very much meant to be. The book does a good job of introducing the concepts of tracking resources like lantern oil and provisions as the party explores. It also explains the concept of exploration turns and their effect on the game, i.e. the distance you can travel in that time, the amount of lantern oil you use per turn, and the likelihood of running into an encounter. I followed all these rules to the letter and they made for some interesting moments in the game. But, to be frank, the weirdness of the setting is the real draw here, not fiddling with rations and light levels. Also, few of the characters lived long enough for starvation or oil-skins to become a problem.

It also has rules for dealing with the spatially distorted, impossibly large areas within the warehouse. It suggests that the players should make Luck or Skill checks to avoid getting lost in these areas, but, in all honesty, I didn’t really require that sort of thing.

Mapping is also a part of the dungeon crawl format and this adventure does want the party to attempt to map the space for themselves. The thing is, when some rooms appear to be a kilometre wide and the next one is spatially normal, that map becomes effectively impossible for them to draw accurately after a relatively short period of time. Eventually, I gave up and just shared the one from the book with the players, trusting their ability to separate player knowledge and character knowledge. My advice, if you are doing this, try get your hands on the PDF version, since the one in the physical book stretches across two pages and the crease obscures part of it.

In fact, the adventure has four maps:

the warehouse floorpan, using 10ft squares to denote distance
a hex crawl for the desert on the roof, replete with points of interest
a map of the Worm-headed Hound tunnels beneath the warehouse, superimposed over the warehouse plan
a largely vibes-based map of Deep Storage

These are all great but usefulness will vary. In our game, the party spent several sessions trapped in Deep Storage but took one look at the desert and noped right out of there. This seems like a good point to note how good all the artwork is in this. There are plenty of colour and black and white illustrations but they leave me wanting even more!

Warehouse Workers and other Beasties

A warehouse is a dangerous place to work, especially when the correct safety protocols are not observed. It doesn’t help at all when you are trespassers and several of the residents are large enough to crush you with a single blow.

The crimson giant, Paude, the pipe-smoking, bearded giant, Arbuthnot and the blue, jelly giant, Gamtomerian. — The giants are not what you might expect.

The giants are the main NPCs of the adventure and Whalgravaak’s only remaining employees. Each one is fabulously interesting, diverse and well-drawn. They have their own motivations and desires. I was gratified that the party managed to encounter all of them during the eight sessions we played. In fact, one player had two different characters killed by two different giants. I will point out that it is entirely possible to avoid violence when dealing with the giants, it’s just that, sometimes, the Monkey Monger on the team has monkeys who decide to fuck with them and one thing leads to another.

The wraith-like Gulf Man Roamer from the swirling vortex of Deep Storage is a potentially lethal foe who has a chance to show up each time the party moves through that already dangerous room. If it captures you in its bag, it’s going to spirit you away to eat you in its extra-dimensional lair.

No warehouse is complete without forklifts. Whalgravaak’s forklifts are humanoid constructs with the face of the wizard himself. They treat intruders like stock, and will attempt to whack them and pack them. They hit very very hard.

Its a black and white dog, with a neck like an earthworm — When you read the words, Worm-headed Hound, is this what you imagined?

There are also a bunch of random encounters, including the Worm-headed Hounds I mentioned before, desert nomads from the roof, and Bandits/Burglars/Bastards. These only turn up on the roll of a 1 on a 1d6 for each turn the party travels. It didn’t occur very often in my game. The Roof and the tunnels have their own random encounter tables as well, but I never used them as the party never spent any appreciable time there.

This is just a selection of the possible encounters you can have in this setting. I haven’t even mentioned the tiny army guys, the sentient crane parts, the Onion God or the Mulled Dead.

The Rooms

I have hinted at rooms that defy physics and rooms with pocket dimensions, and those are usually the big-ticket locations that contain some of the greatest set-pieces in the adventure. Deep Storage alone evoked some of the most inventive use of skills and spells and a great degree of fear and tension from the PCs. It killed one of them (two if you count the Rhinoman eaten by the Gulf Man Roamer.) The Roof could act as an entire short hex-crawl campaign and the Sphere Pool has some truly memorable and dangerous elements to it.

However, many of the other rooms have weird and wonderful contents as well. Some of them, the party will glance at and move on, while others will capture their imaginations and encourage them to interact. I never really knew which reaction I was going to get from them, actually. The room full of melting rope? They had to spend an hour trying to figure out how to set it on fire, the eternal battle between tiny armies playing out across a battlefield seemingly larger than the whole warehouse? Just popped their heads in and left with some captured little men.

Some of the rooms were relatively mundane warehouse style rooms with shelves and containers. The book has tables in the back to help you identify the state those rooms are in and the contents of the containers, which is useful.

One of my over-riding impressions by the end of our game, was that in some ways, the great variety of bonkers content in the rooms served to detract from any unifying theme. There were some elements that went together, such as the warehouse’s disdain for traditional dimensions. If my PCs had explored the Roof or even encountered any of the nomads who dwelt there, they might have found a distinction between those descendants of the ancient striking workers and the giants who continued to obsessively do their jobs even long after their employer had passed on. But, none of that is to say that the rooms weren’t endlessly fun and inventive.

A Note on Lethality

I recently wrote a post sharing some of the obituaries of the characters who met their ends in Whalgravaak’s Warehouse. You can check it out here. There are only three of them in that post. A few months previous to that, I wrote this post, which contained the obituaries of two more. The mathematicians amongst you will have summed those already. That’s five. In the final session, we lost another one. That makes six. That was three character deaths each for two particularly unfortunate/reckless players. Warehouse work is dangerous. Only one of the original party survived to the end. You have been warned.

Conclusions

The covers of the two different versions of Troika! that I own. — Numinous or otherwise, its the same game.

There is so much to recommend in this adventure. It is endlessly entertaining, challenging and bonkers. It has such a variety of locations and such a diversity of encounters that you would need to work hard to get bored in Whalgravaak’s Warehouse. I think it works so well to show off Troika! as a system, too. The problems it asks the PCs to solve and the encounters they have to deal with utilise things like the Luck check really well and encourage players to invent their own unique Advanced Skills. But if they get into fights, especially with the incredibly random nature of Troika! initiative, there is a very high chance they are going to come out of it dead. There are a few opportunities for insta-kills throughout the warehouse too. I can’t overstate exactly how lethal this adventure is. Luckily, my players leaned into that, even when they were creating new characters to join in the same fight the original one died in (they got very quick at creating characters.)

I think it’s also flexible enough for many GMs to easily take it or part of it and fit it easily into their own ongoing Troika! campaign. As I said at the start, our game started as a one-shot and it could have ended there. But we were able to easily adapt it into a short campaign of its own.

Dear reader, let me know if you have played Whalgravaak’s Warehouse or if you would like to! I’d love to know your views on it.

DCC’s The Grinding Keep Review

At one stage, the Elf cast a Magic Missile and it caused a rain of frogs on the entire party and all their enemies, almost killing several on both sides!

DCC Day

I kind of knew it was DCC Day on the 19th of July. It had been advertised to me enough times on Instagram after all. But that was not why I had scheduled a DCC one-shot on the 20th of July. That just happened to be the best day for most of my players. As serendipity would have it, the module I planned to run was the Grinding Keep, an adventure designed by Marc Bruner, which appeared in the Adventure Pack for DCC Day 2024 along with the XCC RPG adventure, Tucson Death Storm!

Hook

I had introduced the hook for this adventure in our recent run of Sailors on the Starless Sea. The PCs discovered a map to a keep and a note hidden in the lining of a cloak in amongst the charnel remains of many butchered humanoids in that adventure’s tower. The note was from the patron of the poor unfortunate who lost their cloak and it indicated that their patron would pay 1000 gp for the safe return to them of a magical lantern. As budding adventurers, most of whom barely had two groats to rub together, this seemed to be motivation enough.

Each player had only one surviving character from the 0-level funnel and one of them was not able to make it to this latest game so I supplemented the four characters who advanced from 0-level to level 1 with a couple of pre-gens kindly provided for the Grinding Keep by Goodman Games themselves.

Big Party

So the party was made up of six level 1 PCs, a Warrior, a Wizard, a Cleric, a Dwarf, an Elf and a Halfling. Two of the players played two PCs each and two of them played one PC each. All of their abilities proved useful. I would say a varied party is very beneficial for this module. On the other hand, if I had to do it again, I probably would have left the players with one PC each even though the adventure calls for 4 to 6 level 1 PCs. They all survived easily enough, although there were a couple of close calls.

Starting the Adventure

SPOILERS! – If you are a player who might want to play this module, stop reading now!

To begin, I plonked them right at the door to the keep as the text suggests. The module wants you to do this. It is designed to be a one-shot by the gods, and it will be! No faffing around in town, shopping or gathering rumours. Just get them in there as quick as you can. I did have to utilise the handy, and essentially invulnerable Leaf Elemental that waits on the grounds of the estate for anyone foolish enough to hold up the proceedings of your one-shot by searching for herbs amongst the overgrown gardens which seem to be under the influence of all four seasons at once. The seasons are a recurring theme and I was gratified to note that the players realised this almost immediately.

Anyway, once they had been chased inside the keep, they were confronted by something that could only have been a magical effect that transformed the interior from a ruin to an immaculately decorated and lit hall. They were greeted by the white robed Host and eventually waited on at dinner by his veiled servants. All of this set up was important. It presented clues to the nature of the keep to the PCs and let their imaginations run with them. Enough strangenesses occur during dinner and upon their investigation of the ground floor of the keep that they should be suspicious. Indeed, before they had even left the dining room, one of my players joked, “the house is a mimic!” He didn’t know how spot on he was…

Of course, the keep is, in fact, an other planar entity who comes to the world to feed, in disguise. The PCs had seen windows and chimneys on the outside but could find no sign of them on the inside. The couldn’t get through any doors that the Host didn’t want them to enter, etc, etc. Clearly, there is enough evidence to allow your players to uncover the truth before things ever really get interesting.

One regret I have is how much time I allowed them to devote to this whole section before Event One occurs. They spent a lot of time searching, theorising, investigating, and it ate into the more adventuresome elements in the latter stages of the module. My advice would be to get them into the Guest Quarters and asleep as quickly as possible. The adventure does not provide much in the way of motivation for the characters to do this, however, so be prepared to improvise.

Event One

Event One is triggered when they wake up after a nights’ sleep in the keep. I was lucky enough that the players wanted to rest and one of them was rendered magically asleep, but without that, it would have been a struggle to get them to wait until the next morning. I probably would have triggered Event One early, if that had been a problem.

What “Event One” means is that the keep is waking up. It will soon be ready to consume a fresh meal of adventurers.

Mechanically, what it means is that every time they open a door, they will be confronted with an intersection of corridors that lead to two randomly determined rooms in the keep. These could be rooms they already visited in the first part of the adventure, or ones that would have been otherwise inaccessible up until this point.

The first room my players visited was the dining room again. This was satisfying as it gave them a chance to kill the Host and his servants from earlier (although, technically they just put the Host to sleep and dragged him around with them for the rest of the adventure.) After that, they encountered one of the three rooms that contained the organs of the keep. They had discovered the journal of a former prisoner/meal in their quarters that gave them hints as to how to deal with each of the organs; eyes, heart and lungs, and that proved useful in the encounter they had with the heart. It is significant that they identified several magic items that act as keys for the doors to these special rooms. But their first instinct was to destroy them if they could. Luckily they forgot about that plan and just kept ‘splorin’ instead. Eventually they managed to overcome the challenge in the heart room and at that point of our session, I realised I was running out of time to get my one-shot done in one shot so I focused things up a bit.

Event Two

The way it was supposed to work was this: every time they left a room, I would start marking that room off as no longer accessible on the random room table, until there was only one possible room left; the one that contained the Alien Intelligence itself. I didn’t have the time for all that. We were approaching the four hour mark at that point and people had work in the morning. So I just told them that, after they destroyed the fiery orb that acted as the keep’s heart, the entire place shook and when they re-opened the door to leave that place, the corridor beyond led to the last room. The players, unknowing, proceeded to their fate. Their fate, as it happened, was to murder the Alien Intelligence of the Grinding Keep, all its Animated Corpses and the Giant Animalcule Swarm that accompanied them. Destroying the heart had pretty much halved the creature’s HP so it wasn’t too difficult. In the end, they fled through the windows in the back of the room, utilising the Feather Fall spell (which two characters had, by coincidence) to safely land in the river at the bottom of the canyon beyond.

Conclusions

Perhaps you can see now why I think I should have made things a little harder for them by reducing their numbers. On the other hand, I am glad they all survived. They had all created and played such interesting and fun characters, even in the context of a game that is not RP-heavy, to say the least.

I was a little disappointed to reach the end of the adventure with so much cool content unexplored. They didn’t find the trap/treasure room where the magic lantern was stored, they didn’t find any of the other organ rooms, which all had really fun mechanics. On the other hand, I felt the adventure was designed to be flexible enough for a Judge to shortcut it exactly the way I did to get them to the end a little quicker, which seemed like good design to me.

This was only the second time any of us had played DCC and the first time with characters of anything other than 0-level. This was a different game to that first experience. PCs used magic and Mighty Deeds at every available opportunity and they got to roll on the crazy magic random tables a lot. At one stage, the Elf cast a Magic Missile and it caused a rain of frogs on the entire party and all their enemies, almost killing several on both sides! This is why we loved DCC. It’s the wonderful and potentially lethal randomness of it and the endless inventiveness of the adventures.

I would recommend the Grinding Keep as a one-shot DCC adventure, as long as you are willing to either cut out bits or extend it to two sessions.

Time for a Change

If you had to choose one, dear reader, which one would it be? If you are one of my potential players, which one would you like to play?

Anniversary Posts

More anniversary guest posts coming soon. In the meantime, have some musings.

Old School Rut?

I’m not sure how it happened but, recently, all I have been playing is OSR, trad and adjacent games. With the exception of Dungeon World, which is about as close to D&D as you can get while also flying the PBTA banner, its been wall-to-wall, dragon games, Borgs and Troikas. And this week? It’s Dragon Age, DCC and maybe some Black Sword Hack or UVG (which is pretty trad in its ruleset to be quite honest.) Am I in a rut or have I just naturally gravitated towards these games? Maybe I have found my niche and I’m occupying it. I don’t think that’s it. I think it has more to do with the ease with which I can roll out one of these games, if I’m the GM, at least. It’s also pretty easy to fall into one of them as a player when you’re familiar with the overall concepts, rulesets and themes. And, don’t get me wrong, it’s not that I’m not enjoying them. But it is time for a change, I think.

Options

So, I have a few options of non-OSR, non-D&D, non-trad games to try out in the near future. My current game of Troika! will be coming to an end next week and Dragon Age probably only has a couple of sessions left in it, for a while. So, some calendar spots are opening up! I’d like to fill them with something completely different.

The Triangle Agency Normal Briefcase Edition

Triangle Agency – I’m reading this at the moment. I have to say, so far, I’m loving the way the game is presented, the really original ideas, the surprisingly bare-bones ruleset and the way it treats the GM (General Manager) as as much of a player as the Agents. It has gotten me excited to play it and I am trying to get potential players excited about it too. The downside is that I feel like I still have a lot to read before I can think about getting it to the table.

Slugblaster – I got this great boxed set for Christmas and have yet to crack the spine of the rulebook in anger. But I have been listening to the excellent My First Dungeon actual play of the game over the last several weeks. It has made me want to try it out despite having little to no understanding of skate culture. I know at least one player who would be very interested in playing so I’m sure I could get a few more. Once again, the difficulty is that I have not even skimmed the rules yet. This is somewhat ameliorated by the fact that I’ve been learning how to play while listening to the podcast.

Blades in the Dark – Although I was a player in a campaign of Blades last year, I still haven’t run it as the GM. I think I would enjoy doing it and it is such a classic, it would be a shame not to put a game of it together. And it is the basis for games like Slugblaster and The Wildsea, which also feature on this list. I have been nicking enough rules from it for my D&D game, also, that I feel confident I would mesh quite well with the ruleset. At least I have read this one cover to cover and played it before, so that’s a big tick in the “pro” column for Blades.

The Wildsea – I wrote about this already last year and still haven’t managed to run it! Essentially, this game imagines a world where the entire surface has been covered in a vast forest and your players are sailors across the canopy, using boats with giant chainsaws attached to sail. Take a look at the last post about it if you want more info. I have rad a lot of this and could probably run it ok, but I am afraid of doing another game where my players are sailors as I am already doing that with Spelljammer and kind of, with UVG.

Deathmatch Island – I also wrote about wanting to play this around this time last year. I having been feeling the urge to scratch the Lost, Severance type itch over the last few months. I watched both of those shows in the last half a year and they have stuck with me a lot. I think Deathmatch Island would be perfect for that. Also, I have read it completely and would be very excited to try out its mechanics. Here’s my post about it from last year.

There are a couple of outsiders as well, Orbital Blues and Apocalypse Keys, both of which I purchased on something of a whim (and a sale.) I’m curious about them but have barely opened either. I know Apocalypse Keys is a PBTA game and that it is beautifully illustrated, but that’s about it. And I know Orbital Blues is a game of sad space cowboys ála Cowboy Bebop and Firefly so that is a big tick in its favour as far as I am concerned.

If you had to choose one, dear reader, which one would it be? If you are one of my potential players, which one would you like to play?

Prep Part 2

Still Prepping

This post is part of a blog bandwagon started on the Roll to Doubt blog.

Click on the link above to take in the blogpost that’s piloting this bandwagon. Wagon-jumpers abound. You can find a very nice read on the same topic and a handy list of related blogposts on the Among Cats and Books blog.

And here’s a link to the first post on this topic on the dice pool dot com.

Between the Sessions

I am an unapologetic shill for Huffa’s Between the Skies. It’s one of my most used and most valuable RPG books. I use it constantly in lots of contexts. But I love using it to prepare for sessions. Its approach to random encounters in particular is one I highly recommend. The encounters are built, not just to make your session interesting, but to introduce potential allies and enemies, recurring characters, locations, objects. In short, they help you to truly build your campaign without relying on GM-written plots that the players may or may not want to interact with.

The methods and tables introduced in the book make for interesting, impactful characters and occurrences. And they have depth, too, enough to hook your players and keep them hooked. You know that old story that your players would die for the unnamed goblin you just made up on the spot but won’t give a shit about the NPC you spent two weeks crafting an elaborate back story for? I feel like the techniques in Between the Skies are almost designed to prevent that. Why? Well, firstly because, if used as your main way to drive the game forward, you are not going to be spending so long lovingly hand-crafting those NPCs, you are just going to roll them up on the tables provided and not worry about whether or not the PCs run into them, because whatever they run into will be interesting and fun enough to capture their imaginations. So, all the NPCs are more like the loveable nameless goblin and you don’t feel the need to make sure the PCs interact with any of them in particular. This has the effect of allowing the players to dictate the direction of the game to a large extent. This is a good thing!

Let’s Interact with the Mechanics

So, Huffa’s advice when it comes to travel is that, unless it is going to be interesting or important, skip it. I can get behind this approach. Recently, I have tended towards the idea of the journey being the game, but sometimes, when you know the next scene you need to play is across the city and its a relatively safe place, just skip to it, or montage it if there is something interesting to see along the way or if its a good opportunity for conversation between characters.

If and when you want to play the travel, though, Between the Skies presents you with two options, progress-based travel and route-based travel.

Route-based travel

Using this method, you use a map, just a basic one that includes routes and locations along them. You roll once on the Encounter die between locations and resolve that before arriving at the next place. Simple. The book includes several ways to generate route maps and destinations but I won’t concern myself with that here.

Your route map should have options, different ways of getting from A to B with more locations in between your starting point and the final destination depending on how long you want the journey to last.

This has the feeling of the caravan travel methods used in Ultraviolet Grasslands.

Progress-based travel

This gives me the impression of beating the resistance of a delve in Heart. Before the journey starts, determine the journey length. There is a helpful table that indicates the amount of Progress points required to reach the destination depending on how long the journey is. You record progress through the resolution of Encounter Die rolls.

The Encounter die works as follows:

Encounter
Something Approaches
Environmental hazard
Complication
Hint as to what is nearby
Progress/breakthrough/boon

So you only get progress points on a 6.

What I did

As with everything in Between the Skies, you can take it or leave it. I have used a combination of the two methods, where I decided that a spelljammer ship journey from the Rock of Bral to the First Home asteroid would take three days and I would have them roll on an encounter table once per day. So this is the table I used:

Wildspace encounter table d6

1-2 No encounter
3 Environmental/Ship Hazard
4 Ship Problem
5-6 Encounter

When you only have three days and so, three possible rolls on the table, I felt it was better to increase the chances of actual encounters/problems/hazards occurring. If it was a more exploratory journey, I would use the progress-based method as described in the book.

Now, using the tables in this book, of which there are many, you should be able to create a fascinating encounter on the fly, but, if you can, I think its nice to prepare a few beforehand, at least one of each kind. So let’s do that here.

I thought it would be a good idea to roll up some options on the spark tables in the book and add them to a d4 table for each encounter type (environmental/ship hazard, ship problem and ship travel encounter.)

Environmental/Ship Hazard

We’ll start with the hazards. For each hazard you want to prepare, you roll 1d6 to determine the hazard type and then d66 to generate a hazard keyword on the Environmental Hazards during ship travel table in Between the Skies.

I shared this table in the last post so lets use the results I rolled up on that.

3 Ship Hazards

Roll 1d4

Hazard 1 – Storm, Flood
Hazard 2 – Disorientation, Sphere
Hazard 3 – Obstruction, Cold
Hazard 4 – Trap, Haunting

I then go ahead and prepare a few details of the hazards. Here’s the first one as an example.

Hazard 1

A solar storm rolls in from the direction of the sun.

The gusts of solar winds batter the ship
The deck is flooded in light and other solar radiation
All those on deck risk blindness
There is also a chance of taking radiant damage
- All on deck must make a Dexterity save, DC 15 to avoid blindness
- If they are afflicted with blindness it lasts 1d4-1 days. If you roll a 1, Roll 2d12-1 for the number of hours it lasts
- Even if they saved against blindness they must make a Constitution save, DC 15, against radiant damage. If they fail they take 4d6 radiant damage. If they succeed they take none.
- This goes for the ship too, if the damage roll beats the damage threshold

You can see that I took the hazard type fairly literally but moved it into a wildspace context. A solar storm seemed obvious but also pretty cool. The keyword, “flood,” took me a little while to work out but I thought flooding the deck with light seemed both like a cool, spacey event and something that could present a real problem for the PCs.

Obviously, you can prepare the details for each entry in the table. They don’t have to involve a lot of work but putting a little extra preparation in at this stage can remove the need for it at the table.

Ship Problem

Similar to the hazards, you simply roll up a problem type and a problem keyword on the Ship Problems tables in Between the Skies. I did this four times and created the d4 table below.

4 Ship Problems

Roll 1d4

Problem 1 – Armament, Separation
Problem 2 – Quarters, Shrinkage
Problem 3 – Cargo, Disappearance
Problem 4 – Bridge (spelljammer helm), Error

Here’s the detail on one of these entries:

Problem 2

One of the crew has stowed something large and awkward in the crew quarters. It is limiting the amount of space available to sling hammocks and the rest of the NPC crew is unhappy about it.
This crew member refuses to be parted from their huge steamer chest as it contains something of extreme personal significance.
The PCs will need to resolve the interpersonal issue.

You can see that the details here are left deliberately vague. You Ould ask the players to decide which member of the crew is the problem, what’s in the chest that’s so important and, most importantly, how the resolve the issue.

Encounters

And finally we have encounters.
There are a lot of different encounter tables in the book. You can choose the one that best describes the surroundings of the PCs at the time. There are two space encounter tables, one for known space and one for wildspace. They are d66 tables. Once you have done rolled on them, you can get some more inspiration by rolling on the encounter keyword, detail and related entities tables.
Once you have rolled on the Encounter distance and awareness tables in Between the Skies to determine how far away the encounter is and how much attention they are paying to the PCs you can roll on the d4 table below.

You’ll note that the results on the table below are not all similar. For instance, encounter 2 doesn’t have a related entity. In general, such entities, as generated by the tables in Between the Skies, are sentient NPCs so I didn’t think it necessary for the parasite I rolled up. But mostly each of them includes an encounter keyword, a related entity, and two encounter details.

5-6 Encounters

Isolationists – Confusion, Related Entity – Unknown NPC, Glittering, Prayers
Ship Parasite – Loss, Scales, Experiments
Ruins, Ancient – Mourning, Related Entity – Petty God, Knots, Miscommunications
Stowaway – Battle, Related Entity – Creature, Eggs, Blindspots

Stowaway

Size, substance and form table: Very small biota, piecemeal.
Weakness: True name
Needs: Brains
Characteristics and details: Pacifist, stalks
Behaviour: Social: Family: 5 appearing
Demeanor and current behaviour: Protective, healing
Attacks: Blast – teleporting

For the final example, I’m using the creature generation tables in the Entities chapter of Between the Skies. You can see all the details and keywords that I rolled up above.

Along with the keywords, battle, eggs and blindspots, that came from the original encounter detail rolls, these will make for a fascinating encounter with some sort of very small fungal entity that has escaped a battle to find refuge aboard the PCs’ ship. The mushroom creature has a desperate need for brains to help heal its young but will not take them by force. Perhaps they only consume the brains of dead beings. Perhaps they have a blindspot that means they cannot sense constructs. And maybe, also, they have crawled into the ship’s stores to try to feed on the eggs, mistaking them for heads containing brains. I like the idea of them lashing out with a teleporting blast to deposit attackers some way off the deck of the ship, leaving them to perish in wildspace. If the PCs can figure out the creatures’ true names, they’ll be able to get them off the ship, but how?

Conclusion

I think you can see the fun you can have preparing encounters and encounter tables using Between the Skies. Once again, dear reader, I can only urge you to go and purchase it. It’s so useful and you won’t regret it!

Prep

Preposition

This post is part of a blog bandwagon started on the Roll to Doubt blog.

What’s clear from even a cursory glance at the other blogs is that no two people are prepping in precisely the same way, so advice and recommendations come with the notice that your way is probably the best way. The thing is, in my experience, you find your way only through trial and error. Here’s my effort to tell you about my trials and my errors.

Preponderance of prep

I used to spend hours and hours preparing my games when I was a kid. To be clear, I loved doing it. I would happily get lost in the world-building, the map-drawing, the character creation and the encounter balancing for hours when I should have been studying. I still often think that I gained more from the time I spent on RPG preparation than I did from learning off -by-heart lists of dates and events or theorems and proofs. But I digress.

My prep used to be pages upon pages of tightly packed hand-writing explaining the background of an adventure, the major NPCs involved, the probable goals of the PCs and far more history about the setting than the PCs would ever be able to interact with. I drew maps by hand as well, when I had to. I didn’t run a lot of published adventures but I did make liberal use of soucebooks. I would select the people, places and things I wanted from those books and elaboate on them wildly, writing more pages on how they would connect with our campaign and adding a lot of extra details.

I sometimes wish I had the time to do preparation like this these days. But, when I do find myself with the time, and I sit at the computer to start working on it, I find I would rather shortcut it. I’ve asked myself why this is on many occasions. I’m not sure I have the answer, or else there are several. It could be to do with the process of writing in a notebook and drawing by hand on grid-paper. I don’t want to prep like that these days because having all of my work backed up digitally is invaluable. Time is still a factor. Even when I feel like I have some extra time on a particular day, I can’t guarantee that I’ll continually have that as the campaign progresses. But I think the main difference for me now is the feeling I get from making the world, its people, the major events, the game, at the table with my players. When you are all on the same page, when everyone comes together to create something greater than I ever could on my own, that’s one of the real joys of this hobby.

So, I don’t really do that anymore.

Preplanned not prepared

It’s taken me a long time to make this change, though. Even looking back at the work I did in preparing for our current Spelljammer game, I had thousands of words written on setting, backgrounds, NPCs, over-arching plot etc. And I would write thousands of words of session preparation while going along too. What I have discovered during the last couple of years of trying to prepare this way, however, is that that sort of prep is close to unusable at the table. Even if I am the one who wrote that dense paragraph of text, I can’t find what I’m looking for in it in the couple of seconds I have to react to something at the table, or to answer a player’s question without delay to keep the flow of the game going. Now, it’s not always a waste of time, I will admit. Sometimes, the very act of writing something will help to embed it in my memory and imagination, so obviating the need to check it at all. But, then again, there is the other effect of writing something down. It has the effect of making something true.

Truth at the table should only come from play. The only real things in the game world are what the PCs experience. Everything else, even things the characters have learned or heard about, is pure conjecture. Until it’s not.

This doesn’t mean I don’t prepare anything of course. I make plans for events I would like to occur or NPCs I want the PCs to interact with. But in those cases, I will write down something about the event, just a few details about what happens, who might be involved, what effects it might have. Or I will give the NPC some quirks, desires, flaws and interesting characterisations to bring them to life. But I will keep them to be used when and where they seem to fit.

Otherwise, I revel in the joys of random tables. I use rumour tables and encounter tables quite judiciously these days. In a game like Ultraviolet Grasslands, I am spoiled with wonderful encounter tables, trade goods tables, carousing tables, and almost any other type of table I could desire. But when it comes to 5E, I am generally disdainful of the encounter tables provided. So I make my own. Made right and used right, these not only make for some interesting sessions, but also act to drive the game forward, introducing NPCs that become important to the plot, enemies that might defeat the PCs or might lead to vengeful associates pursuing them later. Importantly, I feel, they maintain an element of randomness and ensure that the players know their rolls have led them to the encounter, or not. It’s great if you can engineer it so that the players are rolling on random encounter tables at the end of a session. That allows you to take the result of their roll and make preparations for the specific encounter they rolled up for the next session. Usually, these days, I refer to Between the Skies for more tables and for inspiration to make the encounter really interesting.

Between the Skies does not limit encounters in space to just running into creatures, but also gives options for hazards the ship might run up against and problems that stem from the ship itself.

Here are the simple d6 and d4 tables I made to determine if the crew run into anything, and, if so, what it might be:

Wildspace encounter table d6

1-2 No encounter
3 Ship Hazard
4 Ship Problem
5-6 Encounter

3 Ship Hazards

Roll 1d4

Hazard 1 – Storm, Flood
Hazard 2 – Disorientation, Sphere
Hazard 3 – Obstruction, Cold
Hazard 4 – Trap, Haunting

4 Ship Problems

Roll 1d4

Problem 1 – Armament, Separation
Problem 2 – Quarters, Shrinkage
Problem 3 – Cargo, Disappearance
Problem 4 – Bridge (spelljammer helm), Error

5-6 Encounters

Isolationists – Confusion, Related Entity – Unknown NPC, Glittering, Prayers
Ship Parasite – Loss, Scales, Experiments
Ruins, Ancient – Mourning, Related Entity – Petty God, Knots, Miscommunications
Stowaway – Battle, Related Entity – Creature, Eggs, Blindspots

The descriptive words I listed beside each entry come from the spark tables in Between the Skies. These are invaluable resources that give you the inspiration to come up with truly unique situations, problems and obstructions. You should go and buy this book at the link above.

When I get the players to roll on these tables, I either make up the encounter/hazard/ship problem on the spot using the sparks of inspiration or I use the time between sessions to come up with something memorable.

A while ago, I realised the plot I came up with for the Spelljammer campaign was much less interesting to the players or their characters than the shenanigans that they got up to each session. They were more wrapped up in their own shit. And that was very cool. It made me want to make a sandbox for them to play around in instead of expecting them to interact with a plot they had little or no investment in. This goes back to the time I introduced a hex grid to the underside of the Rock of Bral. I did this to allow one of the PCs to drag the whole party with them to rescue their mother who was trapped in the prison down under. It did not serve the overall plot, really, but I had to have fun things for them to do while traversing this area so I made it a hex map and created some random encounter tables for each of the different types of terrain on the underside of the asteroid.

You know, it took me a long time to cop on to this though. The signs were all there. Dear reader, if your players never remember what is happening in the plot of your meticulously crafted campaign from one session to the next, you might be overloading them with plot. Maybe they just want to play their cool character and have fun moments between them and the other PCs and significant NPCs. Or maybe they are only interested in hitting things really hard. Or maybe all they have ever dreamed of is building their very own tower of necromancy built on the bones of their enemies. Or perhaps they just want to find their dad? Ever think of that? Maybe your plot is not that important to them. If you take nothing else away from this post, please take that.

I have drifted a little way away from the central theme of the post but I insist that, in actuality, you should be prepping for the sessions you want to have, and, more importantly, the sessions your players want to have.

Prepaid prep

Most of what I have been talking about is prep for D&D/OSR style games. Games that you can play as sandboxes without upsetting anyone. But, what, you might ask, dear reader, do I do to prepare for other types of RPGs?

I have some very specific examples here.

Free Leagues/Year Zero Engine Games

I have a few of these under my belt at this point. I can say that the type of prep I do for these is significantly different to what I have described above. The ones I can refer to are Tales from the Loop, Blade Runner and Alien. For me, the thing that holds these adventures together is the Countdown. This is something that’s rather integral to most Year Zero engine games. Below you can see the countdown from the Tales from the Loop adventure published in the core rule book, Summer Break and Killer Birds.

Once you get the timeline of events in place for one of these adventures everything can be positioned around it. Tales from the Loop adventures, in particular, I find, can be written with ease in the very specific format that Free League has presented to you in the book. They provide really valuable advice in all of their books for creating your own adventures. Blade Runner also provides lots of useful random tables to help you create your own case files for that game. When in comes to prep for this style of game, just make sure you know the countdown well, and you keep track of the shifts/days of activity for the PCs. After that, the published adventure or the one you have written in the provided format, will do the work for you. The rest is improv.

Resistance System, Spire/Heart

Resist the temptation to do anything other than read up on the specific areas the PCs are likely to interact with the next session and maybe jot down some NPC details/desires/stats. Resistance system games really thrive on improvising at the table and having the PCs drive the narrative forward with their actions and their fallouts. This is particularly true of Spire where most of the game occurs in NPC to PC interactions in my experience.
In Heart, I think it’s a good idea to have some idea of the landmarks your PCs might end up in. In the last game of Heart I GMed, I made it specifically Vermissian themed so that I knew they would be visiting a lot of Vermissian stations on the way down to Tier 4.

Prewritten trad scenarios

I am thinking of the Dragon Age game I’m running right now but I think this is advice you can apply to most adventures that are presented in dozens/hundreds of pages in long dense paragraphs. Read the full adventure, then, read it again, but this time, take all the relevant information from each room description, encounter text or whatever and transcribe it into something more easily digestible and more useful at the table. I use bullet points as that’s what I’m used to. I also usually take the more relevant enemy stats like Health, Defence and Armour Rating and note them too. This is me applying the lessons I learned from the mistakes I made as a kid and applying them to the published adventures written by professionals, I realise that. And maybe that’s presumptuous of me, but, hey, it works.
The second time you read it, you shouldn’t do it all at once. Just make those notes between sessions.

Conclusion

Prep can take many guises. It will be different for every GM. A lot of people use all sorts of apps and other technical solutions. All valid, but all I ever use is a wod processing app and a few dice. Whichever methods you use are probably going to be right for you, even if it takes you a while to figure out how you should do it.

Modular Gaming

Improbable hot-takes

“The Discourse (TM)” has been focusing on running published adventures/modules/campaigns as opposed to custom/homebrew/sandbox games for the last little while. First Quinns reviewed Impossible Landscapes, an epic and almost legendary campaign for the modern Cthulhu-ish game, Delta Green. This is the first time Quinns has reviewed a campaign/published adventure on his RPG review channel, Quinns’ Quest, so it was unusual enough to spark a significant amount of discussion all on its own. And then Thomas Manuel of the Indie RPG Newsletter and Rascal reviewed the same campaign. I believe this was purely coincidental, especially as Impossible Landscapes came out about five years ago now. Both are great reviews in their own right and are based on full play-throughs of the campaign so you know they’re of real value. You should check them both out.

Anyway, on Bluesky, Thomas Manuel went looking for recommendations of other modules to run and this spawned a lot of interesting answers and quote-bleets from RPG luminaries, such as this one, which I found interesting.

I have opinions on the conversation, of course. I have shared a lot of them in other posts from the last year or so, actually. If you want the summary, though, I had a lot of bad experiences running D&D scenarios in the past, especially from the AD&D 2nd edition era. I found they were difficult or impossible to just pick up and run. In fact, they required maybe more preparation time than adventures and campaigns I wrote myself. The one published 5E campaign that I ran, Storm King’s Thunder suffered from the same issues, actually. This made me feel like it was a “me” thing. But, it turns out, a lot of GMs feel the same way, according to Bluesky, at least.

However, I have had my mind changed somewhat by running pre-written adventures for some other games, particularly Free League’s Blade Runner, Dungeon Crawl Classics and, to a lesser extent, the Dragon Age RPG from Green Ronin.

This is a link to my first post on Electric Dreams, the introductory Case File for Blade Runner:

Blade Runner

And this one compares the same module to a 5E murder mystery adventure I played in around the the same time:

Case Closed

Here’s my post about Sailor’s on the Starless Sea for DCC:

Dungeon Crawls are Classic

And this is my post on running Duty Unto Death, a short intro adventure for the Dragon Age RPG:

Dragon Age: Duty Unto Death

And finally, this post, although ostensibly an excuse to discuss DCC adventures, also includes my opinions on the one 5E campaign I ran:

Dungeon Crawl Classics – Individual Modules

I will say that, despite my generally favourable outlook on most of these modules, I still find I have to to do a lot of prep for them. The main fear I have is messing things up so bad that I essentially spoil the rest of the adventure. Although, I should really have more faith in my abilities as a GM at this stage. I feel like I can probably improv my way out of any hole, to be honest. But it does not change the fact that I spend hours rewriting long paragraphs presented in module texts into digestible bite-sized bullet-points. I am running another Dragon Age scenario right now. Amber Rage is from Blood in Ferelden, an anthology of scenarios for the game that came out in 2010. It suffers from verboseness and unnecessary detail and makes for a lot of work from the GM. I’m enjoying the contents of the scenario but its presentation is horrendously dated and needs a sprinkle of OSR magic to tighten it up, in my opinion.

I realise that none of the modules I have mentioned here are anywhere close to having the size and epic scope of something like Impossible Landscapes, but it doesn’t change the fact that they have largely changed my mind about running anything pre-published. The one I have my eye on right now is Dagger in the Heart for Heart: The City Beneath. Actually, I have a post about that right here too:

Dagger in the Heart

OK, I’m off to discuss the discourse on Discord of course!