Translations

In screens

A server has one language, so a screen is simply written in it: the examples are installed already in the server's language, with the words in the HTML where you edit them. Keys are for one file shared by servers in different languages.

<h1 t="title">Shop</h1> reads title from plugins/ExyliaScreens/lang/<code>/screens/shop.yml: the server's language first, then English. The English written in the HTML is kept when no file has the key. t-<attribute>="key" does the same for an attribute.

<h1 t="hub.title">{primary}Galaxy {letters}Hub</h1>

# lang/es/screens/hub.yml
hub:
  title: '{primary}Galaxia {letters}Hub'

An element with t holds only text, since the word replaces its children. Words may hold colour tokens, %placeholders% and ${...}; t('key', 'fallback') reads one inside an expression.

In chest and 3D menus

They hold their own words in the file. The examples are shipped translated: the first start writes them in the server's language (lang/<code>/examples/) when the plugin has it, and in the default English otherwise.

The plugin's messages

messages.yml holds the plugin's own lines (reloaded, problems, unknown menu...). The language setting of config.yml picks them: default follows ExyliaLib's language, or name a folder under lang/. English, Spanish, French, Portuguese, Russian and Turkish folders ship.