Discussion: use of Bukkit's API wrapper instead of MiniNBT

Since Bukkit has its own “NBT API”, we should consider using it instead of a third-party library. This Bukkit one is called PersistentDataContainer or org.bukkit.persistence. Using it requires a Plugin instance for creating a NamespacedKey, but that should be no issue: Gui instances already keep a reference to the plugin that created them. This feature does not have any of the issues described in #45.

I would be more than happy to implement and PR this, I am just asking for input regarding it. This is a place for discussion.

[stefvanschie]

I’ve gone through the dependents and it seems like the majority of plugins are targeting 1.14 or higher and interest in dropping support for 1.12 and 1.13 has also been shown here. Given this, I think dropping these two versions is the best way to proceed; users who wish to continue to support 1.12/1.13 can do so by staying on the current version (0.5.19) or fork the framework and maintain this compatibility themselves.

[Trigary]

They can choose not to use the newer versions of IF. Plugins supporting outdated, unsupported server versions are contributing to the issue and should be unsupported. At least that’s what I believe, but luckily for you, stefvanschie might not be as cruel as me 😃