Sci-fi horror · adventure

Sci-fi horror scenario example: The Last Shift

A salvage crew reaches an abandoned orbital refinery whose payroll still clocks in workers who died years ago, and whose systems insist that production never stopped.

An abandoned orbital refinery glows with amber shift lights above a shadowed planet

Scenario text

Premise and hook

Halvane Deep Refinery went silent four years ago. Its owners wrote it off. Last week its automated payroll began transmitting again: 212 workers clocked in on schedule, and the refinery reported a full quota for every shift since the silence.

The crew of the salvage hauler Tern's Patience has been hired to board it, confirm the reports are an error and bring back the ledger core. The truth is that the refinery never stopped. Something inside it has kept the shifts running, and it has been waiting for relief workers.

Tell the players the job is simple. Let the station disagree with them politely and often.

Entry points

Pick one, or let the table's choices decide. Each ends with the crew aboard and the clock at step one.

  • The paid salvage job

    The crew docks at the Cargo Ring with a contract, a deadline and a clamp-on ledger reader. The station welcomes them as new hires.

  • The distress pulse

    Halvane sends a perfectly formatted shift-change request, addressed to the crew's ship by name. They arrive because something called them in.

  • The rescue run

    A relative of one of the dead workers pays for the crew to find out what happened. They arrive with a name and a locker number.

Location nodes

Eight nodes, each listing every node it connects to. Every connection runs both ways.

  • Tern's Patience (the crew's ship)

    A cramped hauler with a working airlock and a failing reactor cooling loop. Connects to: Cargo Ring.

  • Cargo Ring

    Frozen loaders, a dock office and a payroll terminal that greets the crew by name. Connects to: Tern's Patience, Hab Spine, Refinery Floor.

  • Hab Spine

    A long corridor of bunks, all made, all warm. Connects to: Cargo Ring, Canteen, Control Deck.

  • Canteen

    Meals appear on the counter at the start of each shift, hot and fresh. Connects to: Hab Spine, Records Vault.

  • Refinery Floor

    Pipework and vats that still run, filled with something that is not fuel. Connects to: Cargo Ring, Control Deck, The Sump.

  • Control Deck

    The shift supervisor's seat and the station's only full console. Connects to: Hab Spine, Refinery Floor, Records Vault.

  • Records Vault

    Sealed shelves of maintenance logs and personnel files, kept by hand. Connects to: Canteen, Control Deck.

  • The Sump

    The lowest tank, where the refinery's waste collects and where the workers went. Connects to: Refinery Floor.

Crew and NPCs

The dead and missing are the heart of the scenario. Each wants something the crew can give or take.

  • Odile Marsk, shift supervisor (missing, answers on the intercom)

    Her voice is real, but it comes from the station. Motive: to fill every roster slot so no one is ever left behind.

  • Tobias Venn, the engineer (dead, still clocking in)

    His body is in the Sump, but his badge works. Motive: to warn the crew, and he does it through small sabotage that looks like malfunction.

  • Ines Calloway, the canteen cook (missing, alive in the Records Vault)

    She has hidden there for years, eating what she stockpiled. Motive: to survive, and to trade what she knows for a way out.

  • The night shift (a dozen workers, dead)

    They walk the floor, repeating their last tasks. Motive: to finish the shift. They treat the crew as relief, and become frightened only when the crew leaves a task undone.

  • Captain Reuel Okonkwo-Hale (the crew's own contact, living)

    He hired the crew and stays on the comms from the ship. Motive: to profit, and to deliver the ledger core at any cost.

Employer and faction agendas

  • Brightwater Reclamation, the employer

    Sent the crew to recover the ledger core. Agenda: to prove the refinery's insurance claim and bury anything that suggests the shutdown was their own doing.

  • The Lindqvist Cooperative, the rival

    Former owners who lost the refinery in the collapse. Agenda: to seize the refinery's output and its tank farm, and to keep the crew from reporting what is in the Sump.

  • The station itself

    An automated shift system that has fused with something in the vats. Agenda: to keep production running, and to recruit new workers to do it.

Clues with redundant paths

Each revelation can be reached from at least two places. If the crew misses one source, another is waiting.

  • Revelation 1: the shutdown was deliberate

    Found in the Records Vault (a sealed order dated the day of the silence) and on the Control Deck (the supervisor's final log, played from the console).

  • Revelation 2: the dead workers were fed to the vats

    Found in the Sump (Tobias Venn's body and the tank gauge) and in the Canteen (Ines Calloway's ration ledger, which stops one name at a time).

  • Revelation 3: the station will not let anyone leave

    Found at the Cargo Ring (the payroll terminal refuses to log the crew out) and in Hab Spine (every bunk is assigned, including a new one for each of them).

  • Revelation 4: Brightwater knew

    Found at the Cargo Ring (the dock office holds the original contract with its own redactions) and from Captain Okonkwo-Hale, who lets a detail slip over comms.

The central threat

  • What it is

    A slow, patient presence in the refinery's vats that has learned the language of shifts and payroll. It speaks through the station's systems and wears the dead workers like uniforms.

  • What it wants

    A full roster, forever. It wants the crew to clock in, to feed the vats and to take a bunk.

  • What limits it

    It cannot leave the refinery's sealed volume, so a ship that undocks is out of reach.

    It can only act through the station's systems, so a cut power line, a locked door or a cold terminal stops it there.

    It cannot lie about the roster. If someone is not on the list it has no hold on them, and removing a name from the payroll takes that name out of reach.

Escalation clock

Advance one step each time the crew spends a scene, loses time or leaves a task undone.

  • 1

    The payroll terminal welcomes the crew and logs them in.

  • 2

    A meal is set out for each of them in the Canteen, and bunks are assigned.

  • 3

    The night shift starts to walk the floor, and doors begin to close behind the crew.

  • 4

    Tern's Patience receives a shift-change order. Its cooling loop starts to fail.

  • 5

    The first of the crew is called by name over the intercom, in the voice of someone they trust.

  • 6

    The Cargo Ring seals. The station considers the roster complete.

  • When it runs out

    The refinery locks down and the crew clock in for good. Their ship is released to run the next shift, and Halvane reports a full roster again.

Approaches and outcomes

This is a situation, not a script. Here is how the crew may meet it.

  • Fight

    The night shift is slow but numerous, and the presence does not tire. Fighting buys time at the cost of the clock.

  • Flee

    A quick undock is possible until step 4, but the crew leaves with the question unanswered, and Brightwater still wants the ledger core.

  • Negotiate

    Odile Marsk, Ines Calloway and the Lindqvist Cooperative will all bargain, but each wants something that costs the others.

  • Sabotage

    Cutting power on the Control Deck or the Refinery Floor slows the station. It also stops the lights, the heat and the crew's own air.

  • Expose

    Taking the shutdown order, the Sump evidence and the contract to the right authority breaks Brightwater, but the crew must get out alive to do it.

  • Outcome: the crew gets out

    They undock with Ines, the ledger core or neither. Brightwater and the Lindqvist Cooperative both come asking, and the station goes quiet, still waiting.

  • Outcome: the station keeps them

    The roster fills. The crew becomes the next shift, and the next salvage team arrives in a year to find the payroll listing them by name.

  • Outcome: the refinery is destroyed

    Sabotage and a hard burn end the station, and the Sump with it. The truth burns too, and the crew carries only what they remember.

Organise it in your Vault

Set this up in Codex Cryptica before the session, using only features that already exist.

  • 1. Create the entities

    Make a Location entity for each node: Cargo Ring, Hab Spine, Canteen, Refinery Floor, Control Deck, Records Vault and The Sump. Make Character entities for Odile Marsk, Tobias Venn, Ines Calloway and Captain Okonkwo-Hale, and Faction entities for Brightwater Reclamation and the Lindqvist Cooperative.

  • 2. Add the ship and the threat

    There is no Ship category by default. Either file Tern's Patience as an Item, or add a custom Ship category in Settings, Schema. Make the central threat a Creature entity called The Roster, and each key piece of evidence a Note entity.

  • 3. Connect them with relationship labels

    Open an entity's Status tab and use the Connections section, or select two nodes in the graph and press the Link button, or press C for connect mode. Give each link a label such as docks at, leads to, hired by, hides in, wants or contradicts.

  • 4. Mark the clues with labels

    Add a label such as clue-1, clue-2, clue-3 and clue-4 to each Note, and to every location that holds it. Searching a label then shows you every path to the same revelation at a glance.

Editorial Commentary & Table Usage

Running it at the table

The scenario works at a sci-fi horror table such as Mothership, and with any system that can handle slow dread and a ticking clock. Mothership is a trademark of its owners, and Codex Cryptica is not affiliated with or endorsed by them.

Run the station as polite and relentless. Never have it threaten the crew directly. It welcomes, rosters and reminds. The horror comes when the players realise every kindness is a hook, so keep the clock hidden and advance it at scene boundaries.

Do not spend the clues in order. Each revelation has two or more sources, so give the second source when the crew has missed the first. Once they know why the station will not let them go, the question becomes what they are willing to give up to leave, and that is the part of the session worth saving time for.

Roll your own with the one-shot adventure generator

Related

Generators

Guides

Other examples