The Sutra of Pale Leaves: Dream Eater

I think it’s interesting that each of the scenarios is styled as being possible to run as a one-shot but I can see Dream Eater’s potential in the context of the greater campaign.

Format of the Sutra

This is the second post in my exploration of the 1980s Japan Call of Cthulhu campaign, the Sutra of Pale Leaves. Go here for the first one, which deals with the overall premise and the Campaign Background chapter from Twin Suns Rising. Although the text suggests that you can play the constituent scenarios in any order, they are presented chronologically and I can’t imagine running them any other way. They are also presented in two different books, of which Twin Suns Rising is obviously the first, with its three scenarios taking place between July 1986 and Spring 1987. I thought I’d be able to write about all the scenarios in this book in a single post, but it turns out, I can’t read that fast. Each scenario is long, between 35 and about 50 pages of dense, small-font-size text. So, instead, I’ll just be examining the first of them today, Dream Eater, written by Damon Lang. Please note that I haven’t played or run this scenario, I have only read it. So, take my conclusions and thoughts on it with that in mind.

WARNING: SPOILERS!

I would find it very difficult to write about Dream Eater without massive spoilers, so I am giving you a warning, right now: if you want to be a player in this scenario or the wider campaign, its probably best to skip this post. Come back later! I’ll probably have something for you then. Or check out my ever-growing back-catalog of posts.

Dream Eater

I once wrote two novels about the adventures of a twelve year old Japanese boy who moved to Ireland with his family. In them, he discovered that he was able to use his cat as a conduit to enter the dreams of others. This allowed him to reconnect with his friends at home but his consciousness became trapped in the kitten! Various hijinks and drama ensue. Anyway, suffice it to say, I was very quickly on board with the premise of this scenario given teh Japan and dream-related elements of it.

The premise is that a small, rural Japanese town is beset by sleeplessness and terrifying dreams of monsters. The longer it goes on, the more the citizens worry for their safety and sanity. The authorities have offered financial rewards to anyone who can help them solve the problem or take care of the afflicted.

That’s where the Investigators come in. Perhaps they are from this small town of Ikaruga, or maybe they just heard of their troubles and have come from the city to look into them. Either way, their assistance is greatly welcomed.

Indeed, their investigations are likely to take them quite quickly to the door of an old man, Mr Taneguchi, who was responsible for the death of a young girl in a traffic accident recently. From there, they will visit other sites in the town, and other potentially recurring NPCs, and they will learn of the Baku. This Yokai is the eponymous Dream Eater, and the cause, it would seem, of the town’s problems. The Investigators will have to find a way to defeat, satisfy or neutralise this creature if they are to help.

But, of course, there is another layer to this story, just below the almost obvious one. The Prince of Pale Leaves has worked through one of his recruits to use Mr Taneguchi to spread the Sutra of Pale Leaves. The Prince has been invading the dreams of the people of Ikaruga, through the old man’s chanting of its mantras at night. It has been creeping through the town, insidiously and terribly. This is what has drawn the Baku to this place. It finds dreams of the Prince the most delicious. The Baku is known as a benevolent yokai in Japanese legends, one that takes your nightmares away and lets you sleep soundly. And that is what it’s attempting to do. The thing is, as it eats the dreams of the Prince, erasing them from the memories of the dreamers, the only image they are left with is of a scary looking ,purple, tapir monster, the Baku. And so, it becomes the scape-goat. The Prince attempts to use this misunderstanding and the Investigators’ intervention to defeat the Baku, thus allowing his influence to grow all the faster.

The question is, will the investigators figure this out? Will they destroy the Baku? Will they leave this town better or worse than they found it?

The Flow of the Scenario

The flow of the Dream Eater scenario in visual form. From Ikaruga Town to Talking with Townspeople to Meeting Taneguchi to Horyuji temple or Nightly Prayers to Unpleasant Dreams to The Fortune Teller to Research in the Sutra to Dream Dive to the Final Encounter and finally to the Epilogue. — Dream Eater Scenario Structure

Take a look at this flowchart. This is useful in a scenario like this for a game like this. Call of Cthulhu is a trad game, and, as such, its scenarios rely on these sorts of stepping stones to get you from hook to ending. So I really appreciate it when you get something like this that cleanly represents that idea visually.

So, after a lengthy preamble giving us Keeper background, an intro to the main NPCs and a few PC hooks, we start with Ikaruga town, a place that’s renowned for its truly ancient buddhist temples, which contain the oldest wooden buildings in the entire world. I like that the section on the town asks the Keeper to get in media res and kick things off with a shared dream sequence. Something weird is happening from the off and it gives PCs who don’t know each other yet a good reason to seek each other out.

You get a basic map of Ikaruga in the style of a roadmap, which is a nice touch. Along with this, we have an “Exploring the Town” section, which spells out stuff like population, transport, amenities and accommodation but the only real subheading to this is the Shepherd Bar: A Foreshadowing, the purpose of which is a little too subtle for my tastes.

The scenario, and indeed, the campaign is sprinkled with “Lore Sheets,” which detail elements of Japanese cultural, societal or mythical knowledge that the average Investigator might be expected to know without having to make a Know roll for it. The Keeper is supposed to hand them out as and when the subjects come up. In this section, we have one on Hōryūji Temple, for instance. Each of these includes a little snippet of “Personal Background,” which the player given the lore sheet might adopt for they own character. It’s a nice way to weave the PCs in with the place and the lore of the place.

The Investigators are expected to visit the Town Hall to begin their investigations. The Town Hall section, as is the case with each of the major plot points of the scenario, begins with a handy summary that looks like this:

Location: Ikaruga town.
Leads In: Hooks One, Two, and Four
Leads Out: Meeting Taneguchi (page 62); Talking to Townsfolk (page 61).
Purpose: investigators learn about the case.

This is another incredibly useful tool to assist the Keeper at the table, allowing them to see, at a glance, if they are at the right section, where they should be looking next and the overall purpose of the scene. This last is important to let you figure out where a scene should end, which is not always obvious.

As we get into this section, we notice that precise and exacting answers are provided to every relevant question the PCs might ask Mr Maeda, the Vice-Chairman of the Public Welfare Committee. This is common to most of the NPC interactions in the scenario, which will keep you, as the Keeper, on track with regards to what each of them knows. Once again, it’s a trad scenario. Rather than summarising the things they know and letting you play them as you see fit, things are a little more proscribed here. Of course, if you want to run these interactions differently, you can. It will just mean you spending more time prepping.

We get some general knowledge and descriptions of half-remembered dreams from talking to the townsfolk, but we really get into it when the Investigators go to meet Taneguchi, the old man who is secretly harbouring the Prince of Pale Leaves in his mind. He was approached by a representative of the Association of Pale Leaves and told that, by chanting from he Sutra of Pale Leaves nightly, he would pay off his karmic debt from running over the little girl on the road. Unbeknownst even to himself, he has been making beautiful and elaborate copies of the Sutra at night, when the Prince takes over his body. The APL is planning to use these to spread the Prince’s influence even further across Japan. It is in this section where the Investigators are likely to gain their first exposure to the Sutra, thus beginning their journey towards recruitment by the Prince, themselves.

From here, the investigations might lead to Hōryūji Temple, where they might encounter another recruit, Ukami, a former monk, who is also a martial arts master. Or they might go to the Momijidera Temple, where Taneguchi recites his prayers each night, But eventually, we come to one of the more interesting parts of this scenario, Unpleasant Dreams, where the Keeper can tailor nightmares to individual investigators’ personalities, backgrounds and memories. This is the first time they will encounter the Baku. There will be different outcomes depending on the levels of exposure they have had to the Sutra so far. It could lead to significant Sanity loss, but, on the bright side, it could also lead to Exposure Point (the points which track how exposed you are to the Sutra and how much influence the Prince has over you) reduction.

Lore Sheet 3: Fortune-Telling in Japan and the Fortune-Teller, Madam Inaba. — Lore sheet

After this, they are likely to visit Madam Inaba, the Fortune Teller or go to the aforementioned Hōryūji Temple to find out more about the Baku and how to defeat it. Importantly, they should then go and do some research in the Sutra itself, exposing them once agian to the Princes influence. This will lead them inevitably to the Dream Dive section. The scenario takes us back into dreams here, this time, a shared, lucid dream, which they will have learned how to perform from their research in the Sutra, of course. Rather than have the Keeper craft the dreamscapes they encounter this time, they are put through a “Gauntlet of Nightmares.” I like the nightmares that have been described in this section, they are Japanese-flavoured (I have definitely had nightmares about the mukade myself) and they’re scary, but they seem a little random. They’re not as thematically coherent as other parts of this scenario. At least, until you get to Taneguchi’s Dream: The Accident. In this one, you relive, along with Mr Taneguchi, the night he killed Nakamura Hinako on the road. The scenario presents several ways the Investigators might deal with the situation, from doing nothing to showing some humanity to the dying girl, to rewriting history!

The baku, a big, purple, tapir-like creature, feeding on a n old man who is sleeping on a futon in a tatami room. — Yum Yum

The only thing left to do is to face the Baku itself. By now, the PCs might have learned enough to know that the Baku is not the real threat here. Rather, it comes from the Pale Monk haunting the dreams of Taneguchi, the representation of the Pale Prince. Or they might play right into the Prince’s hands and attempt to defeat the creature, clearing a path for the Sutra to capture more recruits. Whatever they decide, there is a good chance they will have to use signs and magics learned from the Sutra itself to do battle in the Final Encounter. The scenario introduces mechanics by which they can spend Magic Points to summon useful items or weapons to help them, but their opponents can do the same or worse. The Baku can fully transform the dreamscape allowing it easier access to Taneguchi, which is all it wants. It wants to gorge itself on the old man’s Sutra-ridden mind. If the Investigators allow that to happen, it is one of the best endings you can achieve, leaving Taneguchi in a state of extreme dementia, but freeing the town of the Prince’s influence.

Endings

Note that the endings presented here and in later scenarios are labeled and numbered, as is common for indie scenarios in Japan. This enables players to tell others how their game went on social media while avoiding spoilers for everyone else.

I understand this concept and the reason for it. But I don’t particularly enjoy the implication that you can’t have your game end any other way than one of the six potential endings provided here. I am not going to judge it without playing it out, but I will say they are described in terms of one ending being a “failure” and others being “Bad Ending,” “Good Ending,” and “Best Ending.” Of course, these are value judgements. Just because you TPK, doesn’t necessarily mean it was a bad ending for your party, and, to be fair, the text does describe this one as “something of an achievement.”

The inclusion of “Optional Post-credit Scenes” is interesting too. These each present a little vignette of how the Investigators might have changed reality during their adventure through dreams. It explains that they work better if the scenario was run as a one-shot but that they might just serve to show the sheer power of the Sutra over reality.

Conclusion

This feels like a great scenario to start off this campaign dealing with the Prince of Pale Leaves as the antagonist. It immediately introduces the players to the idea that this is a being that exists in the mind of others and is spread through the dissemination of the Sutra, or it should. I can’t say for sure if it does it effectively without playing it. Overall, I like the structure, which is designed to keep the Keeper on track, no matter which way the players decide to go from one scene to the next. I do find the extreme levels of detail in the NPC encounters a little unnecessary. I still think it’s possible to summarise a character’s personality and the things they know in a much shorter manner, that would work just as well, if not better.

I think it’s interesting that each of the scenarios is styled as being possible to run as a one-shot but I can see Dream Eater’s potential in the context of the greater campaign. I’m looking forward to reading the next one, Fanfic, where the APL hatches a plan to recreate the Sutra as an action manga.

Sleighed

You might remember a few weeks ago… I reviewed Slow Sleigh to Plankton Downs. Well, the disclaimer on that review, that I had not played or run it is no longer valid.

Nun too soon for an update

Just a short one this week, dear reader.

You might remember a few weeks ago, for my Halloween post, I reviewed Slow Sleigh to Plankton Downs. Well, the disclaimer on that review, that I had not played or run it is no longer valid. Sister Majid, the Misstep Monastic (a type of nun) and Lee Tuluk, the Scud Miller (meat grinder) formed an unlikely friendship through a misallocated cabin and a game of chance and before you know it they were investigating a murder!

We played one session on Halloween and just finished it up last night. It took about six hours altogether, although there was some time spent on character creation in the first session.

Take a butcher’s at this!

Here are some things I loved about running this adventure:

The new backgrounds are great. Most of them are really far out there but the two that my players chose were obviously quite mundane. They still had some incredible Advanced Skills that got milked for all they were worth. Somehow, our nun used “Reconcile God’s Glory with the Failings of Mortals” constantly. Meanwhile, the Scud Miller managed to use “Fix Anything, Not Necessarily Well, Even with the Wrong Tools” on everything, including relationships. Use the backgrounds if you’re going to play this.
It’s so easy to prepare and run. The keyed descriptions are short enough to easily use on the fly, the premise of the adventure is straight-forward and there are only a couple of unavoidable events that are not difficult to get to grips with. I read it through once, fully, and then reviewed particular sections such as basics of the adventure and the murders before actually running it. It doesn’t take long to do this; its a svelte little scenario.
I really got into describing the aftermaths of the murders and the effects they had on the crew and other NPCs. As rumours spread I had nuns moving in pods and whispering about terrible occurences while blessing themselves, while the porters and mates dealt with grief at the passing of their colleague. Upon the discovery of the second victim, the security guards were puking in corners and staring blankly at blood-soaked toilet stalls. The creature has a silly name, which my players refused to say right, but the murders are gruesome and horrific. It felt important to play into that.
The map of the Nantucket Sleigh Ride. We used this work of art throughout. It was so useful to help the players orient themselves on the hovercraft and it was a genuine pleasure to refer to it. Its beautiful.
The Weather table. I got the players to roll for weather right before the final encounter and they rolled us up a storm. The ship was forced to drop its robotic anchors and ride it out just after the second murder. They figured out who the murderer was and that they were outside on the Observation Deck. What a setup for the final showdown. It was poetic.

A victim, missing its maxilla in a toilet stall. The Maxillary Uslurper in the air vent above. — Aftermath

Conclusion

Dear reader, I would highly recommend you take the Nantucket Sleigh Ride on a trip to Plankton Downs. If you have a couple of evenings to spare and a couple of friends who might enjoy a who-nunnit, as it were, you could do a lot worse. It’s not your typical Troika fare but I am beginning to think there may not be such a thing. You will have horror, you will have laughs and you will definitely have fun.

After the Mind the World Again

Disco Elysium

Have you played Disco Elysium from the much lamented Za/um studio, dear reader? It’s one of those seminal, cult-classic games that shifted my thinking on what video games could be. It’s a mystery game but, is it, really? Even if it is, is the mystery the one presented? Is the goal to find out who killed that guy hanging from the tree in the yard behind the Whirling-in-Rags? I suppose it is, but only up to a point. When playing it, you quickly meet and pass that point, much to the frustration of your ever-suffering partner, Kim Kitsuragi. Psychologically freed of the mundane requirements of your character’s job as a police detective, you can finally get to work on the real mystery; finding yourself. In many ways, the game is a protracted character creation session. You have to do everything from defining his political and romantic persuasions, coming to understand his opinions on art, exploring his relationship with vices of all kinds to just figuring out his name. How does the game handle these revelations? Well, largely through the personification of various aspects of your Detective’s personality. These take the form of his stats, Intellect, Psyche, Fysique and Motorics and the various skills associated with them. They speak to you, often in deranged or idiosyncratic voices representative of their own, niche fragment of his personality, and try to get you to look at the world from their highly rarified perspective or to act based on it.

It’s a unique game. It’s also a unique experience that left me with so many interesting thoughts and questions. One such question was, could you make a TTRPG out of this? The answer is, you can certainly try.

After the Mind…

The Character Sheet screen from Disco Elysium. It shows each of the four main stats, Intellect, Psyche, Physique and Motorics and all of the skills that are associated with them in a grid on a black screen with white text. — The Character Sheet screen from Disco Elysium. The TTRPG stats are not as complicated as this.

Last night, I got together with four other members of Tables and Tales to play a session of After the Mind the World Again by Aster Fialla. The front cover of the game uses the tagline, ‘A murder mystery role-playing game.’ This is not an inaccurate description. However, I feel like the subheading on the next page is getting closer to the facts:

A Disco Elysium-inspired murder mystery TTRPG about a
detective and the voices in his head

In this TTRPG, the inspiration comes not from the fascinating world or the city of Revachol, it doesn’t come from the richly drawn characters of the video game, or even its ubiquitous politics. It comes, instead, from the essentials of the gameplay. In other words, the shit that’s going on in the Detective’s head and how it affects the world around him. You see, this is a GMful game that requires five people exactly, one of which is the lone player with the other four acting as GMs. Each GM represents one of the four stats from Disco Elysium, Intellect, Psyche, Fysique and Motorics. They are collectively referred to as the Facets. One of their responsibilities is to describe various features of the world the Detective moves through. Intellect has responsibility for nerdy people, art pieces, journals, etc. Meanwhile, Fysique gets stuff like buildings, a good strong state, and brawny folks.

At the start of the game, the player comes up with a name, pronouns and presentation for their Detective, as well as their role (they might not be a cop, but a PI or an insurance adjuster or something else.) Each of the Facets also gets a turn here, though. Psyche gets to describe the Detective’s face, while Motorics comes up with aspects of their style and an unusual object in their possession, for instance. I found this very fun, as did everyone else at the table, I think. I even commented that having others make your character for you in other RPGs could be just as fun!

Once that’s done, each of the Facets answers a couple of questions designed to form a baseline for their relationships with other Facets at the table. After the Mind the World Again is Powered by the Apocalypse, so this sort of character building question should be familiar to anyone who has played a game like that before.

Then they get started making the Neighbourhood. You go around the table, starting with the person who most recently played Disco Elysium, and get everyone to answer one of the five questions presented in the book that should give you an idea of the type of area this murder has taken place in.

Once you’re done with that, the Detective tells us a little about the victim and then each of the Facets introduces a piece of evidence from the crime scene. Intellect tells us about any Prior knowledge that’s relevant to the situation, Psyche describes a Person of Interest at the scene, Fysique comes up with a Landmark, in this case, where the murder occurred, and Motorics gets to reveal a clue, something tangible at the scene.

From that point, the Detective starts the investigation, describing what they are doing in the fiction, triggering particular Moves, using the Facets’ stats to make rolls and making Deductions in an effort to solve the murder. This is in line with the Detective’s Agenda:

Explore the world to its fullest.

Make the most of your Facets.

Play to find out the truth.

This is complicated by the fact that each of the Facets wants the Detective to act in different ways, offering sometimes conflicting options and sabotaging each-others’ efforts as they try to have the greater influence on the sleuth and the investigation. Facets’ stats can be boosted or reduced in various ways, often by the actions of the other Facets. Its important to note that the Facets’ Agenda is not focused on solving the murder, rather than constructing an interesting experience:

Create an intriguing world for The Detective to explore.

Highlight the differences between the Facets.

Play to find out what happens.

The Detective investigates, and the Facets Declare Evidence as particular features are described in the world. It’s up to the Detective to combine two pieces of evidence to Make a Deduction. When it comes to that point, they ask the Facets for explanations as to how they fit together. Whichever Facet’s explanation is chosen is the truth and the Facet gets a +1 to their stat, while also getting the opportunity to reduce the stat of another Facet by the same amount.

The investigation is structured into a Deduction Pyramid, which is split into four tiers. On the bottom tier, there should be eight pieces of evidence. These should be combined when the Detective Makes a Deduction so that, you end up with four Minor Deductions on the next tier up. These Minor Deductions should then be combined to come up with two Major Deductions on the penultimate tier. Finally, those Majors need to be combined to come up with the Solution to the murder, sitting right there at the top of the Pyramid.

There are several other mechanics in the game, including one to ensure that the Detective does not simply always choose the explanation of the same Facet all the time, which is clever. A Facet’s stat cannot go above +3 or below -1. If that does happen, the Facet gives the Detective a Condition and goes back to the default value of 1.

…the World Again

A screenshot of the aftermath of the Detective from Disco Elysium punching a twelve year old kid. The scene is in the yard of the Whirling in Rags hostel. A man in a green jacket and yellow flares stands over a prone kid who he just punched. Kim Kitsuragi, dressed in an orange jacket and brown baggy, tapered trousers looks on. — A screenshot of the aftermath of the Detective from Disco Elysium punching a twelve year old kid.

None of us had ever played a game quite like this one before. Obviously, some of us had played PBTA games in the past, so the mechanics were nothing frighteningly new. At points, I even felt echoes of a game of Avery Adler’s The Quiet Year that most of us played last year as we took turns describing the world around our Detective. That Detective was an amateur sleuth named Bruce with a fabulous moustache, a flight jacket, an obsession with whiskey and a curious ability to identify any wooden model aircraft he might come across.

But, sharing GMing duties with three others at the table is a unique and sort of chaotic experience. At the start, it’s actually a little difficult to get into gear. I was playing Motorics and I found I had to be constantly checking my playbook sheet to remind myself what features of the world were within my domain, what my GM Moves were and when I should use them. There are features in there that you might not expect so you have to watch it and you can’t use your GM Moves just whenever. Since all four of us Facets were feeling like this, it kind of stuttered into life as a session, once the character creation bit and the initial set-up of the mystery were done. Meanwhile, Bruce, played ably by relative TTRPG noob, Jude, had to come to terms with the fact that, when it came to any of the really important decisions, he had to give up control and ask the Facets for options before settling on one version of the truth or selecting a course of action.

As we got into the flow of it, though, and as some of us became more lubricated by the liberal application of fine Spanish lager, we found the conversation that was the game began to come much more instinctively. We were interacting with the mechanics and deliberately fucking each other over for stat points, while Bruce began to explore the small, dead silent village of Battersfield and investigate the murder of local baker, Barbara Devons. Evidence has been declared in abundance and two deductions have been made! Bruce managed to finally make it out of the Bakery to explore the office, the bare flour cellar and even the gay bar across the road. Unfortunately, we had to leave the case unsolved after the four hour session. Hopefully we’ll be able to pick the trail back up again soon.

We ended up having a really fun time with After the Mind the World again. The stand out scene for me was when Bruce was interrogating Jenny at the crime scene and all four GMs jumped in to answer in particular ways that they thought reflected their own domain within the one NPC. It worked surprisingly well, even though I’m not sure that’s how it’s supposed to work at all.

I would say that there is no way to play a full investigation in a single three hour session without rushing through scenes and maintaining the sort of laser-focus that Harry Dubois does not exemplify in any way. The character creation and making the mystery section took over an hour alone before Bruce ever rolled a die in anger. If you’re going to give it a go, plan it for two sessions.

Do you think you would like to give this game a try, dear reader? Or would you rather go back to Martinaise and collect some tare in a plastic bag while pondering that old wall again?

Change and the Dark

Another schedule change

They say that procrastination is the thief of time. Nope; its work. Work is stealing my time and there ain’t no time cops coming to recover my purloined hours or to clap Work in cuffs. This is the true crime of late-stage capitalism!

Seriously, though, I have a full time day job that has nothing to do with gaming, writing fun stuff or pretending to be other people. That’s how I can afford this luxury website (ooh la la) and all these RPGs I keep backing. Unfortunately, it does take up the majority of my waking hours. Very recently, I mentioned that I would be posting once every three days from now on. I have found this awkward in a few ways. Firstly, I often get mixed up as to what day I am supposed to be posting on this schedule. Secondly, it has meant a lack of a consistent day of the week that my posts appear. Lastly, it is still a bit of a struggle to keep up with this, I am finding, thanks to work and, you know, actually playing games.

So, instead, I have decided to switch to posting on Wednesdays and Sundays. I love writing this blog and do it mainly for my own satisfaction and I am going to continue to do that, just on a twice-weekly basis. To those of you who are regulars around here, thanks for bearing with my struggle to find the perfect schedule. I think this might be the one!

Anyway, on to the meat of the post. Our Halloween one-shot.

Roadhouse Feast

The trees loom above the rutted country road illuminated only by the staccato shudder of your headlights. This road will be the death of us, you say to your companions in the back seat of your Ford motor car. Just concentrate on getting back to Arkham, you think to yourself, as you trundle past Laura’s Roadhouse. A good, god-fearing woman, Laura. You know the family. You grew up not so far from here. You wonder how they’re doing now.

Crash, badump, badump

You shouldn’t have let your mind wander. You’ve hit something! The automobile! No! The Ford is pitched forward at an unnatural angle. The others have already bailed out. They’ve gone to inspect the carcass left on the road behind. One of them screams.

This is the opening, in my words, of the Cthulhu Dark module, Roadhouse Feast. It was written in 2023 by Linus Weber, with Monster-art by artgeek09 on Fiverr and cover-art by Eneida Nieves on Pexels although, the version I downloaded from itch.io did not have a cover to speak of.

I won’t go into the details of the module, the characters, the plot or the ending. Instead I want to write about our experience with it and general vibes.

The one-shot

There were four of us at the table on Halloween night for this one-shot, including me as Keeper. This was the ideal number, I believe. Numbers for a one-shot are critical to actually getting to the end of it. Any more than four and we would have struggled with that all-important goal. Instead, we played the module from start to finish with a little time over for epilogues. This is what I had been hoping for when I picked this module to run. The author designed it to be run in a single session of two to three hours and that’s exactly what it was. Tick!

The setup is pretty much as I narrated above. The investigators (this is a catch-all term for PCs in Cthulhu Dark. It does not necessarily imply that they are, in fact, in any way, detectives) are driving home to Arkham from a place called Thompson Village, late at night on 31st March 1923. They hit a deer on the road, damaging their car enough that they need to go and get help. This is all classic horror story setup stuff. The 1920s era and forest setting helps by removing the technological advantages of the present day and exuding a creepy, dark, dangerous atmosphere. Tick!

What do you want from a Cthulhu game of any kind? You want your PCs to experience some fucked up shit that has the potential to send them swirling down the plughole of madness at any moment. You want monstrous entities, cultists, forbidden philosophies and the mundane warped and twisted into something otherworldly and inconceivable. Roadhouse Feast has all this in a tidy little package. Tick!

The system

This was our first proper foray into a Cthulhu Dark game. This despite actually owning the book. Since we couldn’t actually find the book in time, I fell back on the original, playtest-style rules that Graham Walmsley published back in 2010 in the form of a 4 page pamphlet. All of the rules fit easily on those 4 pages with room to spare. It is the lightest of systems. I don’t think I have ever played anything lighter. Honey Heist approaches it, but I think Cthulhu Dark wins this contest by virtue of the fact that you only have one stat and no abilities of any kind. The one stat you have is called Insight (although in those original rules that I was using, it was called Insanity.) You can play this game sans character sheet by simply placing a d6 in front of you. It should show the 1 at the start of the game but every time you fail an Insight check, brought on mainly by seeing Mythos shit or using your Insight die to help succeed at actions, you gain a point and flip your die to the appropriate number. If it ever gets to 6, you’re screwed. Your investigator loses their marbles and is removed from the game. We had one investigator hit 6 Insight. She started a forest fire and stood in the road, worshiping the flames. It was a good time.

This mechanic was so good in a one-shot. It works perfectly to keep your investigators worried about what is just around the corner, or about having to use their Insight die to succeed at a check. Of course, the other great strength of the system is that, if they ever face an actual Cthulhu Mythos monster, they’re goners. They will not survive. This gives them the feeling of victims in a horror movie. You cannot fight, you can only run or hide or delay. In this scenario, delaying is a major part of survival and it led to some ingenious moments from the players.

In general, the lightness of the ruleset made for exceptional roleplaying throughout. There were no long breaks to add up dice rolls, no-one ever had to stop to look up rules and there were no character sheets or monster stats to worry about.

All in all, I would recommend the system and the scenario for a horrific one-shot experience, dear reader. Go pick them up if you would like that sort of thing.

Case Closed

The suspects

I finished up two investigative scenarios in the last week or so. The experiences could not have been more different. I was the GM for one and a player in the other. They were in very different genres and systems too. I am going to have a go at dissecting them and trying to compare them, nonetheless.

D&D 5E – An Unexpected Wedding Invitation

I wrote a little about this short campaign here. At the time I wrote that, I didn’t even know it was a murder mystery, to be honest. It is a published, third-party 5E scenario so I could have looked it up, but I avoided reading anything about it online. Our wonderful DM was also the consummate host and was always wonderfully welcoming. She was a great DM too. We met in person over the space of eight sessions, more-or-less every two weeks. Our DM, who has run this scenario more than once previously, informed us afterwards that we took far longer to get through the scenario than other groups. Personally, I think that’s probably because of a couple of very important factors. Firstly, we had a fairly large group, five players and the DM. But, I think the second factor is what really pushed it so far beyond the normal length for the scenario. We were all chewing the scenery at every available opportunity. This group of players does not shy away from the first person, expansive, full-chested role-playing and it honestly does my withered heart good to see it every time we get together. We all had reasons for going ham as well. There was the promise of romance and, failing that, friendship. The possibility for court intrigue and drama was there as well. But, certain sections of the table were there to get their kisses in (in the infamous words of Lou Wilson.) The mystery was almost secondary to those folks.

As for the mystery itself; I won’t go into details. No spoilers except to say that there is a murder and we were not aware of that aspect going in. I don’t know if the DM advice is to keep that from the players until it happens but that was the case for us. Anyway, that was quite exciting actually. To discover there was an actual crime to figure out gave us all a shot in the arm! Up until then we had been essentially casing the wedding for curses and harassing the guests with weird, cryptic questions about the nature of one family’s bad luck. So, when we had a specific thing to investigate, it filled us with the sort of motivation that, I feel, the scenario failed to provide up to that point.

As for the investigation itself, it’s all about the NPCs in this adventure. That seems appropriate for a mystery game and this particular scenario was replete with well drawn NPCs who had distinct personalities, motivations, idiosyncrasies and voices (provided quite expertly by our DM.) You have the bride and groom, of course but you also have a cast of characters drawn mainly from the families on both sides. There are several set-piece scenes that are designed to allow the PCs to get to know the cast and our DM graciously provided us with portraits for all the main NPCs, hanging them on her DM screen. This was very helpful as there were a lot of them and without that constant visual aid, it would have been much harder to keep track. Our interactions with the NPCs seemed to give us positive or negative standing with them, leading to later conversations being more or less difficult for us.

The setting was integral, of course. An opulent country manse belonging to one of the families involved, surrounded by a generous estate on which they enjoyed hunting and picnicking. The adventure provided a couple of maps; more for reference than anything else as there was not a fight to be had at this affair.

As I said, I am not going into spoilers here about the murder, the suspects or the ending but there are a few things I can say. It seems as though the adventure comes with several prepared possible endings. The actions of the players, their standing with the major NPCs and their final pronouncement of who they figure did the murder all seemed to have an effect on that. This served to give it a slightly video-gamey feel, which was neither good nor bad but certainly leant a lot to the idea that everything was laid out in the adventure quite prescriptively.

Speaking of which, the actions of the PCs throughout felt a little restricted. This was purely a result of playing D&D 5E characters in a genre they were never meant to exist in. Few of our powers or abilities were of much use in this milieu and that felt a little frustrating at times.

Equally, there were several timed events that could not be prevented or changed in any real way by the PCs. Once again, this had the effect of making us feel more like spectators than active participants.

Questioning the NPCs, the most important part of the scenario, by far, and the only one where you could make inroads in your romantic or duelling ambitions, was difficult to say the least. Pretty much all of them could have done it, to be honest. That, by itself, is ok, but failing certain rolls here and there made the process feel fruitless at times. Without some mechanic to allow you to fail forward, it was always going to feel like this.

In the end, we failed to catch the killer. We fingered the wrong guy for the crime. This was due, in large part, to us interacting less with the killer than we might have, failing s couple of clutch rolls in interacting with them and the fact that we were left with too many potential culprits at the end that we couldn’t whittle down further with the evidence we had. Our failure was revealed to us in a sort of cut-scene right at the end. After all the effort we had put in, this felt like losing even though we had all enjoyed playing together around the table. The overall consensus from the players was that 5E was not the system for this scenario. It is not built for this sort of investigation and it led to an unsatisfying feeling from the result of the game even if we had a good time playing together, as we always do.

Blade Runner, Electric Dreams

Two blade runners posing like neon noir heroes in front of a stylised Wallace Corp ziggurat beneath the title of the Blade Runner Role Playing Game. — A photo of the front of my copy of the Blade Runner Start Set box.

I wrote a little about this game here while we were still playing it. At the time of writing that, we were only two sessions in and I was greatly looking forward to the next one. There were two players, playing Detective Novak and Fenna. We did this online, using Zoom and Roll20. It took five sessions of two and a half to three hours each. Having checked out other groups’ experiences with the same case file, I can say that’s about average. I could absolutely see it taking both less or more time since it would be dependent on how quickly the blade runners discover the key clues and how quickly they act.

Electric Dreams is also a pre-written scenario but, I think, importantly, it was produced by Free League as the intro to the Blade Runner RPG. There was never going to be a mismatch of scenario and system like we saw in An Unexpected Wedding Invitation. In fact, it felt as though this scenario was close to perfectly designed to bring players into the world and the system at the same time.

If you are a Blade Runner fan but not familiar with the Year Zero engine or RPGs in general, its got elements from the movies for you to geek out over and allow you to feel part of the megacity of LA by referencing the media you know and love. Meanwhile, it holds your hand through the early interactions with the mechanics, kicking things off with a few basic Observation and Manipulation rolls, teaching you that the more successes you get on your dice rolls, the better the result. As time goes on, the references to the movies remain strong, keeping the whole thing feeling like a natural continuation of or bridge between those stories and establishing a consistent and immersive tone and atmosphere. But you get more and more in-depth interactions with the rules as it introduces you to chase mechanics, combat, use of more complicated investigative techniques and character advancement.

And if you are an old hand at Free League’s signature rules engine, you will be good to go from the start. I was somewhere in between when we started playing. I am a big fan of Blade Runner and I have run Tales from the Loop before so I knew how the system worked well enough. But it was a long time since I had played it and I definitely had to look some rules up in play. This was generally fine, and didn’t take too long. What we also found, was that, once we looked up those rules once, we grokked them and didn’t have to keep referring to the rulebook, which was a refreshing change of pace for a group of players who have mainly only played D&D 5E together before (at least in recent years.)

Now, down to the scenario itself. As with the Wedding mystery, this was largely based around really well drawn NPCs, all of whom were potentially important to the plot. But, from the start, it felt as though the PCs knew who their main suspect was. They were rarely dissuaded from that notion, despite (or perhaps because of) the powers-that-be forcefully reminding them about the way they would like to see the investigation go. Since the characters were playing blade runners, cops in the LAPD, there were a number of NPCs that were there purely to back them up or chivvy them along. You had Coco, the medical examiner (who you also meet in Blade Runner 2049) and Deputy Chief Holden (who got his chest punctured in an interaction with Leon the replicant in Blade Runner) as well as any number of ad-libbed beat cops and the AI LAPD Despatch. The Wallace Corp is represented by one of their replicant executives who was immense fun to play. You also had a few NPCs that were witnesses and were never going to be anything but witnesses. The investigation was not designed to send the detectives off on the wrong path. There was no more than one red herring and that was there more to reinforce a theme than as a real way of derailing things.

What we found was that most of the sessions involved them trying to track the one suspect and discover their motivations and whereabouts. This led them into a web of corporate intrigue and moral dilemmas. That’s what Blade Runner should be about, of course, and Free League nailed that. The PCs were able to use the abilities of their pregenerated characters to do that pretty well. In fact, I would say that they were implausibly successful most of the time. On a couple of occasions they rolled so well that I felt compelled to reward them with information that would not, otherwise, have come up until later in the investigation. Moments like these allowed them to make incredibly effective leaps. What I liked about this scenario is that it allowed for that. There is a timeline of events that will happen at particular points of the investigation, but only if the PCs do nothing to prevent them. So, that doesn’t stop you moving them two steps forward, instead of the usual one. I think it actually encourages that sort of thing, in fact, as the timed events are generally pretty bad for the investigators or the other major characters.

We got an ending that was equal parts satisfying and open-ended, with the PCs making the moral, rather than the legal choice after the corporation took the law into its own hands one too many times. We might return to Novak and Fenna someday, maybe in the next published case file, Fiery Angels. The first one ran so well that I would definitely be confident to play the next one.

Conclusion

It is almost unfair to compare these two games, but it has been impossible for me to do anything else. In blade runner, you had a scenario where any outcome the PCs reached was likely to be satisfying and a system that supported the sort of game you were playing, investigative, character driven and darkly themed. In the other, the scenario felt a little too restrictive and was hampered further by a system that was never designed to support the investigative nature or the regency feel. I had fun with both, but I know where I would turn first if someone asked to play a mystery game.

Tales from the Loop – Mascots and Murder

Indie mascot horror

Maybe I’m giving away a bit too much with the title of this scenario. What do you think? I mean, look, here’s the thing; when we set up Tables and Tales a few months ago, I was curious about the kinds of things new members were into. One of them said they liked Indie Mascot Horror. Now, let me tell you, dear reader, I did not know what that was. Since then, I have learned that it refers to video games like Five Nights at Freddie’s and Poppy’s Playtime. I had obviously not played these games but I looked into them a bit and got the vibe. I thought about the types of RPGs that would be good for those themes and tropes. It did not take me long to decide on Tales from the Loop.

Tales from the Loop

If you have never seen the artworks of Simon Stålenhag, do yourself a favour and go check them out. I have taken some photos of his work from his art book, Tales from the Loop and embedded them here but they don’t do the work justice. When I first encountered his work several years ago, it filed me with wonder. He created such a realistic depiction of a past that was largely recognisable to me from my own childhood, interspersed with or shockingly dominated by futuristic architectures and sci-fi wonders. His work excited my imagination like only RPGs had in the past. So when I discovered that Free League were producing a Tales From the Loop game, it didn’t take me long to pick it up. It took a little longer to get it to the table but when I did I discovered that the players loved it.

## Indie mascot horror
Maybe I’m giving away a bit too much with the title of this scenario. What do you think? I mean, look, here’s the thing; when we set up Tables and Tales a few months ago, I was curious about the kinds of things new members were into. One of them said they liked Indie Mascot Horror. Now, let me tell you, dear reader, I did not know what that was. Since then, I have learned that it refers to video games like Five Nights at Freddie’s and Poppy’s Playtime. I had obviously not played these games but I looked into them a bit and got the vibe. I thought about the types of RPGs that would be good for those themes and tropes. It did not take me long to decide on Tales from the Loop.

## Tales from the Loop
If you have never seen the artworks of [Simon Stålenhag](https://www.simonstalenhag.se/), do yourself a favour and go check them out. When I first encountered his work several years ago, it filed me with wonder. He created such a realistic depiction of a past that was largely recognisable to me from my own childhood, interspersed with or shockingly dominated by futuristic architectures and sci-fi wonders. His work excited my imagination like only RPGs had in the past. So when I discovered that Free League were producing a [Tales From the Loop game](https://freeleaguepublishing.com/games/tales-from-the-loop-rpg/), it didn’t take me long to pick it up. It took a little longer to get it to the table but when I did I discovered that the players loved it.

Tales from the Loop is a game about the 1980s that never was. It posits a world in which some astounding scientific breakthroughs occurred in the ‘50s and ‘60s so that, by the time in which the game is set, they are not considered so strange. You have your robots and your hovercraft and your infinitely renewable energy. But most of that stuff is considered mundane in Stålenhag’s world. Not only that, they exist alongside the ‘80s mainstay technologies like Walkmans, cassette tapes, VCRs and Soda Stream. In Stålenhag’s artwork this created some beautifully uncanny images. Most were set in the region of Sweden known as Mälaröarna, where the Loop project was based. This is where the world’s largest particle accelerator was built. Though it is not necessarily directly responsible for the many strange occurrences in the region, the people who populate such a scientifically rarified place usually are. Scientists and administrators and students flocked to the region and started families there. So many of Stålenhag’s paintings involved kids; a toe-headed child threatening an old Volkswagen van marked “Polis” with a giant robot under his control; a pair of woolly-hatted kids digging in the Swedish snow and gazing back at their homes, dwarfed by the cyclopean, other-worldly cooling towers used to release heat from the core of the Loop itself, the Gravitron; a little kid in cold weather coveralls leading his grandfather through the snow to a mysterious sphere, left abandoned in the countryside, its purpose and provenance forgotten. These were the inspirations for the RPG.

The game came out at the height of the popularity of Stranger Things, which helped it gain a lot of traction I think, and then it even had its own, unfortunately not so popular, spinoff [TV series](https://en.wikipedia.org/wiki/Tales_from_the_Loop), which I, at least, loved.

In the RPG you play kids between 10 and 15 years old. You get to choose a Type from such classics as the Computer Geek, the Hick and the Weirdo. You also have to choose some really fun things like your Iconic Item, your key relationships and your favourite 1980s song.

Once you have your Kid, you and your friends can go out and investigate weird shit on your bikes. Stuff like, where are all the birds gone? What are all the adults doing gathered around that weird machine in the field? What’s that dinosaur looking claw print in the snow? You know, normal kid shit.

## Roll mechanics
Tales from the Loop uses a version of the Year Zero engine, and, in fact, it was the first game I played using that system. It’s really straight-forward and intuitive, easy to learn and resolves situations quickly. “Situations” are generally and collectively referred to in the text as “Trouble” with a capital “T,” appropriately enough. For many, the Trouble you got into and out of when they were kids are some of the most enduring and treasured memories. In the game, you combine your ability dice and your skill dice into one dice pool and roll them all to try and get at least one 6. Since you only use d6s in this game, that’s the highest you can roll. The more 6s you roll the better, generally.

The only issue my players and I had with the rules is the Extended Trouble mechanic. The way this works is that, during the final showdown, encounter or whatever, every kid says what they are going to do and the GM tells them how many successes they will need to succeed fully. Then one player rolls all the dice in one enormous pool. Generally, if they don’t succeed fully but they still have a few successes, they might achieve what they were trying to but one or more kids will earn conditions or even become Broken. But, in play, we found this approach to be unsatisfying. Each player wanted their own cool moment to roll for and the all-or-nothing approach meant that they couldn’t attempt to take any rectifying actions if and when they saw things going wrong. Anyway, suffice it to say, we won’t be using the Extended Trouble rule next time.

## Mascots and Murder
Here are the very basics of the scenario I have planned:
Although the first Loop was in Sweden and much of the book is written as though it is the default setting, they do actually provide a second potential setting in it. That’s Boulder City, Nevada, the “Best city by a dam site,” which is a reference to its proximity to the Hoover Dam. There is another Loop in this region and all of the scenarios presented in the core book can be transposed very easily to the desert, believe it or not. This is where the kids in this scenario will be from. It is summer in Boulder City so it’s going to be so sizzling hot that you can fry an egg on the sidewalk. This will be a nice change as all the other Tales from the Loop games I have played were set in Sweden in autumn and winter.

Some teens have gone missing from Boulder City. Although their parents don’t seem too worried about it, our intrepid Kids are going to solve this mystery as they track down the source of the eerie, carnival-like music out in the Nevada desert and figure out what the connection is.

I have had fun writing this scenario, even though I have gone over it and over it to get it right. So, it’ll be ready to play in a few weeks.

The Tales from the Loop core book has some very useful advice for writing and structuring a scenario for it yourself. As long as you stick to that, you’re unlikely to go wrong. This is not actually the first one I have written myself, using these guidelines and, I can tell you, it works really well.

Have you played Tales from the Loop? What did you think of it? If you had to run a particular game for Indie Mascot Horror vibes, what would it be?

Tales from the Loop is a game about the 1980s that never was. It posits a world in which some astounding scientific breakthroughs occurred in the ‘50s and ‘60s so that, by the time in which the game is set, they are not considered so strange. You have your robots and your hovercraft and your infinitely renewable energy. But most of that stuff is considered mundane in Stålenhag’s world. Not only that, they exist alongside the ‘80s mainstay technologies like Walkmans, cassette tapes, VCRs and Soda Stream. In Stålenhag’s artwork this created some beautifully uncanny images. Most were set in the region of Sweden known as Mälaröarna, where the Loop project was based. This is where the world’s largest particle accelerator was built. Though it is not necessarily directly responsible for the many strange occurrences in the region, the people who populate such a scientifically rarified place usually are. Scientists and administrators and students flocked to the region and started families there. So many of Stålenhag’s paintings involved kids; a toe-headed child threatening an old Volkswagen van marked “Polis” with a giant robot under his control; a pair of woolly-hatted kids digging in the Swedish snow and gazing back at their homes, dwarfed by the cyclopean, other-worldly cooling towers used to release heat from the core of the Loop itself, the Gravitron; a little kid in cold weather coveralls leading his grandfather through the snow to a mysterious sphere, left abandoned in the countryside, its purpose and provenance forgotten. These were the inspirations for the RPG.

The game came out at the height of the popularity of Stranger Things, which helped it gain a lot of traction I think, and then it even had its own, unfortunately not so popular, spinoff TV series, which I, at least, loved.

In the RPG you play kids between 10 and 15 years old. You get to choose a Type from such classics as the Computer Geek, the Hick and the Weirdo. You also have to choose some really fun things like your Iconic Item, your key relationships and your favourite 1980s song.

Once you have your Kid, you and your friends can go out and investigate weird shit on your bikes. Stuff like, where are all the birds gone? What are all the adults doing gathered around that weird machine in the field? What’s that dinosaur looking claw print in the snow? You know, normal kid shit.

Roll mechanics

Tales from the Loop uses a version of the Year Zero engine, and, in fact, it was the first game I played using that system. It’s really straight-forward and intuitive, easy to learn and resolves situations quickly. “Situations” are generally and collectively referred to in the text as “Trouble” with a capital “T,” appropriately enough. For many, the Trouble you got into and out of when they were kids are some of the most enduring and treasured memories. In the game, you combine your ability dice and your skill dice into one dice pool and roll them all to try and get at least one 6. Since you only use d6s in this game, that’s the highest you can roll. The more 6s you roll the better, generally.

The only issue my players and I had with the rules is the Extended Trouble mechanic. The way this works is that, during the final showdown, encounter or whatever, every kid says what they are going to do and the GM tells them how many successes they will need to succeed fully. Then one player rolls all the dice in one enormous pool. Generally, if they don’t succeed fully but they still have a few successes, they might achieve what they were trying to but one or more kids will earn conditions or even become Broken. But, in play, we found this approach to be unsatisfying. Each player wanted their own cool moment to roll for and the all-or-nothing approach meant that they couldn’t attempt to take any rectifying actions if and when they saw things going wrong. Anyway, suffice it to say, we won’t be using the Extended Trouble rule next time.

Mascots and Murder

Here are the very basics of the scenario I have planned:
Although the first Loop was in Sweden and much of the book is written as though it is the default setting, they do actually provide a second potential setting in it. That’s Boulder City, Nevada, the “Best city by a dam site,” which is a reference to its proximity to the Hoover Dam. There is another Loop in this region and all of the scenarios presented in the core book can be transposed very easily to the desert, believe it or not. This is where the kids in this scenario will be from. It is summer in Boulder City so it’s going to be so sizzling hot that you can fry an egg on the sidewalk. This will be a nice change as all the other Tales from the Loop games I have played were set in Sweden in autumn and winter.

Photo from the book, Tales from the Loop by Simon Stålenhag.

Some teens have gone missing from Boulder City. Although their parents don’t seem too worried about it, our intrepid Kids are going to solve this mystery as they track down the source of the eerie, carnival-like music out in the Nevada desert and figure out what the connection is.

I have had fun writing this scenario, even though I have gone over it and over it to get it right. So, it’ll be ready to play in a few weeks.

The Tales from the Loop core book has some very useful advice for writing and structuring a scenario for it yourself. As long as you stick to that, you’re unlikely to go wrong. This is not actually the first one I have written myself, using these guidelines and, I can tell you, it works really well.

Have you played Tales from the Loop? What did you think of it? If you had to run a particular game for Indie Mascot Horror vibes, what would it be?

Investigations

The detective dichotomy

We have been enjoying the Blade Runner RPG immensely in the last few weeks. The blade runners are into the second day of their investigation of the murder of Sandor, another member of the LAPD Rep Detect Unit who happened to be a Nexus 9 replicant. So far, it has gone pretty well for them. They have had some incredible luck with dice rolls that even revealed certain clues I was surprised about. Due to uncovering these, I think they are coming up with the basis of a solid theory for what happened.

Here’s the thing: this is an official case file, produced by Free League. I would imagine most people playing Blade Runner have run this scenario; it comes in the starter set. And the details of the scenario, the NPCs, the locations, even the events, to a certain extent, are set. There is a lot of freedom for the PCs to pursue leads when and how they want but the perpetrator/s, their reasons and motivations and the major players in the case are the same for every table.

Now don’t get me wrong, we are really enjoying this format. The setting and the themes and the ways the scenario intersects with them are very well done. But it is hard not to feel like it’s on rails, right? The answers will always be the same although each group might do something different with them.

Of course, maybe that’s true of any prewritten scenario, no matter the genre. There is always a lich at the end of Tomb of Horrors. Strahd is the big bad in Ravenloft. That kind of thing goes without saying. So, what is it about the mystery that makes this seem less free-form? I guess it’s that finding the answers is the whole point. In Ravenloft, the point for the players is probably the fun of exploring Barovia and the castle. They are enjoying the scares and the combat and all of that.

But in the end maybe it doesn’t matter. Of course, my players don’t know the ins and outs of the clues or the perps or the mystery until they find them. So it’s still mysterious to them.

Building with Brindlewood

Of course, there are other ways to do mystery games. The one that comes to mind is Brindlewood Bay by Jason Cordova, of course, and the games that have been Carved from Brindlewood, like Public Access and others. In these games, there are plenty of pre-written and published mysteries but, significantly, they don’t have solutions.

In an inventive and fascinating twist of game design, Brindlewood Bay’s solutions emerge during play. There are elements of investigation, role playing, narrative building and straight up dice rolling that result in your characters either coming up with the right answer or the wrong answer. Or, you have the familiar PBTA option of a correct answer but with some complication on a middling roll of the dice.

I have not yet had the chance to play one of these games but I would love to. I want to see if it is more satisfying than the sort of game where your solution is written in stone.

Have you played any mystery games that made you excited to play them again? Send me some recommendations!