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

# Overview

Welcome! This guide covers installing TCP-MythicTrials, understanding how per-player chamber progression works, and configuring tiers, Mythic gates, seasons, and rewards.

The core idea: **each Trial Chamber becomes a personal difficulty ladder.** Players clear a chamber to raise their tier in it; the next run scales to that tier; better loot waits at the top. Reach tier 20 and — where you've allowed it — break into the Mythic prestige range.

## Where to start

1. [**Installation**](/plugins/mc/mt-documentation/installation.md) — Drop the JAR in, restart, verify.
2. [**How progression works**](/plugins/mc/mt-documentation/how-it-works.md) — Tiers, scaling, clearing, party resolution. Read this first; it's the whole plugin in one page.
3. [**config.yml**](/plugins/mc/mt-documentation/config-yml.md) — Tier telegraph, update checker, debug toggle.
4. [**tiers.yml**](/plugins/mc/mt-documentation/tiers-yml.md) — The band-based difficulty curve, per-mob tuning, and anti-cheese guardrails.
5. [**chambers.yml**](/plugins/mc/mt-documentation/chambers-yml.md) — Opening chambers for Mythic tiers with custom loot.
6. [**seasons.yml**](/plugins/mc/mt-documentation/seasons-yml.md) — Date-driven loot rotations.
7. [**rewards.yml**](/plugins/mc/mt-documentation/rewards-yml.md) — The four chamber-clear reward channels.
8. [**Commands & permissions**](/plugins/mc/mt-documentation/commands-and-permissions.md) — Quick reference.
9. [**The Admin GUI**](/plugins/mc/mt-documentation/admin-gui.md) — Tour of `/tcpmt menu`.
10. [**The Mob Editor**](/plugins/mc/mt-documentation/mob-editor.md) — Custom mob templates, tier/chamber assignments, bosses, and scoped anti-cheese tactics.
11. [**messages.yml**](/plugins/mc/mt-documentation/messages-yml.md) — Translating the player-facing text.
12. [**Integrations**](/plugins/mc/mt-documentation/integrations.md) — VaultCrates, WildSpawners, Vault, PlaceholderAPI.
13. [**Troubleshooting & FAQ**](/plugins/mc/mt-documentation/troubleshooting.md) — Common gotchas.

## What this plugin needs

* **Paper / Folia 1.21.7+** (the admin GUI uses Paper's Dialog API)
* **Java 21+**
* **TrialChamberPro v1.5.4+** — the free base plugin this builds on

Full requirements, the why-this-version detail, and the optional add-ons (VaultCrates, WildSpawners, Vault, PlaceholderAPI) are covered in [**Installation**](/plugins/mc/mt-documentation/installation.md).

## Getting help

The Discord linked from the marketplace product page is the fastest way to get an answer. When asking, include:

* Plugin version (shown in the startup banner in the server console)
* Server software + version (`Paper 1.21.7`, `Folia 1.21.8`, etc.)
* The relevant config snippet
* The full console log around the moment the issue happened
* Steps to reproduce (if possible — not always required)


---

# 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/readme.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.