> For the complete documentation index, see [llms.txt](https://lethium.gitbook.io/lethium-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://lethium.gitbook.io/lethium-docs/gameplay/vouchers.md).

# Vouchers

Tradable vouchers for cosmetics and temporary ranks.

File: `plugins/ClickEmCore/modules/vouchers.yml`. Module id: `vouchers`. Command: `/voucher admin ...` (staff).

A voucher is a **tradable item** that turns into a cosmetic or a temporary VIP rank when the owner **right-clicks it** (in hand, or in their inventory with no menu open). Each is framed in the rarity of what it contains. They can be traded, gifted and listed on the Auction House (add `vouchers` to those modules' allowed lists). Crates and staff hand them out.

| Command                                                  | Use                     |
| -------------------------------------------------------- | ----------------------- |
| `/voucher admin cosmetic <player> <cosmeticId> [amount]` | Cosmetic voucher.       |
| `/voucher admin rank <player> <tier> <days> [amount]`    | Temporary rank voucher. |

A cosmetic voucher is **not used up** if the player already owns that cosmetic.

### Settings

```yaml
material: PAPER
# custom-model-data: 10500
rank:
  commands:
    - "lp user %player% permission settemp clickem.vip.%tier% true %days%d accumulate"
```

| Key                             | Meaning                                                                                                                                                                                                                                    |
| ------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| `material`, `custom-model-data` | What the voucher looks like.                                                                                                                                                                                                               |
| `rank.commands`                 | Console commands run when a rank voucher is redeemed. `%player%`, `%tier%` and `%days%` are filled in. The default gives `clickem.vip.<tier>` for that many days through LuckPerms. `accumulate` adds days to what the player already has. |

If you do not use LuckPerms, replace the command with the equivalent of your permission plugin.

{% hint style="info" %}
On an existing server, add `vouchers` to `allowed-clickem-types` in `trade.yml` and `auctionhouse.yml`, and to `allowed-types` in `gifting.yml`, because those files are never overwritten by a new jar. The shipped lists already include it.
{% 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://lethium.gitbook.io/lethium-docs/gameplay/vouchers.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.