2.1.0-fabric-1.21.11
Compatibility
Changes
Fixes
- Fixed the block overlay rendering in Forge 1.20.1 and NeoForge 1.21.1.
- Fixed the projected flashlight overlay sticking to the screen instead of staying attached to the block faces in the world.
- Fixed the broken multiplayer visual cache that could make other players' flashlight lighting flash or rebuild too aggressively.
- Fixed the worst through-ground and through-water visual issues from the multiplayer lighting update.
- Rebuilt the current hotfix jars after the overlay/rendering corrections.
What Was Wrong
The multiplayer update made other players' flashlights visible, but it also exposed a rendering problem in the block overlay. The overlay was detecting the correct blocks, but some of the render code was mixing camera-space and world-space positions. That made the light look like it was sliding, wiggling, or following the screen instead of sticking to actual block faces.
This update keeps the special projected block overlay, but fixes the coordinate-space issue so the light behaves more like it did before while still supporting multiplayer-visible beams on the Forge and NeoForge builds.
Fabric Support Change
I am dropping routine support for separate Fabric jars from Minecraft 1.21.2 through 1.21.10. Maintaining a different jar for every small Minecraft patch version is too much for this mod right now, especially when most of those versions do not need individual releases.
Going forward, Fabric support will focus on the versions that actually matter most. If I can safely make one Fabric jar support multiple Minecraft versions, I would rather release that than upload a long list of nearly identical jars.
For now, Fabric does not have a confirmed one-jar solution across the full 1.21.x range that i know of i will keep researching. NeoForge/Forge-style version ranges can be easier to express in metadata, but Fabric still needs more testing before I claim one jar works from 1.21.1 through 1.21.11.
Improvements
- Smoothed other players' flashlight beams so turning and walking should no longer create harsh flashing.
- Reworked projected-light caching so multiple players' beams do not fight over one shared render cache.
- Improved depth and water handling so flashlight overlays should not show through ground or make water look removed.
- Improved server-side temporary light placement so lights stop at walls, terrain, and water instead of appearing behind them.
- Added a short cleanup grace period for server-side temporary lights to reduce block-light flicker while players move.
- Split the Fabric source into version-specific compatibility bands so the mod builds correctly across the whole 1.21.x range.
- Added a full-range Fabric build script for checking every supported Fabric version.
- Updated the Modrinth description and changelog to explain the new Fabric support policy.
- Kept the Fabric port focused on the important part first: the flashlight gameplay and shared server-side lighting.
Known Notes
- Fabric currently has gameplay/server-light support first.
- The custom first-person beam visuals and animated item renderer are not fully ported to Fabric yet.
- Third-person dynamic beam visuals are still not supported.
- Fabric 1.21.2 through 1.21.10 are not planned to receive routine separate jars anymore.
- If one Fabric jar can safely cover multiple Minecraft versions later, that will be preferred over maintaining many individual patch-version jars.
Misc
- The previous Fabric 1.21.1 through 1.21.11 compatibility batch is treated as a milestone, not a promise that every future patch version will keep getting its own jar.
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:SemszBhn:rGIAbkNk"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:SemszBhn:rGIAbkNk"
}

