Links
Tags
Creators
Details
4.0.0+26.1.2
Compatibility
Required content
Changes
Hello everyone!
This release is the last release made from github.com. From now on, all further development will be on codeberg.org. In the short term, the GitHub repo will be archived and made read only, until the end of the year. Afterwards, it will be deleted.
I am happy to announce that Lighty for Minecraft 26.1.2 is now available, with the following changes:
- Internal changes w.r.t. Overlay rendering. As a result, we have:
- More performant Overlay Rendering
- Restored Iris/Shader support!
- The pixelated Cross Mode is back, replacing the clean line Cross Mode (because of current technical limitations)
- The overlay is now displayed across the entire render distance. In testing, enabling/disabling the overlay may cause short (<=500ms) game stutters when playing on a Minecraft Render Distance of 32 chunks. Afterwards, there is almost no noticeable performance difference between having the Overlay enabled or not (worst case observed on my hardware was ~30fps). Using sodium, the stutters on Overlay toggle are well reduced, and overall rendering performance increases.
- Overall Lighty code complexity has been reduced. Hopefully less stuff will break from now on, so that I can focus more on new features and improvements!
- Switched to a new MultiLoader Template in response to big build-system changes.
I want to thank everyone who took the time and contributed code, issues, and discussions to Lighty on GitHub. Your contributions are highly appreciated, and maybe we'll meet again over on codeberg.
Additionally, the SchmarrnDevs Discord server has been closed. Further communication will take place over codeberg issues.
Of course, releases will still be made available on Modrinth and Curseforge.
Special thanks to Sophie, without whom I'd have never discovered this alternate way of rendering the overlay.
Thanks for everything, see you on codeberg, and have fun!
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:yjvKidNM:Gn1RUlvZ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:yjvKidNM:Gn1RUlvZ"
}

