> For the complete documentation index, see [llms.txt](https://arcusgame.gitbook.io/arcus/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://arcusgame.gitbook.io/arcus/development-roadmap/phase-ii-utility.md).

# Phase II - Utility

Creating a utility for game finance is crucial in maintaining sustainability and creating more incentive opportunities for players. Utility tokens can provide players with unique benefits, such as exclusive access to tournaments or discounts on in-game items. These tokens can also create a sense of ownership and loyalty to the game, encouraging players to remain engaged and invested in the long term.

Utility tokens can also serve as a means of exchange for in-game assets, creating a secondary market for players to trade virtual items. This can provide players with a sense of agency and control over their virtual assets, enhancing the gaming experience.

Moreover, by creating a utility for game finance, game developers can create a sustainable revenue stream that can support ongoing development and maintenance of the game. This, in turn, can attract more players and foster a thriving community.

Overall, creating a utility for game finance can improve player engagement, foster community building, and generate sustainable revenue for game developers. See our Utility proposition fpr Phase II.


---

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

```
GET https://arcusgame.gitbook.io/arcus/development-roadmap/phase-ii-utility.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.