Running Void Drifters

This chapter covers the GM's operating philosophy and core procedures for running Void Drifters specifically. Not generic GM advice, and not a restatement of the Core Rules. These are the techniques and tools that make this Universe work at the table.

Each procedure in this chapter follows the same structure: trigger (when to use it), GM decision point (what you decide), player-facing signal (what the players see and know), mechanical handling (how to resolve it), consequence (what changes), and recovery or off-ramp (how the situation can improve or be escaped).

The Pressure Model

Void Drifters does not run on a main quest. It runs on overlapping pressure sources.

The five major powers have goals. Corporations have contracts and investments. Factions have resources and methods. Port authorities have rules. Creditors have debts. All of those pressures existed before the crew showed up and will outlast them. The crew is not the center of the universe. They are a small operation caught in the middle of forces that do not particularly care about them as individuals, only about what they carry, where they can go, what they know, or who they know.

The GM's job with the pressure model is threefold:

Make pressures specific. An abstract geopolitical tension between the Irnan Directorate and the Funtari Confederacy means nothing until it is a specific inspector at a specific checkpoint who has been told to flag ships with Funtari registry numbers, and the crew's ship has a Funtari registry number. A Jaziri Caliphate interest in a cargo means nothing until a Jaziri auditor boards the ship at Saint Orra's Rest and starts asking questions that suggest he already knows what is in the container. Abstract pressure becomes real when it has a face, a name, and an immediate demand.

Make pressures personal. The crew should have history with the factions that are pressing on them. A contact who owes the crew a favor works inside a corporation that is currently the most convenient way for a rival faction to create trouble. A border warrant that the crew thought was resolved turns up in a Directorate database at the worst possible moment. Pressure that connects to who the crew already is hits harder than pressure that comes from nowhere.

Make pressures advance. If the crew ignores a faction that has an interest in them, that faction does not wait politely. It takes steps. It calls in allies. It escalates. Chapter Nine covers faction clocks in detail; the short version is that every significant faction or power with an agenda should have a clock that ticks forward whether or not the crew is paying attention, and the players should start to feel that tick before it becomes a crisis.

Managing the Three Zones

The Void Drifters universe divides into three zones that have meaningfully different pressure characters. A GM who knows which zone the crew is operating in can calibrate friction, opportunity, and danger accordingly.

Controlled Space

Controlled space is where a major power has consistent presence. Patrols run regular routes. Checkpoints are staffed. Nav beacons are maintained. Laws are enforced, and enforcement is not a negotiation.

What this means at the table. Jobs in controlled space tend to be legitimate on the surface and complicated underneath. The complication is not the patrol ship; the patrol ship is doing exactly what it is supposed to do. The complication is that the cargo is not what the manifest says, or the contact is using the crew for a purpose they were not told about, or someone on the crew has an outstanding warrant that was supposed to be cleared. Controlled space makes the environment itself a source of pressure rather than just a background detail.

Port behavior in controlled space. Papers are checked. Manifests are compared against known route data. Ships with unusual origins, mixed-builder modifications, or unregistered components attract attention from port officials who have nothing better to do than notice. The crew should feel that operating here requires maintaining appearances, and that those appearances have real costs.

Irnan controlled space is the most procedurally thorough. Documentation matters in triplicate. Directorate ports have standardized inspection protocols and share registry data with other Directorate checkpoints across the region.

Jaziri controlled space combines customs inspection with ideological oversight. A Jaziri inspector may be satisfied with a cargo manifest and still ask questions about crew members' affiliations, AI documentation, and whether any of the passengers are traveling voluntarily.

Shoiyan controlled space is polished and quiet. The friction is less visible but present: genetic identity verification, stack documentation requirements, and the sense that the Concord already knows more about the crew than the crew disclosed.

Funtari controlled space is inconsistent and clan-dependent. What clears one port may not clear the next if different clan factions control different stations. Reputation with specific clans matters more than paperwork.

Antaean controlled space runs on contracts, licenses, and liability. A ship without the correct insurance bond may be denied docking rights on procedural grounds, and appealing that decision costs money the crew may not have.

Fringe Space

Fringe space is where authority is thin. Patrols are infrequent or predictable. Nav beacons may be maintained, missing, or tampered with. Laws exist on paper; enforcement is a matter of who is present and whether they care.

What this means at the table. The friction in fringe space comes from people, not institutions. A port authority with six staff and a single armed cutter is not going to seriously challenge a well-armed crew, but the port's local protection arrangement with a regional syndicate might. The laws do not press on the crew here; the people with informal power do.

Fringe space is where the crew has the most freedom and the most exposure. There are no official rescue services. Repairs require improvisation or expensive independents. The next job may not be waiting at the next port.

Opportunity in fringe space. The jobs here pay better for a reason. Cargo that cannot travel through controlled space without inspection can move through the fringe. People who need to disappear can disappear here. Equipment that is restricted in Directorate ports can be purchased or traded here, with appropriate risk attached.

Dead and Unclaimed Space

Dead space, unclaimed systems, wreckfields, failed terraforms, abandoned colonies, and No Man's Land beyond the eastern edge of the Meridian Verge: these are the extreme end of the spectrum. No rules. Maximum danger. Maximum opportunity for those who can reach them and survive them.

What this means at the table. The crew is on their own here in a way that controlled and fringe space do not replicate. No one is coming to help. The danger is environmental, structural, and alien, not political. Failed colonies have reasons they failed, and those reasons may still be present. Wreckfields have things in them that someone else is already looking for. Dead systems are rarely truly empty.

Dead space as campaign escalation. A campaign that starts in the Meridian Verge may push into unclaimed space when the political pressures become too intense, or when a job requires it. That push should feel like a genuine escalation of risk. The tools and contacts that help in the Verge are no longer available. The crew is operating on what they brought with them.

The Job Framework

Every Void Drifters session needs a job. Not because the game demands a mandatory plot structure, but because the job is the vehicle through which pressure becomes specific and personal. The job delivers the situation the crew actually has to deal with.

Job Sources

Jobs come from people, and people have reasons.

Legitimate employers hire crews for work that is legal on its face: courier contracts, passenger transport, cargo runs, route surveys, security escorts. The complications in these jobs come from what the employer did not disclose, what the cargo actually is, who else is interested in it, and what the route actually involves.

Faction-connected employers hire crews for work that serves a specific faction's interest, usually in ways that would be complicated to do through official channels. A Funtari clan factor who needs cargo delivered quietly. A Directorate intelligence contact who wants a person extracted from a station without any record of Directorate involvement. A Shoiyan medical house that needs a recovered continuity stack transported to a vault that is not on any public registry. These jobs pay well because discretion is part of the contract.

Personal obligation employers are the contacts the crew already has: the person who got them out of trouble in Harrowspan, the mechanic who fixed the ship on credit and has a favor to call in, the old shipmate who is now in a bad situation that requires exactly the kind of crew the players have. These jobs are personal and often do not pay what they are worth.

The crew themselves can generate jobs through their own interests: a lead on salvage, a rumor about a wreckfield, a system they have been wanting to check, a score they have been planning for two sessions. These are valid job origins and should be encouraged.

What Employers Hide

Trigger: The crew accepts a job.

GM decision point: Decide what the employer is not telling them. This is not optional. Every job in Void Drifters has at least one thing the employer concealed, minimized, or genuinely did not know.

Player-facing signal: The job briefing seems complete. There is no visible gap. Players may ask clarifying questions; answer them honestly with the information the employer would actually provide.

Mechanical handling: The hidden element does not arrive immediately. Let the crew get one scene into the job before the concealed element becomes relevant. A cargo run where the cargo is someone's missing sibling: the crew learns this when the sealed container makes a sound at the first rest stop in Slipspace. A delivery where the sender is wanted by the Directorate: the crew learns this when an Irnan patrol contacts them at the exit seam.

Consequence: The hidden element becomes the actual problem the session is about.

Recovery and off-ramp: The crew should always have at least one non-violent exit available, even if it costs them the job fee, reputation damage, or a future complication. A job that becomes untenable should not become a death trap. It should become a choice about what they are willing to do and what they are not.

Job Complications

A complication is the moment the job becomes interesting.

The best complications come from three sources:

The cargo or subject. What the crew is moving has properties that create the complication: it is wanted by someone who is not the client, it is not what the manifest says, it is dangerous in ways the crew was not told, or it has made decisions of its own.

The route. The path between departure and destination creates the complication: a corridor that requires passing through a system where the crew has history, a checkpoint staffed by someone who knows one of the crew, a slipstream instability that forces an unplanned stop at a port that was specifically supposed to be avoided.

The contact. The person the crew is delivering to, extracting, or working with creates the complication: they are not who they said they were, they have changed their mind, they are already compromised, or they want something the crew was not contracted to provide.

Job Consequences

Trigger: The job resolves, successfully or otherwise.

GM decision point: Decide what has changed. Not what reward the crew receives, though that matters too: what is different in the universe now because of what the crew just did?

Player-facing signal: State clearly what the crew knows about the consequence. Do not leave consequences abstract. The Funtari clan factor now owes the crew a favor, and tell the players what that means in concrete terms. The Directorate now has a record of the ship at that checkpoint, and tell the players what that record might mean later. The contact who hired them is dead, and tell the players who knows that and what they might want.

Mechanical handling: Update faction relationships, reputation, and any relevant clocks. Note any new hooks the consequence creates.

Recovery and off-ramp: Failed or compromised jobs should create new opportunities rather than simply subtracting from the crew's position. A job that goes wrong and leaves the crew with damaged reputation with one faction may open access to that faction's rivals. A cargo that was lost may leave the crew with information about why it was lost and who else wanted it.

The Faction Clock

Powers, corporations, and independent factions all have goals that tick forward whether or not the crew pays attention.

A faction clock is a simple tracker: a goal, a resource, a method, and a number of steps between where the faction is now and where its goal will be achieved. When the faction takes a meaningful action toward its goal, advance the clock one step. When the clock completes, the goal is achieved and the universe changes.

What Clocks Track

Clocks track faction progress toward specific outcomes. Not abstract geopolitical movement, but specific, table-relevant outcomes:

• The Irnan Directorate establishes a permanent checkpoint in the Harrowspan wreckfield (four steps: secure a station platform, staff it with a patrol rotation, activate it publicly, begin registry-flagging ships that used the field during the gap period)
• A Funtari syndicate corners the fuel supply at Calder's World (three steps: buy out the independent supplier, establish a price point above independent alternatives, begin refusing supply to crews on a specific blacklist)
• A Jaziri intelligence contact maps the crew's regular routes and contacts (five steps: identify the crew as a target, place an observer at Port Meridian, build a contact map, establish a local asset, make contact with leverage)

Each step is a concrete action the faction takes. The GM advances the clock when that action happens in the fiction, when the faction has the opportunity and the motivation.

When to Advance a Clock

Trigger: Time passes, or the crew takes an action that gives a faction an opening.

GM decision point: Decide whether the faction has had the opportunity and motivation to advance its agenda. Consider: how much time has passed? Has the crew done anything that gives this faction new leverage or urgency? Has the crew done anything that would slow or reverse the faction's progress?

Player-facing signal: Advance clocks are signaled through in-universe details before they become crises. A crew that pays attention should be able to see a clock moving before it completes. The Directorate checkpoint does not appear without prior signals: increased patrol traffic near Harrowspan, a relay message about “navigation safety improvements” in the region, a contact who mentions that Directorate survey ships have been active in the wreck lanes. The players do not need to know the clock exists. They need to see the signs that something is changing.

Mechanical handling: Track clocks between sessions. Advance them at session start or end based on elapsed fiction-time. If the crew spent a week in Slipspace, a faction with good resources and active motivation probably took one step. If the crew resolved the situation that was blocking a faction's progress, the faction took one step immediately.

Consequence: When a clock completes, the outcome is real and immediate. Do not soften it because it is inconvenient. The Directorate checkpoint now exists at Harrowspan. The crew's old route is no longer available without encountering it.

Recovery and off-ramp: Completed clocks are not permanent. They can be reversed through effort, cost, and sometimes violence. But reversal should cost something real. If the crew wants to stop the checkpoint, they need a plan and they need to execute it.

Signaling Clock Progress

The most important skill with faction clocks is signaling progress before it becomes a crisis.

Players should feel that the world is changing around them even when they are not directly involved in the change. A relay news item about new Directorate administrative activity in the Verge. A contact who mentions the fuel prices at Calder's World have jumped. A Jaziri pilgrim ship that seems to have the same itinerary as the crew for the third consecutive port. These signals are not puzzles with solutions. They are the universe doing what universes do: changing because forces are acting on it.

When players start asking questions about the signals, the clock is working correctly.

Travel as Pressure

FTL travel in Void Drifters is not instantaneous and it is not free. A slipstream transit takes days to weeks depending on corridor length and conditions. In-system travel takes additional hours or days depending on the system. Consumables are consumed. Heat accumulates if the crew is pushing the drive. Warrants have expiration dates. People on board get hungry, get bored, and sometimes get into conflict.

The goal is not to make travel an ordeal. The goal is to make the space between ports feel like it has weight.

The Travel Procedure

Trigger: The crew departs for a new system.

GM decision point: Decide one thing that happens in transit. Not necessarily a crisis: sometimes it is a crew conversation that matters, sometimes it is a complication with the cargo, sometimes it is a mechanical issue that requires attention, sometimes it is the crew picking up a relay message that changes what they expect to find at their destination.

Player-facing signal: At the start of transit, tell the players the expected travel time and one known variable: the slipstream corridor is well-established, so no Astrogation Trial is required; or the seam at the destination is flagged as frontier-grade in the charts and will require an Astrogation Trial to locate on arrival; or the corridor has intermittent traffic because of recent Directorate patrol activity and the crew should decide whether to exit at the standard arc or attempt an offset.

Mechanical handling: Use the travel complication table in Chapter Seven to introduce one meaningful event during transit. Not every transit needs a complication; an established corridor with no outstanding heat and no unusual cargo might be uneventful. But most transits should have at least one beat: a decision, a discovery, a problem to address, or a conversation the GM wants to happen between crew members.

Consequence: Arrival conditions reflect what happened in transit. A crew that handled a supply problem during transit may arrive low on something they expected to have. A crew that intercepted a relay message during transit arrives with information the port does not know they have.

Recovery and off-ramp: Travel complications should not be mandatory crises. The correct default is a choice the crew makes in transit that has downstream effects. The fuel consumption is running higher than expected: the crew can push through on the current reserves and arrive below safety margin, or they can reduce speed and arrive two days late. Both are valid. Both have different consequences.

Making Transit Time Meaningful

What is the crew doing for three days? This is the question that unlocks good transit scenes. The ship is the crew's shared space and their home. What happens in that space during transit is often where the most important character work happens. Who is on watch rotation? Who is fixing the thing that broke two sessions ago? Who is reviewing the job details and finding something that does not add up?

Give each transit one beat. A beat is anything that requires a player to make a decision or that reveals something the crew did not know before. It does not have to be mechanical. A beat can be a conversation, an observation, a problem that resolves without dice, or a discovery that changes context for the destination.

Consumables are a clock. The crew's consumables, fuel, food, water, medical supplies, ship maintenance parts, are a slow-ticking clock that rewards players who plan ahead and creates soft pressure when they do not. Do not track consumables turn-by-turn. Track them session-by-session. “You arrive with enough fuel for two in-system transits before you need to refuel” is useful information. “You consumed 0.3 units of consumables during the crossing” is not.

Travel tables. Chapter Seven includes two travel complication tables: one for Slipstream transit and one for the in-system run between seam and dock. Pull from them when you want an unplanned element; discard them when you already have a beat prepared. The tables are a resource, not a mandate.

Ports and Systems

Every port the crew visits is a location, not a menu. It has a power presence or the absence of one, an economy, people who live and work there, things that are available and things that are not, and at least one angle that will create pressure for the crew.

The Port Prep Checklist

Before the crew arrives at a port, know the following:

Power presence. Which power controls or claims this port? Is that control active or nominal? Is there a patrol ship in dock? An inspector on shift? A corporate agent with a flag on the crew's registry? If no power controls it, who provides order, and what does that order cost?

Economy. What does this port need that the crew might provide? What does it have that the crew might want? Jobs available here are almost always connected to the local economy: a port that is short on medical supplies wants a cargo run; a port with a glut of refined ore wants a buyer; a port that is nominally neutral but functionally Funtari-aligned wants a crew that can cross into Directorate space without triggering flags.

The problem. Every port has one active problem. Not an adventure waiting to happen, just a situation that creates friction: a labor dispute that has shut down two of the three fuel suppliers, a recent boarding that left the port authority agitated and checking every manifest twice, a Jaziri pilgrim group that arrived expecting a connection that is not there and is making their displeasure known in the common areas.

The person who causes trouble. At least one NPC in the port will interact with the crew in a way that generates pressure. This is not a villain; it is a person doing their job, pursuing their interest, or responding to a situation in a way that happens to complicate what the crew is trying to do. A customs inspector who has been told to flag ships from a specific builder's model. A local syndicate contact who heard the crew was coming and has a message that was supposed to go to their previous port. A mechanic who can fix the crew's problem but whose price is a favor rather than credits.

The hook. Every port should leave the crew with at least one reason to come back or one lead for the next session. Not a mandatory plot point, a thread. A person who mentioned something that did not quite fit. A relay message that was waiting for someone who is not on the crew, but whose name is familiar. A bulletin board offering double rates for a run to a system the crew knows is currently complicated.

Running a Port as a Living Location

The mistake GMs make with ports is treating them as menus: a list of what is available to buy, one optional NPC, and a job offer. A port-as-menu flattens every location into the same experience regardless of where it is, who controls it, or what is happening there when the crew arrives.

A living port has background activity. People are doing things that are not about the crew. There is a ship in dock with a crew that is visibly in a dispute about something. The food supplier by the main airlock has better prices than the port canteen but is obviously operating on a margin that suggests the goods have a complicated origin. The port authority office has a queue that is longer than it should be.

Background activity makes a port feel like a place rather than a scene. Players will notice it and ask about some of it. Some of what they ask about leads somewhere. Some of it does not. The ratio does not need to be disclosed in advance.

First visits establish the port. The first time the crew visits a location, spend time on sensory detail: what does it smell like, what is the gravity situation, what kind of people are moving through here, what is visible from the dock. Give the port a character that survives the visit.

Return visits build on that character. When the crew comes back, some things have changed and some things have not. The mechanic who charged them a favor last time is still there and remembers them. The long queue at the port authority office has resolved, but the cause of it has become a local story everyone will tell if asked. The ship that was in dock with the arguing crew is gone, and someone at the canteen is willing to say where it went.

The Reputation Track

The crew's name means something, and what it means changes based on what they do.

Track reputation as a set of specific relationships with specific factions, ports, and people, not as a single number. The Irnan Directorate's opinion of the crew is different from the Funtari clans' opinion, which is different from Port Meridian's port authority's opinion, which is different from the Harrowspan salvage community's opinion.

Tracking Reputation

Track the crew's standing with each relevant faction, port, or community using a single scale of six tiers. This is the same reputation track used for faction relationships throughout this book (Chapters Nine and Eleven).

Moving between tiers takes action, not just time. One good job moves the crew from Unknown to Known; a significant service moves Known to Trusted; damaging a faction's interests drops them one or two tiers; and betraying a faction secret or destroying a significant asset can drop them straight to Burned or Wanted.

Specific debts still matter within the track. “Owed” is most useful when it is concrete. A favor owed by a Funtari clan factor at Red Vale is an asset the crew can spend; being on a syndicate's list after a cargo incident at Calder's World is a liability that will surface. Note the specific debt alongside the tier.

Using Reputation Against and For the Crew

In the crew's favor. Trusted standing with Port Meridian's port authority means the customs inspection is perfunctory rather than thorough. Known status with the Harrowspan salvage community means the best jobs are offered before they go public. A specific debt owed to the crew by a Funtari contact means they can call in that favor at a moment of genuine need.

Against the crew. Burned standing with the Directorate means every checkpoint in Irnan space has a flag on the ship's registry. Burned standing with a syndicate that controls fuel distribution in the Verge means the crew pays premium rates everywhere that syndicate has reach, or they find another fuel source. A specific debt the crew owes to the wrong people is a hook in their side that pulls at inconvenient moments.

Reputation changes. When the crew does something that would alter a faction's opinion, update the relevant track. Do not tell the players the mechanical result; show it through the fiction. The inspector who used to give them trouble now waves them through. The port that used to offer them jobs they did not want is now quietly routing the better contracts to crews that are not the crew. The contact who was previously an ally now returns messages late, if at all.

Table Calibration

Session zero is a conversation, not a form to fill out. The goal is to establish what kind of Void Drifters the table is going to play and what everyone needs from the experience.

What Void Drifters Needs from Players

Crew buy-in. The Player's Guide tells players that they share a ship and have reasons to work together. Session zero is where those reasons become specific. Why does this particular group of people share this particular ship? What keeps them from going their separate ways when the job goes bad? The answer does not need to be deep backstory; it needs to be functional at the table. “We owe money on the ship together” is an excellent answer. “We each need the others for different reasons” is excellent. “We are the only crew the ship will take” is a fine starting point for a campaign.

A reason to take jobs. The crew needs a structural motivation for continuing to operate: debt on the ship, a contract obligation, a search they are conducting through jobs that give them cover, a commitment to a contact that requires staying in the region. This motivation does not have to be exciting on its own. It just has to be present so the GM has something to attach jobs to.

Willingness to engage with consequences. Void Drifters works when players are willing to let their characters have real stakes. A player who retreats from every consequence or who treats the game as a puzzle with a correct solution that avoids all cost will struggle here. This does not need to be stated as a rule; it can be framed as a question. “This game has real consequences that can make life harder for your crew. Is everyone comfortable with that?”

What Players Need from the GM

Honest consequences. If the crew does something that would reasonably create a problem, the problem arrives. The universe is not trying to hurt them; it is responding to what they did.

Functional pressure. Every session should have pressure the crew can actually engage with. Not pressure so overwhelming that nothing the crew does matters; not pressure so thin that there is no reason to try. Calibrate to the crew's capability and let the pressure scale with their reputation and choices.

Genuine wonder. Occasionally, something in this universe should be genuinely remarkable. A world that defies expectation. A discovery that changes what the crew thinks they know. A person who turns out to be much more important than they appeared. Void Drifters is a frontier game, and frontiers have things on them that have not been seen before. Let those things exist.

Transparency about the shape of the game. Players should know that this is a game about a crew, not a series of individual stories. They should know that factions remember things. They should know that the ship is a central character. If any of that does not match what a player was expecting, session zero is the time to find out.