[Requestor Storage] => [Producer] => [Producer] => [Producer] => [Output Storage]
Where Requestor Storage:
- Is on the network (request only)
- runs a simple script to request goods
- Has a Store register set to the first Producer
- Has a Portable Transporter component
And Producer:
- Is NOT on the network
- Has a locked slot for each input, and all remaining slots are locked to outputs.
- Has a Store register pointing to the next Producer in the chain, except the last one points towards Output Storage.
- Has a Portable Transporter component
And Output Storage
- Is on the network (supply only)
- Has all slots locked to the production chain output item
I am having three issues with this:
1. Sometimes Requester Storage will pull items back from the first producer in the line, despite that producer not being on the network. Suggestion: prevent requests from being fulfilled by buildings not on the network?
2. ometimes a Producer will reserve all slots of an item type for its production, not passing materials down the line to the next building. Suggestion: prevent production components from reserving items if it does not have enough ingredients to fulfil a production run?
3. Sometimes a Producer will a slots of an item type with "Reserved for incoming order", not getting materials from the upstream building that has them available. This can be fixed by temporarily toggling the building back onto the network, then toggling it back off. Issue: I think there is a weird unintended interaction between Portable Transporter components and network requests. I have not figured out what triggers this.
