Ore Processing Concepts: Difference between revisions

Add most of EIO ore processing
(added some central line starter stuff)
(Add most of EIO ore processing)
Line 52:
== [MV+] EnderIO Conduits - The "Central Line" ==
[[File:Simplest Possible EnderIO Central Line Ore Processing.png|thumb|This shows the simplest version of a "central line" ore processing system. It has one route (priority -2) and is currently useless for anything practical. Gold chest = input and copper chest = output.]]
[[File:EnderIO Ore Processing Macerator Module.png|thumb|This shows the second most basic EIO ore processing setup - a central line with an attached macerator round robin module.]]
EnderIO conduits are your first and cheapest option for creating a truly flexible ore processing system. This system is built around a "'''central conduit line'''" which all ores go through, and connected "'''modules'''" route ores into machines. Because of its modular nature, it is easy to add new routes or expand old ones. This is made possible due to the EIO conduit "'''priority'''" system, which allows us to make override routes.
 
Line 64 ⟶ 65:
The simplest version of this is an input chest set to extract always, some conduits inbetween, and an output chest at -2 priority. Then everything you input (ores, random tinker tools by accident, w/e) will go to the output chest. But obviously this isn't very useful.
 
So you start adding "'''modules'''" to your inbetween conduits. These provide routes for ores to go. Let's start with a macerator module.
 
'''[The Macerator Module]'''
 
For every module, you must choose two things: the filters and the machines. For a macerator, we want to automatically send anything that fits these characteristics:
 
# ore
# crushed ore
# crushed purified ore
# crushed thermal centrifuged ore
 
GT type filters are perfect for this, so let's add four of those and configure appropriately.
 
Now I will add a buffer chest - this will hold items routed by EIO, but not yet processed by machines. If the buffer chest gets full, items will go to the next available route - in this case, the output chest with priority -2. This can lead to undesirable behavior with very large inputs - for example, if the Rare Earth macerator buffer chest gets overfilled, it might accidentally get routed to the normal macerators instead (which is bad). Unfortunately, there are no easy fixes for this besides adding bigger buffers.
 
Now I round robin extract from the buffer chest into my macerators. EIO lets you easily select this option by just hitting a toggle in the menu. For the connections to the macerators, I set input on green (from my buffer chest) and output on red. This programming can get a bit tedious, so I recommend making a conduit probe whenever you can - this lets you copy conduit settings.
 
Finally, I add a "transfer chest." This is just so that my macerator round robin logic doesn't accidentally get sent to the rest of the central line.
 
'''[The Rest of the Line]'''
 
Every module you add will look almost exactly like the macerator module. The only things you swap out will be different filters and machines in place of the macerators. For specific item overrides (eg. I want crushed bauxite specifically to go to thermal centrifuging), remember to use priority 0, as this will override items going to the normal macerator route we defined above.
 
On the right you can see an example of a fully fledged EIO ore processing line.
 
'''[How Desirable is the System?]'''
 
# '''Flexible: S Rank.''' It is very easy to add new modules, and they can be added in any configuration (before or after existing modules) without breaking things. Filters are very explicit and can be examined visually with NEI-like images.
# '''Expandable: S Rank.''' All that you need is a space for item I/O, and EIO lets you do input and output from the same side. If you need fluids later, like for rare earths, you can bundle an ender fluid conduit inside the item conduit.
# '''Unbreakable: A Rank.''' While this system by default is very robust to random items thrown in, like backpacks and tinker tools (these will automatically go to the output chest since they have no routes), the ability for logic to break down if buffer chests fill is a major weakness. While you can always add more chests, it is never able to be "truly" solved - a large enough input can still break your system.
# '''High Throughput: B Rank.''' Item conduits are by default quite slow (4 items every 0.8 seconds or so). You can upgrade them up to 64 per 0.8 seconds, but this is still much too slow for endgame. You can use conveyors into conduits to get a sufficiently high throughput, but using conveyors everywhere is relatively expensive and annoying compared to just using AE interfaces.
# '''Lag Friendly: A Rank.''' EIO conduits are fine unless you're stargate tier. They are pretty optimized, just not to the level of AE.
# '''Minimal Human Intervention: S Rank.''' EIO Conduits are perfect for no intervention ore processing. You only touch the system when adding new modules or doing new upgrades. If you accidentally drop your tinker tool inside, you can simply collect it from the output chest instead of having to figure out what multi input bus it's inside.
 
'''[Other Stuff to Remember]'''
 
# 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.
 
== [EV+] Applied Energistics 2 ==
151

edits