Raptor — Mechanics and Synergies

Raptor is the Nomads mount troop. An adjacent troop can ride it, combining the Raptor's stats with the rider and piercing through the frontline. The planning challenge is to build a real mount-and-rider relationship while keeping enough combat strength to reach the intended target.

Adjacency is the first requirement

Place the intended rider beside the Raptor and verify mounting during battle. A planning diagram can record the candidate relationship; it cannot guarantee that every nearby unit receives a mount or that unit assignment is identical in every battle. The number of actual mounts and riders matters independently of whether two plot names appear beside each other.

Before adding more support, inspect where the mounted units travel and which enemy they engage. Frontline piercing is useful when the unit survives and reaches an important target. A large displayed stat value alone does not establish delivery or the outcome against every opposing build.

Compare Raptor with Boar

Boar uses mount HP to increase a rider's stats. Raptor's documented relationship combines its stats with those of the rider. Those are different mechanics, so a health-scaling formula from Boar should not be pasted into a Raptor build.

This distinction affects support decisions. A Raptor plan should identify which stats are being developed and which troop is doing the riding. Do not add a support building simply because it is often used beside another mount. Read its beneficiary and check the resulting tooltip before committing more cards.

Jurassic is a modifier

Patch 30 increased the Jurassic perk's Raptor damage bonus to 20%. The perk changes a perk-equipped Raptor, not the universal base damage of every Raptor. Keep the loadout with a saved layout if you want another player to reproduce the setup.

The sources used here establish that change but do not publish an independently verified Patch 31 base-HP or damage table. Those values remain unknown in this catalogue. We also do not claim a combined-stat rounding rule, mount-allocation algorithm or measured win rate.

Avoid building around visual bugs

Patch 29 and Patch 30 added safeguards for the ghost Boar/Raptor bug. An older video showing missing or frozen riders may document a bug rather than intended behaviour. Record the current version and inspect a new run before drawing a strategic conclusion from it.

For a practical layout check, confirm adjacency, actual mounting, rider survival and useful target access in that order. If the first relationship fails, stacking more stats will not repair it. If the units reach the wrong part of the opposing army, reconsider the battle plan rather than assuming another level guarantees success.

Sources and version

Card identity and the mounted-stat relationship come from the official card reference. The Patch 30 announcement establishes Jurassic and the bug safeguards. Checked through Patch 31 / 0.9.8 on 13 October 2026. Compare both mounts in the card database.