Links
Tags
Creators
Details
Licensed MIT
Published last year
Updated last month
All versions
1.3.6
Release
FastPipes 1.3.63 months ago 12
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Changes
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.
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:vLNEmWij:kJVcBGxb"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:vLNEmWij:kJVcBGxb"
}

