Tags
Creators
Details
4.1.2
Compatibility
Changes
This release marks the first stable build of ViaFabricPlus for Minecraft 1.21.5
Added support for joining 25w14craftmine servers
Other changes (mainly addressing gameplay and movement-related issues)
- Fixed velocity calculation issues in versions <= 1.21.4 that caused movement desynchronization
- Fixed movement desyncs when inside boats in versions <= 1.21
- Fixed incorrect sprint-sneak movement offsets in older versions
- Fixed various text component-related errors and disconnects in versions <= 1.21.4
- Fixed show_item chat conversion for shulker boxes in versions <= 1.21.4
- Fixed disconnects and kicks when interacting with (glowing) item frames and other block entities in versions <= 1.20.3
- Also fixed tooltips (e.g., spawners) not rendering correctly in some cases
- Fixed invalid advancement tab background in versions <= 1.21.4
- Fixed command-click chat actions not working in versions <= 1.21.4
- Fixed sneaking desyncs when soft-colliding with blocks in versions <= 1.17.1 (Thanks @ManInMyVan)
- Fixed rare edge case where entity position updates were incorrectly interpolated in versions <= 1.16.5
- Fixed sneaking while flying, inside blocks, and in vehicles not working since version 4.1.0 in versions <= 1.13.2
- Improved mod compatibility with mods that alter chat length
- Fixed a regression causing mod incompatibilities with clientcommands and mods that interact with entity ticking
- Improved compatibility with affected mods, which were previously broken silently by ViaFabricPlus (Thanks @wagyourtail)
Special thanks to @lowercasebtw and others for their help in debugging!
Please read the v4.1.1 Changelogs as well
I deeply appreciate any financial support at https://florianmichael.de/donate and will continue working on this project to the best of my ability.
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:3qZVBjMD"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:rIC2XJV4:3qZVBjMD"
}

