[Suggestion] Please add List<ItemStack> analysis in FluidCraftRecipe

[Prunoideae]

Yep, I'm still working on the development of integration between HAC and CT, Mills and Spinning Machine was fully supported but the problem is that I can't pass a list of items to the constructor of FluidCraftRecipe, which caused a result that using OreDictionary while specifying the amount of items will be consumed.

Using strings can of course be a solution, but the amount of items will be consumed is impossible to specify.

Just like what the crusher can do:

Only a suggestion :-P

[Prunoideae]

Here's my code process:

I created a private list of list, adding every input Ingredient to it by using Primer.addInput, and the code will retrieve every item of the dictionary and set amount of it, then pass it to the construction of FluidCraftRecipe in Primer.ignite():

And that's where the problem occurred.

[Prunoideae]

well, using inputs.toArray() doesn't help anything at all, I though the problem is that List itself was recognized as only one variable, but changing this doesn't help.

[Prunoideae]

Using string to represent oredictionary is usable, but not good enough because the item count is always limited to 1......

[Prunoideae]

well, every machine except spinning machine only take one item each operation... that's a problem needs to be solved also :-(

[defeatedcrow]

Liquid Crafting devices (the pot and chemical reactor) consume only one material per slot. Those machines, (like vanilla stove,) can not change the consumption by recipe registration because the consumption of the item is specified as 1 as a constraint on the implementation of TileEntity.

As these machines have multiple input slots, if the recipe has consumption of 2 or more, often "fractional items" will remain in the slots, which hinders the automatic operation of the machine. These were tested and deleted features because they were stressful to me in test play. There are no plans to change specifications in the future.

[defeatedcrow]

If you would like to propose another machine and recipe, please make another issue. They differ in the cause and topic of the issue.

[Prunoideae]

OK, if it's a preserved feature, there's no reason for me to change it.

[defeatedcrow]

The problem is distributed.
What is your request?

My answer is

• There are no plans to change the for "liquid recipe" consume amount.
• About other machines that have only one input slot can be considered. (It takes time because they require redesign of the machine)

The issue was aborted with insufficient conversation. Are you really ok with this?

[Prunoideae]

Well, if other machines are ok, then I think it's good to make things more flexible.
Though my first purpose was just to make liquid recipe consume specific amount, but that's not a big deal.

[defeatedcrow]

OK, I'll consider it about other machines.
I'm sorry about the liquid recipe.