> For the complete documentation index, see [llms.txt](https://avania.gitbook.io/whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://avania.gitbook.io/whitepaper/gameplay/game-mode/adventure-pve.md).

# Adventure (PVE)

![](/files/ox9hZ0QAq3TjFml0Ip5Y)

Avania is a battle card game. Each round, you will play an Aether card to support your guardians and generate mana. Then, you spend your mana to make your guardians perform their special moves. The battlefield is divided into 3 lines which are frontline, midline and backline. Normally, all attacks will target the nearest enemy. If there are more than 2 targets available within the same range, your guardian will decide which one to be the target.

In adventure mode, your enemy would be androids along the path that can come with many wave. the higher the rank of android you can defeat, you can complete you daily task faster. 

Complete a daily task, then you will be rewarded by  NOVA. 


---

# 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://avania.gitbook.io/whitepaper/gameplay/game-mode/adventure-pve.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.