XNet · Troubleshooting · Beginner

XNet Troubleshooting Guide: Fixing Common Network & Connector Issues

Setting up an XNet network is one of the most lag-free ways to automate your base, but a single misconfigured block can halt your entire production line. This troubleshooting guide will teach you how to diagnose and fix the most common XNet errors, including missing connectors, machine sidedness lockouts, and router conflicts. Mastering these core logic rules ensures your items, fluids, and energy flow smoothly without frustrating bottlenecks.

What you need

  • XNet Controller
  • Network Cables (Matching colors: Blue, Yellow, Red, or Green)
  • Standard Connectors and Advanced Connectors (Matching your cable colors)
  • Router and Routing Network Cables (If bridging multiple networks)
  • A forge energy (RF/FE) power source for the Controller
  • Your modpack's in-game guide or JEI to verify crafting recipes

Step by step

  1. 1Verify Controller Power and Status

    Open your XNet Controller GUI and inspect the energy bar on the left side. Unlike passive pipes, the XNet Controller requires a constant supply of energy to operate and uses a small amount of power per active channel and operation. If the energy bar is empty, connect a power cable or energy cell directly to the Controller, or set up an energy channel using a Connector attached to your power generator.

    Tip: The Controller itself does not need a Connector placed on it to join the network; a regular Network Cable touching any of its faces is enough to link it.

  2. 2Fix Connectors Not Showing in the GUI

    If you place a Connector on a machine and it does not appear in the Controller's list, check the physical cable path. Walk along your Network Cables from the Controller to the missing machine to ensure there are no broken spots. Most importantly, verify that the Connector and the Network Cables are the exact same color, as a Blue Connector will completely refuse to connect to a Yellow Network Cable.

    Tip: Name your Connectors immediately by typing into the text box on the physical Connector's right-click GUI. Named blocks are much easier to spot in the Controller list.

  3. 3Resolve Machine Sidedness with Advanced Connectors

    Many modded machines, or even the vanilla Furnace, require inputs through specific faces (such as the top for raw ore and the bottom for fuel). If you place a Standard Connector on the bottom of a furnace, you cannot insert ore into the top slot. To fix this without running ugly cables over the top of the machine, break the Standard Connector, replace it with an Advanced Connector, and open the Controller GUI to select 'Up' or 'North' in the direction drop-down menu.

    Tip: Advanced Connectors also unlock faster transfer speeds and higher internal energy transfer limits compared to Standard Connectors. Check JEI or your in-game manual for the exact transfer rates in your version.

  4. 4Check Channel Enabled States and Modes

    Sometimes a Connector appears in the GUI and has a box assigned in a channel, but nothing transfers. Click on the number at the very top of the channel column (1 through 8) and ensure the 'Enabled' checkbox is ticked for the entire channel. Next, click the specific Connector box inside the column and confirm you have one block set to 'Ins' (Insert) and another block set to 'Ext' (Extract); two 'Extract' nodes on a channel will do nothing without a valid destination.

    Tip: When extracting items, check the 'Speed' setting. Lowering the tick delay makes transfers faster, while specific stack modes wait until a full threshold is met before moving anything.

  5. 5Separate Overlapping Cable Colors

    If your Controller displays an error or strangely merges two separate setups, you likely have two Controllers touching the same color network. XNet provide four distinct colors (Blue, Red, Yellow, Green) specifically so you can run parallel lines directly next to each other without them merging. Replace one of the touching lines with a different color cable and matching Connectors to isolate the two systems.

    Tip: You can right-click a Connector or Network Cable with a vanilla dye in your hand to change its color in-world without breaking it.

  6. 6Clear Router Channel Conflicts

    When your base grows beyond eight channels, you will use a Router to link multiple Controllers together via Routing Network Cables. For a channel to cross the Router, you must open the Controller, select the channel, and give it a specific 'Published' name. Open the Router GUI to check your active channels: if nothing is transferring across the network bridge, you have either exceeded the Router's maximum published channel limit or misspelled the published name between the two Controllers.

    Tip: Only publish the specific channels that actually need to cross between different subnets. Local tasks should remain unpublished to save space on the Router.

How it works

To understand why XNet breaks, you must understand how it optimizes performance. Standard Network Cables are not Tile Entities; they are completely passive blocks that do not tick or hold items inside them. Instead, when you place a cable or a Connector, the Controller scans the connected path once to build an internal address list. If a cable color mismatches or a gap exists, the scan stops, which is why the missing machine never shows up in the Controller GUI.

Because items and fluids teleport instantly from the extraction point to the insertion point based on the Controller's math, the mod relies heavily on Minecraft's internal block-face rules (sidedness). A Standard Connector can only interact with the specific block face it is physically touching. An Advanced Connector bypasses this limitation by telling the Controller's logic to virtually wrap around the block and access a different face in the code, completely eliminating the need for wrapping physical cables around your machines.

When using a Router, you are creating a master network that sits above your individual Controller subnets. Standard colored cables cannot connect directly to a Router; Instead, each Controller and the Router must be touched by a standard Connector linked to gray Routing Network Cables. The Router acts as a traffic switchboard, matching channel types (like Item or Fluid) that share the exact same case-sensitive published text string.

Common mistakes

  • Connecting Routing Network Cables directly to machines: Gray Routing Cables and Routing Connectors are strictly for linking Controllers and Routers together. Use colored cables for regular machines and chests.
  • Forgetting to set an extraction speed or filter: In fluid and item channels, leaving an Extract node on the wrong redstone mode or forgetting to whitelist/blacklist items properly will freeze the line.
  • Putting two Controllers on the same colored cable network: A single continuous line of Blue Network Cable can only have one Controller. Adding a second Controller will disable the entire subnet until one is removed.
  • Exceeding Standard Connector energy limits: Standard Connectors have a capped RF/FE transfer rate per tick. If your machines are starving for power despite a full energy cell, upgrade the connections to Advanced Connectors.

FAQ

Why is my XNet cable connecting to a machine even though I didn't place a Connector?

Standard Network Cables never connect directly to machines or chests. If it looks connected, you either placed a Connector by mistake, or the cable is visually linking to an adjacent XNet block like a Controller or Router.

Can I hide XNet cables inside walls?

Yes! XNet includes Facade blocks. You can craft Facades, combine them with almost any solid building block in a crafting grid, and click them directly onto your Network Cables and Connectors to camouflage them.

Why does my furnace accept coal into the top slot instead of the bottom fuel slot?

Vanilla furnaces and many modded machines are strict about which face accepts fuel versus raw materials. You either placed a Standard Connector on the top of the furnace, or you are using an Advanced Connector and forgot to change the target face in the Controller GUI from 'Up' to 'Down' (or one of the horizontal sides for fuel).

How do I copy settings from one Connector to another without clicking everything again?

Inside the Controller GUI, you can click on a configured Connector box in a channel, press the 'Copy' button in the configuration panel, and then click or Shift-click on empty boxes in the same channel column to paste the exact same insertion or extraction settings.

By ensuring consistent cable colors, supplying steady power to your Controller, and utilizing Advanced Connectors to bypass machine sidedness limits, you can quickly solve any XNet outage and keep your base running at peak efficiency.

More XNet guides

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 · AutomationHow to Automate Ore Processing with a Single XNet CableLearn 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.Intermediate7 steps
XNet · AutomationHow to Use XNet for Clean AE2 & Refined Storage SubnetsAutomating complex machines like Applied Energistics 2 Inscribers or multi-input alloy furnaces often creates a chaotic mess of power, item, and data cables. By pairing an XNet Controller with a single Crafting Interface or Crafter, you can condense all item routing, side-specific insertion, and power delivery into one clean block line. This advanced guide will walk you through building a lag-free, single-cable XNet subnet to handle your most complicated processing chains.Advanced7 steps
XNet · Addon guideXNet Gases Guide: How to Route Mekanism Gases & ChemicalsSetting up Mekanism's multi-tier ore processing usually results in a messy nightmare of Pressurized Tubes, Universal Cables, and Logistical Transporters. By using XNet along with the XNet Gases addon, you can condense your entire 3x or 4x ore processing line—including Oxygen, Hydrogen Chloride, and Slurries—into a single, lag-free cable behind your machines. This guide will walk you through routing Mekanism gases and chemicals cleanly using an XNet Controller and Advanced Connectors.Intermediate7 steps
XNet · Addon guideYNot Addon Guide: Routing Mana, Essentia, and Mek Gases in XNetMoving Botania Mana, Thaumcraft Essentia, and Mekanism Gases usually requires three entirely different sets of pipes, tubes, and sparks that quickly clutter your base. By installing the YNot addon for XNet in 1.12.2 modpacks, you can consolidate all of these exotic resources into a single, lag-free network. This guide will walk you through setting up dedicated XNet channels to route magic and industrial gases alongside your standard items and power.Intermediate6 steps