Tags
Creators
Details
4-alpha.2+1.21.1-neoforge
Compatibility
Required content
Changes
complete rewrite! i hope this publishes correctly! This is an alpha version, and will be rough around the edges. Please report any bugs you find. The final v4 release will have many more changes and additions.
New command:
/particlerainto quickly get to the config screen
Mod support:
- support for minecraft 1.20.1, 1.21.1, 1.21.4, 1.21.5, 1.21.6, 1.21.7
- support for neoforge in addition to fabric
- support for forge (1.20.1 only)
- weather effects are less destructively replaced, sort of, allowing for better mod compatibility, in theory, sort of, perhaps.
Custom particles:
- customise any particle
- create new particles
- whitelist or blacklist biomes and blocks for particle spawning
- assign a custom tint or use the fog, water, or map color
- choose which textures are used
- choose whether the particle is translucent, opaque, or blended
- choose how the particle rotates
Effect improvements:
- fog effect, now called haze, has been made translucent and less dense, and is enabled by default
- rain is now more realistic, angled relative to your movement, appearing to point towards you when moving at high speeds
- particles scale down when hitting a block to reduce clipping through surfaces and ceilings
- particles fade by distance instead of a set animation, looking more consistent when moving around
- wind now varies by coordinates and shifts over time
Spawning improvements:
- particle density scales by speed to be more visually constant while moving quickly
- particles now only spawn above the player unless moving quickly (eg: falling or flying)
- cloud height particle spawn limit is fetched automatically
- splash particles now use the particle render distance
Mist (formerly ground fog), streaks, shrubs, ripples, and sound effects have not been ported from their v3 versions yet and are currently unconfigurable or missing.
Optional dependencies
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:mhruDX1E"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:nrikgvxm:mhruDX1E"
}

