Tags
Creators
Details
All versions
1.21.5-2.5.0.0-beta
Beta
Icaria 1.21.5 2.5.0.0last year 112
Compatibility
Minecraft: Java Edition
1.21.5
Platform
NeoForge
Supported environments
Client and server
Changes
Update to Minecraft version 1.21.5.
Additions
- Suspicious Grainel and Suspicious Silksand
- Marl, Loam, Grainel and Silksand Path Blocks
- small Tree Variants for all Icaria Tree Types
- fallen Tree Variants for all Icaria Tree Types
- a grinding Recipe to grind Cactus Flowers into Pink Dye
- a grinding Recipe to grind Wildflowers into Yellow Dye
Updates
- updated Spawn Egg Textures to be in Line with vanilla Spawn Eggs
- updated Ground Flowers to be in Line with vanilla Petals and Wildflowers
- remodeled and renamed the Sow to Thog as well as all related Blocks and Items
- dead Tree Variant Features for Icaria Tree Types generate with a Chance for longer Variants now
- dead Tree Variant Features for Icaria Tree Types generate with a Chance for growing Tree Shrooms now
- Cypress, Droughtroot, Fir, Laurel, Olive, Plane and Populus Leaves drop fitting falling Leaves Particles now
- Icaria Farmland and Fertilized Farmland can be used to plant Dead Bush on to be in Line with vanilla Behavior
- carried Barrels and Loot Vases rotate with the Player now
- placing and mining a Storage Vase plays an updated Sound, no longer suggesting the Storage Vase broke into Pieces when mined
- the Chest Label Tooltip is restructured for better Readability now
Fixes
- Olive Trees sometimes generate with one or more Leaves Blocks missing
- Rays from Crystals and Mobs as well as thrown Spells no longer are visible through Blindness and Darkness Effects
- carried Barrels and Loot Vases no longer render their Faces shaded when said Face was oriented towards another Block before being picked up
Optional dependencies
Any compatible version
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:y6ptCp9V:S2of34tw"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:y6ptCp9V:S2of34tw"
}

