> For the complete documentation index, see [llms.txt](https://dark-elf-online.gitbook.io/dark-elf-online-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dark-elf-online.gitbook.io/dark-elf-online-docs/events/events/monster_hunt.md).

# Monster Hunt

Hunt down a King Poring together. The last hit wins the biggest prize, every active hunter gets a share.

<figure><img src="https://1554490237-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcDFEKhSgA9v4R1NmIHKc%2Fuploads%2Fgit-blob-84932f6490bdfd40b79107e76242eed3b29c07d3%2Fmonster_hunt.jpg?alt=media" alt="Monster Hunt in game"><figcaption><p>The Monster Hunt arena and its King Poring. Monsters placed for the picture; in a real round the event spawns them.</p></figcaption></figure>

## Quick Guide

**Availability:** Runs on the automatic event schedule, see the [Event Guide](/dark-elf-online-docs/events/events.md). Staff can also start it by hand.

* When "\[Monster Hunt] A King Poring is coming!" is announced, you have **3 minutes** to join: type `@joinhunt` or use **Join event** in `@events`. You wait in the arena (`2025arena6 99 79`).
* At least 2 hunters are needed, or the hunt is cancelled.
* Then a **King Poring** (140,000 HP) appears somewhere in the arena. A map message tells you where it was seen, every minute.
* You have **10 minutes** to bring it down. If time runs out, nobody wins.

**Rules:**

* Death puts you out: you are revived and sent to Elf Island. Logging out or leaving the arena also puts you out. You cannot rejoin a running hunt.
* Helpers must be active: if you did not move, attack or talk in the last 2 minutes before the kill (or you are on autotrade), you get nothing.
* You cannot join while dead, while vending or in a chat room, from another event, or with a second character from the same connection.
* The King Poring drops no items.

## Items

| Role                                         | Item                                                                                                                                                               | Amount |
| -------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------ |
| Last hitter                                  | <p><img src="https://static.divine-pride.net/images/items/item/1002069.png" alt="Proof of Donation" data-size="original"></p><p> Proof of Donation ID: 1002069</p> | 3      |
| Every other active hunter still in the arena | <p><img src="https://static.divine-pride.net/images/items/item/1002069.png" alt="Proof of Donation" data-size="original"></p><p> Proof of Donation ID: 1002069</p> | 1      |

**Note:** Everyone goes back to `mainprt 210 172` after the hunt. If your inventory is full, the prize is mailed to you.

## Commands

| Command     | What it does                                        |
| ----------- | --------------------------------------------------- |
| `@joinhunt` | Joins Monster Hunt during the 3-minute registration |
| `@events`   | Event menu: current event, **Join event**, schedule |


---

# 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://dark-elf-online.gitbook.io/dark-elf-online-docs/events/events/monster_hunt.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.
