What it is
Fortune Core is a stat-modifier ship passive that adds a flat amount to the carrier’s luck stat. It is one of sixteen passives registered in the passive index and is the only entry in the registry whose target stat is luck. The passive uses the standard five-tier rarity ladder shared by every passive definition in the game, with values applied once at run assembly.
Identity
| Field | Value |
|---|---|
| Display name | Fortune Core |
| Description template | +{value} luck |
| Stat target | luck |
| Unit | flat |
| Scaling curve | Utility flat (3 / 6 / 10 / 15 / 22) |
The stat target is the ship’s luck field. The bonus is a flat additive number, not a percentage — so a Legendary Fortune Core adds the literal integer 22 to whatever luck value the hull starts the run with. No triggered effect is attached to the definition, which means the passive flows through the same stat-resolution path as the other flat-stat passives in the registry.
Per-rarity values
| Rarity | Value |
|---|---|
| Common | +3 luck |
| Uncommon | +6 luck |
| Rare | +10 luck |
| Epic | +15 luck |
| Legendary | +22 luck |
The five values come directly from the passive’s values tuple, indexed by the standard rarity-to-index map. The step deltas widen up the ladder: +3, +4, +5, +7. The curve matches the shape used by the other flat-utility passives in the same family (small early steps, larger late steps), so a Legendary roll is just over seven times the size of a Common roll on this passive.
For context, the shared baseline ship-stats table starts every hull with 8 luck before any passive is applied. A Legendary Fortune Core therefore lifts the run-start luck total from 8 to 30 on a baseline hull — a 3.75× swing — before any in-run luck pickups, mod-grid bonuses, or artifact contributions are layered in.
Which ships use it
At the verified commit, no ship in the roster declares Fortune Core as its passiveId. A full-tree search for the string fortune_core matches only the passive’s own definition file and its import plus registration in the passive index. The shared baseline ship-stats record defaults every entry in the 60-hull × 5-star roster to a different passive, and no per-hull override in any of the star-tier stat tables assigns Fortune Core. The passive is registered and resolvable through the helper functions but has no ship binding in the current roster.
How it stacks with other effects
Fortune Core modifies a single named stat (luck) by a flat additive value, so it slots into the same stacking path as any other flat-stat passive. The bonus applies at run assembly through the shared passive resolution rather than through the effect engine — the passive’s effects array is absent, so no triggered handler is registered at run start.
Other sources of luck on a run include: the modifier-grid Luck node, which adds +0.10 to luckMult per rank and feeds into the level-up card rarity roll as (1 + luckMult) applied to the ship’s base luck; and a family of artifacts that push flat luck via the modify-stat effect (the artifact index lists more than ten artifacts whose primary stat is luck, including absorption barrier, bloodlust, caretaker, hunter, lodestone, refresh, event reward, crate buster, and killstreak rain). These flat-luck sources stack additively on top of the Fortune Core contribution; the multiplicative luckMult modifier from the grid then scales the combined base when the level-up rarity roll is computed.
EXTRACT-CANDIDATE: “no ship uses Fortune Core” is true at the verified commit because a full-tree search for the string fortune_core finds only the passive’s own definition file and its import/registration in the passive index — no passiveId: 'fortune_core' reference exists in the ship roster files or any of the per-star override tables. If a future patch wires this passive onto a hull, the “Which ships use it” section will need a ship table.
EXTRACT-CANDIDATE: the passive’s stat field is the literal string luck, and the ship-stat schema also uses luck for the per-hull luck field, so the mapping is direct. However, the exact run-assembly call site that reads the passive definition and adds the value to the ship’s luck field is not visible in the assemble-run service file at the verified commit — the _types.ts comment references an applyPassives() function in that service but no such function is present in the file as read. Confirm the actual application path before adding a precise call-site claim.
EXTRACT-CANDIDATE: ship luck also feeds the metagame stat objectiveSpeed via the formula round(luck * 0.5) in toShipMetaStats. Whether Fortune Core’s luck contribution propagates into objectiveSpeed depends on whether the passive value is added before or after that conversion runs. Confirm against the run-assembly service before adding a claim about Fortune Core affecting hub-side objective speed.
EXTRACT-CANDIDATE: the relationship between ship luck and the level-up card rarity roll is described on the modifier-grid Luck node as (1 + luckMult) * ship.luck consumed by _rollRarity in leveling. The exact mathematical effect of a +22 luck swing on uncommon/rare/epic/legendary card-roll weights is not specified in the passive data file. Confirm against engine/.../leveling.ts before adding a precise drop-rate claim.