[API] I18N - Translate your plugins easier than ever before!

There was an error when using the CONSTANT locale resolver which would always return null as any player's locale. Bug is fixed and the CONSTANT locale resolver should work again just fine!

Taking up a request to add support for Minecraft versions 1.8.(x) here comes support for said versions under the following restrictions: · For Minecraft versions v1.8.3 and above use I18N's regular builds which you can download from the project's GitHub releases page by following the download link of this resource. · For Minecraft versions below v1.8.3 you must clone the project's source code repository yourself and compile it using maven as follows: Code (Text): mvn -Dlegacy-build=true clean install This is due to the fact that these old versions were relocating the Gson dependency, I18N makes use of. JAR files compiled with the legacy-build flag set to true will append '-legacy' to their plugin version numbers. As a side note: the 4.1.0 release of ProtocolLib does not work when using I18N and Spigot version 1.8. Use version 3.6.4 of ProtocolLib instead (the reason being that one of the relocated classes could not be loaded since its constructor's signature has changed in between versions). Enjoy!

I18N does now support all Minecraft versions starting from v1.9. It will load the set of interceptors matching the version the server is running at runtime which means that the interceptors for all versions get readily compiled into the release's JAR file which you may download for all target platforms (BungeeCord and Spigot / CraftBukkit) on the project's GitHub releases page (see external download link). This allows me to make API additions more easily by not having to create separate branches of this library for each supported Minecraft version just so that all supported Minecraft versions will have access to the same feature set provided by I18N. Furthermore, this simplifies the whole process of setting up I18N for server owners as well, so it's a win-win-situation, don't you think?

In accordance to the yesterday's release of Spigot for Minecraft v1.11 I have updated I18N to support v1.11 and its protocol as well. There were two packets used by I18N that had slight version differences in them which means you will have to download the appropriate version for your server (either 1.10 or 1.11). Since no other features have been added, the two versions found here on GitHub for v1.10 and v1.11 respectively are functionally equivalent and may be used interchangeably. Stay tuned! And if you have any suggestions feel free to leave them here!

There's been a lot of change and even some API breaks with this update. Yet I do think that this update can make up for that as it finally decouples API from implementation and already puts this distinction to its best with the brand-new BungeeCord port. Also: after some weeks have passed and I was able to adjust the API to according to further suggestions the current API will become fixed and should stay the same for quite some time. Alongside this update I also wrote a bunch of guides on the project's GitHub wiki to make the learning curve even steeper, so make sure to check it out: https://github.com/BlackyPaw/I18N/wiki . I do expect some bugs to occur with this update so do not hesitate to contact me if you should encounter any of them!

Fixed a bug related to the formatting of chat messages as pointed out in Issue #4 on GitHub and added a new method to TranslationStorage to allow for manually loading translations if the implementation allows to do so. Only for Minecraft versions 1.10 and later.

Updated to Minecraft version 1.10.2. Due to changes in Minecraft's network protocol this version and all of its successors are only compatible with the 1.10[.2] protocol and no longer with the 1.9.x protocol. As there were no changes in I18N's feature set nor its API you may still use I18N on 1.9.x servers by installing version 0.6.0-SNAPSHOT. All plugins depending on I18N will currently work the same on both server versions as long as the correct version of I18N has been installed.

This new version allows you to translate the display names of ItemStacks so that each player will be presented with the localized name of an item when picking it up even after another player with another language has had it before. The usage is as simple as always: Code (Text): ItemStack stack = new ItemStack( Material.IRON_INGOT, 1 ); ItemMeta meta = stack.getItemMeta(); meta.setDisplayName( this.localizer.inject( "stack.ironingot" ) ); stack.setItemMeta( meta ); .SpoilerTarget">Spoiler: en.properties stack.ironingot=Iron Ingot .SpoilerTarget">Spoiler: de.properties stack.ironingot=Eisenbarren There is one exception to this feature, though: Please make sure that an ItemStack that was previously given to a player who is playing in Creative mode will never leave the player's inventory again, be it by putting the item into any container or dropping it. The reason for this is, that Minecraft will re-create item stacks client-side if a player is in Creative mode and will thus overwrite an internal representation of the item stack with one that is already translated into a specific language. This can lead to unexpected behaviour, so make sure that players in Creative mode cannot get rid of translated items or simply avoid using this feature in Creative mode altogether.

Fixed a bug related to misinterpreted UTF-8 characters in native language names and default translations.

Using the newly introduced PlayerLanguageSettingEvent you can now grab the language any player has set inside his Minecraft client's language settings menu and make good use of it. It works by capturing the SETTINGS packet the vanilla client sends after joining a server and after changing the language inside the respective menu (thanks to Acquized for pointing this out).

By listening to the new PlayerSetLanguageEvent you get a chance of getting notified whenever a player has successfully changed his / her language to a new value. This gives you a chance to resend certain components such as scoreboards to the player as players will not see them in their new language until you resend them manually.

You can now translate signs just as easily as all other text I18N currently supports. Players will thus see the very same sign differently depending on their respective native languages.

You can now use nested lists and dictionaries inside your .yml translation files. Translation keys will be concatenated using '.'. See the Translation Storages section of the resource description for an example.

Added support for YAML translation files - you can now put your translation into property-like .yml files and load them with the new YamlTranslationStorage which works the exact same way as the PropertyTranslationStorage!