All versions
mc1.20.3-0.5.6
Release
Sodium 0.5.62 years ago 40.5K
Compatibility
Minecraft: Java Edition
1.20.3–1.20.4
Platforms
Fabric
Quilt
Supported environments
Client-side
Changes
- Reverted back to the 20-byte vertex format, which fixes a number of lighting issues that were introduced with Sodium 0.5. (bug)
- This will cause a slight performance regression, but there is no way to fix the bugs without accepting this.
- The resource pack compatibility scanner has been improved significantly. (commit)
- Resource pack authors can now silence certain warnings if they know the compatibility warnings are incorrect. (pr)
- A compatibility report is now written to the game's log file with more information about the problems.
- The compatibility checks for RivaTuner Statistics Server (RTSS) have been improved so that no crash will happen if a known compatible version is used. (bug)
- Older versions are still not supported, and a pop-up error will be shown if it is detected.
- Added support for using "fast clouds" with Sodium. (bug)
- Please note, using "fast clouds" does not actually improve performance, since our optimized code for cloud rendering is already fast enough.
- Improved compatibility with certain mods (i.e. Caxton) that have unusual vertex formats. (bug)
- Improved compatibility with mods that use custom ColorResolvers. (bug)
- Fixed an issue where other mods using special animated block rendering would not have their textures be animated. (pr)
- Fixed texture alignment problems and other block rendering issues caused by the use of very high-resolution texture packs.
- Added a pop-up message (with installation instructions) for when users attempt to double-click the Sodium JAR file. (code)
- The Video Settings screen now has better descriptions of each option and their performance impact. (change)
- Improved the UX for when the renderer config file is corrupt and can't be used.
- A toast message is shown at startup, and the user is now prompted to reset the config file back to defaults when opening the Video Settings screen.
- Fixed a warning message which could appear when compiling terrain shaders. (pr)
- Fixed a number of problems which caused incorrect rendering between certain render regions. (bug)
- Fixed a problem where the block shape culling cache would always generate a cache-miss after it had exceeded a certain size.
- Fixed some block face culling problems that were caused by hureistics which were too aggressive.
- Added a donation nag screen that appears after a few days have passed after installation.
- This can be disabled permanently by changing the config option
notifications.force_disable_donation_promptstofalse.
- This can be disabled permanently by changing the config option
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:xNJ0Mpbx"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:AANobbMI:xNJ0Mpbx"
}

