Links
Tags
Creators
Details
All versions
v0.9.5-1.19.2
Release
Chika’s Plants Mod v0.9.5-1.19.23 months ago 33
Uploaded by
Compatibility
Minecraft: Java Edition
1.19.2
Platform
Forge
Supported environments
Client and server
Changes
Version v0.9.5-mc1.19.2 – 2026/05/23
Overview
This update adds new trees and related decorative blocks.
- Added new tree species alongside flowers and plants
- Expanded plant usage with drinks and related items
- Added planter support for blocks with AGE/properties (unstable behavior such as growth stopping midway is intentional)
Added
- Added 7 new tree species (camellia, lemon, fragrant olive, ginkgo, maple, paulownia, and ume) (crafting only / no world generation)
- Added building blocks and planters for ume, paulownia, and chestnut wood
- Added 5 types of hedges (camellia, fragrant olive, Japanese spindle, red robin, and ukogi)
- Added 8 drinks (lemonade, apple juice, vegetable juice, sweet berry juice, green tea, oolong tea, black tea, and chamomile tea)
- Added intermediate materials such as tea leaves
- Added podzol flowerbed soil blocks and slab variants
- Added new flower pot color variants (blue medium pot, blue large flower pot, and green lotus pot)
Fixed
- Fixed a spelling mistake in the skunk cabbage texture (texture now displays correctly)
Changed
- Changed tooltip naming conventions (internal change)
- Renamed flower pots and updated recipes due to the addition of color variants
- Partially changed compatibility handling for plants from other mods (replaced dummy block conversion with acceptance tag checks)
Notes
- Future updates are planned to add more gardening decorations and small props
- Please feel free to share any bug reports or feedback!
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:BkSEUbhu:OMIsXCtz"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:BkSEUbhu:OMIsXCtz"
}

