Links
Creators
Details
Licensed Depends on version
Published 4 years ago
Updated last year
All versions
7.99.17
Alpha
7.99.17last year 45
Compatibility
Minecraft: Java Edition
1.12.2
Platform
Forge
Supported environments
Client and server
Required content
Changes
Improvements:
- [#4135] Made Heat Exchanger process arbitrary amounts of fluid.
Ported content:
- (Most) items now show multiple items per stack when travelling in a pipe if the stack had more than a single item.
- [#4080] Re-added the config option to change the rate of oil well generation and generation of a spout.
- [#4149] Ported the paintbrush recipe.
Bug fixes:
- Fixed all item pipes having an implict speedup. (Most buildcraft item pipes explicitly do this, so this doesn't really affect normal builds).
- Fix cobblestone item pipes sending items about 4 times as fast as they should.
- Fix stone item pipes not explicitly slowing down items
- Change sandstone item pipes to match stone item pipes.
- Fixed item pipes allowing multi-tile tickers to send items down pipes faster then normal
- This is primarily a fix for tickers that don't also speed up the client. (Also this sort of speedup behaviour probably won't work with potential future optimisations)
- Fixed chutes having a huge pull radius. Use powered obsidian pipes for that.
- [#3477] Only the wooden pipe attempts to always face a valid direction.
- (This only affects the iron pipe in buildcraft, however addon pipes that extend PipeBehaviourDirection but don't allow the centre will benefit from this).
- [#4014] Gate recipes in the assembly table don't check the NBT of the gate provided.
- [#4082] Fluids can no longer be mined by Mining Well
- [#4124] The direction of an iron pipe cannot be changed by clicking the centre unless the pipe is already facing a direction.
- [#4138] Dupe bugs everywhere with tiles and GUI's. No more details here, as it's an exploit.
- [#4141] The recipe for the pipe plug requires the quarry to exist, rather than the structure pipe.
- This is only a partial fix for the entire issue, which encompasses all recipe mismatches.
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:UU9bGx2s:VNtfhN21"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:UU9bGx2s:VNtfhN21"
}


