Languages¶
Ember Menus ships with 64 translated strings in seven languages, and every player-facing message lives in a file you can edit.
Shipped translations¶
| Code | Language |
|---|---|
en |
English (default) |
de |
German |
es |
Spanish |
fr |
French |
pt_BR |
Portuguese (Brazil) |
ru |
Russian |
zh_CN |
Chinese (Simplified) |
Switching language¶
One line in config.yml:
Restart or /emenus reload. That is the whole process.
Every bundled file is unpacked into plugins/EmberMenus/lang/ the first time
the plugin starts, so you can open the folder and see exactly what shipped
rather than guessing.
Editing the wording¶
The files are yours. Open lang/de.yml, change anything, reload.
Two things to keep:
%placeholders% are replaced by the plugin. Keep them, but move them
wherever your sentence needs them.
Formatting is MiniMessage, so you control colour and emphasis as well as words. That is deliberate: a German sentence emphasises a different clause than the English one, and hard-coding the colours would take that choice away from the translator.
Your edits survive updates
Only en.yml is refreshed when the plugin starts, so new message keys
always appear. Every other file is left exactly as you left it.
Making a new translation¶
- Copy
lang/en.ymltolang/<code>.yml - Translate the values, leaving the keys alone
- Set
language: <code>inconfig.yml
You do not have to finish it. Fallback is per key, not per file:
That is a perfectly usable server. Most plugins would show blank text or raw keys for those 17 lines.
A note on quality¶
The non-English translations were written by the developer, not by native speakers. They are accurate enough to ship, but a native speaker will find phrasing they would do differently.
Spot something wrong? Send it to us on Discord and it goes into the next release with credit.