Client damage-reduction divisors

Mechanic reference

Encounter rules

6 minute read

An encounter-stage reference for comparing Battle Lab damage against named target difficulties.

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

How this damage is calculated

Calculation order

Post-modifier family damage ÷ resolved encounter divisor → pre-cap encounter result

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 encounter reduction

Encounter A divisor

Encounter B divisor

Your calculated result

Changing only the encounter divisor from 3 to 5 lowers the result from 80,000 to 48,000.

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: divisor 3 versus divisor 5

Worked example

The same build and skill reach 240,000 damage before encounter reduction. Only the selected encounter form changes.

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 encounter reduction: 240,000
Encounter A divisor: 3
Encounter B divisor: 5

1
Encounter A result 240,000 ÷ 3
80,000
2
Encounter B result 240,000 ÷ 5
48,000
3
Absolute difference 80,000 − 48,000
32,000
4
Relative decrease 32,000 ÷ 80,000 × 100
40% lower

Example result

Changing only the encounter divisor from 3 to 5 lowers the result from 80,000 to 48,000.

Use the divisor attached to the exact target form and difficulty you selected. Do not treat it as Physical DEF, Magic DEF, or a character damage modifier.

Resolve the encounter form

A named monster can have multiple encounter or difficulty records with different reduction behavior. Select the exact form used by Battle Lab before interpreting the divisor, and keep that form fixed across build comparisons.

The divisor belongs to the encounter stage. It must not be hidden inside Magic DEF, Physical DEF, race damage, or Final Damage because those values answer different player questions.

Use deterministic evidence

The verified handler records the resolved divisor and its input state in the ledger. If a required encounter relation is stale or unavailable, the result must not remain Verified and the library must not publish an exact family claim for that scope.

Name the target and difficulty.
Keep the divisor separate from display and HP-loss caps.
Do not transfer one encounter form’s value to another.

Compare before caps

Inspect the pre-cap encounter result before looking at displayed damage. A cap can hide an improvement even when the underlying attack, defense, modifiers, and divisor stages changed correctly.

Apply this to your build

Use the same verified event at one named difficulty, change one build input, and compare both the post-divisor value and the final capped values.

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.