Tags
Creators
Details
Licensed ARR
Published 5 months ago
Updated 5 days ago
All versions
2.2.0-fabric+26.1.2
Release
MC2 - Interactive Foliage 2.2.0 Fabric 26.1.22 weeks ago 474
Uploaded by
Compatibility
Minecraft: Java Edition
26.1.x
Platform
Fabric
Supported environments
Client-side
Required content
Any compatible version
Any compatible version
Changes
2.2.0 INTERACTIVE FOLIAGE - Update

Added
- VulkanMod support (Fabric 1.21.1, 1.21.11 and 26.1.2)
- Beryl support: foliage lit and shadowed like the terrain (same versions)
- Sable support (1.21.1): foliage on sub-levels (felled trees, ships) is drawn by the GPU renderer
- Interaction with entities on sub-levels
- Sable's dynamic shading
- Works with Sodium and shader packs
- Gravity, inertia and rebound: foliage hangs toward the real ground, lags behind a moving sub-level and bounces when it stops
- Rain wind follows the sub-level's orientation
- cbbg (Color Banding Be Gone) compat
- Plants added by backport mods under vanilla ids now wave and interact
- LambDynamicLights is followed on every version
Fixed
- Crash when turning a shader pack off with 'cbbg' installed
- Light and block changes now show on the foliage on the same frame
- Stutter when many light changes hit the foliage at once
- Animated foliage textures stopped moving under Sodium
- Interaction was lost without shaders when Sable (Veil) was installed
- Layered plant models flickering at the same depth on 1.21.11
Soon
- More mods compatibility (Regions Unexplored, Oh The Biomes We've Gone, Sizeable Foliage, Vibrant Journeys, Cobblemon...)
- Chunks Fade In / Chunk Animator support
- Colorful Lighting
- Nvidium support
- Luxium support
karto
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| mc2_interactivefoliage-2.2.0-fabric+26.1.2-sources.jar | Unknown | 388.16 KiB |
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:ba5MV2CF:C4FGYRLR"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ba5MV2CF:C4FGYRLR"
}

