All versions
1.1.1+0.8.4-mc1.21.11-fabric
Release
[Fabric] v1.1.1 for mc 1.21.115 months ago 5,669
Compatibility
Minecraft: Java Edition
1.21.11
Platform
Fabric
Supported environments
Client-side
Required content
Any compatible version
Any compatible version
Changes
1.1.0
New features
- Updated to support Sodium 0.8.3
- Changed tooltips in the video settings screen to ensure they don't overflow outside the screen
- Added tr_tr translations (thanks to Arcdashckr on GitHub!)
- Added a 'Shaderpacks' button in the top right of the video settings screen when Iris is installed
Changes
- The mod's version number now includes the target Sodium version
- For example
1.1.0+0.8.3-mc1.21.11is ESO v1.1.0, for Sodium v0.8.3 and Minecraft 1.21.11
- For example
- Option values are now displayed in tooltips
- Addresses some issues where it was difficult to tell what the value of an option was if its text was too long
- Using the arrows keys on sliders now changes the value by 1 step instead of moving the handle by 1 pixel to match the behavior of vanillas video settings screen
- Version numbers are now truncated in the video settings screen, hovering over it shows the full version
Fixes
- Fixed some mods appearing in the video settings screen despite having no options. This happened when a mod registered an option overlay but no other options with Sodiums config api
- The 'Back' button can now always be pressed in sub-menus in the video settings screen
1.1.1
- Allow the mod to load on Sodium 0.8.4
Optional dependencies
Any compatible version
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| enchanteds_sodium_options-1.1.1+0.8.4-mc1.21.11-fabric-sources.jar | Unknown | 63.16 KiB |
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:bd7qKEEC:9lCV5s7X"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:bd7qKEEC:9lCV5s7X"
}

