Tags
Creators
Details
Licensed MIT
Published 5 years ago
Updated 2 days ago
All versions
v4.0.4+26.2-fabric
Release
v4.0.4 for 26.2-fabric2 days ago 2,988
Compatibility
Minecraft: Java Edition
26.2
Platform
Fabric
Supported environments
Client-side
Required content
Any compatible version
Changes
Compatibility update part 2. Improves support for: Sable (create aeronautics), Puddles & Floods, Iris, Rain Shield, Ecliptic Seasons, and potentially others
- updated neoforge support for 1.21.9+
- particles with the block spawn type can now spawn on block faces that are facing a collisionless block if said block is in the blocks list
- ripples now spawn on the puddles from Puddles & Floods
- rain and heavy rain now fade in and out with the intensity level of their respective weather types
- weather particles now respect rain shield's weather cancellation
- fixed sable sub-levels taking control of weather particle velocity, causing particles to get stuck on sub-levels
- fixed collision animation
- playing twice as fast due to duplicate method call
- causing jittering by not interpolating due to old size being updated at the wrong time
- fixed heavy rain sometimes appearing during the transition to or from clear weather due to weird vanilla mechanics
- fixed density dropping drastically during movement due to density movement multiplier only updating in intervals
- fixed 'Don't tint water particles when using shaderpack' compat option not applying to vanilla particles
- fixed long config text inputs becoming cut off when opening the gui due to the max length being set too late
- fixed default rain rendering while disabled in versions below mc21.1 when ecliptic seasons is installed
Optional dependencies
Any compatible version
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:nrikgvxm:lqhJvBjN"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:nrikgvxm:lqhJvBjN"
}

