All versions
1.3.1
Release
B'Quarry 1.3.122 hours ago 7
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Fabric
Supported environments
Client and server
Required content
Any compatible version
Any compatible version
Changes
1.3.1
Maintenance update focused on Quarry power consumption, Void Upgrade balance, digital storage reliability and several smaller consistency fixes.
Changed
- Rebalanced all three Void Upgrade tiers and their crafting recipes.
- Void I now focuses on Overworld ores and supports compatible modded ores through common Forge and Fabric tags.
- Void II now provides Nether resources and an exceptionally small chance of Ancient Debris. Its recipe now requires Ancient Debris.
- Void III has a higher Ancient Debris chance than Void II and a substantially more expensive endgame recipe.
Fixed
- Fixed the Quarry not consuming energy or fuel during regular and Void mining.
- Fixed mouse-wheel actions moving items between Digital Terminal slots and the player inventory.
- Fixed Digital Crafting Terminal recipe transfer failing to find ingredients stored on a different terminal page.
- Fixed digital storage insertion simulations reporting more available capacity than a nearly full cell actually had.
- Fixed Fabric digital storage transactions potentially committing a different item amount from the amount accepted by an automation system.
- Fixed Electric Pump upgrades disappearing when the machine was broken.
- Fixed Biological Simulator drops being able to target the Looting Upgrade slot.
- Fixed invalid Quarry model parents that generated missing-model warnings in Forge and Fabric logs.
Compatibility
- Existing 1.3.0 worlds, machines, storage cells and networks remain supported.
- Built for Minecraft Java 1.20.1 and Java 17 on Forge and Fabric.
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:M348KZVe"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:znjk0rfX:M348KZVe"
}

