> For the complete documentation index, see [llms.txt](https://docs.onelitefeather.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.onelitefeather.net/antiredstoneclock-remastered/how-to-guides/change-the-plugin-language.md).

# Change the plugin language

Make the plugin speak your players' language instead of English.

**Before you start:** none.

1. Open `plugins/AntiRedstoneClock-Remastered/config.yml`.
2. Add the language tags you want to the `translations` list, for example:

   ```yaml
   translations:
     - 'en-US'
     - 'de-DE'
   ```
3. Restart the server. Translations are loaded once at startup — `/arcm reload` does not pick up a new language.

Each player then sees the messages in the language their Minecraft client is set to, as long as that language is in the list. Everyone else falls back to `en-US`, which is always loaded.

## Check it worked

Set your client to the language you added, rejoin, and run `/arcm help`. The command descriptions appear in that language.

## If it does not work

The server log names every locale it loaded on startup. A tag that does not match a shipped file is reported there as an error.

To change the wording, or to add a language that is not shipped, put your own `antiredstoneclockremasterd_<tag>.properties` into `plugins/AntiRedstoneClock-Remastered/lang/`. A file in that folder wins over the one inside the JAR.

See also: [Configuration reference](/antiredstoneclock-remastered/reference/configuration.md) for the list of shipped languages.


---

# 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://docs.onelitefeather.net/antiredstoneclock-remastered/how-to-guides/change-the-plugin-language.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.