> For the complete documentation index, see [llms.txt](https://plan-a-labs.gitbook.io/metawara/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://plan-a-labs.gitbook.io/metawara/contents.md). # Contents The content system of Meta WAR is not merely a collection of game modes—it is a fully integrated simulation of war, where **worldbuilding, factional conflict, economic dynamics, and strategic decision-making** come together as one. By participating in each content type, players directly influence the outcome of their faction, their personal rewards, and the overall balance of the world. Meta WAR does not define “war” in a singular way. Instead, it explores war as a reflection of human intention and structured competition. This philosophy is realized through three core content pillars: * **Invasion War**: Real-time faction battles and direct combat between players * **Political War**: Staking and voting mechanics to exert strategic influence * **War for Money**: A survival challenge where only one can claim the prize, regardless of faction Each content type has its own rules, rewards, and style of play—but they are deeply interconnected. For example, voting outcomes in Political War affect buffs in Invasion War; performance in battles shapes one’s standing within a faction; and War for Money provides a solo challenge that transcends the faction system. Beyond the concept of Play to Earn, Meta WAR introduces the idea of **Play to Influence** and **Play to Evolve**. Gameplay is not about repetitive grinding—it is about making choices and proving skill in ways that visibly alter the world. This represents true agency, identity, and economic empowerment within a metaverse ecosystem. Ultimately, Meta WAR’s content is not about completing missions or farming rewards. It is about becoming part of a living history—about being a player who helps shape the fate of factions, economies, and the future of METAWorld itself. --- # 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://plan-a-labs.gitbook.io/metawara/contents.md?ask=&goal= ``` `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.