All versions
1.2.0
Release
B'Quarry 1.2.02 months ago 56
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Fabric
Supported environments
Client and server
Required content
Any compatible version
Any compatible version
Changes
First public release of the multiplatform B'Quarry rewrite for Minecraft 1.20.1.
Added
- Forge and Fabric support through Architectury.
- Forge Energy and Team Reborn Energy interoperability.
- Combustion, magmatic and solar generators.
- Modular multiblock energy cells and fluid tanks.
- Energy, item and fluid cable networks with wrench configuration.
- Reusable item filter tool with recipe-viewer drag-and-drop support.
- Electric Furnace, Electric Crusher, Industrial Washer, Industrial Press, Electric Pump and Automatic Assembler.
- JEI and EMI recipe integration.
- Machine side I/O configuration and automation support.
- Advancement progression covering machines, networks and Quarry upgrades.
- Dedicated machine speed, energy efficiency, generator power and fuel efficiency upgrades.
Changed
- Rebuilt the original Quarry code and interface for the shared multiplatform architecture.
- Standardized machine textures around a shared industrial chassis.
- Rebalanced generation, processing costs, internal buffers and network transfer rates.
- Renamed the old Quarry efficiency line to Drilling Upgrades to distinguish it from general-purpose machine upgrades.
- Energy cells and fluid tanks now combine into larger storage networks.
- Machine interfaces now show effective processing time, consumption and generation.
- Replaced the legacy project icon with the current industrial Quarry design.
Compatibility
- Existing development worlds remain supported, including legacy efficiency cards already installed in machines.
- Built specifically for Minecraft Java 1.20.1 and Java 17.
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:znjk0rfX:xULorMg2"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:znjk0rfX:xULorMg2"
}

