Living stats: why these numbers are always current

Always up to date

The numbers on a plant page aren't typed in by hand, and they aren't a snapshot from some past patch. Move names, move power, HP, ATK, DEF, retreat cost, and the invasive damage multiplier are all computed from the same card the battle screen builds, at the moment you open the page. When a move is renamed or a stat is rebalanced, the wiki shows the new value on your next visit — automatically, with nothing to republish.

A plant's infobox (photo, family, conservation status, toxicity, edibility, native and invasive regions, category) works the same way: it is read straight from the live species record, never copied.

What's live and what's written

Two things make up a plant article:

• Live values — updated automatically: move names, descriptions, and unlock levels; each move's power as a native and as an invasive; HP, ATK, DEF, initiative, and retreat cost; the invasive ATK multiplier; and the prizes conceded on a knockout. These are a snapshot at level 18, where a plant's full kit is unlocked.
• Written analysis — updated by an editor: the strategy, the native-versus-invasive framing, which passive abilities and trait keywords the plant carries and what they do, and its succession match-ups. That is judgement rather than a number, so a person writes it — and revisits it when the game's balance shifts.

So a routine rebalance never makes a page wrong: the figures move on their own, and only a change in how a plant plays calls for an editor.

For contributors: writing with tokens

Article text is stored with {{token}} placeholders wherever an engine value belongs. Each token resolves at render time against the plant's live card, so an author never types a raw number or a move name — they write the token, and it stays correct on its own.

The rule: never bake in a number or a move name — use a token. Reference the snapshot level with {{card.level}} rather than writing "18". An unknown token renders as its literal {{…}}, so a typo stands out in review.

Token	Resolves to
{{card.level}}	the snapshot level (18)
{{move.starter.name}} · {{move.advanced.name}} · {{move.ability.name}}	the plant's actual move names
{{move.starter.desc}} · {{move.starter.unlock}} · {{move.starter.sun}}	a move's effect text · unlock level · Sun cost
{{move.starter.power.native}} · {{move.starter.power.invasive}}	a move's expected damage, per nativity (also advanced)
{{stat.native.hp}} · {{stat.native.atk}} · {{stat.invasive.hp}} · {{stat.invasive.atk}}	combat stats, per nativity
{{stat.def}} · {{stat.initiative}} · {{stat.retreat}}	base DEF · initiative · retreat Sun
{{role.atkMult}} · {{role.prize}}	invasive ATK multiplier · prizes conceded on a knockout

Keep the conditional framing — whether a plant is toxic, thorny, or edible, which passives it carries, and its succession group — as written prose; those are judgement, not live scalars. The full authoring guide ships with the plant-page routine spec.

Related

• Stats · Moves · Nativity · Weaknesses & resistances