All versions
1.7.3
Release
1.7.3last week 53
Compatibility
Minecraft: Java Edition
1.7.10
Platform
Forge
Supported environments
Client and server
Required content
Unavailable version
Any compatible version
Unavailable version
Changes
BOP Integrations - 1.7.3
What is changed?
Change version number from previous to 1.7.3
➕Add:
- Document the honey mechanics feature in the README: hot-block melting, cauldron melting and jar collection, and the redesigned crystallization (world air-exposure plus cauldron heat-removal crystallization that re-melts when heated, no overheat crystallization). Design source: song682/bop-integration-catifized#31.
- Redesign honey crystallization around the cauldron. Remove the overheat solidification path for world liquid honey (Nether honey never re-crystallizes from heat) while keeping air-exposure crystallization. Honey cauldrons now crystallize their liquid contents into a solid honey block once the heat source is removed (faster when open to air, slower when covered) and re-melt when heated again, preserving the fill level via a new solid metadata bit (bit 3) exposed as a CatFrame blockstate property. Add cauldron tracking and normalized cooling progress in EventHoneyMechanics, decode level/solid in jar collection and honey-block melting, add cauldronCrystallizeOpenTime/CoveredTime config (drop crystallizeHotTime), and wire the sorted level+solid blockstate variants to the three new solid cauldron models.
🔧Fix:
- fix gradle
- fix details
- Move thaumcraft compat classes into content.thaumcraft and remove the unused WorldGenNothing generator; rework honey cauldron models to reuse the vanilla empty cauldron model and reindent to 4 spaces; parameterize the CatFrame dependency via cf_version and update the Forge maven URL; fix README mod-name typos, the mixin plugin javadoc link, and the editorconfig JSON indent. Honey crystallization logic is left untouched.
❗❗❗Deprecated:
- No deprecations
Notes
Full Changelog: https://github.com/song682/bop-integration-catifized/commits/v1.7.3
Supplementary resources
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:sxEMw8VW:EvR63QtP"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:sxEMw8VW:EvR63QtP"
}

