Tags
Creators
Details
mc1.21.1-0.8.12-neoforge
Compatibility
Changes
Overview
Sodium 0.8.12 is a backport of modern Sodium 0.8 to Minecraft 1.21.1.
- Significantly improved the performance of rendering the world (up to +115%) on some computers.
- Greatly improved the rendering of transparent objects with complex models, especially when submerged in water.
- Lots and lots of improvements to the user experience in the Video Settings menu.
- Reduced latency and micro-stutter when updating chunks in the world.
- Slightly faster entity rendering, especially for transparent mobs and particles.
- Improvements for hardware and mod compatibility.
- ...And many more bug fixes and improvements...
Using and Building on This Release
It includes the backport of our Config API and other conventions that will hopefully make it easier for mods to interact with Sodium across multiple versions. This release series doesn't get released at the same cadence as our current releases for Minecraft 26.2 and 26.1, and doesn't follow the same alpha/beta numbering. Mod developers can find our artifacts, such as the Config API, on our Maven repository.
Mod compatibility:
- Create Aeronautics works as of 1.3.0
- Sable works as of 2.0.0
- Veil works as of 4.1.2
- Iris works as of 1.8.13
- Not compatible with any version of "Sodium Options API", which is not affiliated with us, and any mods that depend on it.
Some other mods may still be incompatible with this release. If your modpack doesn't work with this release, downgrade to the version of Sodium it was built with and choose appropriate versions of other mods. New or updated modpacks are encouraged to use the latest version of Sodium and compatible mods.
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:S3DUMfBo"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:AANobbMI:S3DUMfBo"
}

