> For the complete documentation index, see [llms.txt](https://daddy-studios.gitbook.io/daddy-studios-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://daddy-studios.gitbook.io/daddy-studios-docs/scripts/daddy-marketplace/configuration/languages.md).

# Languages

Five languages ship with the resource, each a complete translation of the same 421 keys:

| Code | Language | File             |
| ---- | -------- | ---------------- |
| `en` | English  | `locales/en.lua` |
| `tr` | Turkish  | `locales/tr.lua` |
| `de` | German   | `locales/de.lua` |
| `es` | Spanish  | `locales/es.lua` |
| `fr` | French   | `locales/fr.lua` |

Pick one in `config.lua`:

```lua
Config.Locale = 'en'
```

Both the Lua side and the interface use this file — there is no second translation to keep in sync. Restart the resource after changing it.

## Adding a language

1. Copy `locales/en.lua` to `locales/xx.lua`, using your language code.
2. Change the table name on line 7:

   ```lua
   Locales['xx'] = {
   ```
3. Translate the **values**, never the keys on the left.
4. Set `Config.Locale = 'xx'` and restart.

`locales/*.lua` is loaded with a wildcard in `fxmanifest.lua`, so a new file is picked up without any other change. Locale files stay editable in both editions.

## Fallback

English is always loaded as the fallback. A key missing from your language falls back to the English text, so a partial translation still works — nothing breaks, some strings are just English. A completely unknown `Config.Locale` prints a warning and uses English:

```
[Daddy Marketplace] Locale "xx" not found, falling back to "en"
```

## Placeholders

Some strings contain `%s` or `%d`, which are filled in at runtime:

```lua
['notify.item_sold'] = '%dx %s sold for $%d',
```

{% hint style="warning" %}
Keep every placeholder, in the same order and of the same type. Dropping a `%s`, or swapping a `%d` for a `%s`, breaks the formatting of that message — the raw text is shown instead. You may reorder words around them freely, but the sequence of placeholders must stay as it is.
{% endhint %}

## Category labels

`Config.Categories` labels are used as written on English servers. Other languages use the `category.<key>` key from their locale file when it exists, so a custom category you add to `Config.Categories` shows its config label until you add a matching key to each locale file.

## Next steps

* [Discord Webhooks](/daddy-studios-docs/scripts/daddy-marketplace/configuration/webhooks.md)
* [Items & Categories](/daddy-studios-docs/scripts/daddy-marketplace/configuration/items.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://daddy-studios.gitbook.io/daddy-studios-docs/scripts/daddy-marketplace/configuration/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.