Anastasia Calico
Anastasia Calico
~~I'll binary search in a bit to make sure it's not a mod incompatibility.~~ Confirmed that it doesn't work purely on Fabric API and Simply No Report.
Alright, I'll send a better link over.
https://wormhole.app/xEkAx#u-J2X6NuMZ_l3RTrxW3AMA. This will only last for 24h as of sending.
This was apparently fixed in this commit. https://github.com/MrCrayfish/MrCrayfishFurnitureMod-Refurbished/commit/33423a8060d2d6927233ed38e7cad0850842a1e1 However, my guess is that the issue lies in Porting Lib's Recipe Book API not liking it when two mods implement it.
> What does this have to do with Porting Lib? `ItemStack.getRecipeRemainder()` is implemented by Fabric API. Yes, that is the case, but the crash was exposed through Porting Lib's Recipe...
I'm going to guess that it's actually linked to this issue. https://github.com/MehVahdJukaar/FarmersDelightRefabricated/issues/77 A recipe book library that's decoupled from enums might be in order on my end.
Still, not your issue. You are correct.
We are planning on re-doing the dynamic registry system in future updates once we get to post 1.20.2, as the current one is quite scuffed. I unfortunately don't really know...
> Or should this be reported to fabric counterpart You'd have to check if it happens there too, if so, report it.
This is an incredibly strange bug, because according to vanilla behaviour, it should only ever pass in a LivingEntity, which this message trips up whenever the entities that are passed...