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

# Automated Events

Automated Events — current Bloodlust RO guide, reviewed 27 September 2026.

{% hint style="info" icon="party-horn" %}
**A random server event automatically begins every two hours.** The Automated Event Manager keeps activities running throughout the day without requiring a GM to manually start every event.
{% endhint %}

## ⚡ Quick Info

|                          |                                    |
| ------------------------ | ---------------------------------- |
| **Frequency**            | Every 2 Hours                      |
| **Registration Command** | `@joinevent`                       |
| **Point Command**        | `@eventpoints`                     |
| **Winner Reward**        | 3–5 Event Tickets + 5 Event Points |
| **Participant Reward**   | 1 Event Ticket + 1 Event Point     |
| **Current Event Pool**   | 5 Events                           |

## 🕒 Event Schedule

A random event is selected at the following **server times**:

|           |           |           |           |
| --------: | --------: | --------: | --------: |
| **00:00** | **02:00** | **04:00** | **06:00** |
| **08:00** | **10:00** | **12:00** | **14:00** |
| **16:00** | **18:00** | **20:00** | **22:00** |

{% hint style="success" icon="shuffle" %}
The Event Manager prevents the **same event from being selected twice in a row**.
{% endhint %}

## 🚪 How to Join

1. Watch for the automated event announcement.
2. Wait for registration to open.
3. Use **`@joinevent`** during the registration period.
4. Enter the event and follow its specific objective.
5. Complete the event or remain registered for the appropriate reward.

{% hint style="warning" icon="clock" %}
Registration is only available for a short period after an event opens. Join as soon as the server announcement appears.
{% endhint %}

## 🎁 Event Rewards

| Result                     | Event Tickets | Event Points |
| -------------------------- | ------------: | -----------: |
| **Winner**                 |       **3–5** |        **5** |
| **Registered Participant** |         **1** |        **1** |

Winners are marked by the Event Manager and **do not also receive the participation reward** for the same event.

Use **`@eventpoints`** at any time to check your current Event Points.

## 🎮 Current Automated Event Pool

<table data-view="cards"><thead><tr><th></th><th></th></tr></thead><tbody><tr><td><strong>💣 Bombring</strong></td><td>Survive five rounds of Bombrings. Players still alive at the end are winners.</td></tr><tr><td><strong>🎲 Dice</strong></td><td>Choose one of four boxes before the roll. The dice determines the safe box while players in the wrong areas are eliminated.</td></tr><tr><td><strong>⚔️ Last Man Standing</strong></td><td>A PvP survival battle. Defeat the other players in the arena and become the last player standing.</td></tr><tr><td><strong>🧟 Novice vs Zombie</strong></td><td>Survive waves of Zombies as additional Zombies appear every 20 seconds. The last surviving player wins.</td></tr><tr><td><strong>🐣 Poring Catcher</strong></td><td>Search a large group of Porings and kill the Poring with the correct name before anyone else.</td></tr></tbody></table>

## 💣 Bombring

The event runs through **five rounds**. Survive the Bombrings and remain alive through the final round to become a winner.

## 🎲 Dice

Players choose one of **four boxes** before the dice is rolled. The rolled number determines the safe box, while players standing in the wrong areas are eliminated. The event continues until winners are determined or the round limit is reached.

## ⚔️ Last Man Standing

A direct PvP survival event. Defeat the other players in the arena. The **last player standing wins**.

## 🧟 Novice vs Zombie

Zombies spawn inside the arena, with additional Zombies appearing every **20 seconds**. The **last surviving player wins**.

{% hint style="warning" icon="triangle-exclamation" %}
**Entry restriction:** You must be a **Level 1 Novice** and have an **empty inventory** before entering Novice vs Zombie.
{% endhint %}

## 🐣 Poring Catcher

A large group of Porings is spawned. Players must identify and defeat the **Poring with the correct name**. The first player to find the correct target wins.

{% hint style="success" icon="trophy" %}
**Event Tip:** Use **`@joinevent`** while registration is open. Registered non-winners remain eligible for the participation reward.
{% endhint %}

## 🔗 Related Guides

Explore [**Competitive**](/bloodlust-ro-docs/competitive.md) for PvP and MVP rankings. Use the sidebar to return to the **Events** hub.

## Spend your rewards

Use **Event Points** at the Event Shop for its current consumables. Keep **Event Tickets** for VIP quests and promotions; the two currencies are not interchangeable.

[View Event Shop consumables and restrictions](/bloodlust-ro-docs/server-modifications/point-shop-equipment.md)


---

# 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://bloodlust-ro.gitbook.io/bloodlust-ro-docs/events/automated-events.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.