Whoof. Secrets of Shirakawa castle, finally finished. While the module is strong, there are a few places where I feel like I massively screwed up, or could have run things much better. Our actual review is up over here, but lets talk about running the module shall we?
This post will have specifics on running the module, and spoilers. While the other post talks about the module as a whole, this post is just talking about things that I wish I had done differently.
#1. Sei – The Friendly NPC
One of the things I feel like I really suck at the most is having NPC’s with the party, and Sei is a fantastic example of this. Sei’s role in the adventure is to be sorta guide/hint source to the players, while also providing flavor, a bit of lore, and in one situation, combat backup.
However, because I was afraid of using Sei too much, I didn’t actually use them in a single combat encounter, which meant there were multiple encounters where they were just sorta…. standing to the side, and then going “Oh yeah, that thing you just fought. It was a X/Y/Z.” I think that if I wanted Sei to be a more active part of the game, I needed to include them in combat, and to actually have them be a critical part of the team, so that their reveals of their backstory and other such things feel meaningful.
What would I do differently? I think I’d try to have Sei help the party more in certain situations, and decide how they’d react to various things in advance. The players need to care about Sei for some parts of the story to be meaningful, and that means including them in combat. It might even be possible to turn them into a semi-PC if I was to run the module again. I don’t know if this would solve the problem, but I think it might be better.
#2. Managing the NPC’s
Being a social deduction module, Secrets of Shirakawa Castle has quite a few NPC’s, and they’re written quite well, including a very strong list of relationships and such at the back of the module. Each of them has information, secrets, and other such knowledge….
So when I forgot about two of them that was a problem. A big problem, when they’re supposed to be used as a key part of revealing the last bit of the mystery.
Whoops.
What would I do differently?
There are a lot of NPC’s. If I was to run the module again, I’d would make sure to introduce all of them, and for the ones that the players don’t encounter, have them run into them either at the bath house, dinner, or some other point. The players need to meet them. And since there are only a total of seven NPC’s, it wouldn’t be that hard. I’d want to give the players more time to investigate, meet them, and actually get to know them. So when they die, it feels worse.
#3. Running the Module with a Three Week Break
This one wasn’t really my fault, but it was something I failed to consider, and led to some pretty…. rough parts near the end. The module is built on making you care about the NPC’s, and it uses the first half of the module to do this, building up them, their relationships, and their secrets. The last quarter or so is more combat, encounters, and fights, and the weight of those encounters relies on you caring about those who have been murdered.
What would I do differently?
This one is simple. Secrets should be run as either a 6-7 hour one-shot, or if split into parts, the DM needs to find a way to bring the players back, and make them care about the NPC’s again. This might mean improvising or filler, but not using the NPC’s is a big waste of potential of the module.
Final Thoughts – Running Shirakawa well requires the players to buy into the story and the world. As the DM, if you screw up the people, you screw up the module. If I were to run the module again, I would want to focus on the people, their stories, and make sure I don’t miss anyone. Running a game is always a learning experience, and I hope next time I do a better job.
Take care of yourself folks.