Race, size, and MVP/Mini modifiers

Mechanic reference

Damage modifiers

6 minute read

A target-profile checklist for deciding exactly which qualified bonuses activate.

By RO Codex Team Updated August 7, 2026 Foundational mechanic · Reviewed August 7, 2026

How this damage is calculated

Calculation order

Named target profile → matching race, size, and class sources → qualified modifier groups

Follow this order with your own build, but use the grouping and special branches shown by your skill family. The numerical example below demonstrates the mechanic rather than claiming one universal formula for every skill.

Build calculator

Enter the values from your character, skill, and target. Results update as you type, stay in your browser, and are never saved.

Instant result

Your character stats

Enter the totals from the build you use with the selected hero and attack. Action-specific, target-qualified, and Final Damage modifiers remain separate stages.

Damage before target bonuses

All Race Damage

Large Damage

MVP Damage

Your calculated result

When all three qualifiers match as separate stages, the example rises from 10,000 to 15,180.

This calculator follows the ordering described on this page. Skill-specific rewrites and unsupported build lanes still require their own verified family support.

Example calculation: All Race, Large, and MVP Damage

Worked example

A hit reaches 10,000 before target-qualified bonuses. The selected target is a Large MVP, and this build has +20% All Race Damage, +15% Large Damage, and +10% MVP Damage recorded as separate stages.

Use your own values

Replace the sample inputs with your character stats, selected skill level, active modifiers, and actual target. The values below are not a recommended build, damage target, or expected result for your character.

Damage before target bonuses: 10,000
All Race Damage: +20% (×1.20)
Large Damage: +15% (×1.15)
MVP Damage: +10% (×1.10)

1
Race stage 10,000 × 1.20
12,000
2
Size stage 12,000 × 1.15
13,800
3
MVP stage 13,800 × 1.10
15,180
4
Total gain 15,180 − 10,000
5,180 (+51.8%)

Example result

When all three qualifiers match as separate stages, the example rises from 10,000 to 15,180.

Check your target’s exact race, size, and class. A non-matching source contributes nothing, and a family that combines sources inside one group must use that grouping instead.

Use resolved target properties

Every target-qualified bonus must be checked against the selected monster’s published race, size, element, and class. MVP Damage applies to an MVP scope; a race bonus applies only to the named race; size damage uses the target’s resolved size.

All Race Damage applies the same value across every race. A named source such as Demi-Human Damage remains target-specific and activates only against that named race.

Keep groups and sources visible

Several matching sources can contribute to one event, but their grouping and ordering belong to the formula family. Record each source and its scope before combining values, and keep inactive sources distinguishable from missing data.

Confirm the exact monster form and difficulty.
Treat MVP and Mini as distinct when the source does.
Do not activate a bonus from a similar-looking target.

Build target-specific presets

A specialized preset can outperform a general build against its matching target and lose elsewhere. Evaluate both against named monsters with the same skill and progression state before deciding which preset to save.

Apply this to your build

Compare one race-qualified item against an always-active skill bonus on the intended farming monster and one non-matching MVP. Keep all other equipment unchanged.

Evidence and freshness

RO Codex publishes Verified family articles only while the accepted handler and its required evidence remain current. Read the data quality standards for the site-wide accuracy contract.

RO Codex formula trust contract: Defines Verified, Estimated, and Unavailable behavior and requires family-specific fail-closed calculation.
Player-facing calculation ledgers: Ordered Battle Lab steps keep attack, defense, modifiers, encounters, and caps readable without exposing internal references.