> For the complete documentation index, see [llms.txt](https://wiki.arkvalkyrie.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.arkvalkyrie.com/server-features/world-boss-event.md).

# World Boss Event

The World Boss Event is a large-scale server activity built around a global objective, multiple monster waves, a final boss encounter, contribution rankings, World Boss Points, and claimable rewards.

### Current Player-Facing Trigger

The World Boss NPC tracks the server's total monster kills. The current objective is:

> **1,000,000 server-wide monster kills**

Every eligible monster kill made while the World Boss is inactive increases the shared counter. When the requirement is reached, the event start logic is triggered.

{% hint style="info" %}
The core event script also supports scheduled starts and separate MVP/monster-kill requirements. In the current file, weekday and clock labels are present as examples but are commented out.
{% endhint %}

### NPC Location

| NPC        | Map       | Coordinates |
| ---------- | --------- | ----------: |
| World Boss | Ark Lobby |  `104, 263` |

The NPC displays the current server kill count and provides access to the Point Shop, reward claims, reward previews, rankings, and system information.

### Event Flow

1. The server-wide trigger condition is completed.
2. A random event map is selected.
3. A five-minute preparation announcement sequence begins.
4. Wave 1 monsters appear.
5. Each cleared wave is followed by a short countdown.
6. After the final wave, the World Boss appears.
7. The server records wave kills, player damage, and guild damage.
8. Ranking rewards are stored in the database.
9. Eligible players return to the World Boss NPC to claim their rewards.

### Possible Event Maps

The event may select one of the following maps:

* Prontera
* Izlude
* Payon
* Morocc
* Al De Baran
* Alberta
* Comodo
* Geffen

### Monster Waves

#### Wave 1

* Dark Lord ×2
* Dark Illusion ×10
* Zherlthsh ×5
* Phendark ×10
* Mimic ×20
* Alarm ×15

#### Wave 2

* Lord of Death ×2
* Bloody Murderer ×10
* Succubus ×10
* Incubus ×10
* Nightmare Terror ×20
* Fallen Angel ×25

#### Wave 3

* Ifrit ×2
* Salamander ×15
* Kasa ×15
* Imp ×25
* Explosion ×30
* Lava Golem ×20

The next stage begins only after all monsters in the current wave have been defeated.

### Possible Final Bosses

The final World Boss is selected randomly from the configured monster IDs:

* `Ifrit`
* `Valkyrie Randgris`
* `Falling Bishop`
* `Beelzebub`

The exact monster name is resolved from the active server monster database.

### Contribution Systems

#### Wave Kill Ranking

Tracks the number of event-wave monsters defeated by each character.

#### Player Damage Ranking

Tracks the total damage dealt by each character to the final World Boss.

#### Guild Damage Ranking

Combines final-boss damage by guild and ranks guilds by their total contribution.

{% hint style="warning" %}
Guild Damage rewards are claimable only by the guild leader in the current implementation.
{% endhint %}

### Ranking Rewards

The current configuration rewards the Top 3 in each ranking category.

<table><thead><tr><th width="93" align="right">Rank</th><th>Reward IDs</th></tr></thead><tbody><tr><td align="right">1</td><td>Item <code>Light White Potion Box</code> ×5 and Item <code>Light Blue Potion Box</code> ×5</td></tr><tr><td align="right">2</td><td>Item <code>Light White Potion Box</code> ×3 and Item <code>Light Blue Potion Box</code> ×3</td></tr><tr><td align="right">3</td><td>Item <code>Light White Potion Box</code> ×1 and Item <code>Light Blue Potion Box</code> ×1</td></tr></tbody></table>

The same reward quantities are currently configured for:

* Wave Kill Ranking
* Player Damage Ranking
* Guild Damage Ranking

Rewards are saved after the event and must be claimed from the World Boss NPC.

### Claiming Rewards

1. Speak to the World Boss NPC.
2. Select **Claim Rewards**.
3. Choose Wave Kills, Player Damage, or Guild Damage.
4. Select the event record.
5. Review the item list.
6. Confirm the claim.

The system verifies inventory space and carrying capacity before issuing the items. A claimed record cannot be claimed again.

### World Boss Points

The event can award `#WBPOINTS` for defeating configured monsters.

| Monster                   |          Points |
| ------------------------- | --------------: |
| Dark Lord                 |              10 |
| Lord of Death             |              15 |
| Ifrit                     |              20 |
| Other configured monsters | 1 default point |

### Direct Drops and Final Hit Rewards

Selected monsters may scatter item drops around their death location. Some configured monsters also grant a direct reward to the character who delivers the final hit.

The drop distance is currently configured to a radius of `14` cells.

### Rankings History

The NPC can display up to 30 entries for recent:

* Wave Kill rankings
* Player Damage rankings
* Guild Damage rankings

Ranking records are associated with the event's timestamp, allowing previous results to remain available after the event ends.

### Event Completion

After the World Boss is defeated:

* The active-event state is cleared.
* The final-blow character is announced.
* Top ranking results are calculated.
* Rewards are written to the claim tables.
* Players are directed back to the World Boss NPC.


---

# 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.arkvalkyrie.com/server-features/world-boss-event.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.
