What it is
Phase Drive is a stat-modifier ship passive that increases the carrier’s acceleration by a percentage. It is one of sixteen passives registered in the passive index and follows the standard five-tier rarity scaling shared by every percent-stat passive in the game.
Identity
| Field | Value |
|---|---|
| Display name | Phase Drive |
| Description template | +{value}% acceleration |
| Stat target | thrust |
| Unit | percent |
| Scaling curve | Movement percent (5 / 10 / 16 / 23 / 32) |
The stat target is the combat-stat field thrust, which is sourced from the ship’s acceleration value during the run-assembly conversion to combat stats. Acceleration controls how quickly the ship reaches its maximum speed when thrust is applied. The bonus is multiplicative against the ship’s base thrust and applies once at run start through the standard passive-resolution path.
Per-rarity values
| Rarity | Value |
|---|---|
| Common | +5% |
| Uncommon | +10% |
| Rare | +16% |
| Epic | +23% |
| Legendary | +32% |
The five values come straight from the passive’s values tuple, indexed by rarity. Each step grows the gap to the next tier on the way up: +5, +5, +6, +7, +9. The curve matches the other percent-stat passives in this family.
Which ships use it
At the verified commit, no ship in the roster declares Phase Drive as its passiveId. The passive is registered and resolvable through the helper functions in the passive index, but the baseline ship stats default to a different passive and no per-hull override in the ★1 stat table assigns Phase Drive. The passive is available content awaiting a ship assignment.
How it stacks with other effects
Phase Drive modifies a single named combat stat (thrust) by a percent value, so it slots into the same stacking path as any other percent-stat passive. The bonus is applied at run assembly through the shared passive applier — no custom handler or triggered effect is attached to the definition. Other sources of thrust or acceleration modification (mods, artifacts, upgrades) combine with the passive’s contribution according to the run-assembly layer’s stacking rules, not anything intrinsic to this passive’s data.
EXTRACT-CANDIDATE: “no ship uses Phase Drive” is true at the verified commit because a full-tree search for the string phase_drive only finds the passive’s own definition and its registration in the passive index — no passiveId: 'phase_drive' reference exists in the ship roster files. If a future patch wires this passive onto a hull, the “Which ships use it” section will need a ship table.
EXTRACT-CANDIDATE: exact multiplicative-vs-additive interaction between this passive’s thrust bonus and other thrust sources (mods, artifacts, upgrades) is not specified in the passive data file. Confirm against the run-assembly service before adding a stacking-order claim.
EXTRACT-CANDIDATE: the relationship between thrust (combat stat) and acceleration (ship-def field) — confirmed in the ship-to-combat-stat conversion path where thrust is assigned from ship.acceleration — is documented here at a high level but the full conversion table is a candidate for a dedicated combat-stats reference page.