All versions
1.1.0
Release
1.1.0 for Fabric 1.20.13 months ago 210
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Fabric
Supported environments
Client and server
Changes
- Recipe Pipes now support Tag Labels. (#18)
- When a Tag Label is used, recipes that can take any item from a tag will now search the network for any matching item in the tag.
- Tag Labels will automatically be inserted into a Recipe Pipe's crafting grid when using the + button in JEI.
- Tag Labels now render the items they represent when they are placed into the Recipe Pipe crafting grid.
- For technical reasons, labels are now invisible to the network; store them separately!
- Add Inverted Copper Pipes. (#17)
- These are like Copper Pipes but have inverted redstone behaviour.
- Advanced and Fluid variants also available.
- Add Nether Brick Pipe.
- Attaches to containers and Wooden Pipes, but not to any kind of special pipe.
- Minor changes.
- Items being delivered by Request Pipes no longer have a pickup delay and are ejected at a lower velocity.
- Items in a network that cannot be routed are now ejected from the network rather than distributed arbitrarily.
- Bug fixes and compatibility
- (1.20.1 only) Add Recipe Pipe support for Quark's Crafter backport. (#4)
- Fix Stocking Pipes over-sending to a lot of modded blocks. (#12)
- Improve compatibility between pipes and vanilla-like containers that don't use the item transfer APIs provided by mod loaders. (#33)
- (1.21.11 NeoForge only) Fix dupe bug involving Tom's Simple Storage and other mods. (#48)
- Fix blocking mode not working. (#57)
- Fix request menu search bar not matching characters outside the English Latin alphabet. (#58)
- Fix items getting stuck forever in default route Storage Pipes attached to full containers.
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:xX5VOqpH:mLexeLx2"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:xX5VOqpH:mLexeLx2"
}

