# Gameplay Overview Chicken Saga gameplay features an **auto-battler system** where players can use ERC-1155 battle items to leverage their chicken's stats and Instincts for an edge. Each match is played in a best-of-3 rounds format. Players must carefully utilize all stats, adapting to opponents' strengths and weaknesses. Players can take their chickens into battles to compete for rewards. However, if a chicken loses, there is a risk that it may be **permanently lost (burned)**. This % chance of a chicken “dying” serves as a mechanism to control the overall chicken population in Chicken Saga.

When struck by a fatal blow, Takipsilim does not claim their spirits; instead, he observes in silence, his fiery eyes unwavering. Even beings blessed with immortality are reminded of life’s fragile balance.

### Metagame Loop Chicken Saga is built around a dynamic **metagame loop** that rewards players for engaging in various activities such as battling, breeding, crafting, and resource management. At the core of this loop is the chicken, which can be used in multiple ways depending on your playstyle. We’ve designed the system to support a **sustainable game economy** by encouraging players to adopt different roles or **archetypes** such as breeders, battlers, grinders, or crafters. Each path interacts with the ecosystem in a meaningful way, creating value and driving resource flow. By tying rewards to effort, risk, and decision-making, Chicken Saga ensures that players contribute to the economy while shaping their own progression. Every part of the loop is interconnected to maintain long-term balance and fun.
--- # Agent Instructions: 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: ``` GET https://whitepaper.chickensaga.com/gameplay-overview.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.