> For the complete documentation index, see [llms.txt](https://everfall.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://everfall.gitbook.io/docs/first-light-and-progression/dungeons.md).

# Dungeons & minigames

A squad to prepare. A fight to learn. Another reason to try again.

Dungeons turn your character choices and equipment into a challenge. Bring up to three members, choose a destination and see how far the team can go.

## Make the lineup count

Basic attacks happen automatically. Your choices come from the team you bring, the equipment you give them and the moment you commit a skill.

Watch health and energy. Interrupt an attack, time a heal or push for the finish. When a run ends, there is another combination to try.

## Expect a few surprises

Some encounters ask for more than combat. Short challenges break up the journey, with their patterns and discoveries left for players to find.

## Return stronger

Earn Stardust, prepare your next upgrades and work toward harder encounters. Eligible higher-difficulty clears can lead to stronger equipment.

[Build your squad](/docs/first-light-and-progression/squads-and-gear.md) · [Understand your rewards](/docs/first-light-and-progression/currencies.md)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://everfall.gitbook.io/docs/first-light-and-progression/dungeons.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.