> For the complete documentation index, see [llms.txt](https://edseries-plugins.gitbook.io/p/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://edseries-plugins.gitbook.io/p/edperks/essential/messages.md).

# Messages

All player-facing chat text lives in `plugins/EdPerks/messages.yml`. Every value supports `&` colour codes (and hex where your server supports it), PlaceholderAPI placeholders, and the `{token}` replacements listed below. After editing, run `/edperks reload`.

The default file:

```yaml
main:
  no-permission: '&cYou do not have permission to do that.'
  player-not-found: '&cPlayer not found.'
  invalid-amount: '&cInvalid amount.'
  reload: '&aEdPerks configuration reloaded.'

roll:
  no-tickets: '&cYou have no Perk Tickets! Purchase some in the Tool Perks menu.'
  no-tool: '&cYou must be holding a perkable tool to roll a perk!'
  in-progress: '&cA roll is already in progress!'
  result:
    - '&r'
    - '&d&lTOOL PERK ROLLED!'
    - '&7You rolled {perk} &7level &f{level}&7!'
    - '&8| &7{details}'
    - '&r'
  pity-reached: '&5&lPITY LUCK! &dYou hit your pity and received a guaranteed Purple Perk!'

tickets:
  purchased: '&aPurchased &f{amount}x &aPerk Tickets for &f{cost} {currency}&a!'
  not-enough-currency: '&cYou cannot afford &f{amount}x &cPerk Tickets (&f{cost} {currency}&c).'
  given: '&aGave &f{amount}&a Perk Tickets to &f{player}&a.'
  balance: '&f{player}&7 has &f{amount}&7 Perk Tickets.'
```

***

### `main`

| Key                | When it's shown                             |
| ------------------ | ------------------------------------------- |
| `no-permission`    | The sender lacks the required permission.   |
| `player-not-found` | A named target player isn't online / found. |
| `invalid-amount`   | A numeric argument couldn't be parsed.      |
| `reload`           | `/edperks reload` finished.                 |

### `roll`

| Key            | When it's shown                                | Tokens                           |
| -------------- | ---------------------------------------------- | -------------------------------- |
| `no-tickets`   | Player tried to roll with 0 tickets.           | —                                |
| `no-tool`      | Player tried to roll without a perkable tool.  | —                                |
| `in-progress`  | A roll animation is already running.           | —                                |
| `result`       | Sent after a successful roll.                  | `{perk}`, `{level}`, `{details}` |
| `pity-reached` | Sent when a roll was a guaranteed pity payout. | —                                |

`result` tokens: `{perk}` = the perk's display name, `{level}` = the rolled level, `{details}` = the per-stat boost summary for that level.

### `tickets`

| Key                   | When it's shown                            | Tokens                             |
| --------------------- | ------------------------------------------ | ---------------------------------- |
| `purchased`           | A `[buy-tickets]` purchase succeeded.      | `{amount}`, `{cost}`, `{currency}` |
| `not-enough-currency` | A purchase failed (can't afford).          | `{amount}`, `{cost}`, `{currency}` |
| `given`               | `/edperks tickets give\|set` succeeded.    | `{amount}`, `{player}`             |
| `balance`             | `/edperks tickets <player>` balance check. | `{amount}`, `{player}`             |

{% hint style="info" %}
`result` is a **list** of lines — keep it as a list to send a multi-line message. The plugin info/help text (`/edperks`, `/edperks help`) is built in and not configured here.
{% endhint %}


---

# 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:

```
GET https://edseries-plugins.gitbook.io/p/edperks/essential/messages.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.