> 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/squads-and-gear.md).

# Squads & the blacksmith

Bring up to three characters into a dungeon. Melee, ranged and support roles give you different ways to build the team.

## Prepare your squad

Choose members, arrange their positions and assign equipment before entering. Stardust pays for character training and equipment enhancements. Characters can reach level 60; training costs rise as they level up.

Equipment belongs to a shared inventory. Giving an item to another character moves it from its previous owner.

## The blacksmith

Forge or improve a basic sword, bow or staff. Harder dungeon encounters can lead to stronger equipment as your squad progresses.

## More characters, more choices

Star Shards are used for summons. New recruits open up different combinations; materials and duplicates give Stardust instead. During the beach beta, weekly goals award up to 50 Star Shards for 50 pulls.

[Currency guide](/docs/first-light-and-progression/currencies.md) · [Dungeons](/docs/first-light-and-progression/dungeons.md) · [Future gear preview](/docs/first-light-and-progression/progression.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/squads-and-gear.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.