Zum Hauptinhalt springen

Conduits, filters and sensors reference

Mit FlammiCraft ausgelieferte Mod-Version: 0.51.0

Diese Detailseite ist derzeit auf Englisch verfügbar.

Handbook overview

Included systems

  • Item conduits with standard, round-robin, batch round-robin and balanced output distribution
  • Fluid and energy conduits with tiers up to Supreme, plus redstone conduits
  • Optional Mekanism chemical conduits with tiers up to Supreme
  • Conduit filters, facades, probe and wrench behavior. Probe copy/paste messages and tooltips display conduit names, setting labels, colors and boolean values in the client's language.
  • Conduit-probe copy and paste for complete targeted-port settings across compatible tiers using matching filters, upgrades and modules from the player's inventory. Ctrl + right-click copies all conduit types on the targeted connection side and selects Copy/Paste mode; right-click pastes every compatible copied type. Shift + right-click still copies only the targeted conduit type.
  • Drag-and-drop item, fluid and chemical filter entries from EMI, and from JEI through its compatibility layer. Shift-click copies an inventory stack into the next empty filter slot and leaves that stack in the inventory.
  • A multifunction Conduit Probe for inspection, port copying, complete bus copying, network upgrades and channel analysis
  • Conduit configuration screens, rendering and networking
  • Conduit bundles cannot be waterlogged; placing them in water displaces the water in their block space. Previously waterlogged bundles load without water.
  • A configurable redstone Weather Sensor

Requirements

  • Minecraft 1.21.1
  • NeoForge 21.1.256 or newer compatible 21.1 release
  • Java 21
  • Mekanism only when chemical conduits are required
  • Little Big Redstone 1.9.12 or newer for microchip Ender Pipe I/O components

TDEnderPipes must be installed on the server and every connecting client. Server and clients must use the same release. Core network protocol 1.2 removes unused particle channels and retains the menu-scoped write boundary introduced in 0.10.3. Filter edits require a valid open menu, and conduit configuration packets must match the selected conduit type.

Configuration

Settings are stored in config/tdenderpipes-common.toml, directly in Minecraft's config directory. No separate server or client config is currently needed. When updating from an older version, move config/tdenderpipes/conduits-common.toml to config/tdenderpipes-common.toml before starting Minecraft to retain your settings. Config keys and defaults are unchanged. The old path is no longer read.

Tools

For batch round-robin item routing, set the batch size on each machine's insert port and enable batch round-robin on the source chest's extract port. The count is a transfer portion, not a target inventory stock level. A source that receives items intermittently keeps filling the current portion; a destination that stops accepting items is skipped so the next port can receive them. Reducing a batch size below the already transferred portion completes that batch and advances to the next port. If a destination rejects the remaining part of a portion, routing discards that partial portion and continues to the next port. With only one destination, the next transfer attempt starts a fresh portion without exceeding its configured size.

All item routing modes resume extraction after the last successfully served source slot on the next transfer cycle. Continuously replenished stacks no longer prevent later ingredients from being transported. Balanced distribution also retries remaining items when a destination rejects a smaller share.

For Create basins and depots with both Insert and Extract enabled, use separate filters: the insert filter allows ingredients, while the extract filter allows the intended results and byproducts. A basin exposes ingredients and results through the same item capability, so an extract filter that also permits ingredients can send unprocessed items back into the network. Item routing respects these filters and does not infer recipe inputs or outputs.

Item transfers retain destination slot order and recheck destination capabilities for each transfer attempt, so replaced or invalidated inventories are not retained across transfers. Network node accesses check chunk availability once; item filters use the destination handler already resolved for the current attempt. Empty item filter slots skip capability queries; populated filters are still resolved for each attempt so callback changes take effect immediately. Existing neighboring capability cache entries use direct lookups; each access still queries the NeoForge cache so invalidated capabilities are refreshed. Fluid selection reads each source tank once before the existing simulated and actual transfer steps. Fluid selection and drain requests preserve the stack's components, including additional data used to distinguish variants of the same fluid.

Fluid and chemical conduits transfer every five game ticks. Each transfer cycle allows five times the configured per-tick rate, limited by the slowest conduit on the path and the source's remaining transfer budget.

Energy transfer limits apply per game tick to every conduit along the route. Repeated pushes, multiple sides and multiple sources share the remaining budget of any conduit they traverse. A shared lower-tier conduit remains a bottleneck. Simulation reports the currently available transfer without consuming that budget; the budget resets on the next game tick and is not saved in the world.

Item conduits check insert filters and simulate destination acceptance before actually extracting items. Full or filtered destinations therefore do not cause repeated extraction and reinsertion or unnecessary source comparator updates. Partial acceptance limits the real extraction amount. After extraction, the destination and its filter are resolved again before real insertion. Nested transfers from the same source node are rejected while its transfer is active. Unaccepted items return to the current source slot when possible; otherwise they remain in the conduit for retry. Fluid rejected after simulated acceptance also remains in the conduit and is retried before fresh extraction. Recovery queues keep item and fluid components, survive saves and upgrades, and travel with a broken conduit's item when it is placed again. A temporarily missing source capability skips the transfer without discarding retained contents.

When Design n' Decor is installed, its dyed-container comparator and controller lookups during pipe item transfers read only already loaded chunks. This also covers a comparator behind a conducting neighbor across a chunk boundary. Unavailable chunks are skipped instead of synchronously loaded from an inventory callback. Normal container access outside pipe transfers is unchanged; Design n' Decor remains optional.

Filter menus opened from a conduit require the original block and port inventory to remain valid and in reach. Handheld filters support both hands. Network upgrades check build and interaction permissions separately at each target; denied targets remain unchanged and consume no items.

Invalid saved graph edges are quarantined separately from healthy networks. Their original data is retained on save; rejected legacy entries are kept under RejectedLegacyGraphs for manual recovery. Quarantined networks do not tick.

The Conduit Probe combines five modes. Shift + mouse wheel cycles forwards or backwards; the mode key can be changed in Minecraft's controls. The held-tool HUD and tooltip show the current mode. Either hand is supported.

  • Inspection: use a connection to inspect its settings and port items, or the bundle core to list the installed conduit types and tiers.
  • Copy/Paste: Shift + right-click copies the targeted conduit port. Ctrl + right-click copies every conduit type on the targeted side. Right-click pastes the matching configurations across compatible tiers.
  • Copy Bus Sockets: Shift + right-click copies all conduit types and all six directions of one bundle. Right-click applies that complete template to another bundle, keeping north/south/east/west/up/down aligned. Missing conduit types are skipped and reported; the probe does not install conduits. Valid neighboring connections open immediately, disabled sides stay disabled and configurations without an available neighbor remain stored for later connection.
  • Network Upgrade: use the precisely targeted conduit network to upgrade one tier. Survival mode consumes matching higher-tier conduits and returns the old conduits. Available materials permit partial upgrades; a network containing an unloaded node is left unchanged. Every affected target is checked separately.
  • Network Analysis: use a specific conduit type to list occupied colors in its connected physical network. Free channel colors stay above the paged list; hover a symbol to see its localized color name. Occupancy covers the whole inspected network, including channels on other pages. An incomplete scan labels colors as not known to be occupied rather than guaranteed free. If every color is occupied, the overview says None. Energy conduits have no color overview. The paged list combines all configured filter entries across its ports, including multiple entries in one filter. Item names use the client's language. Positive examples, exclusions, tag rules and dynamic filters remain distinguishable; these are configured rules, not proof of actual transfers. Unloaded ports retain their last known descriptions. Older unknown ports become known as their chunks load normally; the view reports incomplete data and never loads chunks to fill gaps. Protected endpoints are filtered before aggregation, and page requests recheck access.

Port templates reuse matching installed cards or consume exact matching or blank cards from the player inventory. Differently configured inventory cards are not silently overwritten. Replaced cards and oversized-stack remainders are returned. A port missing a required item stays unchanged. Timer, counter and other running redstone state is not copied with the settings.

The separate Conduit Inspector and Conduit Network Upgrader items have been removed, including their recipes and registrations. No conversion recipes or migration handlers are provided; saved stacks of those removed items are no longer supported. The existing Conduit Probe item and its saved modes remain.

Weather Sensor

Craft a daylight detector with redstone dust to obtain a Weather Sensor. Its model geometry and item model follow Minecraft's daylight detector, with custom top and side textures. An alternate top marks a nonzero output. The model and textures can be changed independently. Right-click normally to open its configuration screen; no wrench is needed. Select any combination of clear/sun, rain/snow, thunderstorms and offered modded weather types from the list. Only selected types appear in the details pane, with their current signal and editable inactive (Off) and active (On) values from 0 to 15. Both lists have page controls for additional weather types. Changes apply immediately. Initial values are Off 0 for every type, with On 1 for rain/snow, 2 for clear/sun and 3 for thunderstorms. Newly selected types receive an unused active value where possible; all values remain freely editable, including deliberate overlaps and an active value of zero.

The sensor checks once per second on the server, in its own dimension and biome. Vanilla detection requires an exposed position; under a roof every vanilla type is inactive and uses its configured Off value. Rain and snow use the biome's precipitation at the sensor's height. Rain/snow can also match during a thunderstorm. Clear/sun means dry local weather and also applies at night. Dry biomes report clear local weather. Dimensions without skylight or with a ceiling have no vanilla weather activity. Selections and signal values survive chunk unloads and world restarts; deselecting a type retains its values. Existing snow selections become rain/snow. Breaking and placing the block resets its settings to rain/snow with Off 0 and On 1.

An active selected thunderstorm emits its configured On value with priority over all other types, even if that value is lower or zero. Otherwise, multiple active selected types emit the highest On value. Inactive types do not override an active type. When no selected type is active, the highest available selected Off value is emitted. Missing types contribute zero; an empty selection emits zero. The screen also shows the combined block output. Weather intensity does not change the configured signal values.

Minecraft 1.21.1 has no shared registry for modded weather types. Integrations subscribe to de.taker.tdenderpipes.api.weather.WeatherQueryEvent on NeoForge.EVENT_BUS. For each query, offer every supported type, even when inactive, using a stable namespaced ID, a display component, a boolean activity flag and a normalized 0–1 intensity:

event.offer(ResourceLocation.fromNamespaceAndPath("weather_mod", "sandstorm"),
        Component.translatable("weather.weather_mod.sandstorm"), activeHere, localIntensity);

Use event.getLevel() and event.getPos() to evaluate the actual sensor location. Offered types become selectable automatically, sorted by ID, without a client dependency on the weather mod. Integrations may replace vanilla IDs to provide their own local precipitation. Modded weather is queried in every dimension; its exposure rules belong to the integration. Missing types emit zero and retain their saved selection and signal settings. The sensor uses the activity flag; intensity remains available in the integration API. Non-finite intensity values mark that reading inactive; finite values are clamped to 0–1. No particular weather mod integration is bundled.

Time Sensor

Craft a daylight detector with a clock to obtain a Time Sensor. Right-click without a wrench to configure up to 15 free time windows, each with a start, end and inactive/active redstone value from 0 to 15. Hours and minutes have separate adjustment buttons. The default window is 06:00–12:00, Off 0 and On 1; new windows receive unused active values where possible. Windows can be removed. The screen shows the current Minecraft time and combined block output.

Start is inclusive and end is exclusive. A window such as 22:00–06:00 crosses midnight; equal start and end means all day. Overlapping active windows emit the highest On value. If no window is active, the highest Off value is emitted; inactive windows never override an active window, including one with On 0. No windows emit 0. Settings survive chunk unloads and restarts; breaking and placing the sensor resets them.

The sensor reads its dimension's Minecraft day time, with tick 0 displayed as 06:00, and respects fixed-time dimensions. It works under roofs and does not depend on weather or sky visibility. Sleeping, time commands and a stopped day cycle affect its reading. Checks run every game tick so even one-minute windows are detected. The block initially uses copies of the Weather Sensor's model and textures, stored separately for later editing.

Filters

Crouch and use a filter to configure it. Item, fluid, chemical, tag and mod filters can also be opened from the conduit screen.

Each conduit port's filter/card slot accepts one item. Previously inserted stacks can still be removed in full; new stacks cannot be inserted.

Item filters reject a new pattern if another slot already matches the same item. This applies to clicks, shift-clicks and EMI/JEI drops, with the server deciding the result in singleplayer and multiplayer. A rejected insertion keeps the target slot unchanged; recipe-viewer drops resynchronize to the server's result. With Match Components enabled, different component variants may occupy separate slots. Stack counts do not distinguish patterns, and damage remains controlled by the separate damage mode. Edit a limited filter's stock limit in its existing slot instead of adding another entry for that item.

Saved duplicates retain their patterns, slot order and stock limits when loaded. Switching component matching off also keeps existing variants. Remove unwanted duplicates manually; no automatic cleanup or change to transfer matching occurs. Automated menu and save/load tests cover these rules; in-game client and multiplayer acceptance remains pending.

  • Item filters (basic, big, advanced, big advanced, limited), fluid filters (basic, advanced) and, with Mekanism, chemical filters (basic, advanced) match the resources placed in their slots. Shift-click an inventory stack to copy it into the next empty slot; the stack stays in the inventory. A limited item filter keeps that stack's count as the stock limit. Fluids and chemicals dragged from EMI fill the whole slot they are dropped on.
  • The Insert Channel Order card goes in an item insert slot, in place of an item filter. Its color list is the order those channels are served: red, then green, then blue means green items move after red and before blue. A listed color is skipped unless that insert also has the color selected. Cards on one network combine; when two cards disagree, that step keeps the existing channel order. Crouch-use the card or the conduit configure button to edit it. Earlier entries are served first. Choosing a color that is already listed swaps the two entries.
  • The limited item filter fills an insert inventory up to the configured stock and only extracts items above that stock on an extract port.
  • Tag filters for items, fluids and chemicals match up to five tags, for example c:ingots. The mod item filter matches up to five mod IDs, for example mekanism. Both work as allow or deny lists.
  • Redstone filters: NOT, OR, AND, NOR, NAND, XOR, XNOR, toggle, counting, sensor, timer, threshold, pulse and delay. The threshold filter outputs a full signal while the watched signal reaches the configured strength. The pulse filter turns each rising edge on an input port into a pulse of fixed length. The delay filter works on input and output ports and passes a change only after it has lasted for the configured number of ticks and ignores shorter changes. Redstone conduits update every two ticks, so timings resolve to two ticks.
  • Sensor Delay is a single input-only card combining comparator sensing with an off delay. Positive readings pass through immediately, including changes in strength. When the reading becomes zero, the last nonzero strength stays on for the configured hold time, then turns off. A new positive reading cancels the countdown; becoming empty again starts the full time again. Crouch-use to configure 1–72000 ticks (20 ticks = 1 second; default 20 ticks). Craft it from a Sensor Filter and a Delay Filter. Like the Sensor card, it supplies a new input signal; place it before cards that transform the signal. Its settings and countdown are saved with the conduit inventory.
  • Each redstone port has three input and three output card slots. Cards run from left to right, skipping empty slots. NOT followed by Delay inverts the signal, then passes the inverted value after it stays unchanged for the configured time. Timer and sensor cards supply a new input signal; place them before cards that transform it. Output logic cards still read their configured channels; after another card, reads of the port's signal color use that card's result, while other colors continue to read the network. Configure redstone cards by crouching and using them in either hand before inserting them. The editor stays bound to that card and hand; replacing the card closes access.
  • AND, OR, NAND, NOR, XOR and XNOR cards start with two input colors and allow up to six. Use the plus/minus buttons in their configuration menu to add or remove a color. Existing cards keep their two saved colors. AND requires all selected inputs, OR requires at least one; NAND and NOR invert those results. XOR outputs 15 for an odd number of active inputs, XNOR for an even number. Each selected slot is a gate input, including repeated colors. Server and clients must use the same release. Conduit network protocol 10 includes hand-aware probe modes and on-demand analysis pages with network-wide channel occupancy, failure reasons and retryable selections. It also binds redstone edits to the current valid menu and does not accept client-provided timer progress or counter state. Chemical filter entries dragged from EMI use the same channel. It cannot connect to older protocol versions.

Little Big Redstone

When Little Big Redstone is installed, craft its I/O Port with a Redstone Filter Base to obtain an Ender Pipe I/O. The component is also available in both mods' creative tabs and in the microchip's creative component inventory. It can be stored in logic arrays and copied with the normal microchip tools.

Use TDEnderPipes 0.9.1 or newer for the I/O configuration menu. Version 0.9.0 could disconnect the client when opening it because of button initialization.

Choose Output, connect a logic signal to its input, and configure its side, conduit color and signal mode. Fixed emits the selected strength from 0 to 15 while the input is active. Pass through sends the incoming strength, limited to 0 to 15. An inactive input always sends zero. Side selection uses Little Big Redstone's normal world directions. Click Channel to open a list of all 16 colors with their names and the same symbols and order as the conduit color picker. The current channel is outlined. Click a color to return to the component settings, then use Save to apply it. Escape or Cancel closes the color list without changing the channel; the component menu's Cancel still discards all pending configuration changes.

Choose Input to read the selected color from the adjacent redstone conduit into the microchip. Enable Insert on the conduit port. Pass through outputs the received strength from 0 to 15. Threshold outputs 15 when the received strength is positive and at least the selected level, otherwise zero. A threshold of zero therefore accepts any positive signal. Inputs read raw network colors before conduit output filters, independent of the port's chosen vanilla output color. Changing Input/Output changes the component's wire ports; reconnect circuit wires as needed. Existing saved components retain output mode.

Enable both Insert and Extract to read and send through the same physical connection. For example, read Green and Red, combine them in the microchip, and send the result on Blue. Inputs exclude all contributions originating from that same microchip, including its normal redstone output and its other sides. They still receive weaker signals from other sources on the same color. Deliberate feedback between separate microchips follows the normal circuit behavior.

The component's live display shows the received raw strength for inputs or the sent strength for connected outputs. A connected zero appears as 0; -- means no redstone conduit, X means its required port direction is disabled, and ? means the adjacent chunk or network is not ready. The item tooltip explains these symbols. Reading an unloaded neighbor does not load its chunk. Live readings and connection status synchronize with the microchip and reset on world load until recalculated.

Hover over an I/O component on the microchip board to see its side, channel, direction and mode together with live raw strength, logic or conduit output, and a written connection status. Unavailable input readings are explicitly marked rather than presented as a connected zero. Inventory item tooltips show configuration only, so they cannot display another component's live readings.

Attach a redstone conduit to that microchip side and enable Extract on the conduit port. This connection accepts all 16 colors simultaneously. For example, three components on the same side can send Green 7, Red 15 and Blue 3. At each destination, enable Insert and select the color to emit. Multiple sources on the same color combine using the highest strength; they are not added together.

Input filter cards affect the port's configured extract color. Other microchip colors pass directly into their matching network channels. Normal redstone from the microchip still feeds the configured extract color and combines with that color's component output. Signals update on the normal two-tick conduit cadence. Removing a component, disabling its input or disconnecting the microchip clears its contribution on the next network update. After loading a microchip, signals are recalculated from its logic rather than restored as a permanently active output. Component configuration is saved and synchronized through Little Big Redstone's own format.

Little Big Redstone and Mekanism remain optional at runtime. For local compile inputs, set local_mods_dir in gradle.properties or pass -Plocal_mods_dir=<mods directory>. The build requires exactly one matching Little Big Redstone 1.21.1 JAR, NeoForge Tesseract API 1.21.1 JAR, GuideME 21.1 JAR and NeoForge EMI JAR there. These files are read-only inputs and are not bundled into TDEnderPipes.

Mekanism and TDLibrary are resolved through the configured local Maven publications. TDLibrary is a required implementation dependency, with a runtime minimum of 0.41.0 on both sides. The optional -PtdLibraryTestJar=<absolute JAR> override replaces the local Maven input for compilation and tests; it does not install or publish that JAR. The build uses NeoForge 21.1.256.

Run :tdenderpipes:test for tests with Little Big Redstone and Mekanism loaded. Run :tdenderpipes:test -Ptest_without_little_big_redstone=true --rerun-tasks to check the base mod without Little Big Redstone and its dependencies on the test runtime classpath. This excludes the integration-specific tests. Add -Ptest_without_mekanism=true to also test without Mekanism. Its chemical tests are excluded in that run; the base network and worker tests still execute.

The direct TDLibrary slot-index bridge is tested with the regular library input. Use -Pae2TestJar=<absolute JAR> to select an explicit AE2 integration test input without requiring an installed AE2 candidate. Without this override, the test requires exactly one matching AE2 Reforged JAR in local_mods_dir.

Recipes

Base conduits are crafted from iron, a type material and redstone. Every higher tier is crafted from conduits of the previous tier of the same type:

Tier Ingredients Output
Enhanced / Pressurized 8 base conduits, gold ingot 8
Ender 4 previous-tier conduits, 4 ender pearls, diamond 4
Absolute 4 previous-tier conduits, 4 obsidian, netherite ingot 4
Supreme 4 previous-tier conduits, 4 diamond blocks, nether star 4

When Mekanism is installed, the infused alloy replaces the gold ingot, the reinforced alloy replaces the diamond and atomic alloys replace the obsidian. Chemical conduits always use the Mekanism variant.

Migration

World migration from pipio to tdenderpipes is performed by an external migration tool. TDEnderPipes intentionally does not register PipIO aliases or run an in-mod world migration. Registry path names are retained where a pure namespace migration depends on them.

Always test migration on a copied world. Verify conduit contents and settings after a full restart and after the containing chunks have unloaded and loaded.

Legacy item port settings are converted when their bundle attaches. Until then, the network retains the original settings across saves and restarts, including round-robin progress, self-feed and priority. This does not perform a namespace migration.

Malformed bundle entries and recovery lists remain in RejectedBundleData. Malformed world network lists remain in RejectedNetworkData; invalid individual legacy graphs remain in RejectedLegacyGraphs. These tags preserve evidence for manual recovery and are not active transport contents. Keep the original world data and investigate on a copy instead of deleting these tags. Automated checks cover repeated save/load cycles; migration and chunk behavior still need in-game acceptance on a copied world.