Autocrafting gets stuck if the crafted item is moved.
derram opened this issue ยท 7 comments
Issue type:
- ๐ Bug
Short description:
Tested here with a barebones setup of Integrated Dynamics/Crafting/Terminals/Tunnels, Common Capabilities, and Cyclops Core.
Autocrafting continues if output remains in a storage container, thinks the output is missing if the item is moved.
Steps to reproduce the problem:
A setup for crafting granite, no hopper under output (interface on right has highest priority):
Crafting proceeds as expected.
Add hopper below output chest.
Crafting grinds to a halt.
This also happened to me in a modpack when I used a filtered interface to put the output directly into a machine. In that case it was a Create Millstone.
Expected behaviour:
Autocrafting should be able to tell when it's put the crafted item away.
Versions:
Note to self: similar to an issue with crafting item exporter. There, we added a forced index reload once the crafting job is done. We need something like that here as well, to make sure we add the crafted item to the index so it's marked as "completed" before the hopper pulls it out again.
Note the bit I said about the filtered interface.
I was hoping to skirt around the problem by having ID handle the entire process, all on the same network, and it still lost track of the output.
A temporary workaround would be to replace the hopper with an ID exporter that is attached to the main network.
Went back to the pack to implement the change, and I can't tell if I'm hitting the same bug while using the exporter or a similar but different bug.
In the pack I am crafting cobble + quartz to diorite and then diorite and quartz to granite. I think it might be getting stuck on the diorite side of things which doesn't send anything out of the network.
That's just a crafting interface and interfaces on the storage containers, and then the crafting interface for granite pulls from the output from the diorite crafter.