Tags
Creators
Details
4.6.1
Compatibility
Changes
Fixed the game not shutting down properly, which caused errors to be written to the log files when quitting.
Bedrock 1.26.30 support!
- Implemented block break progress translation.
Please note: ViaFabricPlus 5.0.0 will most likely remove Bedrock Edition support ⚠️. Keeping it updated and ensuring it works correctly has become too much of a maintenance burden.
Minecraft 26.2 update changes
- Restored entity dimensions (collision boxes) to their previous values in versions 26.1 and earlier.
- This includes baby variants of most animals and hostile mobs.
- Fixed movement changes introduced by the restitute mechanic in versions 26.1 and earlier. (Thanks to @lowercasebtw and @Exterminate5573)
- This includes bouncing on beds, slime blocks, and slime entities.
- Fixed an error when older servers (prior to 1.14) spawn entities with an ID of
0in versions 26.1 and earlier. - Restored the previous hand-swinging behavior for bone meal and spawn eggs in versions 26.1 and earlier.
Other changes & fixes
- Fixed wolf entity data causing errors when joining servers in versions 1.8 and earlier.
- Improved the performance of item hashing in inventory click packets.
- Also fixed damage-resistant component hashing, which could cause inventory desyncs.
- Added a list of overriding JARs (located in
config/viafabricplus/jars) to the ViaVersion dump. - Updated various translations.
Translation contributors A list of all translators can be found here: https://crowdin.com/project/viafabricplus/activity-stream
Please also read the 4.6.0 changelog: https://github.com/ViaVersion/ViaFabricPlus/releases/tag/4.6.0
Your support means a lot! If you'd like to help keep the project going, consider donating at: https://florianreuth.de/donate
I'll continue improving 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:NVFW4VRx"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:rIC2XJV4:NVFW4VRx"
}

