> 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/drop-level-factor.md).

# Drop Level Factor

NavenRO uses a **Level Factor for monster drops**.

Your Base Level compared with the monster's Base Level can affect the final rate at which that monster drops items.

This means that farming monsters far below—or far above—your character's level may reduce the amount of loot you receive.

## Drop Rate Table

| Player Level Compared to Monster | Drop Rate |
| -------------------------------- | --------: |
| 30 levels above or more          |       50% |
| +15 to +29 levels above          |       60% |
| +10 to +14 levels above          |       75% |
| +6 to +9 levels above            |       90% |
| +1 to +5 levels above            |      100% |
| Equal level                      |      100% |
| 1 to 10 levels below             |      100% |
| 11 to 13 levels below            |       75% |
| 15 levels below or more          |       50% |

The percentage is applied to the monster's normal NavenRO drop rate.

## Safe Farming Range

For the best normal drop rate, hunt monsters close to your own level.

Players receive **100% of the normal drop rate** when they are:

* the same level as the monster;
* up to 5 levels above the monster; or
* up to 10 levels below the monster.

Outside this range, drop rates begin to decrease.

## Examples

### Example 1 — Same Level

**Player:** Level 70\
**Monster:** Level 70

Level difference: 0

**Drop Rate: 100%**

You receive the monster's normal NavenRO drop rate.

### Example 2 — Farming a Lower-Level Monster

**Player:** Level 70\
**Monster:** Level 60

The player is 10 levels above the monster.

**Drop Rate: 75%**

A monster item that would normally have a 10% chance to drop would effectively be reduced to approximately 7.5% before other applicable modifiers.

### Example 3 — Farming Far Below Your Level

**Player:** Level 70\
**Monster:** Level 40

The player is 30 levels above the monster.

**Drop Rate: 50%**

This makes repeatedly farming very low-level monsters less efficient on high-level characters.

### Example 4 — Fighting a Slightly Stronger Monster

**Player:** Level 60\
**Monster:** Level 70

The player is 10 levels below the monster.

**Drop Rate: 100%**

You still receive the monster's normal drop rate.

### Example 5 — Fighting Far Above Your Level

**Player:** Level 50\
**Monster:** Level 65

The player is 15 levels below the monster.

**Drop Rate: 50%**

Challenging monsters far above your level may therefore be less efficient for farming even if you are able to defeat them.

## Why NavenRO Uses This System

The Drop Level Factor is intended to:

* encourage players to farm content appropriate to their level;
* reduce high-level overfarming of beginner monsters;
* make monster progression more meaningful;
* encourage a wider variety of farming maps;
* complement NavenRO's Level-Difference Combat system.

For efficient farming, choosing the **right monster for your level** matters just as much as killing it quickly.


---

# 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/drop-level-factor.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.