> For the complete documentation index, see [llms.txt](https://rules.pixeldebates.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://rules.pixeldebates.com/guides/resource-management/card-draw.md). # Card Draw In general, card draw (and redraw) should be considered an important element to the game. Each player will draw up to five cards at the start of each round. ### Hand You may want to play as many tactics out of your hand as possible so that you will be able to draw 5 fresh cards. Although you may have to waste a tactic, this will get you closer to drawing your most powerful combos. There are times when you must hold a tactic in your hand for several rounds to complete a combo, but you should weigh the importance of that combo in comparison to drawing new tactics. ### Draw vs Discard Card draw mechanics can help overwhelm opponents, cycle through your deck quicker, and shift the crowd. On the other hand, cards like *Ruffle Your Feathers* force your opponent to discard, limiting your opponent's options. This can be devastating, especially combined with *Reiterate*. ### **Reshuffle** If you run out of cards in your deck to draw, the discard pile will be reshuffled into a new deck to draw from. | | | - | --- # 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://rules.pixeldebates.com/guides/resource-management/card-draw.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.