Setting up TDEnderPipes networks
Mod version shipped with FlammiCraft: 0.51.0
Version 0.47.0 requires TDLibrary 0.56.0 or newer. Loaded networks build routing caches under its shared startup budget and wait to transfer until a complete cache is ready. Topology changes or unloaded chunks reject stale work, and preparation resumes automatically. Conduits, filters and contents retain their existing setup.
LBR 0.41.0: EnderPipes retains its LBR components and saved IDs. Data conduits, Network I/O and all 16 color channels use the native LBR API without TDUtilities, including multiple side modems. Other EnderPipes features remain available without LBR.
Ender Pipe I/O through data modems
TDEnderPipes carries items, fluids, energy and redstone; chemicals require Mekanism. Use matching compatible client and server networking versions with conduit protocol 10.
TDLibrary 0.56.0 or newer is required on both server and clients.
With TDUtilities 1.11.0 or newer and Little Big Redstone, the optional LBR Data Conduit shares these bundles and connects data cables and modems.
Bring up one connection
- Place the appropriate conduit between a source and destination.
- Enable Extract at the source and Insert at the destination. The machines' own face settings must permit the same directions.
- Select matching channels where applicable and check redstone control.
- Transfer a small test quantity and confirm its destination.
- Add filtering, priorities and distribution after the basic route works.
The slowest conduit can limit the whole route. Energy transfers share each traversed conduit's per-tick budget. Fluid and chemical transfers run every five ticks with a corresponding cycle budget; visible bursts do not imply a higher sustained rate.
Custom item conduits can set ticks_per_cycle from 1 to 20 in a datapack. Their interval continues across second boundaries; 19 means one cycle every 19 game ticks.
Filters and distribution
Crouch-use a filter or edit it from a port. Shift-click inventory stacks or drag recipe-viewer entries to copy ghost examples without consuming stock. Limited item filters fill to a target stock level on insertion and extract only excess stock.
Item filters reject new duplicate patterns. Component matching permits distinct variants; damage uses its separate mode. Saved duplicates and stock limits remain intact and can be removed manually. See the filter reference.
Open port menus and their embedded filters recheck current protection rights. Revoking access rejects further changes and closes the menu. Reopen it after access is granted again.
Give Create basins and depots separate input and output filters. Permit ingredients inward and finished outputs/byproducts outward; the network does not infer recipe progress. Batch round robin portions are transfer quantities, not target stock levels.
Redstone cards execute left to right. Timers and sensors supply a new input and should precede transformations. Updates resolve to two ticks.
Use the Conduit Probe
Cycle modes with sneak-mouse-wheel and read the HUD. Inspection reads ports. Copy/Paste uses sneak-right-click for one port, Ctrl-right-click for every type on one side, and normal right-click to paste. Copy Bus Sockets copies all six sides without installing missing conduit types.
Network Upgrade consumes matching higher-tier materials and checks each target; unloaded nodes prevent the network upgrade. Network Analysis reports configured channels and filters. An incomplete scan cannot guarantee a displayed unoccupied color is free everywhere.
Analysis also works in singleplayer when TDClaim is explicitly disabled there (debugSingleplayer = false). Other interaction and protection checks remain active. If analysis stops, the window shows the actual reason, the next step and the selected conduit's coordinates. Refresh retries the same selection after temporary failures or missing server responses. Keep holding the probe in Check Network Channels mode and stay within eight blocks of the conduit. Selections expire after two minutes; close the window and click the conduit again then. Failures no longer send a duplicate generic chat message. Singleplayer access, single-color fluid networks and retries are covered by automated tests; in-game acceptance remains pending.
Little Big Redstone and troubleshooting
The Network Monitor shows delivered throughput, a short history and observed bottleneck hints for item, fluid and energy networks. Place it beside a bundle; collection runs only while its menu is open.
Ender Pipe I/O requires LBR. To send a chip signal, choose component Output and conduit Extract. To receive into the chip, choose Input and conduit Insert. Its live view distinguishes connected 0, missing conduit --, disabled direction X and an unready network ?.
For stalled routes, inspect direction, machine face, channel, filter, redstone and chunk availability. Rejected real transfers can retain contents for retry; do not discard conduit data to clear a warning. Quarantined graphs preserve their original data for investigation.
Old item port settings survive saves and restarts until their bundle loads and converts them once. Malformed bundle and recovery data remains in RejectedBundleData, malformed world network lists in RejectedNetworkData, and rejected old graphs in RejectedLegacyGraphs. These entries support manual recovery and are not active transport contents. Preserve the original data and investigate on a world copy. Automated save/load checks do not replace in-game migration, restart and chunk acceptance.
Settings use config/tdenderpipes-common.toml. Existing nested legacy settings need the documented migration before startup. The reference covers sensors, card chains and migration.