Run this drive through the antitelephone →Its row in the atlas →Report card →

FTL: Faster Than Light, the jump drive as a game mechanic

Subset Games' 2012 roguelike puts the drive in the title and makes its one rule, the charge bar, the whole rhythm of play: jump, fight, wait to jump again, with the fleet a beacon behind.

Kind: fiction · Loophole: L4 · Notability: N3 · Coherence: F2 · Causality: C-silent · Last reviewed: 2026-09-12

The drive as depicted

FTL: Faster Than Light was released by Subset Games, the two-person studio of Matthew Davis and Justin Ma, on 14 September 2012 for Windows, Mac and Linux, with the free Advanced Edition update and an iPad version following on 3 April 2014 [HIGH] S3. The player commands a Federation ship, by default the Kestrel, carrying information the Rebel fleet wants, across eight procedurally generated sectors to the Federation's last stand [HIGH] S3. Each sector is a map of about twenty beacons, and the ship moves only by FTL jump from the beacon it is at to one connected to it; there is no other travel, and the map is the drive's whole geography [HIGH] S3.

The drive is defined by its interface, since the game has no manual and little lore. An FTL jump needs a charged drive, working engines, a working piloting system with a crew member in the pilot's chair and one unit of fuel [HIGH] S3. The drive charges after each jump, over roughly a minute of real time at the start, faster with more power routed to engines; a bar on the screen fills and the jump button becomes available [MED] S3. The jump itself is instantaneous and unseen: the screen shifts to the new beacon and whatever is there, a ship, a distress call, a store or nothing. Every jump the player makes advances the Rebel fleet one step across the sector map, and beacons the fleet has reached become dangerous; the only way to shed pursuit is to reach the exit beacon and jump to the next sector [HIGH] S3. Enemy ships have the same drive and use it to flee a losing fight; the charge time is what a battle is fought against on both sides [MED] S3. The environment modifies the drive in stated ways: nebulae slow the pursuing fleet and blind sensors, ion storms halve the reactor's power and so slow the charge, and the Advanced Edition adds augments that speed the charge and a jammer that delays an enemy's [MED] S3.

Fuel is the drive's second rule. The ship carries a stock of fuel, each jump costs one, fuel is bought at stores and found in events, and a ship that runs out can only wait at its beacon for a passing trader or the fleet [HIGH] S3. Distance is never given in light-years and travel time is never given at all; the game's clock is the charge bar.

Origin and lineage

Davis and Ma made the game after leaving 2K China and funded its completion on Kickstarter in 2012; in interviews they have cited tabletop games and the bridge drama of television space opera as the design's models [MED] S3. The title names the mechanic the game hangs on. No real proposal is named in the game or by its designers in any interview this catalogue has found, and none is claimed. The game's influence on later design is real and unsourced here beyond the general histories: the beacon map with a pursuing threat became a pattern in roguelikes of the 2010s.

Which loophole, and why

L4, leave the manifold, by elimination and by convention. The ship does not move through space at all between beacons; it is at one and then at another, with no transit shown, no speed stated and no path through our space implied. The jump is called FTL and the drive a jump drive, which is the vocabulary of leaving space and re-entering it. It is not a continuous speed (L1), no space is carried (L2), and although jumps go only along links between beacons, the links are lines on a map rather than tunnels with two ends in the world (L3); the game never calls a beacon a gate. The beacon network does give the drive a strong secondary L3 character, scored under CON-2 below.

The physics cousins are the extra-dimension dossiers and the one pre-laid route in physics. The Kaluza-Klein hyperspace reading is the negative result for a jump drive: no extra dimension physics knows is somewhere a ship can go and come back from elsewhere; the class bill is B-new. Brane-bulk shortcuts is the nearest real relative, a bulk route beating the brane by one part in $10^{58}$ at a bill of B-new, B-mass and B-caus. The Krasnikov tube is the physics of a route that must exist before it can be used: a metric laid along the outbound sublight journey that makes the return fast, at the price of Planck-thin negative energy layers and a two-tube time machine. A beacon map that only permits jumps along existing links is that shape, and the join is that the physics says any such network costs negative energy laid at sublight speed by someone who went first. The register entry for the class is MAN-1.

The rules it keeps

The Coherence mark is F2, rule-bound, and FTL is the cleanest F2 in the catalogue because the drive is nothing but rules and every one of them holds on every run. A jump needs charge, fuel, engines and a pilot; the charge takes time; the time can be shortened by power and augments and lengthened by storms; jumps go only along beacon links; each jump moves the fleet. Nothing about the drive is ever waived for narrative convenience, because there is no narrative outside the rules, and the game's difficulty is the rules' arithmetic. The rule set is legible enough that players reason about it exactly as they would about a physical system: how many jumps a sector permits before the fleet arrives, how much fuel a route costs, whether to fight or charge.

The mark stops at F2 because none of the rules has physical content. Charge time is a pacing device, fuel is a resource counter, beacons are nodes. The game does not pretend otherwise, and its economy of exposition is a design virtue rather than a coherence failing; but the register asks what the drive costs in physics, and the answer is a minute and a fuel unit.

What it ignores

Everything the register asks. The game never says what an FTL jump is, how far a beacon is from its neighbour, how long a jump takes in the world's time, what fuel is or why one unit moves a ship any distance at all. The pursuing fleet jumps at a fixed rate that is the same in every sector, so the world has a clock, but the clock is never named.

Causality is C-silent. Every ship in the game jumps, the fleet and the player are in a race measured in jumps, and the question of whether the fleet's "one jump behind" means the same thing to both parties, or what a jump does to the order of events at the beacons it skips, is never raised because the game has no apparatus in which to raise it. There is no preferred frame, only a tick counter. Last checked 2026-09-12 against the game and the Advanced Edition: no event text touches the causal cost of the drive.

Constraint scoring

Every entry in the register, one row each, verdict from the fiction vocabulary, with a note that says where in the work the engagement or rule occurs.

ConstraintVerdictNote
CAU-1SILENTJumps are instantaneous and the game has one clock, the fleet's advance; whose clock it is never comes up.
CAU-2SILENTNo chronology protection; no loop is possible in a game with no time axis.
CAU-3SILENTTwo drives in relative motion are every encounter, and the row's construction is never noticed.
CAU-4SILENTThe fleet's fixed rate of advance is an implicit universal clock and is never named as a frame.
CAU-5N/ANo entanglement signalling; the game's distress calls and messages arrive by event text.
ENE-1SILENTThe drive is powered by the reactor through the engines subsystem and fuelled by "fuel"; nothing says what either is or what sign of energy the jump needs.
ENE-2SILENTA ship arrives at a distant beacon before light would, and nothing prices it; Olum's negative energy is never invoked.
ENE-3SILENTNo negative energy, so no inequality.
ENE-4N/ANo bubble.
ENE-5N/ANot a warp metric.
ENE-6N/ANo Casimir energy.
ENE-7SILENTBeacon links behave like fixed connections between points in space, and if they were handles topological censorship would bear on them; the game says nothing about what a link is, so the row is neither answered nor excluded.
CON-1N/ANo warp wall or horizon; control is the charge bar.
CON-2RULEThe stated rule is that jumps go only between linked beacons that exist before the ship arrives, and a ship cannot jump where there is no beacon. That is a pre-laid route network, the shape Krasnikov's bootstrap requires; the game answers the row by making the network a given.
CON-3N/AThe player lays nothing; the network pre-exists. The Krasnikov tube is the cousin, not the mechanism.
STA-1N/ANo superluminal bubble.
STA-2N/ANo throat held open.
STA-3N/ANo chronology horizon.
HAZ-1N/ANothing swept up; the jump is discontinuous.
HAZ-2N/AThe crew are never affected by the jump itself, and the game has no medium in which the jump occurs; the crew's hazards are fire, boarding and vacuum at the beacon.
HAZ-3N/ANo throat.
LOR-1RULEThe ship never accelerates; the stated rule is that engines provide evasion and charge rate, not speed, and the jump is a discontinuity.
LOR-2N/ANo tachyons.
LOR-3N/ANo wave in a medium.
LOR-4N/ANeither Scharnhorst nor OPERA bears on it.
WRP-1N/ANot a warp drive.
WRP-2N/ANot a shell moving inertially.
WRP-3N/ANo positive-energy warp claim.
MAN-1RULEThe stated rule is that an FTL jump moves the ship from beacon to beacon with no transit through space, which is the manifold-leaving move in its barest form. MAN-1 says physics supplies no such move; the game's answer is a charge bar.

Sources