Tags
Creators
Details
All versions
mc1.20.2-0.5.4
Release
Sodium 0.5.43 years ago 38.4K
Compatibility
Minecraft: Java Edition
1.20.2
Platforms
Fabric
Quilt
Supported environments
Client-side
Changes
Highlights
- Slightly improved the performance of immediate-mode rendering (anything which is not terrain) by enabling general optimizations for all parts of the game code and other mods.
- The existing optimizations for entity rendering have been further improved, increasing frame rates by up to 7-10% in busy worlds.
- The automatic detection of graphics driver bugs and software incompatibilities has been improved.
- The game will now crash when Rivatuner Statistics Server (RTSS) is detected, in order to prevent the user's hard drive from being filled up with errors.
- Resource packs which attempt to load incompatible "core shaders" now show a warning.
Misc changes:.
- Fixed a bug where interacting with blocks in a debug world would result in the incorrect visual state being shown.
- Fixed some problems where chunks would not be rendered in the correct order when standing at the extreme extent of a render region.
- Fixed a bug where the client would get stuck at "Loading terrain..." for a very long time when the player's eyes and feet were in different chunks.
- Fixed a problem where animated textures would become de-synchronized with one another, due to texture updates being skipped for not-visible blocks.
- Fixed animated texture interpolation with mods that use unusual texture sizes.
- Improved compatibility with mods that replace the ColorProvider implementation of vanilla blocks.
- Improved compatibility with mods that specify a block entity renderer on "air" blocks. (Please stop doing this.)
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:AANobbMI:lhZYeXLf"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:AANobbMI:lhZYeXLf"
}

