All versions
3.0.0-beta.1-neoforge-26.3
Beta
Dynamic Flashlight 3.0.0-beta.1-neoforge-26.315 hours ago 14
Uploaded by
Compatibility
Minecraft: Java Edition
26.3
Platform
NeoForge
Supported environments
Client and server
Changes
Dynamic Flashlight 3.0.0 Beta 1
Flashlight Gameplay
- Retains the animated flashlight and battery loop: charge drain, depleted state, reload/recharge, item durability/charge display, crafting recipes, and existing upgrade data.
- Keeps the lens and range upgrade modules, focus modes, beam tuning, and the Z-key tuning workflow. Existing non-default key bindings and stored tuning/config values are preserved where that port supports migration.
- Keeps multiplayer flashlight sources server-authoritative. Clients receive validated source snapshots, updates, and removals; the server derives origin and aim from player state rather than trusting a client-supplied beam.
- Keeps server-side illumination and spawn-protection checks separate from the visual client renderer. The projected beam does not place temporary light blocks or rewrite vanilla block-light values.
Lighting And Sources
- Adds configurable groups for placed light sources, including torches and lanterns, redstone lamps/torches and copper bulbs, glowing blocks, fire, lava, and invisible Light blocks. Source presets give users a lower-cost starting point; individual groups can be adjusted, and firework lighting is optional and off by default.
- Adds camera-aware cone lighting with blocker tests, shadow-aware visibility, configurable brightness/range/beam appearance, and local and remote source handling.
- Captures the posed flashlight lens for the visible shaft so the beam follows first-person, offhand, reload, and camera movement more closely than a head-position approximation.
- Includes receiver geometry and material handling for block faces, cutout textures, UVs, fluid surfaces, particles, glass variants, moving blocks, and supported vanilla entity/model surfaces. Unsupported or custom renderer paths retain native rendering rather than being treated as universal compatibility.
- Uses cached section/model geometry and bounded source, receiver, and quality budgets to limit repeated CPU discovery and render work.
26.3 Rendering Work
The newest rendering work is concentrated on the NeoForge 26.3 overhaul; these details are not a claim of feature parity on every listed port.
- Textured surfaces receive localized, per-fragment projected illumination with depth-tested shadows instead of temporary world light blocks or a full-body glow.
- The realism path uses HDR surface accumulation and smooth highlight exposure. Its world-space volumetric shaft is lens-anchored, depth-clipped, shadow-aware, and sampled at quality-dependent rates.
- Camera-ray and FOV corrections account for view bob and lens offsets, reducing detached shafts, near-tip clipping, and visible seams.
- Adds receiver-owned, occlusion-tested glare with bounded strength and timing, plus host-controlled cave/night darkness behavior that preserves vanilla light levels and Night Vision input.
- Adds independent local/remote settings and player-shadow controls. On NeoForge 26.3, posed players, skin layers, armor, vanilla capes, and held items can cast shadows; the carried-light owner is excluded from its own light. Player-count budgets are 2/4/8 for Low/Balanced/High, with an Unlimited option.
- Water, moving pistons, clear/stained/tinted glass, particles, animated sculk, skull variants, capes, armor, and held items have targeted regression coverage on this port.
Interface And Configuration
- Expands the Z-menu tuning workflow with flashlight modules, inventory transfer, focus/range controls, reset/apply behavior, and lighting settings.
- Adds source groups and performance presets so users can opt into more expensive placed-light categories rather than enabling every source indiscriminately.
- Keeps user preferences separate from host-controlled gameplay settings where supported, and includes checks for config migration, disconnect isolation, and persisted key bindings.
- Fabric 1.21.11 includes an optional Mod Menu entry point; Mod Menu is not a required runtime dependency.
Repository And Verification
- The published GitLab history records the August project snapshot and Fabric 1.21.11 port, the October NeoForge lighting/26.x port work, and the November realism-renderer and beam-seam changes. This beta also includes the current local work built after those pushes.
- All ten Fabric/NeoForge targets completed the repository build/check launcher successfully for this beta. Runtime jars are named with the beta version, loader, and Minecraft version; the bundle includes SHA-256 checksums.
- The NeoForge 26.3 test work includes shared lighting/math assertions, camera-ray and photometry checks, server/tuning/network tests, visual scenes, and synchronized two-client scenarios. Its recorded acceptance matrix covers 147 visual scenes across vanilla and Sodium runs, plus 39 multiplayer stages.
- Build success and focused regression passes do not mean every target received the same visual test matrix. In particular, the broad 147-scene/player-shadow evidence is for NeoForge 26.3, not all ten builds.
Beta Limitations
- General shader-pack compatibility remains experimental, not certified. Complementary Unbound/Iris/Sodium combinations have known version-specific behavior; the tested native and Sodium paths do not guarantee shader-pack rendering.
- NeoForge 26.3 has the most complete player-shadow and realism renderer work. Other versions/loaders do not yet have proven full renderer parity.
- Essential account-owned cosmetics, arbitrary third-party entity renderers, and every custom armor/material path have not been visually verified.
- The cinematic test harness can stage a flashlight showcase, but public in-game developer commands for creating fake directional beams are not included in this beta.
- Treat this as a beta: expect renderer/performance differences by hardware, loader, Minecraft version, and mod combination. Include those details and a log when reporting issues.
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:LHtTx43e"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:SemszBhn:LHtTx43e"
}

