GregTech CEu Modern · Automation · Advanced
How to Automate GregTech Machines with Applied Energistics 2 (AE2)
Mastering the integration between GregTech CEu Modern and Applied Energistics 2 (AE2) is essential for surviving the late-game tiers without drowning in manual microcrafting. In this advanced guide, you will learn how to resolve Programmed Circuit conflicts, utilize dual-input mechanics for multi-fluid recipes, and fully automate the notorious Assembly Line with zero deadlocks. Implementing these logistics patterns will allow your factory to process complex crafting trees effortlessly on demand.
What you need
- Established AE2 ME Network with Crafting CPUs and Pattern Encoding Terminal
- ME Pattern Providers and ME Interfaces (both block and cable sub-part variants)
- ME Storage Buses and Quartz Fiber for subnetting
- GregTech Singleblock Machines and Multiblocks (e.g., Large Chemical Reactor, Assembly Line)
- GregTech Input Buses, Input Hatches, and Dual Input Hatches (or ME Stocking Buses/Hatches if available in your modpack)
- Programmed Circuits (or Ghost Circuit functionality in GTCEu Modern)
- GregTech Wrench, Screwdriver, and Wire Cutters
- Item Pipes (e.g., Brass or Electrum) and Fluid Pipes (e.g., Stainless Steel or PTFE) with Conveyor Modules and Electric Pumps
Step by step
1Configure Singleblock Auto-Output and Input
Place your GregTech singleblock machine and attach an ME Pattern Provider directly to one of its faces. Equip your GregTech Screwdriver or Wrench, open the machine's GUI, and click the Item Auto-Output and Fluid Auto-Output buttons to point toward the Pattern Provider. Next, enable 'Allow Input from Output Side' in the GUI settings so the Pattern Provider can both push ingredients and receive finished products through a single face.
Tip: Using a single machine face for both input and output saves immense amounts of AE2 channels and compact cable routing.
2Eliminate Programmed Circuit Conflicts
In GregTech CEu Modern, you do not need to craft physical Programmed Circuits to put inside your AE2 patterns. Instead, open the machine or Input Bus GUI, click the ghost circuit slot in the bottom right corner, and set it to the desired configuration number (e.g., Circuit 1 for basic bending). Build a dedicated machine or Input Bus for each frequently used circuit number rather than sharing one machine across multiple circuit types.
Tip: For multiblocks like the Electric Blast Furnace or Large Chemical Reactor, simply add multiple ULV or LV Input Buses to the structure, setting each bus to a different ghost circuit number.
3Enable Distinct Buses on Multiblocks
When a single multiblock has multiple Input Buses with different ghost circuits, its default behavior is to pool all items together, which breaks circuit separation. Open the GUI of your multiblock's Input Buses or the Controller itself and toggle 'Distinct Buses' to ON. This forces the multiblock to evaluate recipes per individual bus rather than combining inventories, allowing one multiblock to safely handle recipes requiring Circuit 1, Circuit 2, and Circuit 5 simultaneously.
Tip: Note that Fluids do not have a 'Distinct Hatches' toggle; fluid separation must be handled via Pattern Provider Blocking Mode.
4Automate Multi-Fluid and Multi-Item Recipes
Modern AE2 Pattern Providers can push both items and fluids simultaneously, but standard GregTech machines cannot accept both through a single hatch on a multiblock. To solve this without upgrades, place an ME Pattern Provider against an ME Interface connected to a small AE2 subnetwork (powered via Quartz Fiber). Put an ME Storage Bus on the multiblock's Input Bus and another on the Input Hatch (or Quadruple Input Hatch for multi-fluid recipes); the Pattern Provider pushes the mixed package into the subnet, which instantly routes items to the bus and fluids to the hatch.
Tip: Once you reach the LuV tier or if your setup includes Dual Input Hatches, you can skip the subnet and place the Pattern Provider directly on the Dual Input Hatch.
5Enforce Blocking Mode to Prevent Recipe Collisions
Many GregTech machines, especially the Large Chemical Reactor and Mixer, will accidentally craft the wrong product if materials for two different recipes enter the machine at the same time. Open your ME Pattern Provider GUI and toggle 'Blocking Mode' to ON (do not push if inventory contains items). If you are using the AE2 subnet method from the previous step, make sure the ME Interface receiving the items is set to remain empty so the Pattern Provider accurately detects when the target Input Bus and Hatch are still processing the previous batch.
Tip: Always double-check JEI for recipe conflicts before batch-crafting chemicals in a Large Chemical Reactor.
6Prepare the Assembly Line Structure for Ordered Inputs
The Assembly Line is the ultimate logistics puzzle because it requires up to 16 items and 4 fluids inserted into very specific slices in exact sequential order from slice 1 (closest to the controller) to slice 16. Build your Assembly Line using ULV Input Buses for each bottom slice. Using ULV Input Buses is mandatory for simple pipe routing because they only have 1 inventory slot, naturally preventing multiple stacks of the first item from overflowing into a single bus.
Tip: If you use higher-tier buses on an Assembly Line, you will be forced to use Robot Arms set to 'Keep Exact' instead of simple piping.
7Build the Assembly Line Distribution Subnet
Instead of using GregTech pipes which can have travel-time delays, build a dedicated AE2 Subnet along the Input Buses and Input Hatches of the Assembly Line. Attach an ME Storage Bus to every single ULV Input Bus and Fluid Input Hatch. Assign priorities to these Storage Buses in descending order: Slice 1 gets Priority 100, Slice 2 gets Priority 99, Slice 3 gets Priority 98, and so on down the line, doing the exact same priority cascade for the fluid hatches.
Tip: Label your Pattern Provider carefully so you know it belongs to the Assembly Line.
8Encode Ordered Assembly Line Patterns
Place your main network's ME Pattern Provider against an ME Interface on your Assembly Line subnet, and turn Blocking Mode ON. When encoding your Processing Pattern in the Pattern Encoding Terminal, verify via JEI that the items and fluids in your pattern grid are arranged in the exact left-to-right, top-to-bottom order required by the Assembly Line recipe. Because AE2 pushes items out of a Pattern Provider in the exact slot order of the pattern, the first item will automatically snap into the Priority 100 Storage Bus (Slice 1), the second item into Priority 99 (Slice 2), and so on, guaranteeing a flawless craft.
Tip: If an Assembly Line recipe requires two separate stacks of the exact same item in different slices, put a wooden chest buffer between the Pattern Provider and the subnet, pulling items out with a High-Tier Conveyor Module so they insert one stack at a time.
How it works
Understanding why AE2 and GregTech clash comes down to how both mods treat inventories. AE2 Pattern Providers want to dump an entire recipe's worth of items and fluids into a single block face in one tick. While GregTech singleblocks can accept both items and fluids on any face, GregTech multiblocks split their inputs across physically separate blocks: Input Buses for items and Input Hatches for fluids. By placing an AE2 subnetwork (an isolated cable line with an ME Interface and ME Storage Buses, powered only by a Quartz Fiber) between your Pattern Provider and the multiblock, you create a virtual unified inventory. To the main network's Pattern Provider, the subnet looks like a single chest that accepts both fluids and items, while the Storage Buses handle the physical separation behind the scenes.
Furthermore, Blocking Mode works by scanning the target inventory before pushing the next batch. In a standard subnet setup, if the Pattern Provider pushes into a buffer chest, the items leave the chest immediately, tricking the Pattern Provider into thinking the machine is empty and causing it to push a second batch prematurely. By pushing directly into an ME Interface on a Storage-Bus-only subnet, the items are never stored in the Interface; they are written directly to the GregTech Input Buses via the Storage Buses. Consequently, the Pattern Provider can 'see' the items sitting inside the GregTech buses and will faithfully wait until the machine consumes them before pushing the next recipe.
For the Assembly Line, the logic relies on AE2's deterministic array iteration. When a Pattern Provider pushes a batch of items into a destination network, it iterates through the pattern slots sequentially from top-left to bottom-right. As item #1 enters the subnet, the subnet checks for the highest priority Storage Bus with an empty slot—which is Slice 1 (Priority 100). Since you used a 1-slot ULV Input Bus, Slice 1 is now completely full. When item #2 enters the subnet a fraction of a millisecond later, Slice 1 rejects it, forcing item #2 into the next highest available destination: Slice 2 (Priority 99). This marriage of 1-slot inventories and descending priorities transforms chaotic batch-crafting into strict sequential ordering.
Common mistakes
- Encoding physical Programmed Circuits into patterns: Never put a circuit inside the AE2 processing pattern itself unless you plan on ejecting it back into the network, which easily jams machines. Always rely on the internal ghost circuit selector and 'Distinct Buses'.
- Using high-tier Input Buses on the Assembly Line: If you use an MV or HV Input Bus on an Assembly Line slice, its multiple slots will swallow the entire recipe into Slice 1. Always use 1-slot ULV Input Buses for item slices when using priority-based routing.
- Pushing into a buffer chest with Blocking Mode enabled: If you put a crate or chest between your Pattern Provider and your GregTech machine, Blocking Mode becomes useless because the chest empties into the pipes before the machine finishes crafting, allowing recipes to mix and jam.
- Sharing fluid hatches without Blocking Mode: Because GregTech multiblocks do not have a 'Distinct Hatches' feature for fluids, pushing multiple fluid recipes into a Quadruple Input Hatch without Blocking Mode will mix chemicals and create unwanted byproducts.
FAQ
Why is my Pattern Provider refusing to push fluids into the subnet?
Check your ME Storage Buses on the fluid Input Hatches. Ensure you have used a standard ME Storage Bus (which handles both items and fluids in modern AE2 versions) and that the GregTech Input Hatch actually has enough internal capacity (in buckets/millibuckets) to hold the entire fluid amount required by a single batch of the pattern.
How do I handle Assembly Line recipes that require Data Sticks or Data Orbs?
Do not encode the Data Stick or Data Orb into your AE2 pattern. Instead, leave the required Data Stick permanently inside the Assembly Line's Data Access Hatch (or Advanced Data Access Hatch). The multiblock will read the data repeatedly without consuming the item.
What happens if an Assembly Line recipe uses two stacks of the same wire or plate in different slots?
If you push directly into an AE2 subnet, AE2 may try to combine identical items or fail if the stack size exceeds 64 in a single tick. To fix this, have the Pattern Provider push into an inventory buffer (like a GregTech Crate), and use an EV or IV Conveyor Module to pull items out into the subnet's ME Interface. Because the Conveyor pulls stack-by-stack, each stack enters the 1-slot ULV buses sequentially without merging.
Can I automate the Assembly Line using GregTech pipes instead of an AE2 subnet?
Yes, by running an Item Pipe across all ULV Input Buses and a Fluid Pipe across the Input Hatches, and having the Pattern Provider dump into a buffer crate. However, GregTech pipes have travel time and routing quirks that can sometimes put item #2 into slice #1 if the pipe junction isn't perfectly linear. The AE2 subnet method is instantaneous and tick-perfect.
By combining GregTech CEu Modern's Distinct Buses and ghost circuits with AE2's Blocking Mode and priority-ordered subnetworks, you can seamlessly automate everything from simple singleblock chemical processors to complex 16-slice Assembly Lines without recipe jams.