> For the complete documentation index, see [llms.txt](https://docs.spellsofgenesis.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.spellsofgenesis.com/spells-of-genesis/cards/in-game-cards.md). # In-Game Cards Within the Spells of Genesis game, players have the opportunity to amass a collection of in-game cards, which carry the potential to be upgraded, evolved, and ultimately fused into their final stages. Through a process dubbed 'Blockchainization,' these cards can be minted on a Blockchain, transitioning them into NFTs. Acquiring these in-game cards can be achieved in various ways. Players may embark on campaigns across the map, striving to win stars, or alternatively, opt to purchase them directly from the in-game store. Whether selecting individual cards or packs of cards, players can utilize gold or gems to enhance their chances of securing cards that are rare, epic, or even legendary in nature. Prepare yourself for a thrilling hunt for cards! You can check all the infomations about the in-game cards and their evolution in our [cards explorer](https://spellsofgenesis.com/cards). --- # 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.spellsofgenesis.com/spells-of-genesis/cards/in-game-cards.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.