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