-
Notifications
You must be signed in to change notification settings - Fork 116
Network
Much like an ME Terminal, this allows you to view fluids stored on the network. Requires a bucket or something similar (Portable Tank) to add and remove fluids.
Behaves like an ME Interface but for fluids, interacting with tanks, fluiducts and similar. Filter fluids using a bucket or Fluid Pattern.
See ME Export Bus. Filter fluids using a bucket or Fluid Pattern if there is no way to obtain that fluid's bucket.
See ME Import Bus. Filter fluids using a bucket or Fluid Pattern if there is no way to obtain that fluid's bucket.
See ME Storage Bus. Filter fluids using a bucket or Fluid Pattern if there is no way to obtain that fluid's bucket.
See ME Storage Monitor. Configure using a bucket or Fluid Pattern if there is no way to obtain that fluid's bucket.
See ME Level Emitter. Configure using a bucket or Fluid Pattern if there is no way to obtain that fluid's bucket.
See ME Formation Plane.
Behaves like an ME Drive but only holds up to 3 Storage Cells. It can sustain practically any blast.
Behaves like an ME Drive but in the panel form. It can hold 6 Storage Cells.
Behaves like an ME Energy Cell but in the panel form. It can store ? RF.
AE2 cannot autocraft using fluids on the network added by Extra Cells 2. The Fluid Assembler behaves like a Molecular Assembler, allowing crafting with fluids using those in Fluid Storage Cells. Like the Molecular Assembler, it requires a Crafting CPU. It can hold 9 patterns, without the aid of an ME Interface. It currently cannot be upgraded.
Like an ME Export Bus, it exports items from the network, however instead of filtering by item, it filters with the ore dictionary. To know what to type, you can view which dictionary items are in by press F3+H together and then hovering over items. Note that not all items are listed in the ore dictionary, and so cannot be exported in this way.
- Pattern Syntax:
[!][@~]<pattern>
- Filter syntax:
<pattern> [&|] <pattern2> [&|] ...
- Parentheses NOT supported.
-
@
prefix for resource namespace matching (e.g.@minecraft
@AppliedEnergistics
) -
~
prefix for resource path matching -
!
for negation (use before@
and~
if applicable) -
*
can be used in any position, although usage of*
that isn't beginning or end may result in performance hits due to usage of regex matching.
Usage with pure oredict matches (no @
and ~
) will result in querying the oredict once and building a whitelist that is saved and the filter is only evaluated once.
Using @
and ~
will result in the filter being evaluated for every item in AE until it finds a match. May be more performance intensive.
Examples
-
@minecraft & ore*
(All vanilla ores); -
@mine* | @thermal*
(All blocks from mods with namespaces that starts with mine or thermal); -
oreGold | oreIron
(Gold and iron ore only);