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

# The Admin GUI

`/tcpmt menu` opens the admin menu (the older `/tcpmt gui` still works as an alias). Everything here is also doable by command, but the GUI is the fastest way to browse state. Requires `tcpmt.admin`.

## Main menu

Five entries:

* **Chambers** — browse every registered chamber.
* **Mob Editor** — build custom mob templates, assign them to tiers/chambers, and set up bosses. See [**the Mob Editor guide**](/plugins/mc/mt-documentation/mob-editor.md).
* **Tactics** — override the anti-cheese tactics per tier (per-chamber and per-mob overrides open from their own screens — see below).
* **Seasons** — view and switch seasons.
* **Reload** — re-read all config (same as `/tcpmt reload`).

## Chambers

A paginated list of every registered TCP chamber. Each entry is flagged:

* **Standard only** — caps at T20 (no `chambers.yml` Mythic config).
* **Mythic: M1, M3, …** — the Mythic tiers you've opened for it.

Click a chamber to open its detail screen.

## Chamber detail

A summary of one chamber, plus a few actions:

* Its Mythic-tier loot-table assignments (from `chambers.yml`), including any per-tier `damage-mod-override`.
* A **Mob assignments** button → the assignment editor, pre-filled with this chamber so any new assignment targets it.
* A **Tactics** button → override the anti-cheese tactics for mobs in this chamber.
* A **Leaderboard** button → the chamber's top players.

Mythic loot tables are edited in `chambers.yml`, not here — that part of the screen shows you what's currently wired up so you can confirm it at a glance.

## Leaderboard

Top players for the chamber, by tier, shown as player heads with their tier label. The data is read from the plugin's database asynchronously, so the screen opens without lag even on a busy server.

## Seasons

Every configured season, with the active one marked. Click a season to force it active (sets the override); click the active season — or the **Clear override** button — to revert to date-driven resolution.

## Mob Editor & Tactics

The Mob Editor and the Tactics screens are full editors, not just browsers — build mobs, set their gear/stats/loot, assign them to tiers and chambers, set up bosses, and toggle tactics, all in-game. Changes save straight to `my-mob-settings/` and take effect on the next spawn. The [**Mob Editor guide**](/plugins/mc/mt-documentation/mob-editor.md) walks through all of it.

## A note on editing

The chamber/season screens are for browsing and runtime switches (season override, reload). The scaling curve (`tiers.yml`), Mythic loot assignments (`chambers.yml`), season definitions (`seasons.yml`), and reward channels (`rewards.yml`) are edited in their files — they're the kind of structured config that's clearer and faster to manage as YAML. Edit, then `/tcpmt reload` or hit the GUI's Reload button.

***

Next: [**The Mob Editor →**](/plugins/mc/mt-documentation/mob-editor.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/admin-gui.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.