> 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/getting-started/licensing-and-languages.md).

# Licensing and languages

Your ClickEm licence, what happens when it is invalid, and the language add-ons.

### Your licence

ClickEm is licensed **per server**. After purchase you receive a **licence key**. Put it in `plugins/ClickEmCore/config.yml`:

```yaml
license:
  key: "YOUR-KEY-HERE"
```

| Topic                              | Details                                                                                                  |
| ---------------------------------- | -------------------------------------------------------------------------------------------------------- |
| **When it is checked**             | At server start. The plugin contacts the Lethium licence server and needs an internet connection.        |
| **Bound to your server**           | The key is tied to your server hardware. Moving to a new machine or host needs a reset. Contact support. |
| **If the key is wrong or missing** | The plugin will not run its features and prints a licence message in the console.                        |
| **Keep it private**                | Do not share it or post `config.yml` with the key in it.                                                 |
| **Support**                        | Use the contact from your purchase confirmation.                                                         |

{% hint style="info" %}
Changes you make in the licence portal (for example adding a language) take effect when the server **restarts**.
{% endhint %}

### Languages

ClickEm ships with 13 languages.

| Code    | Language                                  |
| ------- | ----------------------------------------- |
| `en_us` | English (**included with every licence**) |
| `de_de` | German                                    |
| `es_es` | Spanish                                   |
| `fr_fr` | French                                    |
| `hu_hu` | Hungarian                                 |
| `id_id` | Indonesian                                |
| `nl_nl` | Dutch                                     |
| `pl_pl` | Polish                                    |
| `pt_br` | Brazilian Portuguese                      |
| `ru_ru` | Russian                                   |
| `th_th` | Thai                                      |
| `tr_tr` | Turkish                                   |
| `vi_vn` | Vietnamese                                |

The **base licence includes English only**. **Language add-ons** unlock more, **two, four or six** of the twelve others. You choose which ones for your server in the licence portal.

* Each player picks their language with **`/language`**, or `auto` to follow their game language.
* Players only see languages your licence includes.
* When a language is not unlocked, players who use it see English.
* Language add-ons also cover **LethiumMessages** announcements and, if installed, **LethiumLanguage** (which translates other plugins such as TAB and crates). See [LethiumMessages and LethiumLanguage](/lethium-docs/server-setup/lethium-plugins.md).
* Translations were written for this game and are not reviewed by native speakers. If you spot an error, override the line. See [Language and text](/lethium-docs/configuration/language-and-text.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 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/getting-started/licensing-and-languages.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.