> For the complete documentation index, see [llms.txt](https://darkstarworks.gitbook.io/plugins/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://darkstarworks.gitbook.io/plugins/mc/mt-documentation/chambers-yml.md).

# chambers.yml

Opens chambers for **Mythic** progression and points each Mythic tier at a custom loot table. A chamber with no entry here caps at Standard tier 20 — Standard progression needs no configuration at all.

## Why Mythic is opt-in

Mythic tiers (M1–M5) are your endgame. They're meant to be rare and rewarding — so the plugin won't let players break past T20 on a chamber unless you've deliberately set up loot worth fighting for. No config, no Mythic. That keeps the prestige range meaningful and entirely under your control.

## Format

```yaml
chambers:
  endgame_pit:
    mythic-tiers:
      M1: { loot-table: "mythic-1-rewards" }
      M3:
        loot-table: "mythic-3-rewards"
        damage-mod-override: 1.1     # +10% on M3's damage curve, just here
      M5: { loot-table: "mythic-5-rewards" }
```

* **Chamber name** — must match the chamber's name in TrialChamberPro exactly (case-sensitive).
* **`mythic-tiers`** — one entry per Mythic tier you want reachable. You don't have to define all five; define the ones you've built loot for.
* **`loot-table`** — the id of a loot table **defined in TCP's `loot.yml`**. When a player at this Mythic tier opens a vault in this chamber, this table is used instead of the vanilla one. **The table must exist in `loot.yml`** — see the warning below.
* **`damage-mod-override`** *(optional)* — a per-tier multiplier layered on top of the global Mythic damage curve for this chamber's tier. `1.0` = no change, `1.1` = 10% harder, `0.9` = 10% easier. Lets you tune a single Mythic step without touching `tiers.yml`.

## How a player reaches Mythic here

1. They climb to T20 on the chamber by clearing it repeatedly.
2. Because this chamber declares `mythic-tiers`, their next clear at T20 promotes them to **M1** instead of stopping.
3. They keep going as far as the configured Mythic tiers allow. If you've only defined M1 and M3, a player at M1 still advances toward M2/M3 — the loot for an undefined intermediate tier simply falls back to vanilla until you add it.

{% hint style="warning" %}
**The loot table must exist in TCP's `loot.yml`.** A Mythic tier pointing at a table that isn't defined there will make the vault open *fail* — the same way any invalid loot table does in TCP (no key consumed, an error logged). Define your `mythic-1-rewards` etc. in `loot.yml` first, then reference them here.
{% endhint %}

## Standard-only chambers

You don't list them. Any registered chamber not in this file simply caps at T20 with vanilla loot — that's the default for every chamber until you opt it into Mythic.

***

Next: [**seasons.yml →**](/plugins/mc/mt-documentation/seasons-yml.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 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://darkstarworks.gitbook.io/plugins/mc/mt-documentation/chambers-yml.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.