Per player localization
Guide to use per player localization
messages.yml is now messages_en.yml and you can create more using proper language codes like messages_de.yml for german.
Examples: en-US, en-UK, en, de, sk, hu In this file, you can add a new section, named custom (which is already there if you do a fresh install:
custom:
stash-title: Item stash
prev-page: '&fPrevious Page'
npc:
quests: <white>QuestsThese values are available in the plugin menus like item stash. You can reference them as {{stash-title}} or {{npc.quests}}. Notice the dot (.) notation for nested structures.
These are also exposed as PlaceholderAPI placeholders: %aurora_lang_<key>% for example: %aurora_lang_npc.quests%
This allows you to add per player localization to any plugin that supports PlaceholderAPI placeholders.
To enable per player localiaztion:
In your config.yml you have to:
add the language codes you support in
supported-languageschoose your default language and set it to
localefieldset
use-per-player-localetotrue
And then you have to:
grant the
aurora.core.user.languageto the players so they have access to the/language commandAfter all these, players will be able to use their desired language.
Notice that in config.yml the number-format section also have a locale value. That is only used when per player locale is disabled, otherwise it will use the player's selected locale.
Default value of the custom section in the migrated messages_en.yml file
As you can see, these are values for the stash menu. The updated default config that uses these values can be viewed on:
Item stashIf you want to use these placeholders in menus, there is a handy utility in AuroraLib which lets you wrap lines by word count in any of the item lore options:
You can nest plugin placeholders like {name} , papi placeholders like %player_name% and language placeholders like {{language-placeholder}} in any depth.
Last updated