Evidence trail

How the calculator gets a number

A useful tool should make a result auditable. This page explains the current model and labels what still needs an in-game check.

Reference model · pending in-game samplesThe dataset uses the published level table, class growth rates and growth-type modifiers from the linked reference pages. It is not an official database, and equipment, unit bonuses and platform differences are not included.

Current model

growthA = halfUp((growthType1 + growthType2) / 2) + classGrowth
growthB = halfUp((growthType1 + growthType2) / 2)
baseStat = halfUp(levelBase[level] / 100 * growthA + growthB) + statOffset
finalStat = baseStat + DewBonus

// Accuracy has the documented +100 display offset.
// Movement is a class value; it is not a combat-stat formula.
// Equipment and unit bonuses remain separate.

Each stat is calculated independently. “Half-up” means a fractional value of .5 rounds away from zero for the positive values used here; the implementation does not rely on a language's banker-rounding default.

Version fields travel with data

Reference trail

Known reference cross-check

High Lord at level 50 with All-Rounder ×2 and no equipment resolves to 104 / 45 / 39 / 43 / 42 / 152 / 67 / 21 / 30 / 44 for the ten combat stats. This is a reference-page cross-check, not yet an in-game golden sample.

Dew model

The Max Dew comparison uses five modeled uses. In the current reference model, HP, Accuracy and Evasion gain +2 per use; the other displayed combat stats gain +1. The tool keeps the result labeled as a model until item-specific behavior is checked in-game.

How to promote a value from reference to verified

  1. Capture the same character/class/level in-game on a named platform and region.
  2. Record equipment, unit bonuses, permanent enhancements and battle state separately.
  3. Compare the observed number with the calculator output and log the difference.
  4. Have a second person reproduce the sample.
  5. Only then mark the row verified and update the source revision.

Report a data issue →