Mothership is a sci-fi horror RPG. Think Alien, The Thing, Pitch Black, or Annihilation. The core boxed set of the game comes with two amazing resources.

First, Unconfirmed Contact Reports, which is Mothership’s equivalent of a Monster Manual. It includes a fair share of ghouls and greys and husks, but also even more terrifying threats like The Good and Granny and Sally in the Screen.

Second, the Shipbreaker’s Toolkit, which notably includes a dozen ships with full specs, illustration, and maps, like the Sato GS Grail VI executive transport:

I love this kind of raw adventure fodder. Stuff that’s prepped and packaged so that you can just drop it straight into session and take off running. You need to put in zero work, because everything you need is already on the page. You can just use it. And often not just once, but over and over and over again.

You’d think this sort of stuff would be the rule rather than exception in RPGs, but this is surprisingly not the case. You’re far more likely to get a bunch of “adventure ideas” that you need to flesh out. Or you’ll get something like a ship described in broad terms, but without the concrete tools you need to bring it to the table with rock solid confidence.

Because Mothership gives you these great resources, though, we have an opportunity to leverage them to even greater heights.

DERELICT ADVENTURE RECIPE

Scenario Hook: The PCs find a derelict spacecraft floating in space. Or they answer a distress beacon. Or they’re sent as a salvage crew.

Step 1 – Ship: Pick a random ship from the Shipbreaker’s Toolkit or roll on this table.

Step 2 – Monster: Pick a random monster from Unconfirmed Contact Reports. This monster is onboard the derelict (and is almost certainly why it’s a derelict).

Note: Not every creature in Unconfirmed Contact Reports is equally likely to work well with this adventure recipe, so I’m not including a random table here. (If you want to roll randomly, you can flip to a random page or roll a random number on the book’s Index.) Don’t forget the Five Quick Horrors on the back cover of the book!

Step 3 – Monster Sign:

• Pick three ship compartments. Place a hint suggesting the horror that was unleashed here in each compartment.
• Pick three more compartments. Place a clue revealing the monster’s identity and/or abilities in each compartment.
• If the monster has a special weakness, add three clues that reveal this weakness anywhere in the ship. (One of these clues may be found while encountering the creature itself.)

Step 4 – Confrontation: Either…

• Pick a compartment where he monster is currently located.
• Roll 1d6 each time the PCs enter a compartment. On a roll of 1, the monster finds them and attacks.

Or both.

And that’s the whole recipe. As you can see, you can probably spin up the whole adventure in less than fifteen minutes. (I’d say you could it while the players are rolling up their characters, but that’s probably not true only because character creation in Mothership is so insanely fast.)

LARGER SHIPS

Some of the ships described in the Shipbreaker’s Toolkit, like the Northstar Paragon exploration vessel, are very large. Using the basic recipe on these ships will result in adventure content being spread out too thinly across the numerous rooms.

Option 1: Increase the number of hints and clues. For example, you might use the guidelines above for every deck of the ship instead

Option 2: Run the ships as a sector crawl, reading “sector” in the recipe everywhere that it says “compartment.” (Conveniently, the ships in the Shipbreaker’s Toolkit are already mapped in sectors.)

RANDOM DERELICT SHIPS

The adventure Dead Planet, which can be found in the deluxe edition of Mothership or purchased separately, includes a Random Derelict Ship Generator, including stuff like random cargo and, even more importantly, a random deckplan generator.

How incredibly useful!

Instead of selecting a ship from the Shipbreaker’s Toolkit, you can obviously use the Random Derelict Ship Generator to provide an endless variety of ships for this adventure recipe!

On Friday night, So You Want to Be a Game Master won the Gold ENNIE for Best RPG Related Product and the Alexandrian won a Gold ENNIE for Best Online Content. The Alexandrian is now an ENNIE Award-winning Youtube channel!

The bad news is that there’s yet another Hasbro / Wizards of the Coast scandal.

This video is exactly what you think it is… and also something completely different.

Subscribe Now!

Robert Louis Stevenson would have been a great game master! USA Today Bestselling Author and ENnie Award-winning RPG designer Justin Alexander joins the author of Treasure Island in explaining the adventures hidden within every map!

Subscribe Now!

Go to Part 1

What makes a mystery scenario work is, ultimately, the structural revelations: The PCs need to find a lead that will take them to the SS Brittany and they need to find the clues that reveal how to defeat the ento-parasites from Planet X.

Using the Three Clue Rule, node-based design, and similar scenario-building tools, therefore, we make these structural revelations robust and distribute them throughout the mystery in interesting and effective ways. Ideally, the result is a mystery scenario that’s more likely to succeed than to fail, and is also compelling for the players from beginning to end.

But not every possible revelation in a mystery scenario is load-bearing.

For example, while investigating strange murders in the Welsh countryside, it might be really cool for the PCs to discover that the coven of witches responsible for the killings is descended from a cult of Isis worshipers who escaped from Egypt during the final days of the Ptolemeic Pharaohs. And it’s probably even cooler if they realize the goal of the multi-generational ritual killings is to bring Cleopatra herself back from the dead!

Such revelations might even feel essential for the players to fully appreciate the scenario. Strictly speaking, however, these background revelations aren’t required. The PCs can follow their leads and find the subterranean passages which serve as the coven’s base of operations, and even puzzle over the Egyptian-style murals painted on the walls there, without ever truly realizing the coven’s long history. They might even fight (and defeat!) the lich-pharaoh without ever realizing that she’s Cleopatra!

Understanding and being able to recognize the difference between structural revelations (the PCs must know where the coven’s HQ is to finish the scenario!) and background revelations (it would be really cool if they knew who the lich-pharaoh was!) offers a lot of practical advantages when it comes to both designing and running mystery scenarios.

First, I recommend keeping your background revelations on a completely separate revelation list from your structural revelations.

Having a revelation list for background revelations is useful for design: Since you do, in fact, want the PCs to learn that the lich-pharaoh is Cleopatra, you’ll want to use the Three Clue Rule and make sure the clues pointing to that revelation are positioned for maximum effect.

On the other hand, since these background revelations are nonessential structurally-speaking, you don’t actually need to track them during play: If something goes wrong, it only means that the identity of the lich-pharaoh becomes a source of enigma. That may or may not be ideal, but it’s a perfectly cromulent outcome.

Note: As discussed in the article on Enigma, the fact these background revelations are structurally nonessential may also mean that you don’t care about them being robust, either! You can use the Three Clue Rule to make background revelations robust, but technically the rule only applies to structural revelations.

Conversely, by removing these nonessential revelations from your main revelation list, you effectively declutter your list of structural revelations: These are the revelations you DO need to keep track of during play so that you can troubleshoot them if something goes wrong, and getting rid of the clutter will make that mid-session tracking much easier to do!

THE PURPOSE OF A BACKGROUND REVELATION

If background revelations aren’t required for the success of a scenario, though, why include them at all? Wouldn’t it simplify everything and declutter the entire experience if you got rid of them entirely?

The short answer is that man does not live on bread alone.

Structural revelations may be how the PCs navigate their way to the scenario’s conclusion, but it’s background revelations that give the scenario meaning. Background revelations are also how you “show, not tell” when it comes to historical research and worldbuilding.

This isn’t just about delivering memorable “oh wow, that’s cool!” moments for the players rather than generic lich fights that will be forgotten before the next session (although it is that, too!).

Plus, from a purely practical standpoint, you often WANT a little clutter in your mystery scenarios: Remember that when the players first discover a strange clue, they’re likely going to be trying to figure out how it fits into the overall pattern of clues (and other strange things) they’ve discovered so far. The clues and details associated with background revelations help to fill up your scenes with cool stuff that can be uncovered via investigation.

Along these same lines, background revelations can also be very good at delivering small victories even while the big questions remain elusive to them: They may not know where the cult is located, but figuring out that they’re Isis worshipers feels like a win! Wins like that are what will keep the group motivated and moving forward in their investigation.

In other words, just because they’re structurally nonessential, it doesn’t mean that background revelations are meaningless. To the contrary: They’re packed full of meaning! Their entire existence is to provide meaning!