Unpackager cannot output into a Packager
malakai97 opened this issue ยท 5 comments
An Unpackager should be able to output into a Packager just like any other inventory.
The reason someone would want to do this is the Unpackager is connected to the main network, but the Packager is on a subnet, such as one set up for parallelization of a crafting task. This would allow one to leverage the Unpackager's blocking mode to get recipe packages into the subnet.
This network-> Unpackager -> Packager setup removes the need for one to duplicate their packagedauto recipes with AE2 patterns.
You might be asking 'why not just use a chest in between?' Then the method to take items from the chest to the Packager would have to have intelligent blocking support that is fully aware of the recipes already encoded in the Unpackager.
It comes to mind that a feature as simple a mode on the Unpackager that changes it to just be a passthrough--that is, it would only move the recipe package from its input slots to its output slots--would solve this need.
The goal is two-fold:
- Output recipe-packages into a chest. (We want to round-robin the recipe packages to a bank of machines from that chest.)
- Create no AE2 patterns. This part is why we need to connect both a packager and unpackager to the AE network.
- By connecting a Packager with a recipe holder to the AE network, the network learns how to craft those packages.
- By connecting an Unpackager with a recipe holder to the AE network, the network learns how to craft each package into the thing it creates.
- Thus, when we tell the network to create something, the unpackager will output the e.g. 7 items into its adjacent inventory.
This third step outputting items instead of recipe packages prevents us from reaching our goal.
By adding a fourth step, one can achieve the goal:
- The adjacent inventory is another Packager not connected to the AE network, which takes the ingredients and outputs a recipe package. [This only works with blocking mode.]