> For the complete documentation index, see [llms.txt](https://wiki.osro-revo.gg/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.osro-revo.gg/oldschool-ro/gameplay-adjustments/mvp-map-pk-rules.md).

# MVP Map PK Rules

<figure><img src="/files/I7wiiO6ORB9gixWxJRvY" alt=""><figcaption></figcaption></figure>

To keep MVP hunting competitive and thrilling, **MVP maps in OldschoolRO: Revo Classic** have special **Player Kill (PK)** rules applied at all times. These rules are designed to create a more strategic and challenging environment for MVP hunters.

***

### PK Status: Always Enabled

* **PK Mode is always ON** in MVP maps.\
  This means players can attack and be attacked by others under certain conditions.

***

### Minimum Level Requirement

* You must be at least **Level 30** to **engage in PK or be a target**.
* Players below Level 30 are **immune to PvP** on MVP maps: They cannot attack or be attacked.

***

### Reminders & Strategy:

* Stay alert when entering MVP maps, especially near spawn points or while fighting MVPs.
* Forming parties with balanced levels can help ensure mutual protection during MVP hunts.


---

# 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.osro-revo.gg/oldschool-ro/gameplay-adjustments/mvp-map-pk-rules.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.