
FirmaLifeHardCore
A mod that completely overhauls Firmalife's cellar and greenhouse mechanics — no Climate Station required. Enclosed spaces are auto-detected via BFS floodfill with dynamic AABB tracking. Any insulating blocks form a functional cellar or greenhouse.
Links
Tags
Creators
Details
0.3.3-beta
Compatibility
Required content
Changes
0.3.3-beta
Fixes
- Cheese wheels can now actually age:
LargePlanterBlockEntity.setValidcomputesshouldAge = valid && climate == ClimateType.CELLARin one pass, so the last broadcast wins. We broadcast both greenhouse and cellar, and cellar came first — the later greenhouse broadcast then recomputedshouldAgeasfalseand stomped the valid cellar state, so wheels never started aging. Vanilla Firmalife only ever sends one climate type per receiver, so this never surfaced there (its plantersetValideven branches onif (climate == ClimateType.GREENHOUSE)first — the bug was our broadcasting order, not the receiver).broadcastToContainersnow sends greenhouse first, cellar last, so the final broadcast the wheel receives is the cellar one.
0.3.2-beta
Fixes
- Reinforced soil beams are now shovel-mineable: the 8 beam variants were missing from
mineable/shovel. Combined withrequiresCorrectToolForDrops(), no tool ever counted as correct, so beams dropped nothing when mined. Now they drop the regular reinforced soil, as intended. - Reinforced soils now count as TFC insulation: added all 16 variants to
tfc:insulation(append,replace: false). Charcoal forge and bloomery multiblocks accept them as valid insulation walls/bottom — consistent with their medium (0.55) thermal resistance in the cellar/greenhouse system, and with real rammed-earth insulation.
Optional dependencies
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:diur6Jqx:8Fm90XRM"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:diur6Jqx:8Fm90XRM"
}
