Links
Tags
Creators
Details
1.0.1
Compatibility
Required content
Changes
LumaClear 1.0.1 — Minecraft 26.3
Compatibility
- Updated for Minecraft 26.3, Fabric and Java 25.
- Requires Fabric API 0.166.0 or newer for Minecraft 26.3.
- Sodium remains optional. Real mixin checks passed without Sodium and with Sodium 0.9.2, 0.9.3-beta.1 and 0.9.3-beta.4.
Lighting and rendering
- Skip unused terrain block/sky-light samples during fullbright while preserving ambient occlusion, directional shading and biome tinting.
- Avoid terrain rebuilds triggered only by lighting updates that cannot change fullbright rendering. Block and geometry changes still rebuild normally; fullbright transitions rebuild terrain to restore baked lighting.
- Keep world/server lighting updates active. The new sampling and light-only rebuild shortcuts fall back to normal behavior when Iris is installed.
- Fix Sodium's fullbright shader integration and reuse bounded shader pipeline variants across settings changes.
- Correct directional-shading hooks across vanilla blocks/fluids, Fabric Indigo and Sodium while retaining ambient occlusion.
- Make individual fog switches independent and prevent fog-only settings changes from rebuilding chunk geometry.
- Fix keyboard preset selection with Enter/Space and reverse cycling with Shift.
Validation and performance
Build, 27 unit tests, four real mixin smoke configurations and eight offline shader combinations passed. The full six-configuration laptop benchmark completed 150/150 valid iterations with zero MineBench warnings; all 2,881,650 frame intervals were independently verified.
On the Adreno X1-85 laptop at 1840×1150 with AO enabled, the mean of five scene-level median FPS values was 410.8 for Sodium, 401.2 for LumaClear Fullbright and 345.1 for LumaClear Clarity. Excluding Nether, Clarity measured 363.2 versus Sodium's 359.6. Sodium controls varied 3.58%, so small differences do not establish a gain or regression. Clearing Nether fog increases the visible terrain workload. These results do not demonstrate a large steady-FPS speedup and are not universal FPS expectations.
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:mYlSYblw:UHlYyahA"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:mYlSYblw:UHlYyahA"
}

