Tags
Creators
Details
0.5
Compatibility
Required content
Changes
Particle Interactions v0.5
This update includes some texture changes, new particle effects and block particle overrides, and some bug fixes and additional performance config options
! IMPORTANT ! : If you are updating from an older version, you may have to reset the config for some of the new features to work properly!
This version will not be backported to older minecraft versions
New Block Particle Overrides
The Biome Leaf override has been removed and replaced with the Pine Leaf and Generic Leaf overrides, which have new textures
- Pine Leaf (applies to birch leaves and spruce leaves by default)
- Generic Leaf (applies to oak, dark oak, mangrove, acacia, and jungle leaves by default)
- Redstone Dust (applies to redstone, redstone blocks, repeaters, comparators, and redstone torches by default)
- Block Shatter (applies to nether portals by default)
Graphical Changes
- The texture for the Snowflake block particle override has been updated
- Grass Blade, Heavy Grass Blade, Pine Leaf, and Generic Leaf block particle overrides are now tinted with a random colour from the block texture (this also takes the biome colour into account), instead of an average colour
- Sparks now spawn a small steam and play a fizzle sound when entering water
New Particles
Block Interactions
- Falling blocks now emit particles while falling and when landing
- Some redstone components (including comparators, repeaters, and redstone dust) now emit red dust particles when interacted with
Block Ambient
- Fire and campfires now emit small ember particles in addition to spark particles
Config changes
- Added a few more performance options to disable some particles from spawning extra particles (such as spark flashes)
- Added an option to collapse lists in the config menu by default
Fixes
- Leaf and grass blade particles will now always stop spinning when they have landed
- Leaf and grass blade particles now have a limit to how fast they can spin, and will spin slightly slower on average
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:xFCYuAs8:aWXpFfcN"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:xFCYuAs8:aWXpFfcN"
}

