> For the complete documentation index, see [llms.txt](https://docs.kampeni.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kampeni.com/tokenomics-and-governance/character-nft-overview/minting-schedule-and-initial-pricing.md). # Minting Schedule and Initial Pricing ### Minting Events Occur at the Start and Middle of Each Chapter Kampeni is a 50 chapter story. Each chapter will have at least one minting event. While mints are random each "tranche" of characters is designed to advance the story to the next chapter. For that reason some traits may not be available in every chapter. Most tranches will be 20,000 for villagers, 7,500 for heroes, and 1-of-1s for legendary characters. Smaller tranches ensure there are sufficient characters for the game to run effectively and t prevent character inflation. ### Characters Can Be Resurrected But Not Breed, Nor Created Characters in Kampeni can only be acquired through minting or trading. There is no "breeding" or creation of characters in game. In limited cases there is an opportunity to reincarnate a character. Given characters can die, NFT character inflation does not happen in Kampeni. --- # 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://docs.kampeni.com/tokenomics-and-governance/character-nft-overview/minting-schedule-and-initial-pricing.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.