architectury
Custom Ingredient API
Both Fabric and Forge support registering custom ingredients now, and the APIs actually do seem reconcilable with just a couple of interface injections at runtime. A slight caveat is that we will have to force people to implement Ingredient on the fabric side as well, but other than that, this should be relatively easy to do
Actually, an alternative solution could be to make the conversion to Ingredient an implementation detail that's only necessary on Forge, and basically just... copy Fabric's ingredient API (that would then explicitly forbid extending Ingredient, since this case is not handled by Fabric's API and they would have to handle serialisation etc. themselves)