> 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/learn-to-play/victory-objectives.md).

# Victory objectives

You can win the game in two different ways, and you only need one of them to achieve victory:

* Win all of your opponent's gems.
* The opponent's hero reaches zero health points.

This means that in order to avoid being defeated by your opponent, you must conserve your gems and be very careful that your hero does not lose all of his health points. Generally, the winner of a match is decided when one of the players collects all of the opponent's gems; however, on some occasions, a player may become careless, causing his hero to die, thus losing the match.

## How to earn gems

In the next section, you'll find out how you can **earn gems** in Hellmaster by getting a stronger card **combination** than your opponent. If you want to learn more about how to form the best card combination, click the "How to Earn Gems" button to learn more.


---

# 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/learn-to-play/victory-objectives.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.