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

# Installation

## What you need

* A Paper or Folia server running Minecraft **1.21.7 or newer**. The admin GUI uses Paper's Dialog API (added MC 1.21.6, Paper bindings since 1.21.7); older Paper versions will fail to load.
* **Java 21** or newer.
* **TrialChamberPro v1.5.4+** already installed and working. The v1.5.4 minimum is required — this plugin listens for the `ChamberEnteredEvent` / `ChamberExitedEvent` (added in TCP 1.5.4) to drive the in-chamber HUD, plus the older `ChamberClearedEvent` (1.5.0) for progression. Grab TCP from [Modrinth](https://modrinth.com/plugin/trialchamberpro); it's free.
* **(Optional)** TCP-VaultCrates, TCP-WildSpawners, and/or Vault for the cross-module integrations, and PlaceholderAPI for the `%tcpmt_…%` placeholders.

## Step 1 — Drop in the JAR

Copy the `tcp-mythic-trials-<version>.jar` you downloaded into your server's `plugins/` folder. Don't rename it.

```
plugins/
├── TrialChamberPro-1.5.x.jar
├── tcp-mythic-trials-<version>.jar     ← new
└── ...
```

## Step 2 — Restart the server

Restart — don't `/reload`. Reloading is unreliable for plugins that register listeners on enable.

## Step 3 — Verify it loaded

Watch the console as the server boots:

```
[INFO] [TCP-MythicTrials] License key sourced from JAR placeholder (production distribution).
[INFO] [TCP-MythicTrials] MythicTrials module active — MythicTierService published; 0 chamber(s) configured for Mythic progression; season none active.
[INFO] ╔══════════════════════════════════════╗
[INFO] ║  TCP-MythicTrials v<version>      ║
[INFO] ║  Licensed via ESMP                ║
[INFO] ╚══════════════════════════════════════╝
```

If you see the banner, you're good. `0 chamber(s) configured for Mythic` is expected on a fresh install — Standard tiers 1–20 work everywhere; Mythic is opt-in (see [chambers.yml](/plugins/mc/mt-documentation/chambers-yml.md)).

## Step 4 — Confirm the GUI works

Join as an op (or anyone with `tcpmt.admin`) and run:

```
/tcpmt menu
```

The admin menu should open. If it works, your install is complete.

## What if it didn't load?

* **"TrialChamberPro not loaded — cannot activate TCP-MythicTrials."** TrialChamberPro is missing or failed to load. Install the free TCP plugin at **v1.5.4 or later**.
* **"License verification FAILED."** The JAR didn't receive its embedded licence. Re-download from your purchase page at [esmp.fun/plugins](https://esmp.fun/plugins) (or whichever store you bought it from).
* **`ClassNotFoundException` mentioning `io.papermc.paper.dialog`** at startup. Your Paper is older than 1.21.7. Update it.

For anything else, hop into the Discord linked from the product page.

## Where the plugin's files live

After first boot:

```
plugins/TCP-MythicTrials/
├── config.yml            ← marketplace, tier telegraph, update checker, debug
├── tiers.yml             ← scaling formula + guardrails + party resolution
├── chambers.yml          ← per-chamber Mythic gating + loot
├── seasons.yml           ← seasonal loot rotations
├── rewards.yml           ← chamber-clear reward channels
├── messages.yml          ← every player-facing string
├── progression.db        ← per-player tier storage (don't share or edit)
└── license-cache.dat     ← offline-grace verification cache (don't share!)
```

The five YAMLs are yours to edit. `progression.db` and `license-cache.dat` are managed by the plugin — never copy them between machines.

***

Next: [**How progression works →**](/plugins/mc/mt-documentation/how-it-works.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/installation.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.