Dump everything in an ME network into chests?

[Ieldra]

I'm trying to find a more compact solution to this than "Use a number of export buses or interfaces equal to the number of different item types in the network divided by 8".

The problem: I'm storing my ores in a subnetwork and would like to send them to be processed with a switch. I've set it all up and it works nicely, however this part of it is unelegant and clumsy: there are about 45 different Extractable ores (counting different ore dictionary versions as one) in an FTB Monster game (possibly more), so I needed to use six export buses and a minimum of two buffer chests to get them all out. I find that unsatisfactory and would like to know if anyone has found a more elegant solution.

When trying this first, I was mislead by the fact that Logistics Provider Pipes can see the whole ME network if connected to an unconfigured ME Interface. Unfortunately, these are the only LP functions which can. Extractor modules and Pipes only see items in the export list of the ME interface, so while you can supply machines with specific items from the ME network with the Provider/Supplier system, Logistics Pipes can't be used to extract items out of the network by the Extractor's "empty blacklist" functionality. The same applies to TE itemducts and EnderIO conduits. You can't even pipe out items from an ME chest.

So...is there any other solution to this?

 

[namiasdf]

You guys and your subnetworks. All I do is attach a storage bus to a chest and preformat it to all the things that I want.

This goes for all the things I want auto-smelted, auto-pulverized, etc.

 

[Ieldra]

You guys and your subnetworks. All I do is attach a storage bus to a chest and preformat it to all the things that I want.

This goes for all the things I want auto-smelted, auto-pulverized, etc.

The thing is, I actually don't want to auto-process my ores when they come in. First, I don't always have the power to process them at the same time I'm mining them. Second, I sometimes mine for something specific and leave the other ores stored until I need them. Third with RoC's ore-quintupling it's more efficient to store the ores rather than the ingots.

It's easy to process something specific at request. Just put a block of ore into an export bus pointing at the extractor and throw the switch. Processing everything at request, that's the clumsy part.

 

[Platinawolf]

Can't you use a small LP network for that effect? I had something similar for tossing out items into barrels and stuff... Quicksort module can take items that have specific places to go out of a AE network.

Interface -> Chassipipe with quicksort module -> LP-network -> Chassipipe with oredictionary item-sinks -> Processing system

 

[Racemol]

I would look into the LP pipes too. As Platinawolf said those pipes can 'interface' (heh) with an AE interface. I use that to remote order stuff from my AE network to an ender chest. I have a linked pouch with me so I can grab stuff from my AE network from wherever I am. I figure this should work kinda similar to what you want. Just let the LP network export the stuff you want melted on a redstone signal or something.

 

[Platinawolf]

The easiest way to disable the export would be to cut off the interface with a dark-cable. Might be able to disable the chassipipes via gates though,,,

 

[Ieldra]

I would look into the LP pipes too. As Platinawolf said those pipes can 'interface' (heh) with an AE interface. I use that to remote order stuff from my AE network to an ender chest. I have a linked pouch with me so I can grab stuff from my AE network from wherever I am. I figure this should work kinda similar to what you want. Just let the LP network export the stuff you want melted on a redstone signal or something.

Yeah, I've been using that method too. However, that method uses the LP request mechanics, which do work with an unconfigured ME Interface. Logistics Pipes extraction mechanics, however, do not work. Thus, I can tell the ME network "give me this specific thing" or automate "give me all you have until my inventory is filled of these these 9 specific things" in case of a supplier pipe. I'd still need five supplier pipes to extract all ores from the subnetwork, which isn't that much better than six export buses, and actually takes up *more* space because I can't replace Logistics Pipes with EnderIO conduits.

@Platinawolf:
I have no problem controlling the start/end of the exporting process. I have a problem to tell the system "export everything" without having to use one export bus for every 8 item types.

 

[Platinawolf]

Yeah, I've been using that method too. However, that method uses the LP request mechanics, which do work with an unconfigured ME Interface. Logistics Pipes extraction mechanics, however, do not work. Thus, I can tell the ME network "give me this specific thing" or automate "give me all you have until my inventory is filled of these these 9 specific things" in case of a supplier pipe. I'd still need five supplier pipes to extract all ores from the subnetwork, which isn't that much better than six export buses.

@Platinawolf:
I have no problem controlling the start/end of the exporting process. I have a problem to tell the system "export everything" without having to use one export bus for every 8 item types.

A tier 5 chassi pipe should be able to hold the various oredict itemsinks that you need (Think each oredict can keep 9 items). And the quicksort module will take anything from a ME network that has another place to put it in other than default path. May it be cobblestone, rubber, wood or ores. Its different from the export modules in that its rather intelligent... Mind you, that was the DW20 pack for 1.64 but it should still work in monster.

Edit:
Did a small test-setup and I realised that there's the Aspect Item Sink. You could get one of those and set it to Metallum and get most of the normal ores. Each aspect sink seems to be able to hold 9 different aspects and if your sub-network only has ores you could use that to get the other ores to.

 

[Ieldra]

Can't you use a small LP network for that effect? I had something similar for tossing out items into barrels and stuff... Quicksort module can take items that have specific places to go out of a AE network.

Interface -> Chassipipe with quicksort module -> LP-network -> Chassipipe with oredictionary item-sinks -> Processing system

Hmm...that might actually work - if the Quicksort extraction works with an unconfigured ME Interface.

 

[belgabor]

Same setup here, unfortunately I don't think that there is a solution. I'm using supplier pipes set to only do full stacks to feed chests, mostly so my extractor doesn't process single items.

 

[Ieldra]

A tier 5 chassi pipe should be able to hold the various oredict itemsinks that you need (Think each oredict can keep 9 items). And the quicksort module will take anything from a ME network that has another place to put it in other than default path. May it be cobblestone, rubber, wood or ores. Its different from the export modules in that its rather intelligent... Mind you, that was the DW20 pack for 1.64 but it should still work in monster.

Yes, I've been using Mk5 Chassis pipes to get my ores into the subnet in the first place. Yet again, extracting things the same way with a quicksort module might work - if the quicksort module can actually see the whole contents of an ME network through an unconfigured interface as the Provider pipe can. Can it?

 

[Platinawolf]

Yes, I've been using Mk5 Chassis pipes to get my ores into the subnet in the first place. Yet again, extracting things the same way with a quicksort module might work - if the quicksort module can actually see the whole contents of an ME network through an unconfigured interface as the Provider pipe can. Can it?

As long as there's some marked place for the quicksort module to put it other than the default route. For example, if you have a ME network filled with cobblestone with an unconfigured interface for the LP system to access and a item-sink configured for cobblestone connected to a chest, the quicksort module will happily take all the cobble it can get and stuff it in the chest.

 

[Ieldra]

As long as there's some marked place for the quicksort module to put it other than the default route. For example, if you have a ME network filled with cobblestone with an unconfigured interface for the LP system to access and a item-sink configured for cobblestone connected to a chest, the quicksort module will happily take all the cobble it can get and stuff it in the chest.

Neat. Many thanks. I'll need to make a separate LP network for that, but that shouldn't be a problem. If I remove some of the now unnecessary chests from my compact setup I should have the space for a Firewall pipe.