# Gameplay

{% hint style="warning" %}
**This whitepaper is outdated:**

We are currently in the process of updating the whitepaper to reflect our most ambitious development phase yet. Stay informed by [signing up](https://gmr.center/sign-up) or joining our [Telegram channel](https://t.me/gmrcenter).

We have kept this version online for informational purposes only.
{% endhint %}

![](/files/zriUp7OEAsA5YTd9xzQp)

Battle Leet is a multi-round arena game where players fight to win rewards. By winning a single round players can earn $GMR, and by winning battles players can win Asset Parts and Asset Loot-Boxes.

Players will use skill and cunning as they navigate in 3D space inside the Battle Arena, avoiding obstacles and enemies, including Battle Droids, to land that perfect shot.

### Cool-Downs

All Leets incur an energy cost for participating in battles. This will lead to a cool-down period for that particular Leet. Players can speed up the cool-down process through special potions, or as we say: Mechanic Packs, or simply use another Leet from their collection.

### Technical Aspects

Battle Leet follows as much as possible the usual logic of things when it comes to multiplayer-connected games. Since we are dealing with a PvP Server authoritative game, the gameplay logic is handled by the server via gamemode or other such classes, while things that the character controls are handled in control-specific classes.

One of the core components in Battle Leet is the gameplay ability system (GAS for short) which allows us to develop a data-driven architecture when it comes to abilities, so we can tweak them and iterate them in real-time.

Abilities will be generally split into parts in order to modify them fast. Gameplay Cues and Gameplay Effects are likely to be tweaked constantly, as necessary.


---

# Agent Instructions: 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:

```
GET https://whitepaper.gmr.center/battle-leets/gameplay.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.