Tags
Creators
Details
4.4.4
Compatibility
Changes
Fixes a few error handling regressions introduced in 4.4.3.
4.4.3 Changelog
- Added a new
/viafabricplus settingscommand to open the settings menu in-game. (Thanks @lowercasebtw)- Fixed a passenger glitch on horses and other vehicle entities in versions 1.21.7 and earlier.
- Fixed invalid commands not being executed in chat click events in versions 1.21.5 and earlier.
- Fixed bucket variant type lore in versions 1.21.4 and earlier.
- Fixed food item translations in versions 1.21 and earlier. (Thanks @RaphiMC)
- Fixed attack animation rendering in versions 1.8 and earlier. (Thanks @lowercasebtw)
- Fixed chunk borders not being visible when Sodium is installed in versions 1.8 and earlier. (Thanks @lowercasebtw)
- Fixed mouse click interactions in inventories in versions 1.5.2 and earlier. (Thanks @lowercasebtw)
- Fixed HUD armor and heart position offsets in versions Beta 1.7.3 and earlier. (Thanks @lowercasebtw)
- Fixed potentially incorrect block entity ID mappings.
- Fixed potential errors with custom or duplicate registry entries.
- Fixed optimized default values not being applied to ViaVersion configuration files.
- Fixed potential loading conflicts with other mods.
There have also been some internal changes:
- ViaVersion’s Server & Player Details Protocol has been implemented. By default, only the Server Details Protocol is enabled. Both protocols can be toggled in the
viaversion.ymlfile using thesend-server-detailsandsend-player-detailsconfiguration options.- ViaFabricPlus now always injects itself (and its Netty handlers used for protocol translation), even when the native client version is selected. Mods accessing the API can now always assume a valid user connection is present during multiplayer connections.
Translation contributors A list of all translators can be found here: https://crowdin.com/project/viafabricplus/activity-stream
Please also read the 4.4.2 Changelogs.
Thanks to @lowercasebtw for their contributions in this release.
Your support means a lot! If you'd like to help keep the project going, consider donating at https://florianmichael.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:FjnISfnJ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:rIC2XJV4:FjnISfnJ"
}

