> For the complete documentation index, see [llms.txt](https://rugzombie.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://rugzombie.gitbook.io/docs/basic-information/gameplay/ally-system.md). # Ally System ## Ally Drafting Row The Ally Drafting Row consists of 5 Ally Cards. Each player chooses 1 (non leader) card for to be placed into the all row. The other 3 ally cards will be randomly generated from the RugZombie collection. Turn the first 3 allies over before battle 1. These allies are available during the first battle. During the second battle, turn over the 4th ally card pile to reveal the ally noble. If there is a 3rd battle, turn over the final ally card. ## Claiming an Ally Whenever a card is played into the battlefield, add ally points according to its mint number (equivalent) to your alliance pool. This pool can be drawn upon on your turn to claim an ally. Claiming an Ally can be done on a player’s turn in addition to playing card abilities or playing cards. The number of ally points needed to attempt any alliance is X. When attempting an alliance, you will spend the required ally points, and be able to claim an ally to place into your hand. --- # 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://rugzombie.gitbook.io/docs/basic-information/gameplay/ally-system.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.