XNet · Setup guide · Intermediate
How to Set Up Item and Fluid Routing in XNet
In 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.
What you need
- 1x Controller (the brain of the XNet network)
- A continuous Forge Energy (FE) or RF power source
- 7x Blue Connector (or any matching color of Standard Connector)
- 1x Advanced Connector (optional, for higher speeds and cross-side access)
- Several Blue Network Cables (color must match your connectors)
- 3x Chests (1 for Input, 1 for Filtered Ores, 1 for Overflow/Trash)
- 3x Fluid Tanks from any compatible mod (1 Input Tank, 2 Output Tanks)
Step by step
1Place and Power the Controller
Start by placing your XNet Controller near your storage area and connecting it to a continuous Forge Energy power source. Attach a Blue Connector directly to the Controller or connect it via a Blue Network Cable. Note that the Controller requires a small baseline amount of energy to stay active, plus a modest amount per active channel and operation.
Tip: You do not need a dedicated connector just to power the Controller if you run a standard power conduit directly into one of its faces.
2Wire Your Storage Blocks and Name Connectors
Place a Blue Connector directly against your Input Chest, Ore Chest, Overflow Chest, Input Fluid Tank, and both Output Fluid Tanks. Link all of these connectors back to the Controller using a continuous line of Blue Network Cables. Right-click each physical connector in the world and type a clear name into its top text box (such as 'Item In', 'Ores', 'Overflow', 'Fluid In', 'Tank A', and 'Tank B') so you can easily identify them inside the Controller GUI.
Tip: Naming your connectors immediately saves massive amounts of troubleshooting time once your network grows beyond a few blocks.
3Create the Item Channel and Configure Extraction
Open the Controller GUI and click on the Column 1 header at the top. Select 'xnet.item' from the dropdown list and click 'Create' to initialize an item channel. Locate your 'Item In' chest in the left-hand list, click the intersection square under Column 1, and click 'Create' in the right-hand panel. Change its mode from 'Ins' (Insert) to 'Ext' (Extract), set the Stack Size to 'Stack' (or 64) to pull whole stacks at a time, and lower the operation ticks field to speed up extraction.
Tip: Using an Advanced Connector allows you to lower the ticks per operation even further than a standard Connector.
4Configure Filtered High-Priority Item Insertion
Still in Column 1, click the intersection square for your 'Ores' chest and click 'Create'. Leave the mode set to 'Ins' (Insert). Locate the 'Priority' field on the right panel and set it to 10. Below that, drag phantom copies of the specific items you want in this chest (such as raw iron, gold, and copper) from JEI directly into the filter slots.
Tip: If you want to block specific items instead of allowing them, toggle the 'Blacklist' button next to the filter grid.
5Set Up the Low-Priority Overflow Destination
Click the intersection square under Column 1 for your 'Overflow' chest and click 'Create' to make an 'Ins' node. Leave its filter slots completely empty so it accepts any item type. Leave its Priority field at the default value of 0. Because 10 is higher than 0, the Controller will always attempt to put matching items into the 'Ores' chest first, and only send non-matching items (or excess ores if the 'Ores' chest is completely full) to the 'Overflow' chest.
6Initialize the Round-Robin Fluid Channel
Click the Column 2 header at the top of the Controller GUI, select 'xnet.fluid', and click 'Create'. Notice the channel-wide distribution mode button near the top right (above the connector configuration panel). Toggle this channel mode to 'Round Robin'. This tells the Controller to alternate fluid deliveries evenly between all valid, equal-priority destinations on this channel rather than filling one tank completely before moving to the next.
Tip: Round Robin works identically on item channels when you want to split items evenly across multiple furnaces or machines.
7Configure Fluid Extraction and Filtered Tanks
In Column 2, click the intersection for 'Fluid In', create a node, and set it to 'Ext' (Extract). Adjust the transfer rate field to define how many millibuckets (mB) are pulled per operation. Next, create 'Ins' (Insert) nodes in Column 2 for both 'Tank A' and 'Tank B', leaving both at Priority 0. Place a bucket of Water (or drag Water from JEI) into the filter slot of both tanks so they only accept water and split the incoming fluid stream evenly.
Tip: Check JEI or the in-game RFTools/XNet manual if you need to see the exact maximum mB transfer rate cap for standard versus advanced connectors in your modpack.
How it works
Unlike traditional piping mods where items physically travel block-by-block through tile entities, XNet cables are completely passive blocks. They do not tick or store data, which is why you can run a cable thousands of blocks with zero server lag. All routing logic lives exclusively inside the single Controller block, which scans connected inventories on a schedule.
When an Extract node ticks, the Controller does not actually pull the item or fluid into the cable. Instead, it first evaluates all Insert nodes on that same channel in descending order of their Priority value. It checks the highest priority Insert nodes to see if their filters match the extracted resource and if the target block has inventory space.
Only when a valid destination is confirmed does the Controller instantly teleport the specified stack size or fluid amount directly from the source to the destination. If multiple valid Insert nodes share the exact same priority level, the channel-wide distribution mode (such as Round Robin or First Match) determines which inventory receives the transfer next.
Common mistakes
- Mixing cable colors without realizing they disconnect: Blue Cables will never connect to Yellow, Red, or Green Cables. Keep your network a single color unless you are deliberately running two separate networks side-by-side.
- Forgetting to supply power to the Controller: If the Controller runs out of Forge Energy, all routing stops immediately. Look at the energy bar on the left side of the Controller GUI to confirm it is charged.
- Putting Extract and Insert nodes on different channels: Channels (columns 1 through 8) are completely isolated from one another. An Extract node in Column 1 can only send items to Insert nodes that are also inside Column 1.
- Setting priorities backward: In XNet, higher numbers mean higher priority. A priority of 10 runs before a priority of 0, and a priority of 0 runs before -5.
- Using standard Connectors when you need sided access: Standard Connectors can only interact with the exact block face they are attached to. If you need to insert into the top face of a furnace while the connector is placed on the bottom, you must upgrade to an Advanced Connector.
FAQ
Can I route items and fluids through the exact same Connector and Cable?
Yes! As long as a block handles both items and fluids (like many modded processing machines), you only need one Connector attached to it. In the Controller GUI, you simply add that single Connector to both an item channel column and a fluid channel column.
How do I stop an Insert chest from filling up completely with a single item type?
In the Insert node configuration panel on the right side of the Controller GUI, look for the numerical count box next to the filter settings. Entering a number here tells the Controller to stop inserting once the target inventory contains that exact amount of the filtered item or fluid.
Why is my extraction speed so slow even with stack size set to 64?
Standard Connectors have a minimum cap on how fast they can tick (usually once every 20 ticks, or 1 second, for items). Craft an Advanced Connector to replace it, which allows you to reduce the operation timer down to 10 ticks and raises maximum fluid/energy transfer limits.
What happens if I need more than 8 channels in my base?
A single Controller supports up to 8 channels. To expand beyond that, you can either build a separate cable sub-network, or use an XNet Router block to link multiple Controllers together into a larger master network.
By combining XNet's single-cable architecture with priority tiers, filters, and round-robin channels inside the Controller, you can sort both items and fluids instantly without causing any pipe lag.