ВЕРСИИ (33)

fix: StackOverflowError from mutual recursion with Mekanism transporters fix: nearest-first routing, wrench sneak-click, walled-in attachment placement

fix: StackOverflowError from mutual recursion with Mekanism transporters fix: nearest-first routing, wrench sneak-click, walled-in attachment placement

fix: StackOverflowError from mutual recursion with Mekanism transporters fix: nearest-first routing, wrench sneak-click, walled-in attachment placement

fix: StackOverflowError from mutual recursion with Mekanism transporters fix: nearest-first routing, wrench sneak-click, walled-in attachment placement

### Added - **Extractor Attachments can now pull energy** — energy pipes used to be entirely passive: they only ever received what a machine chose to push into them. Any device that merely exposes a drainable buffer without pushing — a Sophisticated Backpack with an energy upgrade, most capacitors and accumulators — was therefore unreachable, and would sit permanently full while the pipe next to it stayed empty. Placing an Extractor Attachment on an energy pipe now actively drains the adjacent block into the network. - Extraction rate per tier mirrors the energy pipe tiers: 1,000 / 4,000 / 8,000 / 16,000 / 32,000 FE per tick (`energyToExtract`, `energyTickInterval` in the server config). - The pipe the extractor sits on still caps throughput, matching how the rest of the energy code treats boundary pipes — a Basic pipe never moves more than its own transfer rate no matter which extractor is attached. - Energy has nothing to filter on, so in energy mode the extractor GUI offers no filter slots and the blacklist/whitelist, exact-match and routing controls are disabled. Redstone mode still works.

### Added - **Extractor Attachments can now pull energy** — energy pipes used to be entirely passive: they only ever received what a machine chose to push into them. Any device that merely exposes a drainable buffer without pushing — a Sophisticated Backpack with an energy upgrade, most capacitors and accumulators — was therefore unreachable, and would sit permanently full while the pipe next to it stayed empty. Placing an Extractor Attachment on an energy pipe now actively drains the adjacent block into the network. - Extraction rate per tier mirrors the energy pipe tiers: 1,000 / 4,000 / 8,000 / 16,000 / 32,000 FE per tick (`energyToExtract`, `energyTickInterval` in the server config). - The pipe the extractor sits on still caps throughput, matching how the rest of the energy code treats boundary pipes — a Basic pipe never moves more than its own transfer rate no matter which extractor is attached. - Energy has nothing to filter on, so in energy mode the extractor GUI offers no filter slots and the blacklist/whitelist, exact-match and routing controls are disabled. Redstone mode still works.

### Added - **Extractor Attachments can now pull energy** — energy pipes used to be entirely passive: they only ever received what a machine chose to push into them. Any device that merely exposes a drainable buffer without pushing — a Sophisticated Backpack with an energy upgrade, most capacitors and accumulators — was therefore unreachable, and would sit permanently full while the pipe next to it stayed empty. Placing an Extractor Attachment on an energy pipe now actively drains the adjacent block into the network. - Extraction rate per tier mirrors the energy pipe tiers: 1,000 / 4,000 / 8,000 / 16,000 / 32,000 FE per tick (`energyToExtract`, `energyTickInterval` in the server config). - The pipe the extractor sits on still caps throughput, matching how the rest of the energy code treats boundary pipes — a Basic pipe never moves more than its own transfer rate no matter which extractor is attached. - Energy has nothing to filter on, so in energy mode the extractor GUI offers no filter slots and the blacklist/whitelist, exact-match and routing controls are disabled. Redstone mode still works.

### Added - **Extractor Attachments can now pull energy** — energy pipes used to be entirely passive: they only ever received what a machine chose to push into them. Any device that merely exposes a drainable buffer without pushing — a Sophisticated Backpack with an energy upgrade, most capacitors and accumulators — was therefore unreachable, and would sit permanently full while the pipe next to it stayed empty. Placing an Extractor Attachment on an energy pipe now actively drains the adjacent block into the network. - Extraction rate per tier mirrors the energy pipe tiers: 1,000 / 4,000 / 8,000 / 16,000 / 32,000 FE per tick (`energyToExtract`, `energyTickInterval` in the server config). - The pipe the extractor sits on still caps throughput, matching how the rest of the energy code treats boundary pipes — a Basic pipe never moves more than its own transfer rate no matter which extractor is attached. - Energy has nothing to filter on, so in energy mode the extractor GUI offers no filter slots and the blacklist/whitelist, exact-match and routing controls are disabled. Redstone mode still works.

### Fixed - **Items dropped into the world when the destination was nearly full** — extractors sized their dispatch against a capability simulation, which reports the inventory as it is *now* and not as it will be once items already in transit land. With several ticks of travel time an extractor kept re-dispatching against the same free slot; the surplus arrived to a full inventory, bounced, was refused by output-only sources (farmer villagers, generators) and fell on the ground. Networks now track how many items are in flight toward each receiver and extractors subtract that from the free space they see. The count is rebuilt from the live transports every tick, so it cannot drift out of sync after a bounce, a broken pipe, a chunk unload, a world reload, or a network split. - **Extraction stalled once every destination was partially filled** — a destination was only considered usable if it could accept the *entire* stack, so a chest with room for 3 was skipped when the extractor offered 5, and extraction stopped completely once no destination had full room. Partial room is now enough; the extractor sends exactly what fits. - **Void Attachments never received items** — the full-destination pre-check added in 1.3.1 required an item-handler capability, but a void destination deliberately has no adjacent inventory and no capability, so every extraction toward one was skipped. Void destinations now bypass the capacity probe. ### Changed - Items arriving at a destination that filled up mid-transit are now inserted partially instead of bouncing the whole stack — only the remainder is returned or, as a last resort, dropped. ### Notes - This supersedes the partial fix shipped in 1.3.1 ("items no longer dropped in world when destination inventory is full"). That version pre-checked capacity but had no notion of items already in transit, so the drop could still happen under sustained throughput.

### Fixed - **Items dropped into the world when the destination was nearly full** — extractors sized their dispatch against a capability simulation, which reports the inventory as it is *now* and not as it will be once items already in transit land. With several ticks of travel time an extractor kept re-dispatching against the same free slot; the surplus arrived to a full inventory, bounced, was refused by output-only sources (farmer villagers, generators) and fell on the ground. Networks now track how many items are in flight toward each receiver and extractors subtract that from the free space they see. The count is rebuilt from the live transports every tick, so it cannot drift out of sync after a bounce, a broken pipe, a chunk unload, a world reload, or a network split. - **Extraction stalled once every destination was partially filled** — a destination was only considered usable if it could accept the *entire* stack, so a chest with room for 3 was skipped when the extractor offered 5, and extraction stopped completely once no destination had full room. Partial room is now enough; the extractor sends exactly what fits. - **Void Attachments never received items** — the full-destination pre-check added in 1.3.1 required an item-handler capability, but a void destination deliberately has no adjacent inventory and no capability, so every extraction toward one was skipped. Void destinations now bypass the capacity probe. ### Changed - Items arriving at a destination that filled up mid-transit are now inserted partially instead of bouncing the whole stack — only the remainder is returned or, as a last resort, dropped. ### Notes - This supersedes the partial fix shipped in 1.3.1 ("items no longer dropped in world when destination inventory is full"). That version pre-checked capacity but had no notion of items already in transit, so the drop could still happen under sustained throughput.

fix: ConcurrentModificationException on level tick when network splits mid-iteration

fix: ConcurrentModificationException on level tick when network splits mid-iteration fix: server hangs / crashes on tick — guard chunk loads and network iteration

fix: ConcurrentModificationException on level tick when network splits mid-iteration

fix: ConcurrentModificationException on level tick when network splits mid-iteration

fix: ConcurrentModificationException on level tick when network splits mid-iteration

Fixed Crash on load with Sable / contraption mods — pipes on simulated platforms no longer throw when sending block updates NPE when adding/removing attachments on a temporarily networkless pipe — caused desync (broken render, duplicate drop) Copper Barrel Upgrade now accepts both minecraft:barrel and fastpipes:oak_barrel Changed Mixed-tier energy networks: per-pipe throughput instead of MIN-tier bottleneck. Each boundary pipe rate-limits its own I/O, capacity still sums across all pipes

Fixed Crash on load with Sable / contraption mods — pipes on simulated platforms no longer throw when sending block updates NPE when adding/removing attachments on a temporarily networkless pipe — caused desync (broken render, duplicate drop) Copper Barrel Upgrade now accepts both minecraft:barrel and fastpipes:oak_barrel Changed Mixed-tier energy networks: per-pipe throughput instead of MIN-tier bottleneck. Each boundary pipe rate-limits its own I/O, capacity still sums across all pipes

### Added - **Jade integration for attachments and terminal** — pipe attachments (Extractor / Inserter / Sensor / Void) now appear in Jade's WAILA tooltip with tier, side, redstone mode, blacklist/whitelist, routing mode, stack size, exact mode, and fluid mode. Pipe Terminal shows network status (unique stacks, total items, active user). - **Mixed-tier Energy Pipe networks** — energy pipes of any tier now connect into a single network. Capacity is summed across all tiers; transfer rate is bottlenecked by the slowest tier in the network (no free upgrade — a single Ultimate pipe in a Basic network won't accelerate the whole network). - **Terminal sort mode persistence** — the selected sort (Name / Count / Mod) is saved per-terminal and restored after closing and reopening the GUI. - **Terminal single-user lock** — only one player can have a given terminal open at a time; others see "Terminal is in use by <name>". Auto-recovers from stale locks (crashed/offline holder or menu already closed). ### Fixed - **Items no longer dropped in world on full destination** — extractor now pre-checks destination capacity before pulling; items stay in source if target inventory is full. Bounce-back and orphaned-transport fallbacks scan the entire network for space before resorting to a world drop. - **Removed attachment didn't appear in inventory** — the dropped item used to spawn as an `ItemEntity`, which produced a client-side desync where the pickup sound played but the inventory didn't update until another container was opened. Items are now given directly via `ItemHandlerHelper.giveItemToPlayer` with proper sync. - **Energy flow stopped after adding a second power source** — adjacent energy generators / consumers cached the pipe's energy capability handle which bound to a specific network instance; after a network rescan their cache pointed at an orphaned network and all flow stopped, with pipe energy appearing to reset to 0. The pipe now exposes a stable delegating storage that always queries the current network. - **Wrench shift+right-click not breaking pipes** — wrench item now bypasses sneak-use suppression (`doesSneakBypassUse`), so shift+right-clicking a pipe with the wrench correctly breaks and drops it. - **Barrel upgrade item duplication** — applying a barrel upgrade no longer drops a duplicate copy of the barrel's contents into the world while preserving them in the upgraded barrel. The old block entity is cleared before the block is replaced so `onRemove` has nothing to drop. - **GUI dead zones on attachment edges** — clicking near the edge of an attachment now reliably opens its GUI (falls back to the clicked face when the bounding-box hit misses). - **Terminal cursor sync delay** — items now appear on the cursor immediately after extraction instead of after a tick. - **NPE on pipe network tick** — `Pipe.leaveNetwork` and `ItemTransport.update` are now defensive against transient null-network states during rescans. ### Changed - Wrench right-click on an attachment opens the attachment GUI instead of toggling disconnect on that side. Toggle disconnect still works on bare pipe sides. - Removing an attachment now clears a stale "disconnected" flag on that side so the pipe reconnects normally to the adjacent inventory. ### Notes - Existing worlds with tier-specific energy networks load fine — legacy network IDs are mapped to the unified energy network type, and pipes merge on the next scan. Pre-existing buffered energy in those networks is not persisted (was never persisted) so it resets once after the update.

https://github.com/bigenergy/fastpipes/blob/backport/1.20.1-forge/CHANGELOG.md

Fixed - Barrel upgrade item duplication — applying a barrel upgrade no longer drops a duplicate copy of the barrel's contents into the world while preserving them in the upgraded barrel. The old block entity is cleared before the block is replaced so onRemove has nothing to drop. - Wrench shift+right-click not breaking pipes — wrench item now bypasses vanilla's sneak-use suppression (doesSneakBypassUse), so shift+right-clicking a pipe with the wrench correctly breaks and drops it. - Wrench right-click on attachment now opens its GUI — previously the wrench's "toggle disconnect" action triggered first, silently disconnecting the pipe side instead of opening the attachment. Toggle disconnect still works on bare pipe sides. - Removing an attachment clears stale disconnect state — if a side was toggled disconnected (e.g. accidentally with the wrench while the attachment was installed), removing the attachment now resets that side so the pipe reconnects to the adjacent inventory.

**Fixed** - Items no longer dropped in world when destination inventory is full (pre-check + network-wide fallback) - Terminal extraction broken for aggregated stacks > 127 items (byte-overflow in packet) - GUI dead zones on attachment edges (clicks near borders now reliably open the GUI) - Rare NPE crashes during pipe network rescans **Added** - Terminal sort mode persists across GUI closes - Terminal single-user lock — one player at a time; auto-recovers from stale locks

### Added - **Pipe Terminal** — access all inventories connected to the pipe network from a single block. Supports searching, extracting, inserting, and crafting directly from network resources. Place next to any item pipe to connect. - **Tiered Barrels** — Oak (27 slots), Copper (45), Iron (54), Gold (72), Diamond (90), Netherite (108, blast resistant). Upgradeable in-place with barrel upgrades that preserve contents. - **Waterlogged pipes** — all pipes can now be placed underwater. Water flows correctly around pipe geometry. ### Changed - **Pipe crafting recipes reworked** — tier 2+ pipes now require the previous tier pipe as an ingredient (e.g. Improved Item Pipe = 4× Gold Ingots + Basic Item Pipe). More logical tier progression.

**Forge 1.20.1 backport** — full port from NeoForge 1.21.1 to Forge 1.20.1 (Java 17, Forge 47.3.0). - **Pipe Terminal** — access all inventories connected to the pipe network from a single block. Supports searching, extracting, inserting, and crafting directly from network resources. Place next to any item pipe to connect. - **Tiered Barrels** — Oak (27 slots), Copper (45), Iron (54), Gold (72), Diamond (90), Netherite (108, blast resistant). Upgradeable in-place with barrel upgrades that preserve contents. - **Waterlogged pipes** — all pipes can now be placed underwater. Water flows correctly around pipe geometry. - **JEI descriptions** for all items — barrels, barrel upgrades, Void Attachment, Sensor Attachment, and Terminal now have info pages in JEI.

Extractors now pull unstackable items (tools, armor, weapons) from multiple slots per operation, massively improving throughput for mob farms and similar setups

- Fix NPE crash when deserializing item transport callbacks - Added russian translate

https://github.com/bigenergy/fastpipes/blob/master/CHANGELOG.md

### ✨ New Features - **Fluid Pipes now work!** Full fluid transport between tanks with extraction and filtering support - **Inserter Attachment** — new attachment type (5 tiers: Basic → Ultimate) that marks a pipe side as an item destination with priority routing - **Jade integration** for all pipe types — Item, Fluid, and Energy pipes now show info tooltips (speed, transfer rate, fluid contents, items in transit) - **Pipes accept items from machines directly** — pipes now expose IItemHandler/IFluidHandler/IEnergyStorage capabilities so adjacent machines can push into the network ### 🔧 Improvements - Items now bounce back to sender when no valid destination is found - All pipe stats (speed, capacity, transfer rate) are now configurable via server config - JEI integration — info pages for all pipes, extractors, and inserters - Minimum NeoForge version bumped to 21.1.194 ### 🐛 Bug Fixes - **Fixed Z-fighting / texture flickering at pipe junctions** — inventory attachment model was incorrectly rendered on top of connector rings at every pipe-to-pipe connection - Fixed transparent gaps at pipe junctions — connector rings now have proper cap faces on all sides - Fixed dark seams at pipe junctions — added `noOcclusion()` and disabled ambient occlusion on pipe models - Fixed energy pipe junction rendering regression - Fixed fluid pipe crash (FluidPipeMessage) - Fixed wrong fluid texture in pipes - Fixed broken loot tables - Fixed FluidFilterSlot logic - Fixed FluidNetwork NBT saving

Fixed broken loot tables