Modular Machinery Reborn · Automation · Intermediate
How to Automate Modular Machinery: AE2, Refined Storage, and Pipe Setups
Automating custom multiblocks in Modular Machinery Reborn requires smart routing across multiple input and output blocks rather than connecting to a single machine face. In this guide, you will learn how to integrate tiered Item Input Buses, Fluid Input Hatches, and Output blocks with Applied Energistics 2, Refined Storage, and standard logistics pipes. Mastering these setups prevents recipe deadlocks, stops input buses from overflowing, and enables hands-free batch crafting.
What you need
- A fully assembled Modular Machinery Reborn multiblock structure (showing 'Structure Formed' in the Machine Controller GUI)
- Tiered Item Input Buses and Item Output Buses (e.g., Small, Normal, Reinforced, Big, or Huge tiers depending on your recipe slot needs)
- Tiered Fluid Input Hatches and Fluid Output Hatches (if your recipes require fluids)
- An Energy Input Hatch connected to a stable FE/RF power source
- AE2 setup: ME Pattern Provider, ME Import Bus, ME Storage Bus, Quartz Fiber, and Fluix Cables
- Refined Storage setup: Crafter, Importer, External Storage, and Network Cables
- A buffer chest or crate (useful for combining mixed item and fluid recipes)
Step by step
1Verify Multiblock Structure and Bus Tiers
Right-click your Machine Controller to confirm the structure is valid and formed. Check JEI for the exact recipes you plan to automate and count the maximum number of distinct item stacks and fluid types required. Replace any Tiny or Small Item Input Buses with larger variants (like Reinforced or Big Item Input Buses) if your recipes demand more slots than the bus currently offers.
Tip: You can never interact directly with the Machine Controller for item or fluid transfer; all automation must attach directly to the specific buses and hatches.
2Establish Continuous Power to the Energy Input Hatch
Attach your power cables or flux points directly to the Energy Input Hatch on the multiblock. Check the recipe requirements in JEI to see the FE/t consumption rate, and ensure your Energy Input Hatch tier has a buffer and transfer rate capable of sustaining it. If power drops mid-operation, the recipe progress can stall or reset depending on how the modpack creator configured the recipe.
3Set Up Continuous Processing with Pipes or Hoppers
For passive, single-recipe machines, attach your item pipes directly to the Item Input Bus and fluid pipes to the Fluid Input Hatch. If the recipe uses multiple different items, apply a round-robin or stock-limit filter on your pipes so one plentiful ingredient does not fill every slot in the Item Input Bus. Connect extraction pipes to the Item Output Bus and Fluid Output Hatch to continuously pull finished products into your storage system.
Tip: If your modpack includes LaserIO, XNet, or Pipez, use counting filters to keep exactly one stack of each required ingredient inside the Item Input Bus.
4Configure Simple On-Demand Crafting (Items Only)
If a recipe only uses items and you only have one Item Input Bus, place an AE2 ME Pattern Provider or a Refined Storage Crafter directly against the Item Input Bus. Encode a Processing Pattern with the exact recipe inputs and outputs as shown in JEI, then insert it into the provider or crafter. Because all items enter the same bus, the machine will immediately begin processing as soon as the network pushes the ingredients.
5Build a Subnet or Buffer for Mixed Item and Fluid Recipes
When a recipe requires both items and fluids, a single Crafter or Pattern Provider cannot push directly into both an Item Input Bus and a Fluid Input Hatch simultaneously. For AE2, place a directional ME Pattern Provider against a flat ME Interface to form a subnetwork, then attach filtered ME Storage Buses onto your multiblock's Item Input Bus and Fluid Input Hatch. For Refined Storage or simpler pipe setups, point your Crafter into a buffer chest or tank that supports both items and fluids, or use dedicated filtered pipes to split items into the Item Input Bus and fluids into the Fluid Input Hatch.
Tip: Power the AE2 subnet using a Quartz Fiber bridge from your main network so channels do not mix.
6Enable Blocking Mode to Prevent Recipe Collisions
When automating multiple distinct recipes in the same multiblock, ingredients from two different queued crafts can mix inside the Item Input Bus and cause the wrong recipe to trigger. Open your ME Pattern Provider and enable 'Blocking Mode' (or use lock modes in Refined Storage) so the network waits until the input inventory is completely empty before sending the next batch. If you are using a subnet, make sure your ME Storage Buses on the input hatches have 'Report Inaccessible Items' enabled so the Pattern Provider can see when the buses still hold ingredients.
Tip: Alternatively, use multiple separate Small Item Input Buses on the same multiblock and filter each bus to accept only the ingredients for one specific recipe.
7Automate Multi-Output Extraction
Attach an AE2 ME Import Bus or Refined Storage Importer to every Item Output Bus and Fluid Output Hatch on your multiblock, then wire them back to your main storage network. Check JEI to make sure your Output Buses have enough internal inventory slots to hold all primary products and secondary byproducts from a single craft. If an Output Bus fills up completely, the Machine Controller will halt further crafting until space is cleared.
Tip: Insert Speed or Acceleration Upgrades into your Importers; high-tier machines can finish crafts faster than an unupgraded bus can pull items out.
How it works
Unlike standard single-block machines where sides are configured for input or output, Modular Machinery Reborn separates functionality into dedicated component blocks. The Machine Controller acts as the brain: every tick (or configured check interval), it scans all attached Input Buses and Hatches that belong to its formed structure. Once it detects a valid combination of items, fluids, and energy matching a JSON or KubeJS recipe, it consumes the inputs at the start of the cycle and begins ticking down the recipe duration.
Because the Machine Controller consumes the ingredients immediately upon starting a craft, the Input Bus actually becomes empty while the machine is still running. If you use Blocking Mode, your AE2 or Refined Storage system might push the next batch of ingredients while the current craft is still processing. This is generally safe because those items will sit ready for the next cycle, provided you do not push enough items to overflow the bus slots.
At the end of the crafting cycle, the Machine Controller pushes all resulting items and fluids into the attached Item Output Buses and Fluid Output Hatches. If the output blocks do not have enough free capacity to accept the entire recipe yield, the machine will either pause at the end of the cycle or void excess outputs depending on the modpack's configuration. Therefore, rapid extraction from output blocks is just as critical as controlled insertion into input blocks.
Common mistakes
- Piping into the Machine Controller or Modular Casings: Neither the controller nor the decorative casings have inventories. Always trace your cables and pipes directly to the Item/Fluid Buses and Hatches.
- Clogging a multi-slot Item Input Bus with a single ingredient: Without blocking mode or stock filters, continuous supply pipes will fill every slot of a Big Item Input Bus with the first available item (like Iron Ingots), leaving zero slots for the second required ingredient (like Coal).
- Forgetting to match bus capacity to recipe complexity: Using a Tiny Item Input Bus (which typically holds only one or two slots) for a four-ingredient recipe makes the craft impossible unless you add additional Item Input Buses to the structure.
- Ignoring Fluid Hatch capacity during batch orders: Ordering 100 crafts at once when a recipe requires 1,000 mB of fluid per craft will stall if your Fluid Input Hatch only holds 4,000 mB and your buffer chest dumps all the items in while the fluid backs up inside the pipe.
FAQ
Can I add more Input Buses to the multiblock to make automation easier?
In most cases, yes, as long as the modpack creator used flexible block tags or casing replacements in the machine's JSON/KubeJS structure definition. Check the multiblock preview in JEI to see which casing blocks can be swapped out for extra buses or hatches.
Why does my machine say 'Missing Input' when all items are in the bus?
Check JEI carefully for fluid, energy, or special requirements (such as specific catalysts or upgraded hatch tiers). Also verify that the items are inside an Input Bus rather than accidentally piped into an Output Bus.
How do I handle items that are not consumed during a recipe (catalysts)?
Leave the non-consumed catalyst item permanently inside the Item Input Bus and exclude it from your AE2 or Refined Storage processing pattern. If using Blocking Mode, put the catalyst in a separate, dedicated Tiny Item Input Bus so the main Item Input Bus still registers as empty between crafts.
Can two machines share the same Input or Output Bus?
Check with your modpack's structural layouts, though sharing buses between two controllers can cause recipe conflicts where one machine steals half the ingredients meant for the other. Always build dedicated buses for each Machine Controller for reliable automation.
By routing ingredients into tiered Input Buses using subnet filtering or blocking mode and rapidly extracting products from Output Buses, you can reliably automate even the most complex Modular Machinery Reborn multiblocks.