autocrafting error: "System reported ${INGREDIENT} available but could not extract anything"
mote opened this issue · 3 comments
When attempting to autocraft, we get a message like "System reported 1 Redstone Ore available but could not extract anything"
(it's not always this ingredient, and the ingredient does exist in the system). This happens for every autocraft (regardless of ingredient).
Describe the bug
Server restart fixes this, but only temporarily.
We tried this and it didn't help
- breaking controller and putting it in a totally new place
- removing everything else from the network, except storage disks, crafting processor multiblock, me interface -- directly onto the network (i.e. not behind a p2p)
- Removing and replacing the offending ingredient from the system
- Shuffling all the disks with ME IO Port
- Removing all drawers from AE2 storage, and putting everything in disk
Another clue: this might only happen on the second craft after a boot (i.e. first craft succeeds, second craft fails, even with a different recipe).
Maybe another clue: In the universal wireless terminal, when I shift-click items from my inventory into AE2 storage, it goes into the trash slot or offhand slot. I am pretty sure this started happening around the same time.
To Reproduce
- From ME terminal, request to craft something ("1 iron ingot")
- Get message "System reported 1 pulverized item available but could not extract anything"
Expected behavior
Craft should succeed.
Additional context
No crash, but here's a screenshot:
This looks like it might be similar to https://github.com/PrototypeTrousers/Applied-Energistics-2/issues/58
Environment
SMP server/client.
Minecraft 1.12.2
Forge 14.23.5.2860
AE2 Unofficial Extended Life rv6-stable-7-extended_life-v49ac
In MultiBlock Madness modpack v2.0.4
We are rather late game -- so, a quite large AE2 system, with fluid storage, the lazy ae2 crafting multiblock, etc.
I'm facing exactly the same problem word for world, including the trash slot part. Have you found a solution?
We removed all fluid import/export/storage busses from the network and everything worked again.