XNet · Automation · Intermediate

How to Automate Ore Processing with a Single XNet Cable

Learn how to automate a complete ore-doubling and smelting production line using a single row of XNet cables. Instead of running separate pipes for energy, input items, and output items, you will use one Advanced Connector per machine to handle power, ore insertion, and ingot extraction simultaneously. This approach eliminates cable spaghetti, saves space, and drastically reduces server lag.

What you need

  • 1 XNet Controller
  • 6+ XNet Network Cables (all the same color, e.g., Blue)
  • 5+ XNet Advanced Connectors (same color as your cables)
  • 1 Power Generation source or Energy Cell (providing Forge Energy/RF)
  • 1 Input Chest (for raw ores) and 1 Output Chest (for finished ingots)
  • 1 Ore Crusher/Pulverizer and 1 Electric Furnace (from any standard tech mod like Thermal Series or Mekanism)

Step by step

  1. 1Place Your Machines and Storage

    Set up your blocks in a simple row or cluster: place the Input Chest, your Pulverizer/Crusher, your Electric Furnace, the Output Chest, and your Power Source. Leave the back side of all these blocks completely clear for cabling. Finally, place the XNet Controller adjacent to your Power Source or anywhere along the planned cable path.

    Tip: You can place the blocks directly next to each other, as long as you disable auto-output between the machines so XNet has full control.

  2. 2Attach Advanced Connectors and Cables

    Place an Advanced Connector directly against the back of the Input Chest, Pulverizer, Furnace, Output Chest, and Power Source, as well as the XNet Controller. Connect all of these connectors together using your Network Cables. We use Advanced Connectors rather than regular Connectors because they allow us to interact with any internal side of a machine (like the top input slot or bottom output slot) from a single physical connection point.

    Tip: Right-click each connector and give it a custom name in the top-left text box (e.g., 'Raw Input', 'Crusher', 'Smelter') to make programming the Controller much easier.

  3. 3Configure Your Machine I/O Sides

    Before opening the XNet Controller, open the internal GUI of your Pulverizer and Electric Furnace. If your tech mod uses side-configuration (like Thermal Expansion or Mekanism), set the Top face to Input (Blue), the Bottom face to Output (Orange), and disable any auto-eject features. If your mod has fixed sides, check JEI or the mod's in-game manual to confirm which face accepts inputs and which face allows extractions.

  4. 4Set Up Channel 1 for Power Distribution

    Open the XNet Controller GUI. First, click the slot for Channel 1 at the top and set the channel type to 'xnet.energy', ensuring the Controller itself is receiving a trickle of power to operate. In the Channel 1 column, click the box aligned with your Power Source and click 'Create', then change its mode from 'Ins' to 'Ext' (Extract). Next, create nodes in Channel 1 for the Controller, the Pulverizer, and the Electric Furnace, leaving all three on 'Ins' (Insert) to distribute energy.

    Tip: Check the controller's tooltip or JEI to see the max RF/t transfer rate of Advanced Connectors in your modpack's version.

  5. 5Set Up Channel 2 for Raw Ore to Crusher

    Click the Channel 2 header at the top and set its type to 'xnet.item'. Create a connection in Channel 2 for your Input Chest, set it to 'Ext', and adjust the extraction speed and stack size to your preference. Then, create a connection in Channel 2 for the Pulverizer and leave it on 'Ins'. In the configuration panel on the right for this Pulverizer node, locate the 'Side' dropdown menu and change it to 'Up' (Top) so XNet pushes the raw ore directly into the machine's designated input slot.

    Tip: Use the filter slots on the Input Chest's Extract node if you only want specific raw ores to enter the processing line.

  6. 6Set Up Channel 3 for Crushed Dust to Furnace

    You do not always need a new channel for every step, but using Channel 3 keeps the logic clean without needing complex item filters. Set Channel 3 to 'xnet.item', create a node on the Pulverizer, and set it to 'Ext'. In the right-hand panel for this node, change the 'Side' dropdown to 'Down' (Bottom) so it only pulls from the machine's output buffer. Next, create an 'Ins' node on the Electric Furnace in Channel 3 and set its virtual 'Side' dropdown to 'Up' (Top).

  7. 7Set Up Channel 4 for Final Ingot Extraction

    Click Channel 4 and set it to 'xnet.item' (or re-use an earlier item channel using Priority and Filters if you want to save channels). Create an 'Ext' node for the Electric Furnace and set its virtual 'Side' dropdown to 'Down' (Bottom) to pull out the finished ingots. Finally, create an 'Ins' node for your Output Chest in Channel 4; since chests are not sided inventories, you do not need to change the virtual side for the chest.

    Tip: If your Pulverizer produces secondary byproducts (like rich slag or extra dusts that cannot be smelted), add an 'Ins' node to the Output Chest on Channel 3 with a lower priority than the Furnace so overflow items don't clog the machine.

How it works

Traditional pipe mods require a physical cable to touch the exact face of a machine you want to interact with—meaning you need a power cable on the back, an input pipe on top, and an output pipe on the bottom. furthermore, those cables are usually 'Tile Entities' that constantly tick and check inventories, which causes server lag when built at scale. XNet cables, by contrast, are completely dumb blocks with zero lag; all the logic happens inside one single block: the XNet Controller.

The secret to single-cable automation lies in two mechanics: Multi-Channel multiplexing and Sided Spoofing via Advanced Connectors. The XNet Controller divides a single cable line into 8 isolated logical channels. Channel 1 can carry Forge Energy while Channels 2, 3, and 4 carry Items simultaneously through the exact same physical connector without interfering with each other.

Furthermore, most modded machines segregate their inventory slots by block face (e.g., the top face connects to the input slot, and the bottom face connects to the output slot). While a standard XNet Connector can only interact with the physical face it is attached to (in our build, the back face), an Advanced Connector can 'spoof' or simulate access to any of the six faces. By setting a node's side to 'Up' for insertion and 'Down' for extraction, the Controller tricks the machine into thinking pipes are connected to its top and bottom, all through one connector on the back.

Common mistakes

  • Forgetting to power the XNet Controller itself: The Controller requires a small amount of ongoing RF/FE to function. Always include the Controller as an 'Ins' destination on your Energy channel.
  • Using standard Connectors instead of Advanced Connectors: Standard connectors cannot spoof block faces. If you attach a standard connector to the back of a furnace, you cannot tell it to pull from the bottom output slot.
  • Mismatched internal machine configs: If you tell the XNet Advanced Connector to insert into the 'Up' face, that machine's internal GUI must also have its top face configured to accept inputs.
  • Putting all item movements on one channel without filters: If you put the Input Chest, Pulverizer, Furnace, and Output Chest all on Channel 2 without item filters, raw ores will skip the machines and go straight into the Output Chest. Either use separate channels for each stage or apply strict whitelist filters.

FAQ

Can I do all the item routing on a single Item Channel instead of using three?

Yes. You can put all item extractions and insertions on Channel 2, provided you add item filters to every 'Ins' node (e.g., filter Raw Ores into the Pulverizer, Crushed Dusts into the Furnace, and Ingots into the Output Chest). Using separate channels is simply faster to set up because it avoids the need to manually filter dozens of different ore types.

Why did my Advanced Connector stop transferring items or power?

Check two things: first, ensure the XNet Controller has not run out of power. Second, check if you accidentally clicked the yellow/green toggle lights next to the channel numbers at the top of the Controller GUI, which disables the entire channel.

What is the difference between cable colors?

Cable colors (Blue, Red, Yellow, Green) are purely for physical separation so two distinct networks can run next to each other without connecting. A single XNet Controller can only manage one cable color network directly unless linked via Routers.

By combining XNet's multi-channel Controller with the face-spoofing ability of Advanced Connectors, you can power, feed, and empty an entire ore-processing array using just one clean line of cable.

More XNet guides

XNet · Getting startedXNet Getting Started Guide: First Controller & Cable NetworkXNet allows you to condense complex tangles of item, fluid, and energy pipes into a single, lag-free network line. In this guide, you will craft your first XNet Controller, wire up a basic cable network, and configure a channel to automatically transfer items between two chests. Mastering this fundamental setup is the key to building clean, super-efficient factory automation.Beginner7 steps
XNet · ExplainedXNet Channels, Colors, and Connectors ExplainedMastering XNet allows you to build completely lag-free, single-cable networks that move items, fluids, power, and logic simultaneously across your entire base. In this guide, you will learn the core logic behind the 8 controller channels, how to physically isolate networks using the 4 cable colors, and when to upgrade from Standard to Advanced Connectors. Understanding these fundamentals will help you replace bulky, chaotic pipe setups with clean and efficient automation.Beginner7 steps
XNet · PowerHow to Build a Lag-Free Power Grid with XNetIn this guide, you will learn how to build an ultra-efficient, centralized power distribution grid using XNet to send Forge Energy (FE) or Redstone Flux (RF) from your generators to all of your machines. Unlike traditional energy conduits that constantly calculate paths and cause server lag, XNet uses a single Controller and lightweight cables to move power instantly across huge distances. By the end, you will have a self-sustaining network that powers your entire base and keeps its own brain running smoothly.Beginner7 steps
XNet · Setup guideHow to Set Up Item and Fluid Routing in XNetIn this guide, you will learn how to build a lag-free, automated item and fluid sorting network using XNet. Mastering XNet routing allows you to organize massive storage rooms and processing lines through a single cable line, replacing messy spaghetti pipes with clean, intelligent distribution logic.Intermediate7 steps
XNet · ExplainedXNet Logic Channels & Redstone Control ExplainedMastering XNet's Logic channels allows you to automate complex factory processes without running a single piece of external Redstone dust. In this guide, you will learn how to use internal sensors to monitor item counts, fluid levels, and RF storage, and then use colored internal signals to dynamically toggle other XNet operations on and off. This keeps your builds compact, lag-free, and capable of smart self-regulation.Advanced7 steps
XNet · ProgressionXNet Progression Guide: Scaling Up with Routers & Wireless RoutersA single XNet Controller is strictly limited to eight active channels, which can quickly bottleneck large, automated bases. By mastering XNet Routers and Wireless Routers, you can link multiple controllers together to bypass this limit and transmit items, fluids, and energy across vast distances or even across dimensions. This guide will walk you through building a scalable, multi-controller routing network.Advanced8 steps