> For the complete documentation index, see [llms.txt](https://animvanish.mikart.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://animvanish.mikart.eu/configuration/language-files.md).

# Language files

You can choose your preferred language in the [config.yml](/configuration/config.yml.md#locale-str). The default language is `en-us` (English). The `messages-xx-xx.yml` is formatted using [MiniMessage](https://docs.advntr.dev/minimessage/index.html).&#x20;

### Help us translate the plugin!

To help us translate the plugin create a new file in the `common/src/main/resources/locales/` folder names xx-xx.yml. Name the file using the correct [ISO 639-1](https://en.wikipedia.org/wiki/List_of_ISO_639_language_codes) locale code for your language and dialect.

#### Thing to remember

* **Don't** translate the MiniMessage keys (like `<red>`)
* Do not translate the locale keys themselves (e.g. `not_player`)


---

# 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://animvanish.mikart.eu/configuration/language-files.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.
