What it is
Payload Delivery is a stat-modifier ship passive that increases the carrier’s fire rate 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 | Payload Delivery |
| Description template | +{value}% fire rate |
| Stat target | fireRatePct |
| Unit | percent |
| Scaling curve | Fire-rate percent (4 / 8 / 13 / 19 / 28) |
The stat target is the combat-stat field fireRatePct, a per-ship bonus on top of each weapon’s base fire rate. 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 | +4% |
| Uncommon | +8% |
| Rare | +13% |
| Epic | +19% |
| Legendary | +28% |
The five values come straight from the passive’s values tuple, indexed by rarity. Step-to-step gaps are +4, +5, +6, +9, so the curve accelerates toward the top end. The same curve 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 Payload Delivery 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 Payload Delivery. The passive is available content awaiting a ship assignment.
How it stacks with other effects
Payload Delivery modifies a single named combat stat (fireRatePct) 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 fire-rate modification (mods such as the bank-capacitor template, artifacts such as Frenzy, Surge Coil, Echo, and Heat Racer, and weapon-level scaling) combine with the passive’s contribution according to the run-assembly layer’s stacking rules, not anything intrinsic to this passive’s data. The runtime stores a baseline snapshot of fireRatePct on the ship and re-applies the equipped-mod bonus on top of that baseline whenever mods change.
EXTRACT-CANDIDATE: “no ship uses Payload Delivery” is true at the verified commit because a full-tree search for the string payload_delivery finds it only in the passive’s own definition file and the passive index registration — no passiveId: 'payload_delivery' 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 fireRatePct bonus and other fire-rate sources (mods, artifacts, weapon-level fire-rate curves) 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 description template reads ”+{value}% fire rate” but the isPercent flag on the definition is false. Every sibling stat passive in this family has the same shape, so this is likely a UI/data convention (description carries the percent sign explicitly, flag is reserved for a different rendering path) rather than a bug — but the convention is undocumented in the passive data files and worth clarifying on the passives concept page.