> For the complete documentation index, see [llms.txt](https://castleoverlord.gitbook.io/whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://castleoverlord.gitbook.io/whitepaper/nft-model/booster-packs.md).

# Booster Packs

NFTs in Castle Overlord can be purchased (minted) through booster packs. Each booster pack may contain a single NFT unit or a bundle of multiple units. A booster pack’s theme will also determine the unit type it contains and the faction.

Here are a few examples of booster packs and their contents:

* **Steampunk Trooper Pack.** Contains 1 trooper from the Steampunk faction.
* **Cyber Samurai Trooper Bundle.** Contains 5 troopers from the Cyber Samurai faction.
* **Single Color Military Trooper Pack.** Contains 1 trooper from the Military faction with same-colored unit parts.

Units that players gain through booster packs consist of randomized parts. The randomizer affects the following aspects of a part:

* **Part appearance.** This determines the 3D mesh of a part installed in a unit. 
* **Type variant.** Some parts have type variants, such as the Steampunk faction’s weapon part which may consist of a punch-type weapon or a smash-type weapon. 
* **Part rarity.** This determines the quality of a part, whether it’s common, rare or legendary. Higher rarity results in a higher stat. Legendary parts are only obtainable as long as the stock lasts.
* **Appearance variant.** Once the 3D mesh has been determined, this calculation is executed to apply the material (color and texture) to the mesh. There are 5 available variants for each 3D mesh.


---

# 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://castleoverlord.gitbook.io/whitepaper/nft-model/booster-packs.md?ask=<question>&goal=<endgoal>
```

`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.