> For the complete documentation index, see [llms.txt](https://wiki.metados.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.metados.com/gameplay/battle-royale.md).
# Battle Royale
## Action Phase
The combat system is fast-paced and intense, with engagements happening at any time and anywhere. Players must be on their toes at all times and strategize how to plan their route to get the best equipment. This strategy element makes the gameplay more fun and exciting. Players have to decide if they want to fight or take time to collect items and get ready.
## Classes & Abilities
Customize your hunter with different classes such as offensive, defensive, support, and tech, each with unique abilities and traits. The ability system adds strategy and depth to the battle royale gameplay with a passive ability and an ultimate ability for each Hunter. Mastering each Hunter's abilities is important to succeed.
## Weapons
The game has many different weapons like assault rifles, submachine guns, light machine guns, shotguns, sniper rifles, pistols and grenades. Each weapon has its own specifications, like varying damage, range, accuracy, and rate of fire. Players can equip two weapons and attach scopes, stocks, barrels, and magazines to improve their performance. Attachments in the game can be used to upgrade weapons. These include optics, hop-ups, magazines, stocks, and barrels. You can find them on the game's map or by looting defeated enemies.
---
# 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.metados.com/gameplay/battle-royale.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.
