What it is

Thermal Vents is a stat-modifier ship passive that increases the carrier’s heat cooldown rate by a percentage. It is one of the passives registered in the passive index and uses the standard five-tier rarity scaling shared by every percent-stat passive in the game. The passive has no triggered-effect block — it is a pure stat modifier, applied once at run assembly through the shared passive-resolution path.

Identity

FieldValue
Display nameThermal Vents
Description template+{value}% heat cooldown
Stat targetoverheatCool
Unitpercent
Scaling curveStandard percent (5 / 10 / 16 / 23 / 32)

The stat target is the ship’s heat-cooldown rate, the value that governs how quickly the heat gauge bleeds back down toward zero. A higher cooldown means the gauge clears faster after thrust is released, which in turn shortens the window in which heat-driven side effects (boost from the heat curve, burnout penalty, heat-shake camera effect once past its threshold) are active. The passive only changes the cooldown rate; it does not touch heat buildup, the heat curve shape, the burnout severity multiplier, or the heat-shake threshold.

Per-rarity values

RarityValue
Common+5%
Uncommon+10%
Rare+16%
Epic+23%
Legendary+32%

The five values come straight from the passive’s values tuple, indexed by rarity. Steps between tiers are +5, +6, +7, and +9, identical to the shared percent-stat curve used by other passives in the same family (max HP, max shield, weapon-damage-style bonuses). Legendary is roughly six and a half times the common value.

Which ships use it

At the verified commit, no ship in the roster declares Thermal Vents as its passiveId. The ship roster generates 300 entries (60 hull classes × 5 stars) from a single shared baseline whose passiveId is set to a different passive, and no per-hull or per-star override in the roster file assigns Thermal Vents to any specific ship. The passive is available content registered in the passive index but is not yet wired onto a hull.

How it stacks

Thermal Vents modifies a single named stat 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 heat-cooldown modification combine with the passive’s contribution according to the run-assembly layer’s stacking rules, not anything intrinsic to this passive’s data. Because the passive only adjusts the cooldown rate, it interacts indirectly with any system that reads the live heat value (heat-curve speed boost, burnout state, heat-shake camera intensity) by shortening the time spent above each of those thresholds; the passive does not modify those systems’ parameters themselves.

EXTRACT-CANDIDATE: “no ship uses Thermal Vents” is true at the verified commit because a full-tree search for the string thermal_vents only finds the passive’s own definition file and its registration in the passive index — no passiveId: 'thermal_vents' reference exists in the ship roster file, and the roster’s baseline passive is set to a different ID. If a future patch wires this passive onto a hull, the “Which ships use it” section will need a ship table.

EXTRACT-CANDIDATE: the exact mapping from the overheatCool stat field to the per-tick heat-bleed amount lives in engine code, not in the passive data file. The passive only declares that it raises that stat by a percent; the unit (heat points per second, fraction of max heat per second, or similar) and any non-linear conversion are owned by the heat system itself.

EXTRACT-CANDIDATE: whether the percent bonus operates on the ship’s pre-mod base overheatCool (the heatCooldown baseline of 40 in the shared ship baseline) or on a post-mod intermediate value is not specified in the passive data file. The five-value tuple and the isPercent flag are the only computation inputs declared here; the order of application against other heat-cooldown sources lives in run-assembly code, not in the passive definition.

EXTRACT-CANDIDATE: whether overheatCool is the same stat field as the ship roster’s heatCooldown (or a separate stat the engine reads under a different name) is not confirmed in the passive data file. The passive references overheatCool; the ship baseline declares heatCooldown. Confirm against the run-assembly service or stat-mapping layer before treating them as the same field.