What it is
Void Siphon is a stat-modifier ship passive that grants the carrier a flat hull regeneration rate, measured in hit points per second. It is one of sixteen passives registered in the passive index. Unlike the percent-stat passives in the family, its value is a flat additive amount rather than a percentage of a base stat, and the carrier’s baseline hpRegen on every ship in the roster is zero — so the passive’s value is the entire regen rate it contributes.
Identity
| Field | Value |
|---|---|
| Display name | Void Siphon |
| Description template | +{value} HP regen/sec |
| Stat target | hpRegen |
| Unit | flat (HP per second) |
| Scaling curve | Flat HP-regen (0.5 / 1 / 1.5 / 2.5 / 4) |
The stat target is the combat-stat field hpRegen, the ship’s per-second hull regeneration rate. The passive’s isPercent flag is false, so the tier value is added to the ship’s baseline hpRegen rather than scaling it. Every ship in the roster declares a baseline hpRegen of zero, so the passive’s contribution is the carrier’s full hull regen rate. No triggered effect is attached to the definition, so the passive is purely a stat addition — it does not register any abilities through the unified effect engine.
Per-rarity values
| Rarity | Value |
|---|---|
| Common | +0.5 HP/sec |
| Uncommon | +1 HP/sec |
| Rare | +1.5 HP/sec |
| Epic | +2.5 HP/sec |
| Legendary | +4 HP/sec |
The five values come straight from the passive’s values tuple, indexed by rarity. Step-to-step gaps are +0.5, +0.5, +1, +1.5, so the curve accelerates toward the top end. The legendary tier delivers eight times the common tier’s rate.
Which ships use it
At the verified commit, no ship in the roster declares Void Siphon as its passiveId. The passive is registered and resolvable through the helper functions in the passive index, but the roster’s baseline passive is a different one and no per-hull override in the ★1 stat table assigns Void Siphon. The passive is available content awaiting a ship assignment.
How it stacks
Void Siphon modifies a single named combat stat (hpRegen) by a flat additive value, so it slots into the same stacking path as any other flat-stat passive. The bonus is applied at run assembly through the shared passive applier — no custom handler is attached to the definition. Because every ship’s baseline hpRegen is zero, the passive contribution is the carrier’s full hull regen rate before any other source modifies it. Other sources of hull regeneration (artifacts, mods, upgrades, affix-time effects) 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
EXTRACT-CANDIDATE: “no ship uses Void Siphon” is true at the verified commit because a full-tree search for the string void_siphon finds it only in the passive’s own definition file and the passive index registration — no passiveId: 'void_siphon' 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 additive-vs-multiplicative interaction between this passive’s flat hpRegen bonus and other hull-regen sources (artifacts such as soul-leech-style lifesteal, regen mods, upgrade-tree regen bonuses, affix-time regen boosts) is not specified in the passive data file. Confirm against the run-assembly service and the bridge’s stat-bonus recomputation path before adding a stacking-order claim.
EXTRACT-CANDIDATE: the relationship between the hpRegen scalar and concrete in-game HP-restored-per-frame output is not specified in the passive data file. The five-value tuple and the isPercent flag are the only computation inputs declared here; how hpRegen is consumed per tick lives in engine code, not in the passive definition.
EXTRACT-CANDIDATE: whether hull regeneration runs continuously or is gated behind a post-damage delay analogous to the shield-regen delay is not specified in the passive data file. The shield-regen system declares a separate shieldRegenDelay field, but no equivalent gate is declared alongside hpRegen in the ship-stats interface.