> ## Documentation Index
> Fetch the complete documentation index at: https://docs.elementlabs.net/llms.txt
> Use this file to discover all available pages before exploring further.

# Text is wrong or missing

> The wrong language, a key name on screen, a few untranslated lines, or a gap in a sentence.

## Symptoms

One of these in a product's interface:

* a key name such as `map.waypoint` where a label should be;
* most of the text is in the right language, but a few lines are not;
* the language never changes, whatever you set;
* text you reworded is back to the original after an update;
* a sentence has a gap where a name or a number should be.

## Causes

| You see | Cause |
| - | - |
| A key name on screen | That key is missing from both the language shown and the fallback language. |
| A few lines in another language | Those keys are missing from the language shown, so the fallback language fills them. |
| The language never changes | For a product that uses one language for the server, `active` is not listed in `available`, the file does not exist, or the resource was not restarted. For a product that follows the player's game, the product does not ship that language and shows English. |
| Your wording is back | An update replaced the language file. |
| A gap in a sentence | A placeholder such as `{count}` was renamed or removed. |
| A whole language stopped working after an edit | The file has a syntax error and is ignored. |

## Fix

**1. Restart the resource**

Language files are read when the resource starts.

**2. Look for a language warning**

```text theme={null}
[WARN ] [   Locales] Locale file for "fr" is missing or invalid.
```

The file is missing or cannot be read. Look for a comma after the last entry, a missing quote, or
a comment: language files are plain JSON and take none.

**3. Check the language choice**

For a product with `configs/locales.jsonc`: `active` must appear in `available`, and both must
name files in `locales`. `fr` needs `locales/fr.json`.

**4. Find the missing key**

Search the product's language files for the key shown on screen and add it to the language that
is missing it, in the same place in the nesting. If no file has it, the release does not ship it:
[tell us](https://docs.elementlabs.net/troubleshooting/get-help.md).

**5. Restore placeholders**

Compare your line with the same line in the file the release shipped and put back every part in
braces, with the same name.

**6. If you added a language**

Check all of its steps: the file itself, its line in the `files` block of `fxmanifest.lua`, and,
for a product with `configs/locales.jsonc`, its entry in `available`. Without the
`fxmanifest.lua` line the file never reaches players. See [Languages](https://docs.elementlabs.net/configure/languages.md).

## Check that it worked

Restart the resource. In game, every label is in the expected language, with no key names and no
gaps. Check a screen that shows a count, so plural forms are covered too.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.