- All armored elytra creation/modification is now handled by the ArmoredElytraBuilder class.
- When creating a new armored elytra, the existing NBT data is now no longer removed.
- The durability of armored elytras is now stored in their NBT. This allows us to use custom max durability values for different armor tiers. Currently, only the anvil code uses the new durability system. The rest of the plugin will follow in a future commit, as all parts that interact with durability in any way will need to be updated. The durability returned by the regular methods now only show the display durability.
- The old name of the command to list all registered commands on the server was "listAvailable". This name provides no information about what it actually lists, making it hard to remember or use. The command now has 3 names: "listAvailableEnchantments", "listEnchantments", and "enchantments". These commands should be easier to remember and use.
- The lore, as specified by the translation file, was not applied on ArmoredElytras. This has now been resolved by retrieving the value when creating new AEs.
- Colors of Leather Armored Elytras (as copied from the leather chestplate, if it had a color) is now persistent through AE enchanting/repairing. However, upgrading the AE to a different tier will still remove the data from the AE (as there is no reason to keep it around).
- When a new AE is constructed using leather armor, the armor's color is now stored in the chestplate. Note that this is just an initial implementation, as enchanting/repairing will currently remove the color. This will be fixed in a future commit.
- Fixed not checking return value when trying to give players the result of crafting/upgrading an AE before clearing the items. Thanks, @Tanguygab for the heads-up!
- Added config option to make it possible to upgrade diamond AEs to netherite ones.
- Refactored code a bit to avoid duplicating stuff between the crafting/upgrading classes.
- Switched to using NamespacedKeys for enchantments instead of their names. This means that all properly registered custom enchantments are supported in one go.
- Removed the overengineered enchantment platform stuff. That was built with the idea that every custom enchantment plugin would have their own way of implementing custom enchantments. However, now that I found out that custom enchantments can just be registered using NamespacedKeys, none of this is required anymore.
