Secrets Of Shirakawa Castle – Review Part 2

An RPG Module Review

Module NameThe Secrets of Shirakawa Castle

AuthorsRCG Harlow/Rosemary CG (Same person. First link goes to her stuff on DM’s Guild, second link goes to her twitter.)

System/Character Level – DND 5E for 4-6 Level 4 players

Price – $4 (We were given a review copy for free.)

Well, there was a three week gap between this and our part one review, which is… sub-optimal. But life happens, things go on, and most importantly, we did finish the adventure!

If you want to read the first part of the review, you can find it here.

If you want to read our DM’s thoughts on running the module, you can find part 1 here, and part 2 here.

Two brief notes before we really dive into this article.

This article will contain spoilers for the module. We’re reviewing it, and we can’t review it without talking about the content. Which means spoilers. You have been warned.

There’s also one part of the module that’s not quite fair for me to review. I’ll go into why later, but to put it simply things went a bit off the rails as the end. Who’d have thunk?

Overall, my opinion on Shirakawa remains more or less the same as it did part one: it’s a strong module where the NPC’s are written well, and it has a bunch of interesting monsters that are outside of the traditional fare of role-playing games.

The module’s primary weakness is that it gets a bit linear near the very end. It also feels like most of the combat gets a little less brutal as things go on.

I say ‘most of the combat,’ because my players didn’t actually do the final fight. They mostly just surrendered to become slaves/concubines of the big bad. So yeah, guys, I love you, but god damnit. I even made custom tokens for the fight and everything. And then you all just surrendered into slavery to quasi-immortal fox demon in the shape of a women.

Really?

Really guys?

Even after she told you that she EATS PEOPLE? And was going to eat the 13 year she had taken hostage?

This is why I don’t feel super confident assessing the combat: because it’s quite possible that if your players don’t fall head over heels for this fox lady, it’s going to end up being a brutal battle.

I wouldn’t know because mine offered to be her slaves and/or concubines. I think a lot of stories have a hero who falls to the dark side, but I don’t think many of them have heroes who just fall for the dark side.

In either case, everyone enjoyed playing the module. If you have a few bucks to spare, I’d highly suggest picking it up. The ending is well written, as long as your players at least like… try to defeat the final boss, but I wouldn’t know. It does set up another one shot, Return to Shirakawa Castle, where I’m gonna make them face off against their old PC’s.

Other then that, I don’t have too much else to say. I’m gonna close out this article with some uploaded images of the maps I made for some of the fights. Feel free to use them if you end up running the module on your own.

Central Castle Area
River running through small forest with bloody footprints
Large destroyed house in middle of grove, with dead trees above it, and alive trees and a path leading to the house below.

Running Secrets Of Shirakawa Castle – DM Thoughts Part 2

We finished Shirakawa Castle! Here’s where I screwed up running the game.

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.

Running Secrets Of Shirakawa Castle – DM Thoughts

Unfortunately, I wasn’t able to finish running the Secrets of Shirakawa Castle module this week, but instead I hope to have the second part of the review up next week. If you haven’t read the first part, the link to it is here.

This post isn’t a review, instead, it’s just a collection of quick thoughts on running the Secrets of Shirakawa Castle module before. The primary difference between this and review is that I view these more as areas where I screwed up running the module, and where doing things differently would have been more fun for the players. As such, this post is mostly intended for game masters intending to run the module. So without reading the actual module, this article may not be very useful for you.

The module itself can be bought here, on the DM’s guild.


1. Don’t be afraid to use Sei as part of the investigation.
-I’m always afraid of having NPC’s do too much in games. Its something I need to work on. With that said, the way I ran things, it was almost like he wasn’t there. If I were to do this again, I would try to make him a more active part of the game, especially if I was to run the module as few players as I did. Sei and their lore is a fairly key component to the module, and by downplaying them too much, I think I made things a lot more complex then they needed to be.


2. Actively monitor party resources.
Again, more on me then the module. I wasn’t paying a huge amount of attention to how much HP/Spells/etc my players had. The module isn’t a met grinder, but it is punishing, and with exhaustion and other mechanics in play, it can become very easy to accidentally overestimate how much more the party can take without a short rest.


3. Let the players know that they have options to really explore the castle.
This is honestly my biggest regret. I’m pretty sure it’s how I ran the module, but when collecting feedback at the end, many of my players said they felt railroaded. Here’s the thing: Secrets is very, very open ended. Every room in the castle has a description and something to find in it. There are servants to talk to, a bathhouse to visit, and a small garden and pond. Each of these also has clues and information about the cause of the Yokai infestation. Players really can just wander and explore. If I was to run the module again, I think I would do a short tour of the castle, then have the NPC’s tell the players they can inspect wherever they want, and leave them.

These were my big three take aways. I expect to finish running the module next weekend, and after that I’ll post my final review of it. Hopefully these notes help anyone who ends up deciding to send folks on an adventure of their own!

RPG Module Review: The Great Egg Scramble

Module NameThe Great Egg Scramble

AuthorsDylan Teal

System/Character Level – DND 5E/4 Level 5’s (I ran it with two level 7’s though)

Price – Pay what you want, $2 suggested. ( I had 2$ worth of fun running it, so I bought it afterward.)

I was going to write this post later, and play Minecraft instead, but because I was talked into playing modded Minecraft, my instance is still launching. Seriously, why does this require apparently recompiling my entire game each time I want to launch a mod pack? It’s insane.

So, DND Module Review time! Today I’m gonna talk about a fairly fun adventure I ran last week for two the folks in one of my DND groups, when one person was just dead sick, and one couldn’t make it.

Woo! So, where to start. I actually had a lot of fun running this, and I think folks had fun playing it. It’s a fairly straightforward adventure, with a few encounters, and some custom enemies. It has maps, which is, as always, appreciated. They’re not super beautiful by any means, but they are functional, and the fact that they’re actually included means it won’t be too hard to remake them in whatever software you prefer if you decide they aren’t up to your standards.

While overall I like the module, there were a few places that it did feel a bit weaker/less fleshed out. The first place is the Spring Festival itself. Despite it being a semi-large part of the story, there isn’t much detail in what is actually being sold, whose present, other little bits of flavor. The closest we get is a brief description in the intro, and a few lines about how the party can find most mundane goods they might want, but no magic items, and how they won’t be able to find a horse/cart. And that’s more or less the whole thing.

Second place is the second NPC the players encounter, Lupin. While Lupin is fairly central to the module in terms of driving it forward, the module mostly only contains info about what Lupin knows, and what might happen if the players are able to persuade him to talk. For the Townsmaster Lepus however, we get a full set of information, info about his personality, and also a few other little things that help roleplaying him. I personally would have liked to see Lupin get the same treatment, especially since he’s arguably the main roleplaying set piece of the adventure. (The bandits end up threatening you/fighting you, Townsmaster Lepus is generally pretty helpful. Lupin is really the only one where players really can either sway him to their side, or totally fail to do so. )

Outside of these two places however, I generally felt I had enough to work with in terms of tone and flavor for the adventure.

Here’s what I would do differently if I ran the module again:

  1. Flesh out the festival in advance. Create one or two stalls to visit, selling knick knacks and trinkets. At the same time, make it very clear that the NPC’s in town won’t be willing to part with their carts. (My players got hung up looking for a cart in town when a better way is to try to make a deal with Lupin.)
  2. Decide on Lupin’s personality beforehand, and force the players to lead the negotiations. In my game, I sorta decided that Lupin was a bit pissy with the bandits, and had him take the lead in negotiating with the players. I think for more experienced players, having to really talk him into a deal would be more fun, and reinforce his grumpy sort of personality.

Afterthought:

One small part of the module I’m not thrilled about is the killer rabbit at the end. I think this part fits in best if you run the adventure as a one-shot, and want to just kill some of the party members at the end as a joke. Otherwise, it’s not fantastic, because the party will have done about 4 four encounters by this point. (The Bandits, The Dire Hares, The Return Journey, and the Bad Egg.) Throwing the rabbit at them WILL kill someone especially because the rabbit’s decapitation means that any player it brings down to zero hit points gets their head popped off like a marshmallow.

Until the next time I think of something worth posting, cya, and stay safe folks.

Updated: 4/25/2020 – This article linked to the wrong module/author on the DMG. We confused it with the similarly named module, “The Great Egg Hunt.” The module that was played/reviewed/purchased was in fact, The Great Egg Scramble. The article has been updated to reflect this information.

Murder at Moonveil Manor

An RPG Module Review

Module NameMurder At Moonveil Manor

AuthorsVall SyreneMogman Dubloon (Links go to other stuff they’ve made.)

System/Character Level – DND 5E/4-6

Price – Pay What You Want

I was trying to figure out what to write about when a little voice told me “Why not write about one of the modules you played/ran somewhat recently?” I replied “Great idea little voice” and then the voice told me I should maybe disconnect from the voice chat for the moment and work on the blog post. So! Here we are, Murder At Moonveil Manor, a 5E module for characters level 4-6, though I think that if the players were all level 4, you’d want at least 4 people in the party to avoid a TPK. Some of the combat encounters can be a bit brutal. Also, I’m going abbreviate the title to MMM because typing the whole thing out is pretty long.

So, MMM is a neat mostly self contained encounter that can probably be slotted in almost anywhere you might want to put it. As a player, I played through it as part of a Curse of Strahd campaign, where our DM just slotted into the middle/end of the game, in a way that felt mostly like a breather. As a DM, I ran it as a one shot over two sessions when one of our players couldn’t make it for the weekly game, and gave all of them characters that were very different from their normal ones. There were a few reasons for this. 1. It let me play the monsters as brutally as possible. I’ve run into a problem with RPG games where I find them hard to really “teach” some of the more crunchy/mathy mechanics of combat in a good way, because I can’t just kill the players until they learn. Except in a one shot like this, in this situation I can TOTALLY go for the total party kill. And 2. It forced them to play characters that role-wise were very different from their characters, and I think that let me role play them/act them out a bit more.

Both of these runs were played on a set of maps that a friend of mine made, which brings me to my first issue with the module. No maps are included. While this isn’t a huge issue at the start, it becomes more of a problem once you move into later parts of the module, especially the combat bits, and if your players ever end up running around the mansion. I’ll talk a bit more about this later.

MMM sets itself up into six chapters, each chapter being more or less a phase. Acts one and two primarily set the scene, having the players arrive at the manor, meet the others at the dinner party, and then eat dinner. Acts three and four involve the murder of one of the guests, and a start of an investigation into what happened. Acts five and six conclude the story, involving the confrontation with the murderer, and the end of the adventure. As far as gameplay elements go, one and two are primarily roleplay, three is skill checks, and four through six are where the combat encounters begin.

While I think this general structure is fine, the biggest issue I have with the module is the following: MMM tries to be too many things at once, and it suffers for it. While the adventure sets itself up as a murder mystery, it’s really more horror themed then anything else. The problem is, these two themes sorta clash with each other.

The general progression of a mystery is something like this.

  1. Introduce the Characters/Setting
  2. Introduce Conflict between characters
  3. Crime Occurs
  4. Investigation
  5. Confront the Perp

And horror goes something like this.

  1. Characters arrive at location.
  2. Some small strange things happen.
  3. Characters attempt to leave/get help, only to discover they are trapped/bridges have been cut, communications severed, etc.
  4. Characters are picked off one by one, until the single remaining survivor escapes/defeats the threat.

The structure of MMM though, is something like this.

  1. Introduce characters and setting.
  2. Introduce Conflict
  3. Small Strange Things Happen
  4. Crime Occurs
  5. Characters(NPC’s) are picked off one by one
  6. Investigation
  7. Confront the Perp

It doesn’t really follow either structure, and the nature of the game means that both times I’ve played it, I’ve never seen the players attempt to leave the house. The Scooby Gang doesn’t book it back to the mystery machine when a horrible monster shows up, and neither do PC’s. If you put a dead body in front of your players after a dinner, they will assume this is a puzzle for them to solve, not a danger to be avoided.

This becomes a problem because the module wants to set up all the guests, so that you have suspects, but it then procedes to kill them off one by one, meaning that the mystery aspect of the game solves itself. It also means that any effort you put into setting up conflict between the guests ends up being fairly moot, because by the time it switches genres, the players don’t have a huge amount of time to investigate either. (The module also doesn’t give any dialogue suggestions for how to really run the interactions between the NPC’s, and frankly having to role play two NPC’s arguing with each other isn’t too much fun for your players. )

Secondly, of the seven NPC’s only four of them ever really feel like reasonable suspects, and two of those characters get killed off real fast, bringing you back down to two characters. I don’t really consider a coin flip an investigation.

So, does the module do horror well then? Well, sorta. Some parts of the module work really well, including the mimic attack, the mini-book mimics, and the fight with the murderer and the heart of the manor. The other parts not so much.

After part four, the rest of the manor activates, and this leads to traps being placed in each of the manor rooms. ( Again, maps would be nice here. ) Most of these traps are not remotely horrific or supernatural, and will either do one of two things.

  1. Kill the PC’s (Not horrific, just a death. It happens.)
  2. Not kill the PC’s (Also not horrific, they lived, why would it be horrifying?)

In addition the activation of ANY these traps more or less immediately gives away the identity of the murderer to any player/character. ( Because frankly, if I saw a set of stairs turn into a razor blade shredder, my assumption would not be “Hmm, it must be someone who doesn’t own the house” )

The conclusion of the module, a fight against the murder and the animated heart of the manor feels much better, and does a good job of hitting more of that horrific tone. The stat blocks for the manor heart itself are also pretty decent, and seem to have been well thought out. I would say that this conclusion/wrap up are overall the strongest parts of the module as written.

Overall, Moonveil Manor isn’t amazing, and it isn’t terrible. It’s all right, and I can imagine it slotting decently into another. I think the strongest parts of MMM are some of the fights, the few bits of flavor the module actually chooses to include, and the fact that it can most likely be slotted into almost any campaign very easily as a sort of one-shot/breather type game.

If I was to run it again, here’s what I would change up.

  1. Maps for each room. The lack of maps hurts, and I used some made by a friend who was the one who ran me through the first time. This is good, but it makes the whole house into one big things, instead of letting players really be in a location, where a lot of the module is based around encountering and exploring these rooms.
  2. Re-skin the traps. Given that they already give away the identity of the murderer, and the a lot of the flavor text is based around the house being this eldritch horror, I’d replace the sand pit with a gnashing mouth, the blunderbuss with whipping spikes, etc.
  3. Give the PC’s a reason to attend the party, other than “You were invited to a party”. I think this would encourage people to be a bit more interested in the house, and perhaps a bit more proactive about trying to solve things/protect the NPC’s.

Thanks for reading, and I’ll post more of these as I play em/run em.