All versions
2.1.0-neoforge-26.1-26.2
Alpha
Dynamic Flashlight 2.1.0-neoforge-26.1-26.22 weeks ago 65
Uploaded by
Compatibility
Minecraft: Java Edition
26.2
26.1.x
Platform
NeoForge
Supported environments
Client and server
Changes
Dynamic Flashlight 2.1.0 Hotfix
This update focuses on fixing the new multiplayer flashlight lighting system and cleaning up version support.
Fixed
- Fixed block overlay rendering so projected light sticks to world block faces instead of sliding around the screen.
- Fixed broken/wiggly overlay behavior introduced during the multiplayer lighting update.
- Fixed Fabric temporary light block state issues that could break server-side light placement.
- Improved server-side flashlight light placement so light blocks behave more reliably in multiplayer.
- Reduced harsh flickering from temporary server lights when players move or turn.
- Improved occlusion checks so lights are less likely to appear through walls, floors, water, or terrain.
Added
- Added Fabric support jar for Minecraft
26.1-26.2. - Added NeoForge support jar for Minecraft
26.1-26.2.
Changed
- Fabric support is being simplified going forward.
- Support for non-essential individual Fabric versions between
1.21.2and1.21.10is being dropped unless a safe universal/banded jar can cover them. - The goal is fewer, cleaner release jars instead of uploading too many nearly identical files.
Notes
- The main flashlight effect is still focused on the light itself: projected block lighting, server-visible brightness, and a survival-friendly battery flashlight.
- NeoForge
26.1-26.2currently uses a functional compatibility build. The full custom client renderer for NeoForge 26.x still needs a proper port because Minecraft/NeoForge 26 changed the rendering API heavily.
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:ODep8Jnf"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:SemszBhn:ODep8Jnf"
}

