What it is
Ram Prow is a stat-modifier ship passive that increases the carrier’s ramming-damage multiplier 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 | Ram Prow |
| Description template | +{value}% ramming damage |
| Stat target | meleeMult |
| Unit | percent |
| Scaling curve | Melee multiplier percent (8 / 15 / 24 / 35 / 50) |
The stat target is the combat-stat field meleeMult, a per-ship multiplier applied to ramming damage dealt to enemies through contact collisions. The baseline value of the stat is 1.0 and is bounded to a 0.1x to 3.0x range in the run-config schema. The passive 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 | +8% |
| Uncommon | +15% |
| Rare | +24% |
| Epic | +35% |
| Legendary | +50% |
The five values come straight from the passive’s values tuple, indexed by rarity. Step-to-step gaps are +7, +9, +11, +15, 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 Ram Prow 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 ★1 override assigns Ram Prow. The passive is available content awaiting a ship assignment.
How it stacks
Ram Prow modifies a single named combat stat (meleeMult) 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. The ramming damage formula in the collision resolver multiplies the speed-scaled base ram damage by meleeMult, so Ram Prow’s contribution lands directly on the damage figure dealt to the rammed enemy. The Ramming Prow artifact (“battering_ram”) grants periodic speed-boost and weaponDamagePct pulses but does not write to meleeMult, so its contribution stacks through a separate stat channel rather than compounding with this passive on the same multiplier.
EXTRACT-CANDIDATE
EXTRACT-CANDIDATE: “no ship uses Ram Prow” is true at the verified commit because a full-tree search for the string ram_prow finds it only in the passive’s own definition file and the passive index registration — no passiveId: 'ram_prow' 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 meleeMult bonus and other ramming-damage sources (per-ship base meleeMult, the weaponDamagePct channel used by the Ramming Prow artifact, and any heavy-class ramming bonuses) is not specified in the passive data file. The collision resolver multiplies the speed-scaled base ram damage by meleeMult only; whether the run-assembly layer composes multiple meleeMult sources additively or multiplicatively is not documented in the passive data.
EXTRACT-CANDIDATE: the description template reads ”+{value}% ramming damage” and the isPercent flag on the definition is true. The sibling Payload Delivery passive uses the same description-with-percent-sign convention but with isPercent: false. The two flag settings within the same family are not reconciled in the passive data files and the rendering-path difference is worth clarifying on the passives concept page.
EXTRACT-CANDIDATE: the related Ramming Prow artifact shares thematic naming and an overlapping fantasy with Ram Prow but writes its damage bonus into weaponDamagePct rather than meleeMult, so the artifact does not boost ramming damage through the same channel as this passive. Whether this is the intended design or a mismatch between artifact theme and stat channel is not specified in the artifact or passive data.