> For the complete documentation index, see [llms.txt](https://docs.dantegames.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dantegames.com/hellmaster/consumables/packs.md).

# Packs

Packs are a important resource in Hellmaster, allowing you to obtain powerful **spells** and other **NFT cards** that will help you improve your strategy and performance in the game. These packs contain a variety of exclusive rewards and are essential for those looking to expand their collections and increase their chances of success in battles.

**How to get Packs**

To get a pack, you'll need **shards**, one of the game's currencies. Shards can be earned by defeating your opponents in Adventure Mode, in public Battle Arena matches, or by ranking up in seasonal competitions. As you accumulate shards, you'll be able to redeem them for these packs and access their special rewards.

Every time you open a **Pack**, you have the chance to obtain new **NFT cards**, key elements to improve your strategy and gain an advantage in Hellmaster's most challenging competitions.


---

# 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.dantegames.com/hellmaster/consumables/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.
