Messages & Language
Editing the built in messages, and adding a translation of your own alongside English, French and Spanish.
Vowbound ships three complete language files under lang/: en_US.yml, fr_FR.yml and
es_ES.yml, each a native translation rather than a machine, word for word one. English
is always kept loaded as a fallback underneath whichever one you pick, so a key missing
from your file, or from a translation you write yourself, still shows something rather
than a raw key name.
# config.yml
language: en_USPoint language at any file name in lang/ without the .yml part. Drop your own
lang/de_DE.yml in and set language: de_DE to use it. Vowbound loads it if present and
warns on any missing key, falling back to English for those specifically.
What is in a language file
Message keys are grouped: messages.* for command feedback, help.* for the paginated
help pages, ceremony.* for everything the Father and the ceremony itself say, npc.*
for NPC related lines, menu.* for menu titles and item names, and admin.* for the
admin command tree's own confirmations.
lang.yml is not the same file
lang.yml, at the plugin root rather than inside lang/, only holds the three keys eco
itself requires to route its own permission and player-only checks: messages.prefix,
messages.no-permission and messages.not-player. It's never touched by the language
picker and shouldn't be confused with the real message files under lang/.
Writing a translation
Copy lang/en_US.yml to lang/xx_XX.yml, translate the values, leave the keys alone,
and set language: xx_XX. Anything you haven't gotten to yet falls back to the English
line underneath it, so a partial translation never breaks the plugin, it just shows
English for the keys you haven't reached. Every MiniMessage tag and every {placeholder}
inside a value has to stay exactly where it is, only the surrounding text should change.