> For the complete documentation index, see [llms.txt](https://lethium.gitbook.io/lethium-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://lethium.gitbook.io/lethium-docs/gameplay/echoes-advanced.md).

# Echoes: advanced settings

Echoes in depth: substat pool, levelling curve, salvage, presets and terminals.

Everything below lives in `plugins/ClickEmCore/modules/echoes.yml`. Start with [Echoes](/lethium-docs/gameplay/echoes.md).

### Substats (`substats:`)

The pool every rolled line comes from. Each entry: `stat` (see [Stats](/lethium-docs/configuration/stats-and-limits.md)), `min` and `max` (the **Legendary** range, others scale by `roll-multiplier`), `weight` (how often it is picked) and `bias` (above 1.0 pushes the roll toward `min`).

```yaml
substats:
  boss_damage_percent:
    stat: BOSS_DAMAGE
    min: 1
    max: 10
    weight: 1
    bias: 2.5
```

Echoes deliberately roll only **combat** stats, never Coins, Vault or XP. `substat-colors` is an automatic common-to-rare colour gradient by `weight`.

### Levelling

Roll Fragments are **deposited** (`/echoes deposit` or the Deposit button) into **Roll XP**. Levelling never costs Coins.

| Key                                    | Default | Meaning                                                      |
| -------------------------------------- | ------- | ------------------------------------------------------------ |
| `leveling.base-cost`, `cost-growth`    | 8, 1.08 | Roll XP to go up a level: `base-cost x cost-growth^level`.   |
| `leveling.roll-cost-per-breakpoint`    | 50      | Roll XP spent when a level-up rolls a new substat.           |
| `leveling.min-scale-percent`           | 30      | A line's real strength at level 1, as a percent of its roll. |
| `leveling.main-stat-max-scale-percent` | 150     | At max level the Main Stat reaches this percent of its roll. |
| `leveling.substat-max-scale-percent`   | 75      | Same for substats.                                           |

### Salvage

Shift-right-click an Echo, or `/echoes salvage <id>`. Payout: the rarity's base (15 for Common up to 2000 for Event) plus `upgrade-refund-percent` (65%) of the Roll XP spent levelling it.

### Presets

Up to `presets.count` (5, 0 hides the button) saved loadouts. Left click equips a preset (an empty one saves your current set), right click overwrites, shift-right clears. An Echo in any preset cannot be salvaged or withdrawn.

### Echo terminals

Staff can place a world block that opens the Echoes menu: look at a block and run `/ceadmin echoes set-block`. Saved in `data/echo-terminals.yml`. `unset-block` removes it and `hitbox` shows the click area.


---

# 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://lethium.gitbook.io/lethium-docs/gameplay/echoes-advanced.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.