Tags
Creators
Details
1.9.1
Compatibility
Required content
Changes
Note: Despite the networking changes in this release Forge 1.20.1 is still not fully client sided, however, progress has been made and may be fixed in the next update or so
Additions
- Added a snowflake effect for freezing mobs/players
- Added wiki link to ModMenu menu
Changes
- The particle and sound registries are no longer synced from server to client. This should allow all clients to join a server with the mod installed whether the client has the mod or not. There is a server config to disable this functionality in case something breaks
- NeoForge now properly checks if the packet channel exists on the client before sending packets
- Particles using the 'custom' render type are no longer culled. This specifically is to fix the elder guardian effect being culled when it shouldn't
- Improvements to sparks spawning around lava
- Lava cauldrons now play ambient sounds and pop vanilla lava sparks
- Replaced the powder snow snowflakes
- Improvements to thrown egg sounds
- Config is now a volume slider rather than a toggle
- The pitch is now somewhat randomized
Fixes
- Fixed item rarity particles crash with Item Borders support (#64)
- Fixed drowning bubbles spawning too much (#65)
- Fixed composter particles sometimes crashing with other mods (#66)
- Fixed entity effects not being affected if the tick rate is frozen (#67)
- Fixed mob skull shaders sometimes not applying correctly
- Fixed vanilla XP bottle effects not appearing for clients without the mod installed on servers with the mod
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:4q8UOK1d:twYIcSzO"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:4q8UOK1d:twYIcSzO"
}

