A Void Drifters campaign is a situation, not a plot: a crew, a ship, a region, and a set of factions all moving at once. The GM's job is not to write the story but to keep the situation alive, responsive, and surprising. This chapter gives you the tools to do that across many sessions without the campaign losing momentum or the universe losing coherence.
The tools here are practical and fast. None of them require extended prep. The goal is a campaign that you can run session after session with confidence that the universe will keep generating material.
In This Chapter
- Session Zero: what to establish before the first session
- Fast NPC creation
- The ship as a character with history and problems
- Port dressing tables
- Encounter tables by zone type
- Campaign escalation: three arc tiers
- The between-session checklist
Session Zero
Session Zero is not character creation. Character creation can happen in session zero, but session zero's primary job is to establish enough shared context that the first session can start with momentum instead of setup.
The following checklist covers what you need to establish before session one.
The Crew's Reason for Being Together
The crew shares a ship. Why? This does not require elaborate backstory, but it needs at least a practical answer: they share a debt on the ship, they were hired together for a previous job, they inherited the ship from someone, they all ended up stranded at the same port and pooled resources. The reason does not need to be emotional. It needs to be functional.
If the players want deeper connection, they can develop it through play. What they need at session zero is a reason to stay in the same room.
The Starting Ship
Go around the table and establish the following together:
- Builder and model. Whose hull is it? A Model 20? A KR-41? An older Crown Meridian cutter acquired after military surplus? The builder establishes what the ship does well and what it does badly.
- The ship's best system. What is the one thing this ship does better than expected? It might be the Glarrion engine that was installed as an upgrade, or the nav suite that was swapped in from a Jerinna Systems component, or the cargo hold that was modified by a previous owner who knew exactly what they were doing.
- The ship's problem. What is wrong with it right now? Not catastrophically wrong, but persistently wrong: a heat management issue that makes the engineer's life difficult, a navigation calibration that keeps drifting, a docking interface that is three standards out of date. The problem is not there to punish the crew; it is there to give the engineer something to work on and to create texture.
- Who the ship owes to. Debt is almost universal. The ship has a mortgage, a lien, a salvage-title condition, or an obligation to a previous owner. The details live in the Vehicles Manual; what matters at session zero is the name of the entity the crew owes and the approximate shape of the obligation. The default is a high-hours Model 20 on standard terms: 122,500cr purchase, 10 percent down, and 2,756cr a month for ten years. The missed-payment ladder that puts the ship on the bounty boards is in Chapter Ten.
The Starting Position
Where is the crew at the beginning of the campaign? In the Meridian Verge context:
- Are they based at Port Meridian, or do they operate out of Harrowspan or Calder's World?
- Do they have existing relationships with any of the three powers present in the Verge, or are they unknown?
- Do any crew members have a prior relationship to the Verge that might be relevant?
Establish the starting position as specifically as possible. “Docked at Port Meridian, Unknown to all factions, with one lead on a potential first job” is a starting position. “Somewhere in space” is not.
The First Job Hook
Give the crew a job offer before session one ends. Do not force them to take it. Present it as a specific offer from a specific contact: name, faction alignment, what they want, and what they are paying. If the crew takes it, session one begins with the job in motion. If they negotiate, session one begins with the negotiation. If they refuse, find out what they want instead and use that as session one's frame.
The first job should be simple in structure: one goal, one route, one complication. Complexity accumulates through play. Session one's job should be completable in a single session if things go reasonably well.
Faction Relationship Starting Point
At session zero, establish each crew member's starting tier with the major factions. Most will start at Unknown. One or two crew members may have prior relationships with specific factions based on their backgrounds. Start with Known at most. Trusted at session zero requires a specific background reason.
NPC Creation Fast
A good NPC has four things: a role, a motivation, a leverage point, and one specific detail. Creating an NPC in two minutes means choosing one thing for each category.
Role
What function does this NPC serve in the current situation?
- Employer: Offers the job and holds the payment.
- Contact: The destination person, the local guide, the person who knows the thing.
- Obstacle: The checkpoint officer, the rival crew, the suspicious local authority.
- Asset: The mechanic, the informant, the ally who has something useful.
- Complication: The person who makes an already difficult situation harder without necessarily being hostile.
The role is the NPC's relationship to the crew's current situation, not their identity.
Motivation
What does this NPC want, right now, in this situation?
Good motivations are simple and personal. “Wants to be paid” is a motivation. “Wants to retire before her debt catches up with her” is a better motivation. “Wants to keep his clan's name out of the treaty court filing” is a specific motivation that can drive scenes.
Avoid motivation lists that require the crew to investigate before the NPC is interesting. The motivation should be apparent through normal interaction: it leaks out of the NPC's decisions and responses.
Leverage
What does this NPC have that the crew needs, and what does the NPC need that the crew could provide?
Leverage is not always pressure. It can be positive: the NPC has information, access, or a skill the crew needs. The leverage defines what kind of relationship is possible. An NPC with something the crew desperately needs and no particular need for the crew has a different relationship to them than an NPC who is mutually dependent.
The Specific Detail
One sensory or behavioral detail that makes the NPC feel real. Not their appearance in full, but one thing:
- “She apologizes for everything, even things that aren't her fault.”
- “He keeps his hands very still when he is lying.”
- “She speaks three languages in the same sentence when she is excited.”
- “He has a Funtari clan tattoo that stops at the collar, which means he left before finishing it.”
- “She remembers every ship she has ever seen and will mention this casually.”
The specific detail is the thing the players will remember. It is the detail that makes the NPC a person rather than a function.
NPC Roster
Keep a running roster of NPCs the crew has met, with a one-line note on each: role in the campaign, motivation, current relationship to the crew, and whether there is unfinished business.
| Name | Role | Motivation | Crew Relationship | Status |
|---|---|---|---|---|
| (name) | (role) | (motivation) | (Unknown / Known / Trusted / Owed / Burned) | (active / resolved / unresolved) |
Review the roster before each session. Unresolved NPCs are hooks. Burned relationships are incoming complications. Owed relationships are favors that will be collected.
The Ship as a Character
The crew's ship is the one constant across the campaign: the crew changes, relationships shift, ports come and go, but the ship is always there. Give it enough history that it feels like it has been somewhere before the crew arrived.
Ship History
A ship's history has five elements.
Builder and age. An older KR-41 hull from the Confederacy's frontier expansion era is a different object than a recent Model 20 from an Antaean commercial yard. Age affects what the ship looks like, what components it is likely to have, and what kind of maintenance history it carries.
Previous owners. At minimum one, ideally two. Previous owners leave traces: modifications that made sense for someone else's use, compartments that were clearly built for something specific, registry records that have been amended, relationships with factions that now extend to the current crew by association. Identify each previous owner with a name, a rough occupation, and one thing they left behind.
The ship's best system. What is it genuinely good at? Not every ship is good at everything. A ship that is fast and responsive in a chase but has a navigation suite that requires manual correction every four hours is more interesting than a ship that is adequately good at everything.
The ship's persistent problem. What requires ongoing management? Not a problem that will destroy the ship, but a problem that creates texture: the secondary docking coupling that jams in cold environments, the AI integration that runs hot after high-demand sequences, the cargo door seal that works fine until it doesn't.
A secret. Optional but recommended. Something the previous owner left that the crew may not have found: a hidden compartment, a modification that serves a purpose no one has identified yet, a registry flag that has never been explained, a component from a builder that should not be compatible with this hull but is running fine anyway. The secret does not need to be revealed. It exists to give the ship a sense of depth.
d10 Previous Ship Uses
| d10 | Previous Use |
|---|---|
| 1 | Mining survey vessel; carries trace mineral deposits in the cargo hold lining that could interest a corporate assay. |
| 2 | Medical transport; the clean-room compartment is still functional and occasionally attracts questions about what it was used for. |
| 3 | Impounded contraband carrier; released at auction with a registry flag that the previous owner's legal team never fully cleared. |
| 4 | Military surplus; decommissioned from a power's patrol fleet, which means the hull has hardpoint mountings that are technically not licensed for civilian use. |
| 5 | Stolen and recovered; the ship has a theft record in one power's system and a clear title in another's, because the recovery was done through irregular channels. |
| 6 | Inherited; the previous owner left it to someone who owed them a debt, and the chain of inheritance is murky enough that an old claimant might surface. |
| 7 | Long-haul freight; the ship has years of route records that represent a very complete picture of who was shipping what through several systems. |
| 8 | Courier; the previous owner was very careful about who they worked for, and the ship's transponder has three sets of registration codes in its memory. |
| 9 | Research vessel; Xenodyne Institute markings were painted over, but the specialized equipment mounts in the secondary bay are unmistakable to someone who knows what they are. |
| 10 | Rescue and salvage; the ship's crew roster still shows three names that have not been formally cleared from the registry, because the owners who filed those names are still looking for the ship. |
Port Dressing Tables
Every port the crew visits needs enough texture to feel like a real place. Use these tables to generate that texture in under a minute.
d10 Who Is at the Docking Bay
| d10 | Who Is There |
|---|---|
| 1 | A dockworker who is clearly doing two jobs and irritated about it. |
| 2 | A corporate rep in clean clothes who is waiting for a ship that is overdue. |
| 3 | A crew from another ship arguing about a fuel surcharge. |
| 4 | A checkpoint officer doing paperwork at a temporary desk, not inspecting anything yet. |
| 5 | A family with too much luggage and not enough credits for their actual destination. |
| 6 | A mechanic who does not work here but clearly knows where everything is. |
| 7 | A cargo handler asleep against a container who wakes up when the crew arrives. |
| 8 | A pilot from a Funtari-flagged ship watching the arrival berths without appearing to watch them. |
| 9 | A port authority official with a manifest discrepancy that involves someone else's ship, not the crew's. |
| 10 | No one. The bay is quiet in a way that is either scheduled maintenance or something else. |
d10 Current Port Atmosphere
| d10 | Atmosphere |
|---|---|
| 1 | Busy and impersonal. Everyone has somewhere to be and no one is interested in anyone else. |
| 2 | Tense. Something happened recently and the details are not being shared openly. |
| 3 | Relaxed. Whoever was causing problems has left or been resolved. |
| 4 | Watchful. An authority figure is present and people are behaving carefully. |
| 5 | Crowded. More ships in port than the docking schedule would suggest. |
| 6 | Quiet. The port is operating below normal traffic and the staff is either bored or worried. |
| 7 | Festive. A local calendar event, a religious occasion, or a commercial opening has drawn a crowd. |
| 8 | Transactional. Everyone is here to make a deal and the social niceties are minimal. |
| 9 | Anxious. A rumor is circulating that has not been confirmed and will not be confirmed. |
| 10 | Divided. Two groups are not speaking to each other and the crew has arrived in the middle of whatever this is. |
d10 Immediate Local Complication
| d10 | Complication |
|---|---|
| 1 | A berth the crew needed is occupied by a ship that will not be leaving when scheduled. |
| 2 | Fuel costs are above the rate the crew expected, and the port authority is not interested in negotiating. |
| 3 | A cargo the crew is delivering requires a signature from a contact who is not currently available. |
| 4 | The port's relay connection is running slow; anything time-sensitive will be delayed. |
| 5 | A checkpoint officer wants to inspect the crew's ship before clearing them for cargo operations. |
| 6 | A merchant approaches the crew with an offer before they have cleared the docking bay. |
| 7 | The port administrator has a notice about a previous incident involving the crew's ship registry. |
| 8 | Another crew in the same bay recognizes the ship from somewhere and wants to know something. |
| 9 | A repair the ship needs is available here but from a mechanic with a specific personal reputation. |
| 10 | The crew's contact at this port is not where they were supposed to be. |
d8 What the GM Can Overhear
| d8 | Overheard |
|---|---|
| 1 | Two dockworkers discussing a ship that came through last week with unusual cargo and an unusual crew. |
| 2 | A merchant complaining that a relay message they were waiting for never arrived. |
| 3 | A port authority officer on a comm saying that someone is asking about a specific ship registry. |
| 4 | A traveler telling another traveler that something changed at a checkpoint on the route the crew is planning to take. |
| 5 | A crew member from another ship saying that a job they just finished went wrong in a specific way. |
| 6 | A dockworker mentioning to another that a faction representative has been asking questions around the port. |
| 7 | Two merchants arguing about whether a specific route is still safe after something that happened recently. |
| 8 | Someone ordering a large amount of supplies that does not match the size of the ship they arrived on. |
Encounter Tables
These tables give you something to do with any space transit scene that is not a planned job beat. Not every encounter leads to a fight. Most should be complications, choices, or information.
Controlled Space: d10 Encounters
Controlled space has active patrol presence, functioning relays, and operating checkpoints. Encounters here are more likely to involve authority than pirates.
| d10 | Encounter |
|---|---|
| 1 | Routine patrol check: registry, manifest, destination. Nothing is wrong unless something is wrong. |
| 2 | A distress beacon from a ship that has suffered an engine failure. The ship's registry is an interesting flag. |
| 3 | A convoy of corporate freight with an escort that is clearly understaffed. Someone is watching them. |
| 4 | A relay maintenance crew doing work that has degraded communications in the area temporarily. |
| 5 | A checkpoint that has a longer queue than normal; an inspection is happening ahead for reasons the authority will not share. |
| 6 | An authority vessel on an intercept course that resolves without incident once papers are verified, but the officer asks one question too many. |
| 7 | A licensed passenger ship with a passenger who is clearly not traveling voluntarily. |
| 8 | A faction representative's personal courier who wants to send a message through the crew's next destination. |
| 9 | A patrol ship following a course that would take it directly through a route the crew was planning to use. |
| 10 | Two authority vessels from the same power but different departments, clearly not coordinating with each other. |
Fringe/Disputed Space: d10 Encounters
Fringe space has thin or inconsistent authority, unreliable relays, and opportunists of every kind.
| d10 | Encounter |
|---|---|
| 1 | A ship running without transponder that alters course when it sees the crew. |
| 2 | An independent salvager claiming priority on a debris field the crew was planning to use for cover. |
| 3 | A patrol from one power in a system that is technically neutral, running a checkpoint with no legal authority to do so. |
| 4 | A ship broadcasting a commercial offer: they have something to sell, they will not say what, and they prefer not to dock anywhere official. |
| 5 | A settlement on a nearby world sending an emergency signal that mentions a specific faction by name. |
| 6 | Two ships, clearly from competing factions, that have been watching each other without acting. The crew's arrival changes the balance. |
| 7 | A derelict that still has power and a life support signature. |
| 8 | A hired security escort operating in this space on behalf of a client the crew knows. |
| 9 | A ship that matches the description of one involved in a job the crew took, or declined, several sessions ago. |
| 10 | No ships, no signals, and a relay node that is offline. The silence itself is a complication on this route. |
Slipstream Transit: d8 Complications
Slipstream transit is not empty. The corridor is a compressed space with its own hazards.
| d8 | Complication |
|---|---|
| 1 | Phase turbulence from another ship's recent transit is still dissipating. The crew's transit will be rougher than normal. |
| 2 | A corridor saturation warning from a relay before entry; the corridor has seen unusual traffic. |
| 3 | A ship entered the corridor ahead of the crew and is running slower than the crew's drive can comfortably handle. |
| 4 | A navigation drift that will push the exit arc outside the planned emergence point. The navigator needs to compensate. |
| 5 | A signal fragment in the corridor: partial data from another ship that was in here recently and left something behind. |
| 6 | Drive wake heating is running higher than expected. The engineer needs to decide whether to manage it now or on exit. |
| 7 | The exit seam arc is narrower than the charts show. The pilot needs to thread it cleanly or the exit is rough. |
| 8 | Another ship exits the corridor ahead of the crew and is stopped, running no transponder, at the seam. |
Dead/Unclaimed Space: d10 Encounters
Dead space has no authority, no reliable relays, and no one who is supposed to be there. Everyone present is there for a reason they prefer not to explain.
| d10 | Encounter |
|---|---|
| 1 | A survey marker that does not match any current survey license. Someone has been here. |
| 2 | A wreck that is newer than the charts suggest anything large has passed through this space. |
| 3 | A hidden cache: supplies, components, or cargo that someone stored here and may still be coming back for. |
| 4 | A ship running with minimal power output, clearly trying not to be seen. |
| 5 | An automated relay running a repeating message that does not resolve into anything recognizable. |
| 6 | Evidence of recent habitation: a temporary structure, power traces, life support residue. No one is currently here. |
| 7 | A navigation hazard that the charts do not show: debris, an unstable mass, a seam anomaly. |
| 8 | A ship in trouble that did not come from any direction the crew can account for. |
| 9 | An active scanner hit from something that does not appear visually and does not respond to hailing. |
| 10 | Complete quiet, but the crew's sensors register they are being passively scanned from a source they cannot locate. |
A first arrival in an uncharted system uses the What Is Here table in Chapter Six instead; this table is for dead space someone has already been through.
Campaign Escalation
A Void Drifters campaign escalates naturally if you let faction clocks run and consequences accumulate. The crew starts as unknown operators in a complex situation and ends as a known force that factions calculate around. This escalation has three tiers.
Early Campaign: Sessions 1 through 4
The crew is finding its footing. They take jobs, accumulate contacts, and begin to understand the political texture of the Verge. At least one faction clock has activated. The crew has completed at least one job that changed their reputation with one faction.
GM focus at this tier:
- Keep jobs structurally simple. One goal, one route, one complication.
- Introduce faction signals early. The crew should see Directorate activity, Funtari presence, and Caliphal organization before they become directly entangled.
- Let consequences accumulate. Do not resolve them for the crew. Let a warrant sit, let a reputation ding linger, let a contact who was burned become a name in the NPC roster with “Burned” next to it.
- Establish the ship's problem. It should come up in at least one session before the campaign leaves the early tier.
Transition to mid: The crew has a reputation with at least two factions. At least one faction clock has reached step three or beyond. A consequence from an early session is still unresolved and has become relevant again.
Mid Campaign: Sessions 5 through 10
Faction clocks are activating. The crew's choices have visible consequences in the Verge. At least one major power has taken direct notice of the crew, either positively or negatively. The unresolved consequences from the early tier are now active complications.
GM focus at this tier:
- Run three or four clocks simultaneously. Use the interaction rules from Chapter Nine to let clocks respond to each other.
- Introduce corporate and organization clocks. The powers are not the only factions with goals.
- Let the crew's reputation create pressure. A crew that is Trusted with the Directorate will be approached by the Directorate with increasingly significant jobs. A crew that is Burned with the Confederacy will have Funtari-adjacent problems on every route through the Verge's western approaches.
- Escalate the consequences. A faction debt that was manageable in the early campaign is now overdue. The warrant that the crew ignored has propagated to a new power's systems.
Transition to late: The crew is Known to all three Verge powers and either Trusted or Burned with at least two of them. A faction clock has filled and the consequence is visible in the universe. At least one major NPC the crew has worked with or against has a specific agenda regarding the crew.
Late Campaign: Sessions 11 and Beyond
The crew is known. They have power, reputation, enemies, and obligations. Their choices have shaped the Verge in visible ways. Faction clocks that filled have changed the universe, and new clocks have opened in response. The powers are no longer just background pressure: they are responding to what the crew specifically has done.
GM focus at this tier:
- Let the consequences of filled clocks define the universe. The Directorate inspection post exists, or it doesn't. The Funtari salvage law is in effect, or it was stopped. The Verge looks different because of what the crew did and didn't do.
- Open arc-level clocks: goals that will take an entire sub-campaign to resolve. A power repositioning, a corporation making a major move, an organization reaching for something that could change the Verge permanently.
- Make the crew's position explicit. They have earned enemies with resources. Those enemies are no longer sending obstacles; they are sending responses calibrated to what the crew specifically can do.
- Keep jobs in the frame. Even a late-campaign crew needs work. The difference is that the jobs are now entangled with everything else. A simple delivery in sessions one through three is a simple delivery. A simple delivery in session twelve has a faction clock attached, a reputation consequence attached, and probably involves an NPC the crew has history with.
The Between-Session Checklist
Keep this checklist short. Void Drifters prep should not take more than thirty minutes per session after the campaign is established. The between-session checklist is the core of that prep.
1. Advance Faction Clocks
Look at each active clock. Apply the advancement rules from Chapter Nine. Note any changes.
- Which clocks advanced?
- Did any clock fill? If so, what has changed in the universe?
- Did any new clock open in response?
2. Update Reputation Trackers
Look at each major faction's tracker for the crew. Based on what happened last session:
- Did any tier shift?
- Is any faction now at Burned or Wanted? If so, what are the immediate consequences?
- Is any faction now at Owed? What might they ask for?
3. Review Unresolved Consequences
Look at the consequence list from the Jobs chapter. Which consequences from previous sessions are still active?
- Is any consequence overdue to become relevant again?
- Has enough time passed that a warrant should have propagated, or a debt come due?
4. Update the NPC Roster
Review the roster. Any NPC with “Unresolved” status is a hook.
- Is any unresolved NPC due to resurface based on what happened last session?
- Did any NPC's situation change because of a clock that advanced?
5. Prep the Next Job
Have one job ready before the session starts. It does not need to be detailed: a source, a goal, a route, and one complication. Use the Job Generator from Chapter Ten if nothing comes immediately to mind.
Ask: why is this job available now? What faction or consequence created the conditions for it?
6. Identify the Pressure
What is the crew's most pressing problem right now? Name it specifically. This is your session's anchor: whatever else happens, this pressure exists. The session does not need to resolve it, but it should be present.