Capability Invalidation for Chests is broken on NeoForge
shartte opened this issue ยท 5 comments
This overridden method breaks the NeoForge patch that triggers capability invalidation if a chest is changed from single to double (or back):
The @Intrinsic
actually seemed correct, why is that commented out?
Mixin apply failed lithium.mixins.json:util.inventory_change_listening.ChestBlockEntityMixin -> net.minecraft.block.entity.ChestBlockEntity: org.spongepowered.asm.mixin.transformer.throwables.InvalidMixinException @Intrinsic method must be prefixed interface method, no rename encountered on setCachedState(Lnet/minecraft/block/BlockState;)V in lithium.mixins.json:util.inventory_change_listening.ChestBlockEntityMixin [ -> MAIN Applicator Phase -> lithium.mixins.json:util.inventory_change_listening.ChestBlockEntityMixin -> Apply Methods -> (Lnet/minecraft/block/BlockState;)V:setCachedState]
In fact, I just now saw that neoforge overrides this method.