> For the complete documentation index, see [llms.txt](https://warena.gitbook.io/warena/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://warena.gitbook.io/warena/gameplay/phase-1-2d-tower-defence-game.md).

# Phase 1: 2D Tower Defence Game

We aim to give players ownership over their in-game assets which will allow these assets to increase in value through active play. This is a key component of the play-to-earn business model. By participating in the in-game economy, players create value for themselves, other players and the developers. This constant chain of value-adding activities feeds back into the Warena community, in which we are all a part of.

Players will be rewarded with in-game assets. These digital assets can be anything ranging from cryptocurrencies to in-game resources that are tokenized on the blockchain. This is how we arrived at our conclusion that the Play-to-Earn (P2E) business model works perfectly with an NFT-enabled gaming experience.


---

# 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://warena.gitbook.io/warena/gameplay/phase-1-2d-tower-defence-game.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.