What it is
Afterburner is a stat-modifier ship passive that increases the carrier’s maximum movement speed by a percentage. It is one of sixteen passives registered in the passive index and follows the standard five-tier rarity scaling shared by the percent-stat passive family.
Identity
| Field | Value |
|---|---|
| Display name | Afterburner |
| Description template | +{value}% movement speed |
| Stat target | maxSpeed |
| Unit | percent |
| Scaling curve | Movement percent (5 / 10 / 16 / 23 / 32) |
The stat target is the combat-stat field maxSpeed, which caps how fast the ship can travel once thrust has fully ramped up. The bonus is a percentage modifier applied through the standard passive resolution path at run start. No triggered effect is attached to the definition, so the passive is purely a stat multiplier — it does not register any abilities through the unified effect engine.
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. Step-to-step gaps are +5, +5, +6, +7, +9, so the curve accelerates slightly at the top end. The same curve is shared with other percent-stat passives in this family.
Which ships use it
At the verified commit, no ship in the roster declares Afterburner 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 Afterburner. The passive is available content awaiting a ship assignment.
How it stacks with other effects
Afterburner modifies a single named combat stat (maxSpeed) 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 is attached to the definition. Other sources of speed 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. A separate artifact carries the display name “Afterburner” with an id of heat_racer; despite the shared label, it is a different entity with its own buff loop and is unrelated to this passive’s definition.
EXTRACT-CANDIDATE: “no ship uses Afterburner” is true at the verified commit because a full-tree search for the string afterburner finds it only in the passive’s own definition, the passive index registration, an artifact whose display name reuses the word, and an effect-engine comment example — no passiveId: 'afterburner' reference exists in the ship roster file. 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 maxSpeed bonus and other speed 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 artifact named “Afterburner” (id: heat_racer) shares only a display label with this passive — clarifying the naming collision on the artifacts page would prevent confusion when both can appear in the same run UI.