> For the complete documentation index, see [llms.txt](https://wiki.navenro.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.navenro.com/gameplay-systems/level-difference-system.md).

# Level-Difference System

NavenRO uses a custom **PvE level-difference system** to make monster level meaningful.

The system only gives an advantage when the **monster is higher level than the player**. Equal-level monsters, lower-level monsters, and a monster only 1–5 levels above you do not receive a level-gap damage advantage.

## Damage brackets

| Monster level above player | Player → Monster | Monster → Player |
| -------------------------: | ---------------: | ---------------: |
|                 0 or lower |             100% |             100% |
|                   +1 to +5 |             100% |             100% |
|                   +6 to +9 |              90% |             110% |
|                 +10 to +14 |              75% |             125% |
|                 +15 to +29 |              60% |             200% |
|                +30 or more |              40% |             300% |

### Example

A level 100 player fighting a level 115 monster has a +15 monster advantage:

* the player deals **60%** of the normally calculated damage;
* the monster deals **200%** of the normally calculated damage.

The normal rAthena damage calculation still happens first. The NavenRO level modifier is applied as an additional PvE multiplier near the end of the calculation.

## Effective monster combat stats

Higher-level monsters also receive effective combat scaling against lower-level players:

| Monster level above player | Effective monster HIT/FLEE/normal attack frequency |
| -------------------------: | -------------------------------------------------: |
|                   +1 to +5 |                                               100% |
|                   +6 to +9 |                                               105% |
|                 +10 to +14 |                                               110% |
|                 +15 to +29 |                                               115% |
|                +30 or more |                                               120% |

This scaling is dynamic. NavenRO does **not** permanently rewrite the monster's stored base stats.

The system currently affects:

* HIT when the higher-level monster attacks the player;
* FLEE when the underleveled player attacks the monster;
* normal monster attack frequency through effective attack-delay scheduling.

It does not use this mechanic to alter monster HP/SP or STR/AGI/VIT/INT/DEX/LUK.

## Where it applies

The NavenRO level-gap mechanic is intended for normal **Player ↔ Monster PvE** combat.

It is excluded from versus-map categories such as PvP, GvG/WoE/WoE:TE, and Battleground environments.

## Why NavenRO uses it

The goal is to discourage skipping too far ahead purely through gear or raw damage. Players can still challenge stronger content, but the risk rises sharply as the level gap increases.

Once the player reaches the monster's level—or exceeds it—the hidden level disadvantage disappears.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://wiki.navenro.com/gameplay-systems/level-difference-system.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.