> For the complete documentation index, see [llms.txt](https://digalabs.gitbook.io/whitepaper_eldarune/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://digalabs.gitbook.io/whitepaper_eldarune/eldarune-game-studio/elda-rush-moba.md).

# Elda Rush (MOBA)

Elda Rush is a revolutionary development in the world of MOBA gaming, set to take the eSports scene by storm. Elda Rush combines the strategic intensity of legendary titles like League of Legends and Dota 2 with the innovation of blockchain technology. This game will be available on both PC and mobile platforms, ensuring that gamers can immerse themselves in the action wherever they go.\
\
**Elda Rush** offers a dynamic gaming experience with various modes, including 3v3 and 5v5 battles, allowing players to assemble their dream teams and engage in epic clashes of skill, strategy, and teamwork.\
\
Like WoE, in ELDA Rush, there will be cooperative dungeons and clan battles


---

# 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://digalabs.gitbook.io/whitepaper_eldarune/eldarune-game-studio/elda-rush-moba.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.