AE2FC: Difference between revisions
m Cleaned up the page |
m Cleaned up |
||
| Line 22: | Line 22: | ||
This feature is intended but can be disabled in the config. Fluid patterns have a purple design. [[File:FluidPattern.png|frameless|A Fluid Pattern]] |
This feature is intended but can be disabled in the config. Fluid patterns have a purple design. [[File:FluidPattern.png|frameless|A Fluid Pattern]] |
||
== Dealing with ABS recipes == |
|||
[[File:IndalloyGifAE2FC.gif|frameless|left]] |
[[File:IndalloyGifAE2FC.gif|frameless|left]] |
||
Inserting with containers is especially useful for Indalloy since NEI struggles to insert the recipe for ABS recipes into any pattern terminal. 100 flasks with 144ml of indalloy will be sufficient to make the recipe. To get all the items in the proper quantity for a recipe, simply CTRL + SHIFT + A the recipe in NEI and it will bookmark all ingredients. |
Inserting with containers is especially useful for Indalloy since NEI struggles to insert the recipe for ABS recipes into any pattern terminal. 100 flasks with 144ml of indalloy will be sufficient to make the recipe. To get all the items in the proper quantity for a recipe, simply CTRL + SHIFT + A the recipe in NEI and it will bookmark all ingredients. |
||
| Line 36: | Line 32: | ||
== Fluid Interface == |
== Fluid Interface == |
||
[[File:FluidInterface.png|frameless|left|alt=Fluid Interface|Fluid Interface]] The Fluid Interface works as you might think. Insert the purple pattern into it and it will start extracting both items and fluids. It can work on all sides so if one side is full, it will try to find another find to output to. It can output to any container and will try to output fluids first then items, unless you use the pattern in a normal ME Interface. Then it will send in order as the pattern is described. |
[[File:FluidInterface.png|frameless|left|alt=Fluid Interface|Fluid Interface]] The Fluid Interface works as you might think. Insert the purple pattern into it and it will start extracting both items and fluids. It can work on all sides so if one side is full, it will try to find another find to output to. It can output to any container and will try to output fluids first then items, unless you use the pattern in a normal ME Interface. Then it will send in order as the pattern is described. |
||
| Line 56: | Line 41: | ||
== Fluid Decoder== |
== Fluid Decoder== |
||
[[File:FluidDecoder.png|frameless|left|alt=How to use the Fluid Decoder|How to use the Fluid Decoder]] |
[[File:FluidDecoder.png|frameless|left|alt=How to use the Fluid Decoder|How to use the Fluid Decoder]] |
||
The Fluid Decoder can decode Fluid packets. It has to be connecte to a ME System and a place to store the liquid in otherwise it won't work. You can attach a fluid storage bus from Extra Cells to it in order to make it functional similar to a fluid extractor. The Decoder in the picture only got energy and functions as its own sub-me. |
The Fluid Decoder can decode Fluid packets. It has to be connecte to a ME System and a place to store the liquid in otherwise it won't work. You can attach a fluid storage bus from Extra Cells to it in order to make it functional similar to a fluid extractor. The Decoder in the picture only got energy and functions as its own sub-me. |
||
| Line 81: | Line 58: | ||
[[File:IngredientBuffer.png|frameless|left|alt=Ingredient Buffer|Ingredient Buffer]] |
[[File:IngredientBuffer.png|frameless|left|alt=Ingredient Buffer|Ingredient Buffer]] |
||
The Ingredient buffer is what allows easy management for Multiblocks. It accepts the items the Fluid Interface sends to it and stores it in its internal buffer. There is a default and a large version. The normal one can store 9 items and 4 fluids, the large buffer can store 27 items and 7 fluids. |
The Ingredient buffer is what allows easy management for Multiblocks. It accepts the items the Fluid Interface sends to it and stores it in its internal buffer. There is a default and a large version. The normal one can store 9 items and 4 fluids, the large buffer can store 27 items and 7 fluids. |
||
| Line 116: | Line 87: | ||
== Automating Singleblocks== |
== Automating Singleblocks== |
||
Automating single blocks is very easy. For example raw carbon fibre: |
Automating single blocks is very easy. For example raw carbon fibre: |
||
| Line 126: | Line 96: | ||
== Assline == |
== Assline == |
||
[[File:AE2FluidCraftingPattern.png|frameless|left|alt=AE2FluidCraftingPattern|AE2FluidCraftingPattern]] |
[[File:AE2FluidCraftingPattern.png|frameless|left|alt=AE2FluidCraftingPattern|AE2FluidCraftingPattern]] |
||
First of all, make a pattern as shown. This can be simply done by shift clicking from NEI as usual. |
First of all, make a pattern as shown. This can be simply done by shift clicking from NEI as usual. Place the Pattern in a NORMAL Me Interface (not fluid interface!) for the Assembly line. This allows the fluid to be an item instead of a fluid, allowing automation. Then, follow the instructions on the picture below. |
||
Place the Pattern in a NORMAL Me Interface (not fluid interface!) for the Assembly line. This allows the fluid to be an item instead of a fluid, allowing automation. Then, follow the instructions on the picture below. |
|||
[[File:AE2FCAssline.png|frameless|center|alt=Assline|Assline]]On the bottom you can see the output bus connected with 2 me interfaces. The one facing the bottom is the interface to collect the item once the Assline has finished. The other one pointing forwards is the one containing the patterns. Those two ME-Devices are the only one connected to your main network. Set the Pattern Interface to Blocking Mode (dont push when inventory contains items) |
|||
[[File:AE2FCAssline.png|frameless|center|alt=Assline|Assline]] |
|||
On the sub net, attach an item p2p (input), one anywhere on the sub net and one directed at the input bus. Connect them (1 input [Pattern] 2 outputs [input bus&anywhere]). |
|||
Get a fluid packet and insert fuzzy cards into storage buses from P16 to P19 (Priority). We want the fluid packets to go there. P1 to P4 are fluid storage busses from EC. |
|||
Revision as of 10:22, 28 July 2022
A Quick Guide to Applied Energistics 2 Fluid Crafting. In this wiki page we will concentrate on how to automate Singleblock Machines, Multiblocks and the Assembly line as well on the principles of AE2FC.
AE2FC can be composed of 5 important machines that will be explained further in detail below.
ME Fluid Discretizer
When the ME Fluid Discretizer is attached to your ME System, it will represent the Fluids that are stored in your ME Fluid Storage Cells (Or Storage bus) as drops. They will be the item equivalent of drops. Its just another way to show fluids, it won't actually convert your fluids to items.
Each fluid drop is equivalent to one litres of the repsective fluid. (1000l = 1 Bucket)
A Fluid Discretizer is needed to properly use AE2FC. Every ME-System should only accept one ME Fluid Discretizer as more will cause visiual bugs.
Note that drops will get removed in the future.
You can treat the item drops as actual items and transport drops using an export bus to transport fluids in a different way, but that is not recommended to do.
ME Fluid Pattern Terminal
As the name suggests, it is simply the Pattern Terminal functional with fluids. When using NEI's built in + feature for creating patterns immediately, it will also contain the fluid. You can insert fluid manually with any fluid container such as buckets, cells, flasks. If you insert the Pattern into a Fluid Interface it will try to output both fluids and items. However, if you place the pattern in a normal ME Interface it will send the fluid as a fluid packet which can later be turned back into an actual fluid. This principle will be used for the Assembly line:
This feature is intended but can be disabled in the config. Fluid patterns have a purple design. 
Dealing with ABS recipes
Inserting with containers is especially useful for Indalloy since NEI struggles to insert the recipe for ABS recipes into any pattern terminal. 100 flasks with 144ml of indalloy will be sufficient to make the recipe. To get all the items in the proper quantity for a recipe, simply CTRL + SHIFT + A the recipe in NEI and it will bookmark all ingredients.
Fluid Interface
The Fluid Interface works as you might think. Insert the purple pattern into it and it will start extracting both items and fluids. It can work on all sides so if one side is full, it will try to find another find to output to. It can output to any container and will try to output fluids first then items, unless you use the pattern in a normal ME Interface. Then it will send in order as the pattern is described.
Fluid Decoder
The Fluid Decoder can decode Fluid packets. It has to be connecte to a ME System and a place to store the liquid in otherwise it won't work. You can attach a fluid storage bus from Extra Cells to it in order to make it functional similar to a fluid extractor. The Decoder in the picture only got energy and functions as its own sub-me.
Ingredient Buffer
The Ingredient buffer is what allows easy management for Multiblocks. It accepts the items the Fluid Interface sends to it and stores it in its internal buffer. There is a default and a large version. The normal one can store 9 items and 4 fluids, the large buffer can store 27 items and 7 fluids.
Automating Multiblocks
This is one way of automating a Multiblock with EnderIO cables. Extracting the fluids and items from the ingredient buffer and sending it to different hatches. If you want, you can use a sub-me and (item/fluid) storage bus to distribute items.
Automating Singleblocks
Automating single blocks is very easy. For example raw carbon fibre: Make a pattern to turn 1 ingot of PET to 144l of molten PET and put it in a fluid interface dedicated for a fluid extractor. (Or a sub-net)
Make another pattern with the actual raw carbon fibre recipe and put it in a fluid interface for an autoclave. And done! Make sure to allow input from output (screwdrive front) and it will work perfectly fine. You can also use fluid storage bus to use fluids instead of making a fluid extractor recipe for it.
Assline
First of all, make a pattern as shown. This can be simply done by shift clicking from NEI as usual. Place the Pattern in a NORMAL Me Interface (not fluid interface!) for the Assembly line. This allows the fluid to be an item instead of a fluid, allowing automation. Then, follow the instructions on the picture below.
On the bottom you can see the output bus connected with 2 me interfaces. The one facing the bottom is the interface to collect the item once the Assline has finished. The other one pointing forwards is the one containing the patterns. Those two ME-Devices are the only one connected to your main network. Set the Pattern Interface to Blocking Mode (dont push when inventory contains items)
On the sub net, attach an item p2p (input), one anywhere on the sub net and one directed at the input bus. Connect them (1 input [Pattern] 2 outputs [input bus&anywhere]).
Get a fluid packet and insert fuzzy cards into storage buses from P16 to P19 (Priority). We want the fluid packets to go there. P1 to P4 are fluid storage busses from EC.