What it is
Shield Capacitor is a stat-modifier ship passive that increases the carrier’s maximum shield pool by a percentage. It is one of sixteen passives registered in the passive index and uses the standard five-tier rarity scaling shared by every percent-stat passive in the game.
Identity
| Field | Value |
|---|---|
| Display name | Shield Capacitor |
| Description template | +{value}% max shield |
| Stat target | shieldMax |
| Unit | percent |
| Scaling curve | Defensive percent (5 / 10 / 16 / 23 / 32) |
The stat target is the ship’s shieldMax field, which sets the upper bound of the shield pool that absorbs damage before hit points are touched. The bonus is multiplicative against the ship’s base shieldMax and applies once at run start through the standard passive-resolution path. The shield pool is the same value that governs shield regeneration top-up — increasing it raises both the absorbing buffer and the ceiling that regeneration refills toward.
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 roughly doubles the gap to the next tier on the way up: +5, +5, +6, +7, +9. The curve is identical to the other defensive percent-stat passives (max HP, armor-style bonuses).
Which ships use it
At the verified commit, no ship in the roster declares Shield Capacitor 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 ship roster file assigns Shield Capacitor. The passive is available content awaiting a ship assignment.
How it stacks with other effects
Shield Capacitor modifies a single named stat (shieldMax) 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 shieldMax modification (mods, the shield-bundle and shield-cap modifier paths, 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. The passive only adjusts the pool ceiling; it does not change shield regeneration rate or shield regen delay, which are tracked by separate stat fields.
EXTRACT-CANDIDATE: “no ship uses Shield Capacitor” is true at the verified commit because a full-tree search for the string shield_capacitor only finds the passive’s own definition file and its registration in the passive index — no passiveId: 'shield_capacitor' 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 shieldMax bonus and other shieldMax sources (the shield-bundle modifier rated around +15% per rank, the standalone shield-cap modifier rated around +25% per rank, the Core Reactor and Titan Frame mods that grant flat shieldMax, artifacts, upgrades) is not specified in the passive data file. Confirm against the run-assembly service before adding a stacking-order claim.
EXTRACT-CANDIDATE: whether the percent bonus operates on the ship’s pre-mod base shieldMax 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 shield-pool sources lives in run-assembly code, not in the passive definition.