Tags
Creators
Details
3.4.4
Compatibility
Changes
Minecraft 1.21.1 support!
The mod can be runned on both 1.21 and 1.21.1 as there are no relevant protocol or game changes.
Added remaining 1.21 -> 1.20.6 changes
- Restore knowledge book interaction behaviour
- Restore interactions with lead item
- Restore milk bucket interaction behaviour
- Add setting to hide download terrain screen transition effects (@NekosAreKawaii)
ViaVersion 5.0.3
Updates the internal protocol translation and fixes various issues
- Fixed handling of custom armor trim patterns and materials in <= 1.20.3
- Fixed erronous area effect cloud particle handling in <= 1.20.2
- Fixed an edge case with custom item frame rotation handling in <= 1.16.4
ViaBedrock update
Server auth movement works and many other features got implemented
Other changes
- Fixed strikethrough effect displayed wrongly in <= 1.12.2 (@lowercasebtw)
- Restore old swing/interaction behaviour with items in <= 1.8
- Fixes animations to be slower than in original clients for sword, bow and other items
- Fixed bedrock version not working on some servers due to RakNet compatibility issues (@RaphiMC)
- Add setting to restore old game menu screen layouts and/or to hide "Player reporting"
- Fixed armor bar being displayed wrong with hud modifications in <= b1.7.3
- Fixed arm with shield following third person rotation in <= 1.20.2 (@lowercasebtw)
- Updated polish translations (@Blayung)
- Updated simplified chinese translations (@Andypsl8)
- Save scroll states in important slot list screens
- Fixed "login" translations not being applied in classicube screens
- Move scrollbar in various screens next to entries (previously at the right side of the screen)
If you want to help me out financially, consider sponsoring at https://florianmichael.de/donate.
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:rIC2XJV4:pGX8JE4z"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:rIC2XJV4:pGX8JE4z"
}

