Due to the benefit of Mojang mappings, we can now have a "latest" volatile code handler which a higher version can attempt to load and use, instead of having exclusive versions, making equal the gamble of upward version support with the rest of the plugin, as well as reducing duplicate code per version.
The effort to transition to Kotlin has only been completed for the volatile code handler and since then abandoned. Removing it at this point reduces the built jar size by 60%.
Due to the benefit of Mojang mappings, we can now have a "latest" volatile code handler which a higher version can attempt to load and use, instead of having exclusive versions, making equal the gamble of upward version support with the rest of the plugin, as well as reducing duplicate code per version.
The effort to transition to Kotlin has only been completed for the volatile code handler and since then abandoned. Removing it at this point reduces the built jar size by 60%.