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

# messages.yml

Every chat-facing string the plugin sends lives here. Edit it, run `/tcpmt reload`, and changes apply immediately.

## Format

MiniMessage syntax throughout — gradients, hover events, click events, the lot. Placeholders use `{name}` style.

```yaml
prefix: "<dark_aqua>[MythicTrials]</dark_aqua> "

command:
  no-permission: "<red>You don't have permission to use this command."
  player-only: "<red>This command must be run by a player."
  unknown-subcommand: "<red>Unknown subcommand:</red> <yellow>{sub}"
  reload-success: "<green>Reloaded MythicTrials config."
  reload-failed: "<red>Reload failed: {error}"

progression:
  tier-up: "<gold>⚔ <yellow>{chamber}</yellow> cleared — you advanced to <gold>{tier}</gold>!"
  mythic-unlocked: "<gradient:#a020f0:#ff55ff>✦ MYTHIC UNLOCKED ✦</gradient> <gray>You broke through to <light_purple>{tier}</light_purple> in <yellow>{chamber}</yellow>!"

reward:
  currency: "<gold>+<yellow>{amount}</yellow> coins"
  key: "<gold>A <yellow>{crate}</yellow> key dropped at your feet!"

# Tier telegraph titles, shown to players inside a chamber when scaled mobs
# first spawn. Not auto-prefixed — they carry their own framing.
announce:
  tier-telegraph-title: "<{color}><bold>⚔ {tier}</bold></{color}>"
  tier-telegraph-subtitle: "<gray>{chamber} — brace yourself!"

# Update checker (shown once on join to admins when a newer version is available).
update:
  available: "<gold>⬆ A new version is available:</gold> <yellow>{latest}</yellow> <gray>(you have {current})</gray> <aqua><click:open_url:'{url}'>[Download]</click></aqua>"
```

## Placeholders

| Key                                | Placeholders                     |
| ---------------------------------- | -------------------------------- |
| `command.unknown-subcommand`       | `{sub}`                          |
| `command.reload-failed`            | `{error}`                        |
| `progression.tier-up`              | `{chamber}`, `{tier}`            |
| `progression.mythic-unlocked`      | `{chamber}`, `{tier}`            |
| `reward.currency`                  | `{amount}`                       |
| `reward.key`                       | `{crate}`                        |
| `announce.tier-telegraph-title`    | `{tier}`, `{color}`, `{kind}`    |
| `announce.tier-telegraph-subtitle` | `{chamber}`, `{tier}`, `{color}` |
| `update.available`                 | `{latest}`, `{current}`, `{url}` |

`{tier}` renders as a short label — `T8`, `M2`, etc. `{color}` is a MiniMessage colour name chosen by tier (Mythic = `light_purple`, high Standard = `red` / `gold`, low Standard = `yellow`).

## Auto-prefixing

Player-facing keys are automatically prefixed with the `prefix` value, so you get a consistent `[MythicTrials]` lead-in without repeating it. Keys under `gui.`, `hologram.`, and `announce.` namespaces are *not* prefixed (they carry their own framing).

## Schema check

On startup the plugin compares your `messages.yml` against the keys it expects and logs a single warning listing any that are missing — so a key you accidentally deleted (or one added in an update) doesn't silently fall back without you noticing. Missing keys use the built-in defaults, so the plugin keeps working either way.

## Removing the prefix

Set `prefix` to an empty string (`prefix: ""`) for unprefixed messages.

***

Next: [**Integrations →**](/plugins/mc/mt-documentation/integrations.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/messages-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.