EMI integration broken?

[Cobyt3]

Hi, I changed the composting output to Farmer's Delight's Organic Compost Block, but I noticed that EMI still shows Bone Meal as the composting result:

I then checked the closed issues and found this issue, suggesting EMI integration back in 2024.
As far as I understood that thread, you successfully implemented EMI support? But it seems to be broken now, or is there something I am missing?

Minecraft 1.21.1
Neoforge 21.1.222
Compost 3.0.1
EMI 1.1.22+1.21.1+neoforge

I'll send you my compost.json as well as a short clip of the issue. If you need anything more, let me know.

compost.json

javaw_aKlJpo3HV1.mp4

[yurisuika]

There was never really "integration", rather Compost was mixing into REI/EMI's displays to modify the fixed output (bone meal) that (here) the EmiCompostingRecipe uses as the output for anything it is offered as an "input" (which is just a list of itemstacks from the compostables map). In the vanilla composter, bone meal is a hardcoded output that it generates upon state change being as it has no real container inventory, which it cannot have as the vanilla composter has no block entity. As such, there is no sort of recipe or the likes that EMI can use for its display, so itself hardcodes bone_meal in its recipe widget.

However, being that this way of supporting REI/EMI was hacky and unstable, and that there is no good way to know what should actually be displayed as a singular output when generating loot from a loot table, these mixins were removed. In this new paradigm where the composter output can be dependent on things like the compostables and anything you can compose with an origin parameter (location, amount of light, if its raining, etc), it is never going to be correct except for the most simplistic of configurations. Back in December this question was put on the back burner as I wanted to get something out post-1.21.11 release, but I still don't have an answer for this. They would have required being rewritten to be functional, so it was a hindrance to release and the inherent inaccuracy of what they were displaying didn't make them any more of a necessity.

So yes, I would like to reintroduce support but do it properly with real integration. There are some technical issues I foresee, however.

Before EMI was being made to display random possible outputs regardless of their chance. Of course this was never correct either as every input was fixed to one possible output on their display. Compost was simply randomly picking an entry from the config that the server sent the client and changing the widget output slot to display it. Being as there are many pages of possible inputs, you'd eventually get all the outputs shown, so while technically wrong, it did offer something I suppose. If we were to simply stick to just replacing the singular output as before, we could use that singular input item for the compostable context param, but whatever it may contextually generate wouldn't necessarily get displayed whether we had a single output slot or even multiple, as that entirely depends on how the loot table conditions are structured.

Keep in mind the old config was simply a list of entries and chances. Loot tables can nest conditions, so they can get vastly more complex. For something remotely accurate, this would require creating a whole different design for an EMI recipe widget to display more output items for each possible input. While it may be preferable to just displaying bone meal, it is still trading inaccuracy for inaccuracy.

I don't think it would be possible to handle origin based conditions without using some static block position, which itself isn't accurate, and just lends itself to more pointless inaccuracy trading. EMI doesn't know anything about the player, so we can't use the player pos, and come to think of it probably doesn't know anything about the world anyways, so actually this may be impossible to do anything for.

[Cobyt3]

Thanks for the detailed explanation. So on Mojang for hard-coding bone meal for the composter then :/

And yeah I guess that workaround of cycling through possible outputs would only work for simple configs like mine, where no matter the input or condition, it spits out the same item. But for more complicated configs it wouldn't really work.

I'm probably best off just adding an info tab to the item and hiding the composting category from EMI, so it won't show the bone meal outputs.