All versions
1.45
Release
Cryofloric Arts 1.4510 months ago 35
Compatibility
Minecraft: Java Edition
1.20.1
Platforms
Forge
NeoForge
Supported environments
Client and server
Changes
Update Log:
- Modified the rendering of Over-Rooting. It will now render the model directly instead of creating a new entity for rendering.
- Removed the rendering entity: Tuberous Root.
- Modified the Creative Mode inventory, adding some previously unimplemented items.
- Implemented Snow-Ornamented Farmland: Using a hoe on Frosted Dirt will now turn it into Snow-Ornamented Farmland.
- Added three new crops, which can be planted on Snow-Ornamented Farmland:
- Sweet Curling Grass: Has three growth stages. When harvested and consumed, it quickly restores health, grants the Frost Powder effect, consumes 8 hunger points, and increases saturation by 4.8.
- Salt Crystal Bean: Has five growth stages. While growing, it fertilizes nearby fertilizable blocks. The item can also be crafted into Salted Mashed Beans, which can be used for fertilization.
- Winter Thorn: Has three growth stages. When consumed, it increases hunger by 12 points but decreases saturation by 3.6. It also applies the Frost Powder and Frosted effects.
- Modified the texture for the Blindfrost Beast Egg.
- Added Frost Grass: Mining it has a chance to drop seeds for the three new crops.
- Modified the Transformation Sac. It now has a 75% chance to transform into Frost Grass, 15% into Dryas Ice Petal, 10% into Frostsore Grass, and 5% into Blight-Sorrow Sapling.
- Fixed a bug where the Surge Frost Dust Generator could be transformed into Powder Snow.
- Added the Frost Dust Block. It can be used in machines within the mod that consume Frost Dust to generate energy. Its burn time is 9 times that of Frost Dust and requires Frost Dust to craft.
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:jVtKrVHq:WrePTImE"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:jVtKrVHq:WrePTImE"
}

