The backend error reports are flooding the screen.

[kosroy]

The console keeps spamming error messages in a loop, causing the log file to take up more and more memory. It is currently 1GB in size. The server is on the Paper 1.21.7 branch, and all the plugin versions used are the latest available.

[20:09:02] [Server thread/ERROR]: Could not pass event BlockDropItemEvent to libreforge v4.76.1
java.lang.NoSuchMethodError: 'net.minecraft.core.Holder org.bukkit.craftbukkit.CraftRegistry.bukkitToMinecraftHolder(org.bukkit.Keyed, net.minecraft.resources.ResourceKey)'
at [更多附魔前置]eco-6.76.2-all.jar/com.willfp.eco.internal.spigot.proxy.v1_21_7.common.modern.NewEcoFastItemStack.getEnchantmentLevel(NewEcoFastItemStack.kt:79) ~[[更多附魔前置]eco-6.76.2-all.jar:?]
at libreforge-4.76.1-1752032551749.jar/com.willfp.libreforge.effects.impl.EffectAutosmelt.handleEvent(EffectAutosmelt.kt:74) ~[libreforge-4.76.1-1752032551749.jar:?]
at libreforge-4.76.1-1752032551749.jar/com.willfp.libreforge.effects.impl.EffectAutosmelt.onTrigger(EffectAutosmelt.kt:60) ~[libreforge-4.76.1-1752032551749.jar:?]
at libreforge-4.76.1-1752032551749.jar/com.willfp.libreforge.effects.impl.EffectAutosmelt.onTrigger(EffectAutosmelt.kt:22) ~[libreforge-4.76.1-1752032551749.jar:?]
at libreforge-4.76.1-1752032551749.jar/com.willfp.libreforge.effects.Effect.trigger(Effect.kt:162) ~[libreforge-4.76.1-1752032551749.jar:?]
at libreforge-4.76.1-1752032551749.jar/com.willfp.libreforge.effects.ChainElement.doTrigger(ChainElement.kt:64) ~[libreforge-4.76.1-1752032551749.jar:?]
at libreforge-4.76.1-1752032551749.jar/com.willfp.libreforge.effects.ElementLike.trigger$trigger(ElementLike.kt:142) ~[libreforge-4.76.1-1752032551749.jar:?]
at libreforge-4.76.1-1752032551749.jar/com.willfp.libreforge.effects.ElementLike.trigger(ElementLike.kt:161) ~[libreforge-4.76.1-1752032551749.jar:?]
at libreforge-4.76.1-1752032551749.jar/com.willfp.libreforge.effects.executors.impl.NormalExecutorFactory$NormalChainExecutor.execute(NormalExecutorFactory.kt:15) ~[libreforge-4.76.1-1752032551749.jar:?]
at libreforge-4.76.1-1752032551749.jar/com.willfp.libreforge.effects.Chain.trigger(Chain.kt:31) ~[libreforge-4.76.1-1752032551749.jar:?]
at libreforge-4.76.1-1752032551749.jar/com.willfp.libreforge.effects.Chain.trigger$default(Chain.kt:27) ~[libreforge-4.76.1-1752032551749.jar:?]
at libreforge-4.76.1-1752032551749.jar/com.willfp.libreforge.effects.EffectBlock.doTrigger(EffectBlock.kt:89) ~[libreforge-4.76.1-1752032551749.jar:?]
at libreforge-4.76.1-1752032551749.jar/com.willfp.libreforge.effects.ElementLike.trigger(ElementLike.kt:58) ~[libreforge-4.76.1-1752032551749.jar:?]
at libreforge-4.76.1-1752032551749.jar/com.willfp.libreforge.effects.EffectBlock.tryTrigger(EffectBlock.kt:81) ~[libreforge-4.76.1-1752032551749.jar:?]
at libreforge-4.76.1-1752032551749.jar/com.willfp.libreforge.triggers.Trigger.dispatchOnEffects(Trigger.kt:155) ~[libreforge-4.76.1-1752032551749.jar:?]
at libreforge-4.76.1-1752032551749.jar/com.willfp.libreforge.triggers.Trigger.dispatch(Trigger.kt:81) ~[libreforge-4.76.1-1752032551749.jar:?]
at libreforge-4.76.1-1752032551749.jar/com.willfp.libreforge.triggers.Trigger.dispatch$default(Trigger.kt:77) ~[libreforge-4.76.1-1752032551749.jar:?]
at libreforge-4.76.1-1752032551749.jar/com.willfp.libreforge.triggers.impl.TriggerBlockItemDrop.handle(TriggerBlockItemDrop.kt:51) ~[libreforge-4.76.1-1752032551749.jar:?]
at org.bukkit.plugin.RegisteredListener.callEvent(RegisteredListener.java:71) ~[leaf-api-1.21.7-R0.1-SNAPSHOT.jar:?]
at io.papermc.paper.plugin.manager.PaperEventManager.callEvent(PaperEventManager.java:71) ~[leaf-1.21.7.jar:1.21.7-25-88303ed]
at io.papermc.paper.plugin.manager.PaperPluginManagerImpl.callEvent(PaperPluginManagerImpl.java:131) ~[leaf-1.21.7.jar:1.21.7-25-88303ed]
at org.bukkit.plugin.SimplePluginManager.callEvent(SimplePluginManager.java:629) ~[leaf-api-1.21.7-R0.1-SNAPSHOT.jar:?]
at org.bukkit.craftbukkit.event.CraftEventFactory.handleBlockDropItemEvent(CraftEventFactory.java:410) ~[leaf-1.21.7.jar:1.21.7-25-88303ed]
at net.minecraft.server.level.ServerPlayerGameMode.destroyBlock(ServerPlayerGameMode.java:405) ~[leaf-1.21.7.jar:1.21.7-25-88303ed]
at net.minecraft.server.level.ServerPlayerGameMode.destroyAndAck(ServerPlayerGameMode.java:309) ~[leaf-1.21.7.jar:1.21.7-25-88303ed]
at net.minecraft.server.level.ServerPlayerGameMode.handleBlockBreakAction(ServerPlayerGameMode.java:242) ~[leaf-1.21.7.jar:1.21.7-25-88303ed]
at net.minecraft.server.network.ServerGamePacketListenerImpl.handlePlayerAction(ServerGamePacketListenerImpl.java:2047) ~[leaf-1.21.7.jar:1.21.7-25-88303ed]
at net.minecraft.network.protocol.game.ServerboundPlayerActionPacket.handle(ServerboundPlayerActionPacket.java:51) ~[leaf-1.21.7.jar:1.21.7-25-88303ed]
at net.minecraft.network.protocol.game.ServerboundPlayerActionPacket.handle(ServerboundPlayerActionPacket.java:10) ~[leaf-1.21.7.jar:1.21.7-25-88303ed]
at net.minecraft.network.protocol.PacketUtils.lambda$ensureRunningOnSameThread$0(PacketUtils.java:27) ~[leaf-1.21.7.jar:1.21.7-25-88303ed]
at net.minecraft.server.TickTask.run(TickTask.java:18) ~[leaf-1.21.7.jar:1.21.7-25-88303ed]
at net.minecraft.util.thread.BlockableEventLoop.doRunTask(BlockableEventLoop.java:155) ~[leaf-1.21.7.jar:1.21.7-25-88303ed]
at net.minecraft.util.thread.ReentrantBlockableEventLoop.doRunTask(ReentrantBlockableEventLoop.java:24) ~[leaf-1.21.7.jar:1.21.7-25-88303ed]
at net.minecraft.server.MinecraftServer.doRunTask(MinecraftServer.java:1485) ~[leaf-1.21.7.jar:1.21.7-25-88303ed]
at net.minecraft.server.MinecraftServer.doRunTask(MinecraftServer.java:165) ~[leaf-1.21.7.jar:1.21.7-25-88303ed]
at net.minecraft.util.thread.BlockableEventLoop.pollTask(BlockableEventLoop.java:129) ~[leaf-1.21.7.jar:1.21.7-25-88303ed]
at net.minecraft.server.MinecraftServer.pollTaskInternal(MinecraftServer.java:1466) ~[leaf-1.21.7.jar:1.21.7-25-88303ed]
at net.minecraft.server.MinecraftServer.pollTask(MinecraftServer.java:1460) ~[leaf-1.21.7.jar:1.21.7-25-88303ed]
at net.minecraft.util.thread.BlockableEventLoop.managedBlock(BlockableEventLoop.java:139) ~[leaf-1.21.7.jar:1.21.7-25-88303ed]
at net.minecraft.server.MinecraftServer.managedBlock(MinecraftServer.java:1415) ~[leaf-1.21.7.jar:1.21.7-25-88303ed]
at net.minecraft.server.MinecraftServer.waitUntilNextTick(MinecraftServer.java:1424) ~[leaf-1.21.7.jar:1.21.7-25-88303ed]
at net.minecraft.server.MinecraftServer.runServer(MinecraftServer.java:1304) ~[leaf-1.21.7.jar:1.21.7-25-88303ed]
at net.minecraft.server.MinecraftServer.lambda$spin$0(MinecraftServer.java:299) ~[leaf-1.21.7.jar:1.21.7-25-88303ed]
at java.base/java.lang.Thread.run(Thread.java:1583) ~[?:?]

[kosroy]

@WillFP

[DeltaEon]

I saw an earlier attempt to fix/catch similar to this in pull #391

However the call to .bukkitToMinecraftHolder on line 79 of NewEcoFastItemStack.kt looks to have the inputs backwards.

If you go look at line 110 of Paper's CraftRegistry.java. It certainly looks to be receiving the other way around unless I'm misunderstanding something here.

[kosroy]

To be honest, I just want this issue to be resolved or to be able to block the error logs. The errors started after I updated to version 1.21.7 and the latest version of EcoEnchants. Moreover, the "infernal_touch" enchantment in EcoEnchants has stopped working. I've seen others say that the author made a mistake in the code. I hope a new version can be released on spigotmc as soon as possible. Many thanks to anyone who can solve this problem—God bless you!

[kosroy]

@WillFP

[DeltaEon]

Correction of my observation,
the call on line 79 to .bukkitToMinecraftHolder should look like

         val minecraft = CraftRegistry.bukkitToMinecraftHolder<Enchantment,
            Registries.ENCHANTMENT>(
               enchantment
            )

[LoJoSho]

I can replicate this on my own server, annoying me in the neck right now.

[kosroy]

Not everyone knows how to program or build things, nor does everyone know how to find the corresponding GitHub, register an account, and post comments. What's more, even posting a single comment requires connecting to a paid VPN and relying on translation software to communicate. Please take this issue seriously and release a new version as soon as possible. I'm in tears!.

[kosroy]

@WillFP

[DeltaEon]

Since I clearly misunderstood and that PR I made was wrong, will keep on researching.

[DeltaEon]

Have replicated this, and it appears to be an issue with 1.21.7 and 1.21.8 specifically.
Tried paper 1.21.4 and it ran fine there.

[DeltaEon]

Have gotten a testing fix that has highlighted the main problem. Eco's FastItemStack interface is blowing up in 1.21.7+

I swapped out FastItemStack handling over in Libreforge's EffectAutosmelt.kt for a bukkit item handle and it's now working without error in my little test instance. Will keep digging into it later, if someone else doesn't get there before me.

    private fun handleEvent(player: Player, event: EditableDropEvent, config: Config) {
        val fortune = player.inventory.itemInMainHand
            .getEnchantmentLevel(Registry.ENCHANTMENT.get(NamespacedKey.minecraft("fortune"))!!)

and no, I tried passing this working enchant code into FastItemStack.wrap(). It blew up with the same error in the first post.

@WillFP

[WillFP]

Currently testing