ClassLoaderFixer

Methods to trick out the ClassLoader.

The JavaPluginLoader removes the plugin's class loader from its List right after calling onDisable() and closes it. This leads to issues when classes are needed to be first loaded in onDisable() - for example, kotlin.collections.EmptyIterator is often needed for the first time in onDisable() when iterating over module's storages, registered listeners, etc.

I am confused as to why this is causing issues, because onDisable() is called blocking and hence should complete before the classloader is actually killed - maybe it's only a Paper issue.

I have also noticed that even using lambdas or other anonymous classes in onDisable() sometimes cause issues, for example the NamespacedStorage class's shutdown() method sometimes throws NoClassDefFoundError for its usages of forEach { }.

Note that all this only sometimes causes problems. The following methods use some dirty tricks to make sure that the classloader is not removed from the list and closed before onDisable() completes, and it loads classes that are known to cause issues right during onEnable().