> For the complete documentation index, see [llms.txt](https://meversedex.gitbook.io/pocketbattlesnftwar/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://meversedex.gitbook.io/pocketbattlesnftwar/pocket-battles/game-system/hero-soldier.md). # Hero / Soldier Pocket Battles: NFT War consists of 4 races: Human, Beast, Divine, and Undead. Players can combine a total of 12 NFT Heroes, 19 Heroes, and 39 soldiers to create their own powerful squad to fight. Heroes are divided into four types: legends, elites, and rare, depending on their level of rareness, and assault, distance, assassin, and support, depending on their combat orientation. In addition, each hero has its own active and passive skills, so players have to select and play the hero according to the battle situation. Soldiers are divided into legends, elites, rare, and normal levels according to their level of rarity, and like heroes, they have their own attributes and skills. Players can participate in various game modes, including Campaign mode that has 10,000 stages to clear with your swad, Castle Defence to defend a total of 6 attacks, Boss Rivals to defeat large boss monsters, PvP arena, Legend's Tower to climb a total of 600 floors, and Battle Camp for each race. Through the rewards from various game modes, players can acquire Pocket Stone to build a more powerful squad by strengthening heroes and soldiers. Pocket Stone can also be exchanged with Pocket Token, MEVerse-based P2E Token. --- # 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://meversedex.gitbook.io/pocketbattlesnftwar/pocket-battles/game-system/hero-soldier.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.