[2.0.14] Foundry: set recipe mismatch (mismatched order)
Posted: Tue Nov 05, 2024 2:15 pm
Currently, setting "molten iron" (the liquid) as recipe does not select "molten iron" (the recipe)-- it selects "molten iron from lava" instead. Same for copper.
Expected behavior:
When sending a "molten iron" (the liquid) signal to a forge, the "Molten iron (Recipe)" should be selected.
When sending a "molten copper" (the liquid) signal to a forge, the "Molten copper (Recipe)" should be selected.
This is especially impactful because this is primarily encountered on space platforms and takes a lot of extra circuits to fix.
The current behavior is never desirable in my opinion (because regulating lava processing on Vulcanus is pretty much pointless anyway, while regulating non-lava ore smelting makes sense both in space and on other planets).
It is also a bug in my opinion because "Set recipe" should map to the recipe with the same name when possible and not to something else.
See example: This is a loosely related bug that is going to be fixed (similar issue for crushers):
viewtopic.php?f=30&t=119690
Expected behavior:
When sending a "molten iron" (the liquid) signal to a forge, the "Molten iron (Recipe)" should be selected.
When sending a "molten copper" (the liquid) signal to a forge, the "Molten copper (Recipe)" should be selected.
This is especially impactful because this is primarily encountered on space platforms and takes a lot of extra circuits to fix.
The current behavior is never desirable in my opinion (because regulating lava processing on Vulcanus is pretty much pointless anyway, while regulating non-lava ore smelting makes sense both in space and on other planets).
It is also a bug in my opinion because "Set recipe" should map to the recipe with the same name when possible and not to something else.
See example: This is a loosely related bug that is going to be fixed (similar issue for crushers):
viewtopic.php?f=30&t=119690