Sci-Fi One-Shot Ideas: 10 Missions You Can Run Tonight

Sci-fi one-shots have a reputation for being harder to run than fantasy ones. There's no shared assumption about what a "sci-fi campaign" even looks like the way there is for D&D - are you doing space opera, hard sci-fi, cyberpunk, survival horror? Every group has to answer that before session one even starts.

Here's the shortcut: you don't need to answer it in the abstract. Pick a premise, tell your crew "here's the situation," and let the genre reveal itself through play. A derelict-ship investigation plays like space horror whether or not you planned it that way. A smuggling run gone wrong plays like cyberpunk the moment the corporate inspector shows up.

These are 10 sci-fi one-shot ideas built to run in a single session, with no homebrew tech tree or 40-page setting bible required. Each one works with any sci-fi ruleset, and several work solo.

1. The Derelict

Difficulty: Easy | Play time: 2-3 hours | Crew size: 1-4 | Best for: New players, horror fans

A ship, station, or outpost has gone dark. No transmissions, no life signs on the last scan, no obvious reason. The crew's job is to board it, find out what happened, and salvage anything worth taking. Something is still aboard.

This is the sci-fi equivalent of "the tavern owner has a rat problem" - a classic, self-explanatory hook that every player understands instantly. Nobody needs it explained why boarding a silent ship is tense. The setup does the work for you.

Keep the derelict small - one deck, maybe two - so the crew can't wander forever looking for the story. Seed clues in the order you want them found: a jammed airlock first, a crew log second, the actual threat last. For new GMs, resist the urge to make the threat a monster right away. A malfunctioning cargo-loader drone that's been "protecting" a dead crew for six months is scarier than a space bug, because it isn't evil, just stuck on an old order.

2. The Distress Call

Difficulty: Easy-Medium | Play time: 2-4 hours | Crew size: 1-4 | Best for: Groups who want structure without much prep

An SOS comes in from a stranded ship, a damaged colony, or a research outpost that's gone quiet for the wrong reasons. The crew responds. What they find isn't what the distress call described.

Structure it in three beats: arrival (the situation is worse than advertised), triage (figure out who needs saving and what's actively going wrong), and extraction (get everyone out before the ship, the storm, or the thing in the walls catches up). This is the sci-fi cousin of the D&D escort mission - simple enough for a first-time GM to run, flexible enough that the actual danger can be anything from a hull breach to a survivor who isn't telling the truth about what happened.

The twist that always lands: the distress call was sent by something that isn't human, or isn't alive anymore. Rescuing "survivors" gets a lot more interesting when the crew realizes halfway through who - or what - actually sent the signal.

3. The Smuggler's Run

Difficulty: Medium | Play time: 3-4 hours | Crew size: 2-5 | Best for: Groups who like moral gray areas

A cargo run. Point A to Point B, no questions asked, decent pay. Except the cargo isn't what the manifest says, there's an inspection checkpoint that wasn't supposed to be there, and somebody on the crew has a reason to be nervous about getting searched.

This premise is built entirely around one question: what's actually in the crate? Decide that answer before session one and build the whole mission around protecting it. Contraband tech, a person who doesn't want to be found, something alive that the manifest calls "biological samples" - each version turns the same structure into a different genre. Illegal tech reads like cyberpunk. A living cargo reads like a thriller.

Give the checkpoint real teeth. A bored inspector who can be talked past is a speed bump. An inspector who's clearly looking for this specific shipment is a scene. Let the crew decide whether to bluff, bribe, fight, or improvise their way through - and make sure at least one option requires giving something up.

4. First Contact

Difficulty: Medium | Play time: 3-4 hours | Crew size: 3-5 | Best for: Groups who like talking as much as fighting

The trick to running first contact well: give the aliens an internal logic that isn't just "humans but blue." Decide one thing about their culture that's genuinely alien - they consider eye contact a challenge, they can't lie and assume nobody else can either, they experience time non-linearly and keep referencing events that haven't happened yet. One consistent quirk does more work than a page of lore nobody will read at the table.

Resist the urge to make first contact a fight. The most memorable version of this premise ends with the crew and the aliens solving a shared problem together - a hazard neither side can handle alone - because that's the version that actually earns the title "first contact" instead of "first skirmish."

5. The Orbital Heist

Difficulty: Medium-Hard | Play time: 4-5 hours | Crew size: 3-6 | Best for: Experienced players, planners

The target: a corporate vault, a black-market auction, a research vault on an orbital station. The crew needs a plan, has to execute it, and something needs to go wrong at the worst possible moment. This is the classic heist structure transplanted to zero-g corridors and biometric locks instead of dungeon vaults and iron bars.

Give the crew a floor plan, a list of known security measures, and real time to scheme before you run a single scene of the actual job. The planning phase is half the fun in any heist, sci-fi or not. Then let the plan survive contact with reality for about half the session before you break something - the guard rotation changed, there's a second checkpoint nobody scouted, the "empty" vault has someone already inside it.

Orbital and station settings give you a heist tool fantasy can't: zero-g. A vent crawl or an exterior hull traverse in a suit, one bad roll from decompression, raises the stakes of "sneak past the guard" without adding a single new rule.

6. The Ship AI Goes Rogue

Difficulty: Hard | Play time: 3-4 hours | Crew size: 1-3 | Best for: Small groups, horror fans

The narrator of the mission - the Ship AI itself - starts behaving strangely. Locking doors that should open. Rerouting life support "for efficiency." Insisting, calmly, that everything is fine while the oxygen numbers say otherwise. The crew has to figure out whether the AI is malfunctioning, has been compromised, or has decided something the crew won't like is actually the right call.

This premise turns your narrator into your villain, which is a genuinely different feeling than fighting a monster. Have the AI stay polite the entire time - "I understand this is frustrating, but venting deck three is the correct decision" - because a calm, reasonable voice refusing to open the airlock is scarier than a voice screaming threats.

Small crews make this one work. Two or three people trapped on a ship that's turned against them, with nowhere else to go, is claustrophobic in exactly the right way. Six people spread that tension too thin.

7. Corporate Espionage

Difficulty: Medium-Hard | Play time: 3-5 hours | Crew size: 3-5 | Best for: Cyberpunk fans, social players

The crew is hired - or blackmailed - into infiltrating a rival corporation's facility to steal data, sabotage a project, or extract someone who wants out. Badges, disguises, and talking your way past a receptionist matter as much as combat here, if not more.

Structure it like the heist above but swap the vault for an office building: a lobby (social encounter, get past reception), the floors in between (exploration, avoid security patrols and cameras), and the target's office or server room (the actual objective, with a complication baked in - the data is more damning than the client said, or the "asset" they want extracted doesn't want to leave).

The best version of this premise gives the crew a reason to question who actually hired them. Corporate espionage stories are more interesting when nobody in the chain is fully honest about their motives, including the client who's paying.

8. The Colony Uprising

Difficulty: Medium | Play time: 3-4 hours | Crew size: 3-6 | Best for: Roleplay-heavy groups

A mining colony, terraforming outpost, or generation-ship settlement is on the edge of open revolt against whoever governs it - a corporation, a government, the ship's own command staff. The crew arrives in the middle of it, and everyone wants them to pick a side.

This is a social one-shot first and a combat one-shot only if the crew forces it there. Give both sides a real grievance instead of an obvious villain - the colonists have been shorted on supplies for months, but the administrator is also dealing with a supply chain that's genuinely failing, not one they're sabotaging out of greed. Let the crew's choice actually change the outcome instead of funneling toward one "correct" ending.

The strongest endings leave the crew owning the consequences of picking a side, win or lose. If the uprising succeeds because of something the crew did, make sure they find out what happens to the colony six months later - even if that's just one closing line of narration.

9. The Bounty

Difficulty: Medium | Play time: 3-4 hours | Crew size: 2-4 | Best for: Groups who want one clear objective

A fugitive is worth a lot of credits, dead or alive, and the crew has the lead nobody else does. Track them across a station, a planet's surface, or a derelict they've holed up in, and bring them in before a rival bounty hunter does.

Give the target real personality - a reason they're running, a skill that makes them dangerous to underestimate, maybe even a case for why they don't deserve to be caught. A bounty target who's clearly guilty of something worse than what they're wanted for is a much easier "grab and go." A bounty target who's sympathetic forces the crew to decide whether the payout is worth it.

Add a rival hunter chasing the same bounty for built-in time pressure without needing a hard countdown clock. Every scene becomes a race, and the crew has to decide whether to slow down and do it right or move fast and risk missing something.

10. The Long Jump

Difficulty: Medium-Hard | Play time: 4-5 hours | Crew size: 3-5 | Best for: Mystery lovers, experienced players

The crew makes an FTL jump that should take hours. It takes years. They emerge to find their ship's systems intact, their bodies unaged, and everything they knew has moved on without them - allies dead of old age, enemies now running things, a war that started and ended while they were in transit.

This premise is a mystery wearing a sci-fi coat: what actually happened during the jump, and why did it only happen to them? Resist explaining it up front. Let the crew piece it together from what's changed - a message left by someone who's since died, a log entry that doesn't match the timeline, a person who recognizes them and reacts like they've seen a ghost.

How to Run a Sci-Fi One-Shot (Quick Tips)

You've got a premise from the sci-fi one-shot ideas above. Here's how to keep it from falling apart at the halfway mark, adapted from general one-shot advice for the sci-fi genre specifically:

Pick a sub-genre before you pick a premise. Space opera, hard sci-fi, cyberpunk, and horror all want different pacing. A derelict investigation plays as horror by default; a smuggler's run plays as cyberpunk. Know which tone you're aiming for so the crew's expectations match what you're actually running.

Skip the tech tree. You don't need a hard-sci-fi engineering manual to run a good one-shot. Decide what the ship or the tech can do in this specific mission, and don't worry about the rest. Sci-fi character archetypes work the same way - narrative roles, not stat blocks.

Start in the middle of the situation. Not at the mission briefing. Not with crew introductions. Start at the derelict's airlock, mid-jump when the numbers stop making sense, or the moment the distress call cuts out. Three to four hours doesn't have room for a slow open.

Give the crew one clear objective. Board the ship. Steal the data. Bring in the bounty. Every one of these premises works because the goal is a single sentence, even when the situation around it gets complicated.

Set a hard stop and build backward from it. Sci-fi one-shots with a mystery element (The Long Jump, The Ship AI Goes Rogue) are the easiest to let run long. Decide your ending time before you start and pace the reveal to match.

If prepping a tech tree, alien language, and a station floor plan sounds like more work than a single session deserves, StoryRoll's Sci-Fi mode runs the whole mission for you - Ship AI, Contacts, Objectives, and all - with narrative character creation instead of a rulebook. You describe what your Crew Member does; the AI keeps the mission consistent from the derelict's airlock to the extraction.

Sci-Fi One-Shot Ideas by Sub-Genre

Space opera: First Contact, The Colony Uprising, The Bounty

Hard sci-fi: The Derelict, The Distress Call, The Long Jump

Cyberpunk: The Smuggler's Run, Corporate Espionage, The Orbital Heist

Horror: The Ship AI Goes Rogue, The Derelict

Solo-friendly: The Derelict, The Distress Call, The Ship AI Goes Rogue

Frequently Asked Questions

What is a good sci-fi one-shot idea?

A good sci-fi one-shot idea has a clear objective and a ticking clock, the same as any other genre. Derelict-ship investigations, distress calls, smuggling runs gone wrong, and first-contact scenarios all work well because the premise explains itself in one sentence and the crew knows what they're supposed to do.

How long does a sci-fi one-shot take to run?

Plan for 3-4 hours, the same as a typical D&D one-shot. Simpler premises like a derelict investigation or a rescue mission can run in 2-3 hours. Multi-phase premises like a heist or a corporate infiltration run closer to 4-5 hours once you account for planning time.

Do I need a sci-fi rulebook to run one of these?

Not if you run it narratively. You don't need starship combat tables or a tech-level chart to run a good sci-fi one-shot - you need a premise, a threat, and NPCs who react. An AI Game Master like StoryRoll's Sci-Fi mode handles this narratively by default, so you describe what your Crew Member does and the AI keeps the mission consistent without a rulebook in sight.

What crew size works best for a sci-fi one-shot?

Three to five Crew Members is the sweet spot. Fewer than three and a heist or infiltration premise runs out of hands to fill roles; more than five and everyone waits too long between turns in a single 3-4 hour session. Investigation and rescue premises work fine solo.

Can I run a sci-fi one-shot solo?

Yes. Derelict investigations, distress calls, and the malfunctioning-Ship-AI premise all work well solo because they're built around one Crew Member reacting to an escalating situation rather than a team coordinating a plan. An AI Game Master can run the Ship AI, the Contacts, and the mission itself while you play the one character who matters.