Tags
Creators
Details
5.7.0
Compatibility
Changes
A bunch of config changes and a few fixes!
- Moved and renamed logging related config options under a new
loggingsection- Added
max-error-lengthto reduce or increase information in ViaVersion errors - Includes
log-blocked-joins,log-entity-data-errors,log-text-component-conversion-errors,log-other-conversion-warningsandmax-error-length log-text-component-conversion-errorsandlog-other-conversion-warningshave been disabled by default and will not be migrated from their previous values
- Added
packet-limiterconfig options will be automigrated to higher values if you still had lower defaults from previous versions- Added
migrate-default-config-changesconfig option to allow disabling such migration of defaults (though we highly recommend keeping this enabled unless you go through every changelog and manually adapt your config with changes) - Fixed packet limiter tracking if packet size tracking was disabled (by EnZaXD)
- Fixed errors when loading config files with poorly auto-placed line breaks
- Fixed occasional item desyncs in merchant inventories in 1.21.5+
- Fixed world border lerping in 1.21.9->1.21.11 (by MrKinau)
- Fixed atlas sprite paths paths in 1.21.9->1.21.11
- Fixed dripstone lava particles in 1.21.9->1.21.11 (by riku6460)
- Fixed error if a creative client tried interacting with a spear ghost item in 1.21.9->1.21.11 (by booky10)
- Fixed handling of
block_state_propertyenchantment terms in custom enchantments - Fixed mossy wall block connections in 1.12->1.13 (by lowercasebtw)
- Added
use-1_8-hitbox-marginconfig option to use new 1.21.11 item components for weapon hitbox changes (enabled by default, by roccodev) - Added step height and interaction range entity attributes for 1.20.5+ clients on 1.8 servers (by RK_01)
- Fixed lit_furnace item display in 1.8->1.9 (by EnZaXD)
If you want to get larger version updates early, consider supporting me via https://viaversion.com/donate. See the previous update notes for more info.
Optional dependencies
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:P1OZGk5p:EZj8sFTH"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:P1OZGk5p:EZj8sFTH"
}



