OpenComputers · Late game
OC XNet Centralized Factory Control & Monitoring Hub
This late-game control hub integrates an OpenComputers Server Rack with an XNet routing infrastructure to dynamically monitor and throttle factory logistics. By reading storage buffer levels and controlling XNet Redstone Proxy blocks via Bundled Redstone I/O, the system automatically diverts items, fluids, and energy only where needed. Building this prevents server lag from overflowing buffers and prevents power brownouts during heavy processing spikes.
- Footprint
- 9x5x4 blocks
- Power
- ~500 RF/t for control overhead (check JEI for exact modpack config)
- Throughput
- Up to 8 distinct XNet routing channels per Routing Network
- Difficulty
- advanced
Flow diagram
How items, fluids and energy move through the setup, left to right.
Swipe sideways to see the whole diagram
Materials
| Item | Count |
|---|---|
| Rack | 1 |
| Server (Tier 3) | 2 |
| Central Processing Unit (CPU) (Tier 3) | 2 |
| Memory (Tier 3.5) | 4 |
| Graphics Card (Tier 3) | 1 |
| Hard Disk Drive (Tier 3) (4MB) | 2 |
| Redstone Card (Tier 2) | 1 |
| Network Card | 2 |
| EEPROM (Lua BIOS) | 2 |
| OpenOS (Operating System) | 1 |
| Disk Drive | 1 |
| Screen (Tier 3) | 6 |
| Keyboard | 1 |
| Power Converter | 1 |
| Capacitor | 2 |
| Adapter | 4 |
| Redstone I/O | 2 |
| Cable | 32 |
| Controller | 2 |
| Router | 2 |
| Redstone Proxy | 4 |
| Network Cable (Blue) | 64 |
| Advanced Connector (Blue) | 16 |
Build it step by step
1Construct the Power and Server Core
Place the Power Converter connected to your main base energy grid, and attach two Capacitors beside it to buffer internal OpenComputers energy. Place the Rack adjacent to the Capacitors and an external Disk Drive next to the Rack. Insert the OpenOS floppy disk into the Disk Drive so the servers can boot and install their operating systems.
2Assemble the Tier 3 Servers
Shift-right-click a Tier 3 Server in hand to open its internal inventory. Populate it with a Tier 3 CPU, two Tier 3.5 Memory modules, a Tier 3 Graphics Card, a Tier 2 Redstone Card, a Network Card, a Lua BIOS EEPROM, and a Tier 3 Hard Disk Drive. Place the assembled Server into the top slot of the Rack, and configure a second server for backup data logging in the slot below.
3Mount the Display Wall
Place six Tier 3 Screens in a 3x2 grid near the Rack to form a large multi-block monitor, and attach the Keyboard directly to the side of the lower-left screen. Run OpenComputers Cable from the back of the Rack to the Screen and Disk Drive. Open the Rack GUI and ensure the Server slot is set to connect its lines to the external sides where your cables are attached.
4Wire the Monitoring Adapters
Place OpenComputers Adapters directly against your primary factory storage chests, fluid tanks, and energy cells. Connect these Adapters back to the Rack using OpenComputers Cables. When loaded with an Inventory Controller Upgrade or Tank Controller Upgrade inside the Adapter, the server can query exact item counts and fluid levels across the factory.
5Establish the XNet Control Backbone
Set up your XNet Controller and XNet Router near the control room, wiring them together and out to your factory machines using Blue Network Cables and Advanced Connectors. Along the XNet cable line near the Rack, attach four XNet Redstone Proxy blocks using standard XNet Connectors. Place OpenComputers Redstone I/O blocks directly touching these Redstone Proxies and connect the Redstone I/O blocks to your OC Cable network.
6Configure XNet Logic & Lua Scripts
Boot the primary Server, install OpenOS to the Hard Disk Drive, and write a Lua monitoring script that reads storage metadata from the Adapters every two seconds. In the XNet Controller GUI, create logic or item/fluid/energy channels and set their activation condition to require a specific redstone signal on the Redstone Proxy connectors. Have your Lua script toggle the Redstone I/O outputs high or low based on whether destination buffers fall below threshold capacity.
How it works
While XNet is exceptionally fast at moving items, fluids, and energy, its built-in logic channels are limited to basic threshold checks and lack global awareness across separate sub-networks. By introducing an OpenComputers Rack into the system, you separate the heavy lifting of item transport from the complex conditional logic of factory management. The OpenComputers Adapters inspect the metadata of storage tanks, battery banks, and input chests, pulling real-time telemetry into a centralized Lua control loop.
When the Lua script detects that a specific processing line is backed up or that main base power is dipping below 50%, it sends a digital command down the OC Cable to the Redstone I/O blocks. The Redstone I/O blocks emit targeted analog or vanilla redstone signals directly into adjacent XNet Redstone Proxies. The XNet Controller reads the state of these proxies and immediately suspends or enables specific transport channels without needing to break cables or manually toggle machine states.
Using a Server Rack instead of a standard Computer Case allows you to run up to four independent servers within a single block space. In this setup, the primary server handles real-time telemetry and GUI rendering on the 3x2 Tier 3 Screen, while the secondary server listens over an internal virtual network to log historical consumption rates and handle manual overrides input via the Keyboard.
Upgrades and scaling
- Add a Wireless Network Card (Tier 2) to the Server and craft a Tablet with a Wireless Network Card to remotely monitor and toggle XNet factory lines from anywhere in your base.
- Install an Internet Card into the primary server to push factory telemetry and storage statistics to an external web dashboard or webhook.
- Replace standard redstone toggling between the Redstone I/O and Redstone Proxy with Bundled Redstone cables if your modpack includes compatible bundled cable mods, allowing 16 independent XNet triggers per Redstone I/O side.
- Scale the XNet network across dimensions or distant outposts by linking multiple XNet Routers via XNet Wireless Routers, all managed by the same central OpenComputers Rack.
Common mistakes
- Forgetting to configure the Rack GUI: By default, servers inside a Rack are disconnected from external sides. You must open the Rack interface and click the colored node lines to bridge the Server to the sides where your OC Cables connect.
- Exceeding the OpenComputers component limit: Each CPU tier only supports a maximum number of connected components (check JEI or documentation). Connecting too many Adapters and Redstone I/O blocks to a single server without upgrading to a Component Bus (Tier 3) inside the Server will cause the computer to crash on boot.
- Using regular XNet Connectors instead of Advanced Connectors on machines that require high transfer rates or specific side insertion, which bottlenecks the system even when the OC script enables the channel.
- Running XNet Network Cables and OpenComputers Cables directly parallel and touching without realizing OC Cables do not carry XNet channels; keep the two cabling networks clearly separated except where Redstone I/O blocks touch Redstone Proxies.
FAQ
Why use XNet Redstone Proxies instead of putting Redstone I/O blocks directly on every machine?
Running OpenComputers Cables to dozens of machines quickly exhausts the server's component limit and costs a lot of materials. By toggling XNet channels via Redstone Proxies at the controller level, one Redstone I/O block can govern an entire category of machines across your base.
My Server refuses to boot and gives a 'No bootable medium found' error. How do I fix this?
Ensure you have placed the OpenOS floppy disk into the external Disk Drive connected to the Rack, and check that the Server itself has a pre-flashed EEPROM (Lua BIOS) installed in its EEPROM slot.
How does the Adapter read items inside chests or fluids in tanks?
An empty Adapter can only interface with blocks that have native OpenComputers support. To read standard vanilla chests, fluid tanks, or modded storage, shift-right-click the Adapter or open its GUI and insert an Inventory Controller Upgrade or Tank Controller Upgrade into its internal slot.