> For the complete documentation index, see [llms.txt](https://rouniverse.gitbook.io/wiki/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://rouniverse.gitbook.io/wiki/server-feature/undefined/undefined-4.md).

# 𝐒𝐮𝐩𝐞𝐫 𝐌𝐨𝐧𝐬𝐭𝐞𝐫 𝐚𝐧𝐝 𝐒𝐮𝐩𝐞𝐫 𝐌𝐕𝐏

## Super Monsters & Super MVPs

Super Monsters and Super MVPs are empowered versions of standard monsters, mini-bosses, and MVPs in Universe RO. These enemies spawn with a distinct glowing aura, significantly increased stats, and provide high-risk, high-reward encounters that encourage group hunting.

### Super Monsters

Super Monsters are empowered variants of regular field monsters and mini-bosses.

* Visual Indicator: Glowing aura effect.
* Spawn Chance: 50% chance for eligible monsters to spawn as a Super variant.
* Scaling Mechanics: Stat boosts scale progressively based on the monster's level.

#### Level Scaling Table

| **Monster Level** | **Stat Boost Rate (%)** |
| ----------------- | ----------------------- |
| 10                | +0.15%                  |
| 20                | +0.3%                   |
| 30                | +0.45%                  |
| 40                | +0.6%                   |
| 50                | +0.75%                  |
| 60                | +0.9%                   |
| 70                | +1.05%                  |
| 80                | +1.2%                   |
| 90                | +1.35%                  |
| 99                | +1.5%                   |

### Super MVPs

Super MVPs are heavily boosted versions of standard MVP bosses. They spawn with a unique glowing aura and receive randomized stat increases within fixed ranges.

#### MVP Stat Multipliers

| **Attribute**                             | **Boost Range (Min \~ Max)** |
| ----------------------------------------- | ---------------------------- |
| HP                                        | +100% \~ +500%               |
| ATK                                       | +100% \~ +300%               |
| FLEE                                      | +100% \~ +300%               |
| HIT                                       | +100% \~ +300%               |
| DEF                                       | +100% \~ +150%               |
| MDEF                                      | +100% \~ +150%               |
| Base Stats (STR, AGI, VIT, INT, DEX, LUK) | +100 \~ +200 flat bonus      |

### MVP PvP Mode

To heighten competition, MVP maps dynamically activate PvP mechanics whenever an MVP monster is alive on the map.

#### Map PvP Rules

* Activation: PvP is forcibly active while the MVP lives.
* Minimum Level Requirement: Base Level 30.
* PvP Level Gap: Players can only engage in combat with other players within a 10-level range of their own base level.


---

# 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://rouniverse.gitbook.io/wiki/server-feature/undefined/undefined-4.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.