> 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/currencies.md).

# Currencies

Each resource has a purpose: strengthen your squad, recruit characters or progress through fishing.

| Resource                | What it does                                                   | How it is earned                                                                                                              |
| ----------------------- | -------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------- |
| **Stardust**            | Train characters, forge basic weapons and buy fishing supplies | Tutorial rewards, eligible dungeon clears, summon duplicates, eligible gear dismantling, progress goals and Stardust Crystals |
| **Star Shards**         | Recruit characters through summons                             | Beach beta weekly goals: earn up to 50 Star Shards, equal to 50 pulls                                                         |
| **Fishing points**      | Track your fishing leaderboard score                           | Turn in fish to the Angler                                                                                                    |
| **Rift coins & points** | Track encounter progress and run scores                        | Complete encounter objectives                                                                                                 |

## Stardust strengthens. Star Shards summon.

Use **Stardust** to improve the characters and equipment you already own. Use **Star Shards** to recruit through summons.

A summon can also award Stardust. These resources serve different purposes; there is no general Stardust-to-Shard exchange announced.

## Beach beta summons

**1 Star Shard = 1 pull.** Earn up to **50 pulls per week** through the Progress journal.

| Weekly goal             | Star Shards |
| ----------------------- | ----------- |
| Catch 100 fish          | 20          |
| Clear 10 squad dungeons | 30          |
| **Total**               | **50**      |

Weekly goals reset on Monday at 00:00 UTC. This is the beach beta setup; later phases may use different rules.

## Fishing follows its own path

Turn in your catches to the Angler to earn fishing leaderboard points. Points cannot be spent or exchanged for Stardust. Buy bait and fishing supplies with Stardust.

**Pearl Dust** and **Weathered Scrap** are scrap items with no use during the current playtest.

[Explore squads & the blacksmith](/docs/first-light-and-progression/squads-and-gear.md) · [Go fishing](/docs/first-light-and-progression/fishing.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/currencies.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.