What it is
Precision Salvage is a stat-modifier ship passive that increases the carrier’s currency-drop bonus. It is one of sixteen passives registered in the passive index and follows the standard five-tier rarity scaling shared by the stat-modifier passive family.
Identity
| Field | Value |
|---|---|
| Display name | Precision Salvage |
| Description template | +{value}% currency drops |
| Stat target | currencyBonus |
| Unit | flat (per definition flag); percent (per description template) |
| Scaling curve | Currency bonus (3 / 6 / 10 / 15 / 22) |
The stat target is the combat-stat field currencyBonus, a per-ship bonus that influences currency drops at run scope. The bonus is 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 modifier — it does not register any abilities through the unified effect engine. The definition flags the value as flat, while the description template renders it with a percent sign; this mirrors the convention used by sibling stat passives in the same family.
Per-rarity values
| Rarity | Value |
|---|---|
| Common | +3% |
| Uncommon | +6% |
| Rare | +10% |
| Epic | +15% |
| Legendary | +22% |
The five values come straight from the passive’s values tuple, indexed by rarity. Step-to-step gaps are +3, +4, +5, +7, so the curve accelerates toward the top end.
Which ships use it
At the verified commit, no ship in the roster declares Precision Salvage 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 Precision Salvage. The passive is available content awaiting a ship assignment. Every ship in the ★1 stat table carries a baseline currencyBonus of 6 regardless, since that stat field exists on the combat-stat record independent of which passive is equipped.
How it stacks
Precision Salvage modifies a single named combat stat (currencyBonus) by a value, so it slots into the same stacking path as any other stat-modifier passive. The bonus is applied at run assembly through the shared passive applier — no custom handler is attached to the definition. The same stat field is also written by the run-config layer (rewards that confer a currency bonus stack with the combat currencyBonus), so multiple sources can contribute to the same final value. The runtime stores a baseline snapshot of the stat on the ship and re-applies equipped bonuses on top of that baseline whenever the source set changes. The bridge writes the resolved currencyBonus from the combat-stat record onto the ship object each frame the stats sync.
EXTRACT-CANDIDATE
EXTRACT-CANDIDATE: “no ship uses Precision Salvage” is true at the verified commit because a full-tree search for the string precision_salvage finds it only in the passive’s own definition file and the passive index registration — no passiveId: 'precision_salvage' 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: the description template reads ”+{value}% currency drops” but the isPercent flag on the definition is false. The same shape appears on sibling stat passives in this family, 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 — worth clarifying on the passives concept page.
EXTRACT-CANDIDATE: exact stacking behavior between this passive’s currencyBonus contribution, the run-config currencyBonus field on rewards, and any other currency-drop source (artifacts, mods, biome modifiers) is not specified in the passive data file. The run-config comment notes that the run-config currencyBonus “stacks with combat currencyBonus” but does not specify whether the combination is additive or multiplicative, nor what other sources feed the same stat. Confirm against the run-assembly service and the currency-drop resolution path before adding a stacking-order claim.
EXTRACT-CANDIDATE: the precise effect of the currencyBonus stat on drop quantity, drop chance, or drop value is not specified in the passive data file or the combat-stat type definition. The stat field is named and threaded through the bridge, but the downstream consumer that turns it into a gameplay outcome is not referenced from this passive’s source. Confirm against the drop/loot system before claiming a specific mechanic.