0.1.1a
Compatibility
Changes
New Feature: Heat Captures While Pick Up Block
Blocks can now preserve heat state by capturing it into NBT before removal and restoring it after placement.
By implement ISHeatContainerBlock Interface:
captureHeatToStack(Level, BlockPos, ItemStack): call before breaking a block, writes heat particles into NBT.restoreHeatFromStack(Level, BlockPos, ItemStack): call after placing, reads and restores particles.
New Feature: Heat Source Buoyancy
Heat sources now emit particles with an inherent upward bias, making heat propagation more physically intuitive.
Fix: World Heat Data Persistence
World saves now persist the full heat simulation state across server restarts while setting clearParticlesOnSave to false.
Other Fixes:
- Block Placement Erasing Restored Heat Data
- Thermal Property 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:QLBL3rAZ:5mV3F56h"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:QLBL3rAZ:5mV3F56h"
}

