What it is
Tractor Array is a stat-modifier ship passive that increases the carrier’s magnet range 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 | Tractor Array |
| Description template | +{value}% magnet range |
| Stat target | magnetRange |
| Unit | percent |
| Scaling curve | Magnet-range percent (8 / 15 / 24 / 35 / 50) |
The stat target is the combat-stat field magnetRange, the radius around the ship within which XP orbs, currency drops, and other pickups are pulled toward the ship. 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. The baseline magnetRange on a fresh ship state is 130 units before any passive, mod, or artifact contribution.
Per-rarity values
| Rarity | Value |
|---|---|
| Common | +8% |
| Uncommon | +15% |
| Rare | +24% |
| Epic | +35% |
| Legendary | +50% |
The five values come straight from the passive’s values tuple, indexed by rarity. Step-to-step gaps are +7, +9, +11, +15, so the curve accelerates toward the top end. The same accelerating shape is shared with other percent-stat passives in this family.
Which ships use it
At the verified commit, no ship in the roster declares Tractor Array 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 Tractor Array. The passive is available content awaiting a ship assignment.
How it stacks
Tractor Array modifies a single named combat stat (magnetRange) 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 magnet-range modification combine with the passive’s contribution according to the run-assembly layer’s stacking rules, not anything intrinsic to this passive’s data. Known other sources at the verified commit:
| Source | Type | Contribution |
|---|---|---|
| Baseline ship stat | Static | 130 flat |
| +MAGNET mod (array-magnet) | Mod stats | +80 flat magnetRange, +4 flat luck |
| Companion Droid artifact | Artifact passive | Flat magnetRange |
| Quartermaster artifact | Artifact passive + triggered buff | Flat magnetRange (refresh, 1 stack) |
| Salvager artifact | Triggered buff | Flat magnetRange (refresh, 1 stack) |
| Shieldless Fury artifact | Triggered buff | Flat magnetRange (refresh, 1 stack) |
| Stockpile artifact | Artifact passive + run-start buff | Flat magnetRange (duration 0, persistent) |
| Surge Coil artifact | Triggered buff | Flat magnetRange (refresh, 1 stack), paired with fireRatePct |
| Vitality Surge artifact | Triggered buff | Flat magnetRange (refresh, 1 stack), paired with weaponDamagePct |
The runtime mirrors the ship’s magnetRange field onto the engine ship and reads it from the pickups and XP-orb pull layers each frame. The mod-stats baseline is snapshotted at run assembly and re-applied whenever equipped mods change.
EXTRACT-CANDIDATE
EXTRACT-CANDIDATE: “no ship uses Tractor Array” is true at the verified commit because a full-tree search for the string tractor_array finds it only in the passive’s own definition file and the passive index registration — no passiveId: 'tractor_array' 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 percent magnetRange bonus and the many flat magnetRange contributions (mods and artifacts above) is not specified in the passive data file. The bonus combines with flat sources according to the run-assembly layer, not anything intrinsic to this passive’s data — confirm against the run-assembly service and the bridge’s stat-bonus recomputation path before adding a stacking-order claim.
EXTRACT-CANDIDATE: the related Lodestone artifact is referenced in this page’s frontmatter but magnetRange does not appear in Lodestone’s artifact-definition stat list at the verified commit. If Lodestone’s effect interacts with magnet range only indirectly (for example through pickup behavior rather than the stat field), the relationship should be documented on the Lodestone page rather than implied by adjacency here.