Bug Closed · Invalid

MythicDungeons cannot obtain NMS normally in paper 1.20.2

#5903 opened by Unknown 1 year ago

Unknownreported this bug

cannot be found net.minecraft.world.entity.Mob

[08:49:22 INFO]: [MythicDungeons] Enabling MythicDungeons v2.0.0-SNAPSHOT [08:49:22 WARN]: java.lang.ClassNotFoundException: net.minecraft.world.entity.Mob [08:49:22 WARN]: at org.bukkit.plugin.java.PluginClassLoader.loadClass0(PluginClassLoader.java:197) [08:49:22 WARN]: at org.bukkit.plugin.java.PluginClassLoader.loadClass(PluginClassLoader.java:164) [08:49:22 WARN]: at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:526) [08:49:22 WARN]: at java.base/java.lang.Class.forName0(Native Method) [08:49:22 WARN]: at java.base/java.lang.Class.forName(Class.java:421) [08:49:22 WARN]: at java.base/java.lang.Class.forName(Class.java:412) [08:49:22 WARN]: at MythicDungeons-2.0.0-SNAPSHOT-228.jar//net.playavalon.mythicdungeons.utility.helpers.ReflectionUtils.getNMSClass(ReflectionUtils.java:58) [08:49:22 WARN]: at MythicDungeons-2.0.0-SNAPSHOT-228.jar//net.playavalon.mythicdungeons.utility.helpers.ReflectionUtils.prepMemoryLeakKiller(ReflectionUtils.java:180) [08:49:22 WARN]: at MythicDungeons-2.0.0-SNAPSHOT-228.jar//net.playavalon.mythicdungeons.MythicDungeons.onEnable(MythicDungeons.java:175) [08:49:22 WARN]: at org.bukkit.plugin.java.JavaPlugin.setEnabled(JavaPlugin.java:281) [08:49:22 WARN]: at io.papermc.paper.plugin.manager.PaperPluginInstanceManager.enablePlugin(PaperPluginInstanceManager.java:190) [08:49:22 WARN]: at io.papermc.paper.plugin.manager.PaperPluginManagerImpl.enablePlugin(PaperPluginManagerImpl.java:104) [08:49:22 WARN]: at org.bukkit.plugin.SimplePluginManager.enablePlugin(SimplePluginManager.java:507) [08:49:22 WARN]: at org.bukkit.craftbukkit.v1_20_R2.CraftServer.enablePlugin(CraftServer.java:646) [08:49:22 WARN]: at org.bukkit.craftbukkit.v1_20_R2.CraftServer.enablePlugins(CraftServer.java:557) [08:49:22 WARN]: at net.minecraft.server.MinecraftServer.loadWorld0(MinecraftServer.java:627) [08:49:22 WARN]: at net.minecraft.server.MinecraftServer.loadLevel(MinecraftServer.java:424) [08:49:22 WARN]: at net.minecraft.server.dedicated.DedicatedServer.e(DedicatedServer.java:308) [08:49:22 WARN]: at net.minecraft.server.MinecraftServer.w(MinecraftServer.java:1086) [08:49:22 WARN]: at net.minecraft.server.MinecraftServer.lambda$spin$0(MinecraftServer.java:315) [08:49:22 WARN]: at java.base/java.lang.Thread.run(Thread.java:1583)

Unknowncommented

Hey there! This is actually harmless, it just means it can't do some extra protection against memory leaks. Normally it doesn't spit out an error like this and just quietly fails but I forgot to hide the error, oops!

Not all memory leak fixes are available on earlier versions of Minecraft but I do my best to provide what I can. This particular fix is only available on 1.21+ as far as I'm aware.

Sign in to join the discussion.