Chassi+provider module not working with multiple chests connected to it
Opened this issue · 6 comments
This is my setup
When I look into a request pipe I only see items from 1 chest, but if I change the chassi for a provider pipe it works. I'm using the chassi to also have an itemsink module which only routes items into 1 chest.
Yes, this is the way chassis pipes work.
They choose one inventory to connect to, and you can change which one with a wrench or something.
It's actually really useful when working in tight spaces.
On Aug 25, 2016, at 2:58 AM, tutkis [email protected] wrote:
This is my setup
When I look into a request pipe I only see items from 1 chest, but if I change the chassi for a provider pipe it works. I'm using the chassi to also have an itemsink module which also only registers 1 chest.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
Yeah, as @1n5aN1aC said this is how pipes were designed, There is no way to tell which provider module work with which chest, it can be done only in per-pipe basis. So if you wanna work with multiple chests, connect a pipe for each of them. I recommend you a mk2 pipe with a provider and a itemsink/polymorphic module. Protip: if you use polymorphic, don't forget to set the provider to leave 1 item per type.
Indeed, Chassis Pipes are DESIGNED to only be able to connect to one inventory. Its also indicated by the Orange Dots on the the Pipes, Structural Arms that face the currently connected Inventory.
Notice one Side of the Pipe has both a Red and an Orange mark on it. thats the currently selected Inventory.
Im sorry but theres no way you can access 4 Inventories With both In and Output in a single pipe. And thats by design.
Ahh okay thank you all. Redesigned my system, using a provider and a basic for 2 double chests.
@Bitterholz i think we could close this then.
