Mothership RPG Explained: Running Sci-Fi Horror with Minimal Prep

Mothership RPG is a rules-light sci-fi horror TTRPG built for the kind of sessions where the air recyclers fail, the comms crackle, and someone realizes the cargo is breathing. It aims for quick character creation, fast rulings at the table, and pressure that escalates without needing a 40-page plot.

Advanced RPGs has covered plenty of systems that shine through crunchy options, deep setting bibles, or tactical subsystems. Mothership RPG goes the other direction. It treats procedure as the content. Stress rises, panic hits, resources run low, and the group makes ugly choices under time pressure.

A concrete picture helps. Imagine a salvage crew boards a derelict research ship. The lights are out. The ship’s AI repeats the same three words on loop. Nobody needs a lore lecture to feel the problem. Mothership RPG is designed to start there and keep moving.

What Makes Mothership RPG Distinct on the Table

Most sci-fi games ask, “What can your character do?” Mothership RPG asks, “How long can your character keep it together?” The rules focus on failure states, stress accumulation, and the cascading consequences of bad information.

The big distinction is pacing. Many systems reward careful optimization and long-term competence. Mothership RPG rewards clear decisions under uncertainty. The math stays light, but the outcomes stay sharp.

Example: a marine tries to cut open a sealed lab door. In a heavier system, the table may look up breach charges, structural integrity, and a long equipment list. In Mothership RPG, the GM calls for a roll, stress ticks up because the corridor is too quiet, and the door finally opens onto a room that smells like pennies and hot plastic. The scene lands because the procedure pushes it forward.

A Brief History of Mothership RPG (and Why Sci-Fi Horror Fits)

Mothership RPG grew out of the modern OSR-adjacent wave that values speed, high stakes, and strong adventure modules. Tuesday Knight Games published it with a clear goal: make sci-fi horror easy to run and easy to write for.

It also arrived at a moment when sci-fi horror had fresh mainstream oxygen again. The lineage is obvious even when nobody names it: Alien’s industrial dread, Event Horizon’s cosmic wrongness, and the “blue-collar space” tone where duct tape matters as much as bravery.

Example: a character wants to “scan for life signs.” In many sci-fi settings, that becomes a clean answer. In Mothership RPG, a scan can be a trap. It can return a number that does not make sense. It can show life in the walls. The system’s tone supports that kind of result without the GM having to fight the rules.

Mothership RPG vs. the Expanse (Books, TV, and TTRPG)

The Expanse novels and TV show lean hard on physics, politics, and cascading consequences. The horror exists, but it is often tied to scale: protomolecule outbreaks, existential threats, and systems-level collapse. The Expanse TTRPG supports that with character-driven drama, social mechanics, and a campaign structure that can follow crews across factions and years.

Mothership RPG sits closer to the episode where the crew is trapped in a single location and the problem is immediate. It is less interested in interplanetary diplomacy and more interested in whether the air is breathable for the next 20 minutes.

That difference shows up in play.

Example: a Belter medic in The Expanse TTRPG can build relationships, pull favors, and navigate a faction web. In Mothership RPG, the medic is deciding whether to spend the last dose of antibiotics on the engineer with a fever or the captain with a bite that is “probably fine.” Both are good sci-fi. They just aim at different emotional targets.

If a table wants political maneuvering, long arcs, and the slow burn of alliances, The Expanse TTRPG is a better fit. If a table wants a tight scenario where the ship is a pressure cooker, Mothership RPG is the faster route.

The Core Gameplay Loop: Stress, Panic, and Survival

Mothership RPG revolves around a simple loop.

Characters enter a dangerous situation. They take stress from fear, injury, isolation, and hard choices. Stress makes panic more likely. Panic creates complications that feed back into the danger.

The best part is that the loop is visible. Players can feel the dial turning.

Example: the android finds a frozen body in a maintenance shaft. The crew argues about whether to report it. The argument costs time. The ship’s temperature drops. Stress rises because the environment is hostile. A later roll fails, panic triggers, and the character bolts down the wrong hallway, slamming a bulkhead behind them. Nobody forced that outcome. The system made it plausible.

A practical GM habit helps here. Track stress openly. Keep the numbers on the table. When stress climbs, players start making different choices, and that is where the horror lives.

What Characters Do Session to Session

Mothership RPG characters tend to have simple, readable goals: survive, get paid, keep the ship running, and get home without bringing anything back.

Session to session, play often looks like this:

• Take a job (salvage, escort, retrieval, quarantine).

• Enter a location (ship, station, outpost, asteroid facility).

• Investigate and improvise solutions under pressure.

• Spend resources (ammo, oxygen, time, trust).

• Escape, or fail to.

Even in a short arc, characters change because the stress economy changes them. They pick up injuries, trauma, debts, and grudges. Those are campaign fuel without needing an epic metaplot.

Example: after a one-shot on a mining rig, the crew limps out with a single crate of recovered ore and a dead teammate. In the next session, the company offers hazard pay to go back for the missing data core. The crew takes the job because they need the money, and because the panic table result last time left one survivor convinced the rig is “calling.” That is a campaign hook born from play, not from a prewritten chapter.

Why Mothership RPG Excels at One-Shots and Short Arcs

Mothership RPG works best when the situation is contained and the stakes are personal. One-shots thrive because character creation is quick and the system does not require a slow ramp to competence.

Short arcs thrive because consequences stack cleanly. A crew can survive scenario one, carry scars into scenario two, and fall apart by scenario three. That arc feels earned, and it fits the genre.

Example: run three connected jobs.

1. A distress call on a medical shuttle.

2. A quarantine inspection on a frontier station.

3. A black-site retrieval where the employer lies about what is in the crate.

By the third session, the group has enough history to feel the dread, and not enough power to feel safe.

What a GM Needs to Prep (and What Can Wait)

Minimal prep does not mean no prep. Mothership RPG runs smoothly when the GM prepares four things: a ship or location, a problem, a countdown, and a few NPCs.

Ship or Location: A Map That Creates Decisions

A good location has choke points, blind corners, and at least one area players will avoid until they have to go there.

Example: a small research vessel with five key zones.

• Docking ring (easy entry, easy ambush)

• Crew quarters (personal clues, locked footlockers)

• Lab (the “why” of the horror)

• Engineering (power, heat, and noise)

• Cargo bay (big space, bad sightlines)

A sketch is enough. Label doors, vents, and any place where sound carries.

A Problem: Something That Cannot Be Solved Cleanly

The problem should force trade-offs. “Kill the monster” is fine, but “kill the monster without venting the ship” is better.

Example: the ship’s reactor is overheating and the coolant is contaminated. Fixing it requires entering a maintenance tube where something has nested. The crew can shut the reactor down, but that kills life support in 30 minutes.

A Countdown: The Engine of Pacing

A countdown keeps the session from turning into endless caution. It also prevents railroading because the pressure comes from the environment, not from the GM’s hand.

Example: a six-step countdown.

1. Power fluctuations begin.

2. Internal doors lock on a timer.

3. Comms degrade; only short-range works.

4. Temperature drops; frost forms in corridors.

5. The ship initiates an automated purge.

6. Hard reset: lights out, gravity off, panic everywhere.

Advance the countdown when the crew wastes time, makes noise, or triggers security systems. Say it out loud when it advances. The table should feel the clock.

A Few NPCs: Two Useful, One Dangerous, One Unreliable

NPCs in Mothership RPG work best when they are simple and actionable.

Example set for a station scenario.

• Chief Engineer Rina Kwon: wants power restored, will trade access for help.

• Dockmaster Hale: wants the crew gone fast, knows more than he admits.

• Corporate Auditor Velez: dangerous because of authority, not because of a gun.

• Security Drone “MILO”: unreliable because it is running an outdated threat profile.

Give each NPC one desire and one secret. That is enough to generate scenes.

Practical GM Tips for Tone, Pacing, and Player Fear

Tone in Mothership RPG comes from details that imply a world, then refuse to explain it fully. Pacing comes from alternating quiet investigation with sharp consequences. Fear comes from agency under pressure, not from forced outcomes.

Use Concrete Sensory Details, Then Stop Talking

A GM does not need purple prose. One strong detail lands harder than five vague ones.

Example: “The medbay smells like antiseptic and burnt hair. The autoclave is running with no power.” Then wait. Players will fill the silence with questions, and those questions create momentum.

Cut on Decisions, Not on Travel

If the crew debates for five minutes, cut to the moment after the decision.

Example: after arguing about splitting up, cut to the engineer alone in the crawlspace, hearing a slow tapping that matches their breathing. The cut respects the choice and speeds the session.

Make Failure Complicate, Not Stall

A failed roll should change the situation. It should not create a dead end.

Example: a failed hacking attempt opens the door, but triggers a quarantine alarm and seals the corridor behind the crew. The story moves, and the cost is real.

Handle Player Fear without Railroading

Horror tables sometimes drift into “the GM controls the scare.” Mothership RPG works better when players steer into danger for understandable reasons.

Use three tools.

1. Clear stakes: describe what happens if the crew does nothing.

2. Meaningful options: give at least two approaches, each with a cost.

3. Honest consequences: follow through when they choose.

Example: the crew hears movement in the vents.

• Option A: seal the vents, which reduces airflow and raises CO₂ levels.

• Option B: send someone into the vent system to check, which is faster and much worse.

Either choice is player-driven. The fear comes from owning it.

Who Mothership RPG Is Best For

Mothership RPG fits groups that want fast setup, high tension, and scenarios that end with a clean scar on the character sheet.

It is a strong pick for:

• GMs who prefer situations over plots.

• Players who enjoy problem-solving under stress.

• Tables that like horror that is grounded in logistics: air, light, doors, and time.

It is a weaker fit for:

• Groups that want long political campaigns with stable power growth.

• Players who dislike their characters breaking down under pressure.

Example: if a group loves The Expanse for its faction chess and slow-burn relationships, Mothership RPG can still work, but it will feel like a bottle episode where the ship is the antagonist.

A Simple First-Session Outline You Can Run Tonight

This outline is built to fit a 3–4 hour session. It uses the same prep structure: location, problem, countdown, NPCs.

Scene 1: The Job Offer (10 Minutes)

Give the crew a clear contract and a reason to accept.

Example: “Recover a black box from the cargo hauler Hesperus. Bonus pay if the ship is returned intact. No questions.”

Hand them one printed page: the contract, a docking code, and a grainy photo of the ship.

Scene 2: Docking and First Clue (20 Minutes)

Start with a sensory detail and a small complication.

Example: the airlock cycles, but the inner door is welded shut from the inside. A thin line of dried blood runs under the seam.

Let them choose how to enter. Advance the countdown when they make noise.

Scene 3: The Investigation Loop (60–90 Minutes)

Rotate through three zones and seed three clues.

Example clues.

• Crew quarters: a log mentioning “specimen transfer.”

• Engineering: coolant tanks replaced with something that looks like resin.

• Lab: a broken containment unit with claw marks on the inside.

Keep stress moving. If the table stalls, advance the countdown and show a new consequence.

Scene 4: The First Panic (20 Minutes)

Aim for a moment where stress pays off.

Example: a character fails a check while trying to pull a body out of a locker. Panic triggers, and they scream, alerting whatever is in the vents.

Do not script the monster’s entrance. Script the pressure. The creature can arrive when the countdown says it makes sense.

Scene 5: The Choice Point (30 Minutes)

Offer an objective that conflicts with survival.

Example: the black box is in the cargo bay, but the bay doors are jammed and the manual release is inside the vent network.

Make the options clear. Let the crew argue. Advance the countdown once during the argument.

Scene 6: Escape or Containment (30–45 Minutes)

End with a decisive sequence.

Example: the crew can vent the bay to space to flush the threat, but that risks destroying the black box and voiding their pay. If they keep the ship intact, they need to lure the creature into a sealed zone and lock it down.

When the session ends, give one concrete aftermath detail.

Example: “Back on the dock, the crew’s suits smell faintly of antiseptic. The station’s customs scanner flags an unknown organic residue.”

That last line is a sequel hook if the table wants a short arc, and it is also a clean full stop if they do not.