🌍 Languages / i18n (v2.1.0)
Vault v2.1.0 ships with 11 official translation files insideplugins/Vault/messages/. The active language is controlled by a single key in config.yml.
1. The 11 supported languages
2. Change the active language
Editplugins/Vault/config.yml:
You will see something like this in console:
Note about fallback: if a key is mistyped or doesn’t exist in yourmessages_es.yml, the plugin uses whatever is inmessages_en.ymlso it doesn’t show Missing translation: cmd.common.xxx.
3. Typical structure of messages_xx.yml
Base file messages_en.yml (section summary):
4. Translation placeholders ({key})
Inside each messages_xx.yml you can use curly braces { } that the plugin replaces at runtime. These are Vault’s own syntax, not PlaceholderAPI.
5. Create your own translation (custom language)
Step-by-step to addmessages_it.yml (Italian, not included):
-
Copy the base language:
(PowerShell:
Copy-Item ...) -
Edit
messages_it.ymland translate the values to the right of:. Do not change the keys on the left. ✅: -
Now tell
config.ymlyou want that language: -
Run
/vault reload. If all goes well you’ll see:If it says(68/74 keys, 6 falling back to en)it means 6 keys are missing and it’s picking up the English text — check for typos. -
(Optional) Also adjust
currency.localeso the separators match:
6. Colors (&0 … &f, &l, &n, &k)
Vault uses the old Bukkit color codes with &. It also supports Paper hex codes (&#RRGGBB if your server is Paper 1.16.5+).
Quick reference (put & + character):
Example:
7. Checklist: change language from EN → ES (quick)
Your balance: 1.234,56 € — congratulations, i18n is working.