Sponge already contains its own TypeSerializer for Vector3i (or, more accurately, contains a DataTranslator for Vector3i and contains a TypeSerializer for all types with a registered DataTranslator). Since your implementation is different from Sponge’s, anyone installing this plugin will immediately break all configs from other plugins that use Vector3is in their configs.
Meanwhile, if you don’t mind me asking, why do you reimplement, wrap, or use utility methods for so much of the Sponge API? Using the API directly generally results in much cleaner code, and requiring an additional plugin is a bit odd when said plugin doesn’t (as far as I can see, yet) have any new functionality?
@pie_flavor
Thanks for the informations “TypeSerializer”.
The goal of EverAPI is usefull because he manage all plugins and services.
Example : Priority of title, ActionBar, Scoreboard, …