> For the complete documentation index, see [llms.txt](https://wiki.aero-revolution.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.aero-revolution.com/events/hourly-events.md). # Hourly Events The automated events that run every hour. All of these pay **100 PvP Tickets to winners / 20 for participating** (unless noted) and need at least 3 players. ### 🕹ī¸ :00 — Last Man Standing Free-for-all PvP on an arena map; the last player alive wins. 3-minute registration, 10-minute limit. ### 🕹ī¸ :15 — Dice The **Dice Master** (quiz\_02 55, 93) rolls a die; stand on the surviving number (1–4) to advance. 10 rounds. ### 🕹ī¸ :22 — Find the Poring (even hours) Among 125 look-alike Porings, kill one of the **2 real "Poring"** monsters to win — kill a fake and you're out. Multiple winners possible. 4-minute limit. ### 🕹ī¸ :22 — Bombring (odd hours) Gear is stripped; survive 6 waves of self-destructing Bomb Porings (blast radius 5 cells). Every survivor wins. ### 🕹ī¸ :30 — Run For Your Life (Zombie) Gear stripped, movement only. Invulnerable zombies pour from four corridors, getting faster every 20 seconds. Touch one and you're out; last alive wins. ### 🕹ī¸ :45 — Disguise The **Disguise Master** (prt\_evt\_in 33, 43) turns into a random monster — first to type its name in chat wins the round. **15 rounds, 40 seconds each, 10 PvP Tickets per round won** (up to 150). --- # 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://wiki.aero-revolution.com/events/hourly-events.md?ask=&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.