Ore Processing Concepts: Difference between revisions

m
no edit summary
(Added AE setup "walkthrough")
mNo edit summary
 
(12 intermediate revisions by 7 users not shown)
Line 1:
{{cleanup|Some of the images use a texture pack which makes it impossible to know what blocks are in use. Needs new screenshots.}}
GTNH is all about technology (mechanical or magical). But lets face it, you won't be getting anywhere by just slapping those wooden logs together. All the metals you need have to be ripped out of the ground and processed from their useless ores into a pure form (usually dusts) for further processing. And that's why you're here.
 
Line 48 ⟶ 49:
== Overview of Designs ==
{| class="wikitable"
|+[[Tier]] Comparison of Ore Processing Designs
!Ore Processing Design
!Tech Tier
Line 153 ⟶ 154:
# Although I made a "linear" looking central line in the images above, you can actually put the output chest anywhere. In practice I tend to put the output chest right next to the input chest to make interfacing with other logistics (eg. AE) easier. This is because the priority system doesn't care where an inventory is, only that it follows the priority rules.
 
== [HV+] GTEnderIO PipesConduits &+ GT Type Filters ==
A fully specified ore processing system using EnderIO Conduit colors with GT Type filters, with all exception item filters up through moon rock processing fully specified can be found here on Reddit: [https://www.reddit.com/r/feedthebeast/comments/s6oxxu/gtnh_hv_tier_sequential_material_refining_engine/ Sequential Material Refining Engine]
 
== [HV+] Item Pipes & Type Filters ==
 
== [EV/IV+] Applied Energistics 2 ==
Line 180 ⟶ 184:
# ME Storage Cell. Place inside the ME Drive. You will need at least 1.
# ME Interfaces (the full block type). These will serve as the import blocks, from which the outputs of your machines will be pushed into to enter the AE network. How many you need depends on how creative you are with your GT piping.
# ME Storage Buses. You will need 1 for each input bus of your multiblock machines, and one extra to handle overflow (optional).
# ME Oredictionary Filter Cards. This is the magic that makes AE amazing for ore processing. You will need at least 1 per storage bus, with some exceptions.
 
Line 195 ⟶ 199:
ME Storage Buses attempt to push out compatible items, when immediately received by the network via '''either''' ME Interfaces '''or''' ME Import Buses, into the inventories that they face. Conventionally, these would be storage blocks like chests/drawers/barrels. But note that Input Buses also have internal inventories. Thus, when we place an Oredict card inside a ME Storage Bus facing towards an Input Bus, we have created an intelligent exporter of items!
 
Another thing to note is that the Oredict Card is capable of filteringusing an arbitrarilya complex setmix of requirements (limited to 120 characters) for the items being exported by the storage bus. Asterisks (*) serve as fuzzy placeholders, vertical bars (|) serve as OR conditionals, exclamation points (!) serve as NOT conditionals, and ampersands (&) serve as AND conditionals. The oredict card does not support parenthesis.
 
For our purposes we will want the following definitions (within the brackets) inside our ME Storage Buses, based on the machines they are facing. The brackets themselves are not required for the Oredict definitions.
 
# To Macerators: ( crushedCentrifuged* | ore*). In& human-speak,!oreOilsands this& !oreBlackgraniteOilsands This means Ores OR Centrifuged Ores AND exclude Ore Oilsands, which cannot be macerated. This enables initial maceration of whole ores (from VMs) and maceration of centrifuged ores (from LTRs) to recover tertiary byproducts.
# To OWPs: ( crushed* & !crushedPurified* & !crushedCentrifuged* &!crushedBastnasite & !crushedMonazite). This means Crushed Ores that are NOT Purified and are NOT Centrifuged, as well as NOT Crushed Bastnasite and NOT Crushed Monazite This is needed because (crushed*) by itself also encompasses crushed, purified AND centrifuged ores due to the ways they are oredicted. The crushed Bastnasite and Monazite ores go into the Lanthanide Processing Line.
# To LTRs: ( crushedPurified* & !*Galena* & !*Sphalerite*). This means Purified Ores that are NOT containing Galena AND are NOT containing Sphalerite in their names. This is needed as we want to export these 2 specific purified ores for indium processing later.
# To Large Sifters: No definitionsThere are required,2 althoughstrategies you '''should'''can use. For either of them you need to increase the priority forof thesethe Storagestorage Busesbuses to be significantly higher than those on the LTRs as purified ores that can be sifted '''might'''may be sent to the LTRs instead of the Large Sifters if you don't change the priority. You must also have enough/fast enough sifters to keep up with your your input or sift-able ores will overflow into the LTRs.
## On the storage bus, use capacity cards and manually specify each item you wish to sift. You can pull these from NEI, make sure to use the proper version of the ore: ie purified certus quartz, not crushed.
# To output from the Ore-proc Subnet: (crushedPurifiedGalena | crushedPurifiedSphalerite) on 1 ME Storage Bus, and (*dust* | *gem*) on another ME Storage Bus. This means Purified Galena and Purified Sphalerite Ores, as well as all Dusts and Gems.
## Have no filter on the storage bus and use a screwdriver to turn on the Input Filter on the input buses on the large sifters. This setting prevents any items that don't have recipes from being inserted into the bus, thus combined with the higher priority of the bus will result in sifting anything that can be.
# 2 storage buses are required to output from the Ore-proc Subnet:
## crushedPurifiedGalena | crushedPurifiedSphalerite (external processing)
## *dust* | *gem* (desired products)
 
Thus, to setup an AE-compatible system, we will do the following.
Line 212 ⟶ 220:
# Setup the ME Interfaces to collect back the outputs from the multiblock machines. No extra fiddling with the interfaces is required besides initial placement and hooking up to the network. For the player on a channel budget, you can use GT pipes with large throughputs (platinum or quantium) to funnel outputs from multiple output buses into a single ME Interface.
# Setup an Output. This involves ME Storage Buses with the appropriate definitions as above, facing towards a Chest Buffer (ideally IV-tier) pushing into an ME interface linked to your '''main AE Network.'''
# (Optional) Setup an Overflow. The overflow should be a storage bus with minimum priority but with no definitions at all. Any items that is not supposed to go to output but does not have anywhere else to go (because all the input busses are full) should go here, and should be pushed back into the '''Input.''' (This is only needed if your system cannot process all the materials fast enough, and if you usually have some downtime between ore-processing batches, which is common in EV/IV. Note that having an overflow buffer is a lot less useful with VMs as you don't have any downtime to process the items in the overflow. Get more machines.)
 
And like this, you now have an AE-linked ore processing machine capable of:
Line 231 ⟶ 240:
== [LV+] Limited Flexibility GT Pipes ==
placeholder
 
[[Category:Guides]]
3

edits