Pipez · Addon guide · Advanced
How to Maximize Server TPS with Pipez Lag Fix & Pipez Optimizer
While the Pipez mod is built from the ground up to be lightweight, sprawling automation networks with poorly configured upgrades can still bring a multiplayer server's TPS (Ticks Per Second) to its knees. In this guide, you will learn the underlying logic of how Pipez handles block entities, why certain configurations generate massive CPU overhead, and how to combine intelligent in-game pipe engineering with the Pipez Lag Fix and Pipez Optimizer addons to eliminate server lag.
What you need
- Pipez mod installed on both client and server
- Pipez Lag Fix or Pipez Optimizer addon (installed server-side)
- Pipe Wrench (or any forge:tools/wrenches compatible wrench)
- Filter Destination Tool
- Pipe Upgrades (Basic, Improved, Advanced, and Ultimate Pipe Upgrades)
- Access to server configuration files (for server administrators) and a profiler like Spark or Observable
Step by step
1Minimize Extracting Nodes (Block Entities)
Walk through your base and inspect every connected Item Pipe, Fluid Pipe, Energy Pipe, Gas Pipe, and Universal Pipe. Remember that a standard pipe segment is just a passive block, whereas any pipe connection set to extract becomes an active ticking Block Entity. Use your Pipe Wrench to sneak-click and disable extraction on any pipe face that does not strictly need to pull resources, such as machine sides that only receive inputs.
Tip: Consolidate outputs into a single buffer chest or tank whenever possible so you only need one extracting pipe node instead of ten.
2Segregate Megacables with the Pipe Wrench
When you run a single continuous line of pipes across dozens of machines, every extracting node on that network must scan all connected inventories to find valid destinations. Sneak-click with your Pipe Wrench on the joints between unrelated pipe segments to physically disconnect them. Breaking one massive backbone into twenty isolated point-to-point sub-networks drastically reduces the pathfinding math the server performs every tick.
Tip: Replace Universal Pipes with dedicated Item, Fluid, or Energy Pipes whenever a machine only requires a single resource type, as Universal Pipes check multiple capabilities per tick.
3Downgrade from Ultimate Pipe Upgrades on Idle Lines
Open the GUI of your extracting pipes by right-clicking the extraction collar. Many players slap an Ultimate Pipe Upgrade into every slot out of habit, which forces the pipe to attempt transfers at the maximum possible tick frequency—even when the source inventory is empty or the destination is full. Swap out Ultimate Pipe Upgrades for Basic or Improved Pipe Upgrades on low-throughput machines (like slow crop farms or trickle-charging batteries) to reduce how often the pipe polls attached inventories.
Tip: Check JEI or your server's modpack configs to see the exact tick delay and transfer rates assigned to each upgrade tier.
4Lock Routes with the Filter Destination Tool
When using an Advanced or Ultimate Pipe Upgrade on a network with dozens of outputs, the pipe spends CPU time evaluating every inventory slot along the path. Craft a Filter Destination Tool and right-click the exact block face where you want items or fluids to enter. Open the extracting pipe's GUI, click Add Filter, and place the configured Filter Destination Tool into the destination slot to force the pipe to check only that specific inventory instead of scanning the entire network.
Tip: You must click the exact side of the target block that the pipe is physically connected to, otherwise the destination filter will not link.
5Optimize Distribution and NBT Matching Modes
Inside the extracting pipe GUI (with at least an Improved Pipe Upgrade installed), inspect your Distribution Mode button. Switch networks away from Round Robin or Random over to Nearest First whenever uniform splitting is not required, as Nearest First stops scanning the network as soon as it finds the first valid slot. Next, if you are using filters with an Advanced Pipe Upgrade, examine the NBT matching button and disable exact NBT matching unless you are explicitly sorting tools, armor, or enchanted books.
Tip: You can copy properly optimized filter setups by crafting a configured Pipe Upgrade together with a blank upgrade of the same tier in a crafting grid.
6Use Redstone Modes to Sleep Idle Extractors
Insert at least a Basic Pipe Upgrade into any extracting pipe attached to intermittent setups, such as mob farms or batch crafting arrays. Click the Redstone Mode button in the GUI and set it to 'On when powered'. Place a Redstone Comparator reading the source inventory or link the pipe to your factory master switch so the extracting block entity completely halts its capability checks when there is nothing to move.
7Deploy and Tune Pipez Lag Fix & Pipez Optimizer
For server administrators and single-player world owners, shut down the server and drop the Pipez Lag Fix or Pipez Optimizer addon jar into your server's mods folder. These addons patch the core Pipez transfer loop by caching capability lookups, adding dynamic backoff timers when destination inventories are full, and stopping pipes from ticking endlessly against clogged machines. After starting the server, open the generated config files in your server's config directory to adjust the cooldown multiplier and cache invalidation ticks based on your modpack's scale.
Tip: Run a Spark or Observable profile before and after installing the optimization addons to identify which specific player bases still have unoptimized pipe loops.
How it works
To understand why Pipez lags on large servers and how to fix it, you must understand its block entity architecture. Unlike traditional pipe mods where every single cable segment is a ticking block entity that passes items to its neighbor, Pipez makes non-extracting pipe blocks completely passive. Only the pipe segments that you sneak-click into 'Extract' mode create a Block Entity. When multiple pipes touch, they form an internal network graph that caches all connected blocks.
The TPS bottleneck occurs during the extraction tick. When an extracting pipe ticks, it queries the capability (Item, Fluid, Energy, or Gas) of the block behind it, and then iterates through the list of all valid destination inventories connected to its network graph. If you have 50 extracting pipes connected to a single sprawling backbone with 100 chests, and every extractor holds an Ultimate Pipe Upgrade, the server is forced to perform thousands of inventory slot checks and NBT comparisons every single tick. This overhead skyrockets when destination chests are completely full, because the pipe searches every single slot of all 100 chests before failing and trying again on the very next tick.
Addons like Pipez Lag Fix and Pipez Optimizer target this exact failure state at the code level. Instead of allowing an Ultimate Pipe Upgrade to hammer a full chest 20 times a second, these addons introduce dynamic tick throttling (sleeping the extractor for several ticks after a failed transfer) and improved destination caching. When you combine these server-side patches with proper in-game network isolation and Nearest First routing, the CPU time spent on Pipez drops to near zero.
Common mistakes
- Using Universal Pipes for everything: Universal Pipes check four separate capability types (Items, Fluids, Energy, and Mekanism Gas) on every operational cycle. Always use dedicated single-type pipes unless a block genuinely outputs multiple resource types from the same face.
- Putting Ultimate Pipe Upgrades in clogged item systems: An Ultimate Item Pipe trying to push items into a full storage drawer wall will scan every connected inventory at maximum tick speed. Either void excess items, use redstone shutoffs, or install Pipez Lag Fix to enforce dynamic sleep timers on full destinations.
- Leaving accidental NBT data in filters: When you click an item from your inventory into a filter slot, it automatically copies any NBT data on that item into the text field. If you leave Exact NBT matching enabled by mistake on bulk items, the server wastes CPU cycles running string/tag comparisons on every single item passing through.
- Setting every side of a pipe intersection to Extract: New players often spam sneak-click with the Pipe Wrench until items start moving, accidentally turning intermediate junctions or input faces into extracting block entities that futilely poll empty blocks.
FAQ
Do clients need to install Pipez Lag Fix or Pipez Optimizer to join the server?
In most cases, performance addons that only alter block entity tick logic and server-side capability caching are strictly server-side (or for single-player worlds). However, always check the specific addon's version notes for your Minecraft loader, as some versions may require client synchronization if they alter upgrade config values.
Why does my Universal Pipe still show high tick times in Observable after I downgraded the upgrade?
Even with a Basic Pipe Upgrade or no upgrade at all, a Universal Pipe has to cycle through Item, Fluid, Energy, and Gas handlers. If it is attached to a complex multiblock or a storage controller with thousands of slots, querying those four capabilities will always be heavy. Replace the Universal Pipe with a specific Item or Fluid Pipe.
Does a longer pipe line create more lag than a short pipe line?
No, as long as the middle pipe segments are not set to extract and do not branch off into dozens of unnecessary inventories. Fifty passive Item Pipe blocks between Machine A and Chest B cost virtually zero TPS because they do not have block entities; only the number of connected inventories and extracting ends matters.
How do I stop pipes from lagging when extracting from a massive storage controller (like Refined Storage or Applied Energistics)?
Never put an unfiltered extracting Pipez node directly on a main network interface or storage controller with thousands of slots. Instead, make the storage system push items into a small buffer chest (like a vanilla Barrel), and have the Pipez node extract from that small buffer.
By isolating pipe networks, right-sizing your Pipe Upgrades, locking routes with the Filter Destination Tool, and installing the Pipez Lag Fix or Pipez Optimizer addons, you can scale your factory to thousands of pipes with virtually zero impact on server TPS.