Techguns and Sponge clashing


#1

Caused by: java.lang.ClassCastException: techguns.entities.npcs.ZombieMiner cannot be cast to net.minecraft.entity.player.EntityPlayerMP
at techguns.items.armors.GenericArmor.damageArmor(GenericArmor.java:469) ~[GenericArmor.class:?]
at org.spongepowered.mod.util.StaticMixinForgeHelper.acceptArmorModifier(StaticMixinForgeHelper.java:126) ~[StaticMixinForgeHelper.class:1.12.2-2705-7.1.0-BETA-3126]
at net.minecraft.entity.EntityLivingBase.applyArmorDamage(EntityLivingBase.java:5110) ~[vp.class:?]
at net.minecraft.entity.EntityLivingBase.damageEntityHook(EntityLivingBase.java:3691) ~[vp.class:?]
at net.minecraft.entity.EntityLivingBase.func_70097_a(EntityLivingBase.java:3506) ~[vp.class:?]
at net.minecraft.entity.monster.EntityMob.func_70097_a(EntityMob.java:70) ~[ade.class:?]
at net.minecraft.entity.player.EntityPlayer.func_71059_n(EntityPlayer.java:3891) ~[aed.class:?]
at net.minecraft.entity.player.EntityPlayerMP.func_71059_n(EntityPlayerMP.java:1420) ~[oq.class:?]
at net.minecraft.network.NetHandlerPlayServer.func_147340_a(NetHandlerPlayServer.java:2605) ~[pa.class:?]
at net.minecraft.network.play.client.CPacketUseEntity.func_148833_a(SourceFile:69) ~[li.class:?]
at net.minecraft.network.play.client.CPacketUseEntity.func_148833_a(SourceFile:13) ~[li.class:?]
at org.spongepowered.common.network.PacketUtil.onProcessPacket(PacketUtil.java:148) ~[PacketUtil.class:1.12.2-2705-7.1.0-BETA-3126]
at net.minecraft.network.PacketThreadUtil$1.redirect$onProcessPacket$zlb000(SourceFile:539) ~[hv$1.class:?]
at net.minecraft.network.PacketThreadUtil$1.run(SourceFile:13) ~[hv$1.class:?]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) ~[?:1.8.0_161]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) ~[?:1.8.0_161]
at net.minecraft.util.Util.func_181617_a(SourceFile:46) ~[h.class:?]


#2

its not game breaking, but it spams up console. i have also let techguns author know of this issue aswel


#3

It’s a known issue with Techguns. The mod is not doing instance checks correctly as I’ve outlined on the previously reported GitHub issue. If you want to contact the author and point them to that comment, that should fix the problem.