XNet · Progression · Advanced
XNet Progression Guide: Scaling Up with Routers & Wireless Routers
A 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.
What you need
- At least two XNet Controllers
- XNet Routers (one for each local Controller subnet)
- XNet Wireless Routers (for long-distance or cross-dimensional setups)
- Antenna base and Antenna Dish (or standard Antenna tiers, check JEI for exact names)
- Network Cables and Connectors (matched by color: Blue, Yellow, Red, or Green)
- Routing Network Cables and Routing Connectors
- A reliable Forge Energy (FE) power source
Step by step
1Isolate Your Local Subnets
Build two separate XNet networks, each with its own Controller, colored Network Cables, and Connectors attached to your machines or chests. Ensure that the standard Network Cables of Subnet A do not physically connect to the standard Network Cables of Subnet B. If they are close together, use different cable colors (such as Blue for Subnet A and Yellow for Subnet B) so they do not merge.
Tip: Always name your Connectors inside the Controller GUI immediately so you do not confuse inventory blocks later.
2Attach Routers to Each Subnet
Place one XNet Router near Subnet A and another near Subnet B. Connect Subnet A's colored Network Cable directly to the first Router using a matching colored Connector. Do the exact same thing for Subnet B and the second Router. The Router now acts as a bridge device on each respective local network.
Tip: A Router does not require its own power to function, unlike the Controller and Wireless Router.
3Name Your Local Channels
Open the Controller GUI for Subnet A and create a channel (for example, an Item channel on Channel 1). Notice the text box at the top of the channel settings where you can give the channel a custom name. Type a unique identifier, such as 'MainStorage', and configure your local chests or machines to extract or insert on this channel as normal.
Tip: Routers blindly ignore any channel that does not have a custom name assigned to it in the Controller.
4Link Routers with Routing Cables
Now you must connect the two Routers together so they can share their named channels. Place a Routing Connector against both Router A and Router B, then link them using Routing Network Cables (which are always gray/white). Do not connect Routing Cables directly to standard machines; they are strictly for linking Routers and Wireless Routers together.
5Publish and Route the Channels
Open the GUI of either Router. You will see a list of 'Local' channels (from its immediate Controller) and 'Remote' channels (discovered via the Routing Cables). To merge a channel between Subnet A and Subnet B, give a channel in Controller B the exact same name ('MainStorage') and type (xnet.item) as the one in Controller A, and make sure it is enabled inside the Router interface. The two controllers are now linked on that specific channel while retaining seven other independent channels each.
Tip: A single routing network has a hard limit on the total number of published channels it can handle (typically 32, check the Router GUI to track your usage).
6Add Wireless Routers for Long Distances
To link a remote base or another dimension without running thousands of Routing Cables, place a Wireless Router next to Router A. Connect the Wireless Router to Router A using a Routing Connector and Routing Network Cable. Supply the Wireless Router with a constant stream of Forge Energy (FE), as wireless transmission drains power continuously based on distance and active channels.
7Install the Antenna
A Wireless Router cannot broadcast on its own; it requires an Antenna structure directly on top of it. Place an Antenna Base on top of the Wireless Router, and then place an Antenna or Antenna Dish on top of the base. Check your in-game guide or JEI for the exact recipes and range tiers: standard Antennas cover moderate to large overworld distances, while the Antenna Dish allows cross-dimensional transmission at a much higher energy cost.
Tip: Make sure both the sending and receiving Wireless Routers are chunk-loaded, otherwise the connection will drop when you leave the area.
8Tune the Wireless Frequency
Build an identical setup (Controller, Router, Wireless Router, Antenna, and Power) at your remote location. Open the GUI of both Wireless Routers and set them to the exact same numerical frequency. You can set the network to Public (accessible by anyone on the server on that frequency) or Private (restricted to your player UUID). Once powered and tuned, your remote channels will magically appear in the local Router's GUI.
How it works
To understand XNet routing, think of a Controller as a local office manager and a Router as the building's switchboard. A single Controller can only manage 8 distinct channels. If you try to place two Controllers on the exact same colored cable network, the network will malfunction and shut down to prevent conflicts. By isolating Controllers into separate colored subnets, each Controller gets its own fresh set of 8 channels.
The Router bridges these isolated subnets without merging the Controllers themselves. When you name a channel inside a Controller, the Router connected to that subnet detects the named channel and exposes it to the Routing Network. Routing Cables form a backbone—a meta-network that only carries data between Routers.
When Router A and Router B both expose an item channel with the exact same name to the Routing Network, XNet merges their logic. An item extracted into 'Channel 1 (MainStorage)' on Subnet A can be instantly inserted into a chest on 'Channel 5 (MainStorage)' on Subnet B. Because XNet cables are not tile entities, this entire routing hierarchy causes virtually zero server lag, regardless of how many blocks the cables span.
Common mistakes
- Placing two Controllers on the same colored cable network: Never link two Controllers directly with standard Network Cables. They must be separated into distinct subnets and bridged exclusively via Routers.
- Forgetting to name the channel in the Controller: If a channel does not have a text name typed into its Controller configuration tab, it will remain entirely invisible to the Router.
- Using standard Network Cables to link Routers: Standard colored cables connect a Controller to a Router. To connect a Router to another Router (or to a Wireless Router), you must use the gray Routing Network Cables and Routing Connectors.
- Mismatched channel types or names: If Subnet A names an Item channel 'MobDrops' and Subnet B names a Fluid channel 'MobDrops', they will not link. Both the channel type and the exact capitalization of the name must match.
- Underpowering the Wireless Router: Cross-dimensional Antenna Dishes require significant continuous FE/t. If your power buffer empties, the wireless link severs immediately, halting all automation on those remote channels.
FAQ
Do the routed channels need to be in the same numbered slot on both Controllers?
No. A channel named 'PowerGrid' can be on Channel 1 in Controller A and on Channel 8 in Controller B. As long as the channel type and the custom name match, the Router will link them.
Why are my Routing Cables not connecting to my machines or chests?
Routing Cables and Routing Connectors are exclusively designed to connect Routers to other Routers (or Wireless Routers). You must use standard colored Network Cables and standard Connectors to interface with machines and inventories.
Is there a limit to how many channels I can pass through a single Routing Network?
Yes. While you can link many Controllers together to get dozens of local channels, a single Routing backbone has a maximum cap on how many shared channels can be published across it at once (typically 32). Keep purely local operations unnamed so they do not clutter the Router.
Does the Router need RF/FE power to operate?
A standard wired XNet Router does not require power. However, the Controllers on each subnet and any Wireless Routers you use do require a constant supply of energy.
By isolating XNet Controllers into local subnets and bridging named channels through Routers and Wireless Routers, you can infinitely scale your base automation beyond the eight-channel limit and across dimensions with zero lag.