> 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/welcome.md).

# 🌟 Welcome to NavenRO

A midrate Episode 10.1 Ragnarok Online experience with a 99/70 cap and custom gameplay systems designed to make progression feel fresh.

**NavenRO** is an upcoming **midrate Ragnarok Online server** based on **Episode 10.1**, with a **99/70 level cap** and carefully selected custom gameplay systems designed to create a fresh progression experience without losing the classic feeling of Ragnarok Online.

The goal is simple: keep the familiar world, classes, combat, and progression that players remember, while introducing new mechanics that make leveling, equipment, exploration, farming, and long-term progression more meaningful.

## Server Concept

| Feature            | NavenRO                                    |
| ------------------ | ------------------------------------------ |
| Server Type        | Midrate                                    |
| Episode            | 10.1                                       |
| Base Level Cap     | 99                                         |
| Job Level Cap      | 70                                         |
| Gameplay Direction | Classic foundation with custom progression |
| Custom Systems     | Yes                                        |

NavenRO is not designed around overwhelming players with hundreds of unrelated custom features. Each modification should have a clear purpose and fit naturally into the game.

## A Different Progression Experience

One of the main ideas behind NavenRO is that **where you level and what you fight should matter**.

The **Level-Difference System** makes monsters above your level increasingly dangerous, while the **Drop Level Factor** makes farming monsters far outside your level range less rewarding.

Combined with **Equipment Durability** and other custom mechanics, progression becomes less about rushing directly to one optimal map and more about building your character through the world.

## Explore the Wiki

Use the navigation on the left to explore NavenRO's player-facing features, including:

* Getting Started
* Gameplay Systems
* Level-Difference System
* Drop Level Factor
* Equipment Durability
* Auto Attack
* VIP System
* Marketplace
* Auction House
* Streamer System
* 28-Day Daily Rewards
* Items & Economy
* NPCs
* Events
* Commands
* Change Logs
* FAQ

This wiki focuses on **what players can see, use, and experience**.

> NavenRO is an independent community server and is not affiliated with Gravity Co., Ltd.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://wiki.navenro.com/welcome.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
