> For the complete documentation index, see [llms.txt](https://warbuds.gitbook.io/war-manifesto/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://warbuds.gitbook.io/war-manifesto/business-model.md).

# Business Model

By offering a range of different ways for players and members to engage with the project and to support it financially, we developed a sustainable model that allows us to continue offering a high-quality experience to all members.

WarBuds will have a variety of sources that ensure the longevity of the project, including tournament registration fees, in-game currency purchases, sponsorships, and NFTs.

In addition, WarBuds will focus on building a strong and passionate community of players and fans by fostering a sense of camaraderie among players and by continuously improving and innovating our gameplay features and offerings.

Finally, WarBuds will concentrate on building collaborations with other projects and gaming communities. By working with other organizations and teams, we create new opportunities for growth and build a larger and more diverse community.


---

# 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://warbuds.gitbook.io/war-manifesto/business-model.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.