> For the complete documentation index, see [llms.txt](https://mode-development.gitbook.io/atomcombat/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mode-development.gitbook.io/atomcombat/getting-started/language.md).

# Languages

Every player-facing message in AtomCombat lives in `plugins/AtomCombat/languages/`, not scattered across module config files. AtomCombat ships two files out of the box: `en.yml` and `es.yml`.

## Choosing a language

```yaml
# config.yml
language: es
```

This loads `languages/es.yml`. Change it to `en` to load `languages/en.yml`, or to the name of any file you add yourself.

## File layout

Each language file has a global `prefix` and one section per feature:

```yaml
prefix: '&8[&cAtomCombat&8] &r'

general:
  no-permission: '&cYou do not have permission to use this command.'
  player-only: '&cThis command can only be used in-game.'

bounties:
  bounty-created: '&aA bounty of &f%amount%&a was placed on &f%target%&a. ID: &f%id%&a.'
  ...

rank-abilities:
  ...

combat-rules:
  ...

stats:
  ...

effects:
  ...

admin:
  ...
```

Legacy `&` colour codes are supported everywhere. Tokens like `%player%`, `%amount%` or `%seconds%` are replaced per message — each message's available tokens are shown in that module's documentation page.

## Adding a new language

1. Copy `languages/en.yml` to `languages/<your-code>.yml` (e.g. `fr.yml`).
2. Translate the values (never the keys on the left).
3. Set `language: <your-code>` in `config.yml`.
4. Run `/atomcombat reload`.

## Missing keys

If you are editing `en.yml` or `es.yml` directly and remove or forget a key, AtomCombat falls back to that key's value from the bundled copy of that same file, so a partially edited `en.yml`/`es.yml` never breaks. A brand-new file under a different name (e.g. `fr.yml`) has no bundled counterpart to fall back to, so start it as a full copy of `en.yml` or `es.yml` rather than a blank file.


---

# 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://mode-development.gitbook.io/atomcombat/getting-started/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.