LocaleAPI

What is it for? Developers using this API can provide the ability to simultaneously use multiple languages.
For example. On your server there are players from different countries and they understand only their language. If there is a localization file in which there will be messages corresponding to the client language chosen by them, they will see the messages of your plugin in that language.
Version 6 of the plugin and newer ones provide a convenient API for creating and managing plugin configurations.
Since version 7, support for configuration formats has been added: Jackson, XML, Toml (my own implementation with support for comments using the NightConfig library) and Yaml with support for comments(using GeyserYaml). XML also supports comments.
Starting from version 7, the server administrator can override the configuration and localization formats of plugins that use the appropriate features provided by LocaleAPI. And also change the preferred location for storing localizations.

For server admin:

All localization files are saved in the following path, where “pluginid” is the directory for the localization files of a particular plugin. ./{ConfigDir}/localeapi/{pluginid}/[LocaleFiles]
This only applies to plugins that use LocaleAPI.
You can add translation files you need to the plugin localization directory. When you add a localization file, it will be downloaded automatically. If you make changes to existing files, they will also be automatically reloaded. The load/reload operation cannot be performed more than once every 10 seconds(API8-10). This time limit has been added to eliminate the possibility of server performance degradation.

For developers:

The localization file name must be in the format en-US, ru-RU, etc. Select the file type depending on which configuration you prefer to choose. For the correct work of the plugin is necessary to generate a default localization file - en-US. https://github.com/SawFowl/LocaleAPI