> 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/troubleshooting.md). # Troubleshooting & FAQ ## The plugin won't load * **"TrialChamberPro not loaded."** Install the free TCP plugin at **v1.5.4 or newer**. MythicTrials hard-depends on it. * **`ClassNotFoundException` mentioning `io.papermc.paper.dialog`.** Your Paper is older than 1.21.7. The admin GUI needs the Dialog API. Update. * **"License verification FAILED."** Re-download the JAR from your purchase page at [esmp.fun/plugins](https://esmp.fun/plugins) (or whichever store you bought it from) — the embedded licence didn't make it into your copy. ## If `/mt` doesn't work but `/tcpmt` does Another plugin on your server also registers an `mt` command, and Bukkit gave it the bare alias. Since 0.1.4 MythicTrials reclaims `/mt` automatically one tick after startup (`command.claim-mt-alias: true`, with a console log naming the displaced plugin). On older builds, use `/tcpmt` or `/mythictrials`. ## Mobs aren't scaling * **The chamber must be registered in TrialChamberPro.** Scaling only applies to mobs that spawn inside a registered chamber. Wild spawners and unmanaged mobs are left vanilla by design. * **Tier 1 is baseline.** A player at T1 sees vanilla-strength mobs — that's intended. Clear the chamber a few times and watch them get tougher. * **Check party resolution.** With `lowest` (the default), a group is scaled to its least-progressed member. If a fresh player is in the chamber, the mobs scale to *their* tier. ## Tiers aren't going up * A tier only increases when the chamber is **fully cleared in one run** — every spawner completes a wave before the chamber resets. If your chamber's reset interval is short, players may be running out of time. Increase the reset interval in TCP. * **Update TrialChamberPro to 1.5.6+.** Older TCP builds cached the chamber's spawner count once and never refreshed it — after a discovery merge, a `/tcp scan`, or a broken spawner block, the clear threshold went stale and the chamber-cleared signal could fire early or **never**. TCP 1.5.6 re-counts automatically. * **Check the chamber isn't an oversized auto-discovery merge.** Run `/tcp info ` — if discovery merged several structures into one registration, the chamber can contain 30+ spawners, making a one-run clear practically impossible. Fix on the TCP side: `/tcp delete ` and let discovery re-register the structures separately (lower `discovery.max-merged-volume` / `merge-distance-blocks` if it keeps merging). * While players grind, you can unblock testing or seed a starting rank with `/tcpmt tier set all ` (every chamber at once) or the `progression.default-tier` config option. * Confirm the clear is firing: enable `debug.verbose-logging: true` in `config.yml` and watch for `[ChamberCleared]` lines from TCP and the follow-up tier bump. ## Mythic won't unlock * Mythic is **opt-in per chamber**. The chamber needs a `mythic-tiers:` block in `chambers.yml` with at least M1 configured. Without it, T20 is the ceiling. See [chambers.yml](/plugins/mc/mt-documentation/chambers-yml.md). ## Vault opens are failing after I set Mythic/seasonal loot * The loot table you referenced **must exist in TCP's `loot.yml`**. A missing table makes the open fail (no key consumed) — that's TCP's standard behaviour for any invalid loot table, not a bug here. Define the table in `loot.yml`, then `/tcpmt reload` (and `/tcp reload` for the loot file). ## Currency / key rewards aren't dropping * **Currency** needs Vault + an economy plugin. Check the console for the "Vault economy unavailable" note on startup. * **Legendary keys** need TCP-VaultCrates, and the player must be at or above the `min-tier` in `rewards.yml`. Remember the roll is a *chance* — `chance-per-tier` scales it with tier. ## Does progression survive a restart? Yes. Tiers live in the plugin's own `progression.db` (SQLite), independent of TCP's database. A TCP database reset does **not** wipe progression. ## Can I wipe a player's progression? Use `/tcpmt tier set T1` to reset one chamber. There's no bulk wipe command in v1.0 — for a full reset, stop the server and delete `plugins/TCP-MythicTrials/progression.db` (it regenerates empty on next boot). ## How do I move my config to another server? Copy the five YAML files (`tiers`, `chambers`, `seasons`, `rewards`, `messages`). **Do not** copy `progression.db` unless you also want to move player progression, and **never** copy `license-cache.dat` — it's tied to your license and machine. *** Still stuck? The Discord linked from the marketplace product page is the fastest way to get help — see [what to include](/plugins/mc/mt-documentation/readme.md#getting-help) when you ask. --- # 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/troubleshooting.md?ask=&goal= ``` `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.