NEXUS Systems & Networks

## NEXUS 1.0.11

**Autocrafting: machine results may come back any way**
- A job that sends ingredients to a machine no longer gets stuck when the result comes back through a different block. The result is recognised by item (and its components) and amount, whatever the way in: the Machine Feeder that sent the recipe, another Feeder, an Importer, an Interface, a pipe or hopper from another mod, a Block Breaker, a player depositing it, or a chest read by an Inventory Port that the machine fills on its own.
- Partial deliveries count as they arrive: the job screen shows the results received (5/20, 13/20, 20/20) and the job finishes on its own when everything is there.
- Several jobs waiting for the same item share it oldest first, and each item counts for one job only.
- Items already stored before the job started waiting, and items only moving inside the network (a job returning its leftovers, an exporter putting back what did not fit, a hopper between two stored chests), never count as a result.
- A cancelled job stops waiting: results arriving later are simply stored. Progress is kept when the world is saved and loaded.

**Tested**: 167/167 automated GameTests on Minecraft 1.21.1 (alone and with AE2, Refined Storage, Mekanism and Integrated Dynamics installed) and 148/148 on Minecraft 26.1.2, including 9 new ones for these cases.