# Languages

The **DealOrNoDeal** plugin supports multiple languages through external language files.

This system allows server administrators to translate plugin messages without modifying the plugin code.

***

### Language Folder

All language files are located inside the plugin folder:

```
/plugins/DealOrNoDeal/languages/
```

Each file represents a specific language used by the plugin.

***

### Available Languages

The plugin currently includes the following language files:

| Language             | File        |
| -------------------- | ----------- |
| English              | `en.yml`    |
| Bulgarian            | `bg.yml`    |
| German               | `de.yml`    |
| Spanish              | `es.yml`    |
| French               | `fr.yml`    |
| Italian              | `it.yml`    |
| Japanese             | `ja.yml`    |
| Korean               | `ko.yml`    |
| Polish               | `pl.yml`    |
| Portuguese (Brazil)  | `pt_br.yml` |
| Russian              | `ru.yml`    |
| Turkish              | `tr.yml`    |
| Chinese (Simplified) | `zh_cn.yml` |

***

### Changing the Plugin Language

The active language is defined in the main configuration file.

File:

```
config.yml
```

Example:

```yaml
language: en
```

This setting tells the plugin which language file to load.

***

### Language Command

Administrators can also manage languages using commands.

Example:

```
/dond language list
```

Shows all available languages.

```
/dond language set <language>
```

Changes the plugin language.

Example:

```
/dond language set en
```

***

### Customizing Language Files

Server administrators can modify language files to customize messages.

Each language file contains all plugin messages such as:

* game messages
* banker offers
* GUI text
* command responses
* system notifications

Example entry:

```yaml
plugin_enabled: "DealOrNoDeal has been enabled successfully!"
```

***

### Creating Custom Translations

If you want to create your own translation:

1. Copy the `en.yml` file.
2. Rename the file using the language code.
3. Translate the message values.
4. Set the new language in `config.yml`.

This allows the plugin to support virtually any language.
