XNet · Explained · Advanced
XNet Logic Channels & Redstone Control Explained
Mastering 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.
What you need
- XNet Controller
- Network Cables (Blue, Yellow, Red, or Green)
- Connectors (or Advanced Connectors for faster speed and cross-side access)
- A Forge Energy (FE/RF) power source to keep the Controller running
- Inventories, Fluid Tanks, or Energy Cells to monitor and control
- Machines or Redstone-sensitive blocks to act as outputs
Step by step
1Establish the Physical Network
Place your XNet Controller and connect it to a reliable power source using a Connector. Run Network Cables from the Controller to all the inventories, tanks, and machines you want to monitor and automate, placing a Connector directly against each target block. Ensure all Connectors share the same cable color so they appear on the same network grid.
Tip: Always name your Connectors inside the Controller GUI by typing into the Name field; labeling them 'Input Chest' or 'Furnace' prevents confusion later.
2Initialize a Logic Channel
Open the XNet Controller GUI and click on one of the eight numbered channel columns at the top. Click the Type dropdown menu, select 'xnet.logic', and confirm to create a Logic channel. This channel will not move physical resources; instead, it reads block states and broadcasts internal color signals across the Controller.
Tip: Dedicate Channel 8 to Logic across all your builds so you always know where your control systems live.
3Create a Sensor Connector
Locate the target block you want to monitor in the left-hand list of the Controller GUI. Click inside the intersecting box under your new Logic channel column and hit 'Create' on the right panel. Change the connector's mode from the default to 'Sensor' using the top-right dropdown menu.
4Configure the Sensor Conditions
With the Sensor mode active, you will see four sensor slots on the right panel. Change the first slot from 'Off' to 'Item', 'Fluid', 'Energy', or 'RS' (Redstone) depending on what you want to measure. Next, pick an operator (such as '<', '>', or '=') and enter the threshold number in the text box, then click the colored square next to it to choose which internal color channel (e.g., Red, Green, Yellow) turns on when this condition is met.
Tip: If you are checking for a specific item or fluid, drag that item from your inventory or JEI directly into the filter slot next to the sensor dropdown.
5Link Logic Color to a Resource Channel
Now select a standard resource channel, such as an 'xnet.item' or 'xnet.energy' channel that is actively extracting or inserting materials. Click on the specific Connector operation (Extract or Insert) that you want to automate. In the right-hand configuration panel, locate the four grayed-out colored squares under the 'Redstone / Color' enable section.
6Set the Activation Color
Click the colored boxes on your resource connector to match the exact color your Logic Sensor is outputting. For example, if your Sensor outputs 'Green' when a chest has less than 64 Iron Ingots, enable the 'Green' square on your Item Extraction connector. Now, that extraction will completely pause whenever the Green signal turns off.
Tip: If you select multiple colors on a single connector, ALL selected colors must be active simultaneously for the connector to run (functioning as a logical AND gate).
7Output Physical Redstone Signals (Optional)
If you want to toggle an external machine or Vanilla Redstone component directly, go back to your Logic channel column and create a node on the Connector attached to that machine. Set its mode to 'Output' instead of Sensor. Select which internal color signal it should listen to, and adjust the Redstone output level (up to 15) that the Connector will physically emit into the attached block when that color is active.
Tip: Use an Advanced Connector if you need to emit a strong Redstone signal into a specific side of a machine that your cable cannot physically reach.
How it works
XNet's Logic channel operates as an internal virtual state machine inside the Controller. Instead of sending physical Redstone updates through the world (which causes lighting updates and server lag), the Controller polls the attached block via the Sensor connector at fixed tick intervals. When the polled data (like RF stored or item count) satisfies your mathematical operator, the Controller flips a virtual boolean flag for one of its seven internal color variables.
Every connector node across all eight channels in an XNet Controller has access to these seven virtual color flags. When you highlight a color square on an Item, Fluid, or Energy connector, you are telling the Controller to wrap that connector's execution in an 'IF' statement. If the designated color flag is true, the transfer happens; if false, the Controller skips that connector during its work cycle.
Because a single Sensor connector has four independent evaluation slots, and multiple Sensors can exist on the same Logic channel, you can easily build complex Boolean logic. Have two different Sensors output to the same color to create an OR gate, or have two Sensors output to two different colors and require both colors on a target connector to create an AND gate.
Common mistakes
- Forgetting to put a ghost item in the Sensor filter: If you set a Sensor to 'Item > 64' without placing an item in the filter slot, it counts the total of ALL items in the inventory rather than a specific item.
- Confusing Cable Colors with Logic Colors: The 4 physical Network Cable colors (Blue, Yellow, Red, Green) only keep physical networks separated in the world. The 7 internal Logic colors exist entirely inside one Controller's GUI and have nothing to do with the cable blocks you placed.
- Enabling the Redstone icon instead of a Color square: Next to the internal color squares on a connector, there is a small Redstone Torch icon. Clicking the torch makes the connector listen to external, physical Redstone hitting the Connector block itself, ignoring your internal Logic channel colors.
- Unpowered Controller brownouts: Logic channels require constant base FE/RF to poll sensors. If your Controller runs out of power, all internal color signals default to OFF, which can break automated power-generation loops if they rely on a 'True' signal to feed fuel.
FAQ
How do I create an inverted (NOT gate) signal when a condition is met?
Instead of trying to invert the output color, simply invert the mathematical operator inside the Sensor itself. For example, change 'Greater Than (>)' to 'Less Than or Equal (<=)' so the color only broadcasts when the threshold is not exceeded.
Can one Logic channel communicate with a different XNet Controller?
Not directly via internal colors, because internal colors are local to a single Controller. However, you can place two Connectors from two different networks against a Redstone Lamp or solid block, having one network emit a physical Redstone Output and the other read it with an 'RS' Sensor.
Why is my Sensor not accurately reading the inventory of a machine?
Many modded machines side-lock their internal slots (e.g., top for input, bottom for output). A standard Connector can only read the slots accessible from the physical side it is attached to. Upgrade to an Advanced Connector, which allows you to specify which face of the machine to read in the GUI.
How fast do Logic Sensors update their status?
Sensors check their attached blocks based on a configurable tick rate in the panel. Standard Connectors have a minimum tick delay, whereas Advanced Connectors can be set to check faster; check the tooltip in your Controller GUI for the exact tick limits in your modpack.
By pairing XNet Logic Sensors with internal color filters, you can seamlessly automate inventory stock levels, power backups, and machine processing within a single, lag-free cable network.