0.10.0-alpha.1+26.2-fabric
Compatibility
Required content
Changes
0.10.0-alpha.1
This version comes with an absolute ton of internal changes, I don't expect anything to be majorly broken but a couple features haven't been extensively tested yet. As always please be sure to report any bugs you find!
New resourcepack features
- Block and fluid particle overrides can now be controlled fully with resourcepacks
- Resourcepacks can now create new particle types which can be used in particle overrides or other places
- There are now 'emitter rule' files present in resourcepacks that can be used to control which particles are emitted for certain actions, for example when using a flint and steel
- Proper documentation will come soon for resourcepack features! However feel free to poke around the mod files if you're curious how it all works
General changes
- Ported to Minecraft 26.2
- Old config files (from v0.9 only) are now updated automatically, you do not need to reset your config this time! yay!
- Falling blocks now emit particles based on the particle override when placed above non-solid blocks, this functionality is copied over from an older mod of mine (Better Falling Block Particles)
- Removed blaze damage particles, these may be added back in the future however they have been removed for now as I'm not happy with how they were implemented
- Changed the look of lava bucket placement particles to look more similar to lava surface bubble particles
- Reduced the duration of underwater bubble stream particles
- Removed some config options related to particle intensity as they were inconsistent with each other, this can now be controlled via resourcepacks instead (as mentioned above proper documentation coming soon)
- Sugar cane, mangrove root, and bamboo particles now float in water
Fixes
- Sprinting on snowy grass blocks now shows snow particles instead of grass #60 #34
Optional dependencies
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| eg_particle_interactions-0.10.0-alpha.1+26.2-fabric-sources.jar | Unknown | 523.62 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:xFCYuAs8:ME6dww5f"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:xFCYuAs8:ME6dww5f"
}


