Links
Creators
Details
Licensed MMPLv1
Published 4 years ago
Updated 2 years ago
All versions
7.1.9
Release
7.1.92 years ago 5,062
Compatibility
Minecraft: Java Edition
1.7.10
Platform
Forge
Supported environments
Client and server
Required content
Unavailable version
Changes
This version requires BuildCraft 7.1.26 or later.
Additions:
- [BuildCraft/#4709] Builder rotation support for the Apiarist's Pipe.
- Apiarist's Pipe GUI improvements, by Thibaut Fagart:
- Make clicking through the list of bee filters and species work like clicking through gate triggers/actions:
- Shift-clicking clears the selected filter.
- Left-clicking advances the selection forward.
- Right-clicking moves the selection backward.
- Added support for NEI drag-and-drop to the bee species filter.
- Make clicking through the list of bee filters and species work like clicking through gate triggers/actions:
- Enabled the incomplete Project: Red bundled redstone support from ten years ago.
- Pipe Gates can now use triggers and actions to react to P:Red bundled cables.
- Project: Red does not have the restriction on only allowing connecting freestanding wires to pipes. It's unlikely the upstream mod is going to have the necessary APIs exposed cleanly at this point.
- ... Wait, it's been ten years?
- Pipe Gates can now connect to bundled emitters/receivers directly, without a cable placed in between.
- To match Project: Red support restrictions, added a config option to allow connecting non-freestanding wires to pipes in RedLogic and BluePower as well.
- Added a config option to allow connecting wires to gates.
Bugs fixed:
- [#99] Fixed MineTweaker /mt reload error when adding Refinery recipe
- Fixed the "Bundled Redstone Inactive" trigger not working correctly.
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:yp1R2apI:7gHdRW4A"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:yp1R2apI:7gHdRW4A"
}

