Minecraft Java · Experimental voxel lighting
Rethinking Voxels r0.1-beta9 turns block lights into sharper, colored shadow casters while keeping the broader look of its Complementary Reimagined roots. The effect is distinctive, but the creator still labels the project WIP and documents sudden brightness changes. Install this release through Iris and keep a known-good fallback.
Exact beta selected
| Version | r0.1-beta9 |
|---|---|
| Channel | Beta |
| Modrinth ID | cpD4esk9 |
| Filename | rethinking-voxels_r0.1-beta9.zip |
| Minecraft | 1.21.1–1.21.10, 1.20.4, and 1.20.1 |
| Loader | Iris |
| License | Complementary Agreement 1.3 |
The beta9 notes list three fixes: an unbound-profile compile error, pixelated block light, and apparent desaturation on some light sources with fewer false positives in unknown-light detection. Those corrections do not turn a beta into a universal stable release.
Based on Complementary does not mean “install both ZIPs”
Rethinking Voxels is an edit of Complementary Reimagined. That describes its code and visual lineage. The current beta9 record does not list a separate Complementary shader file as required content; the Rethinking Voxels ZIP is selected as its own shader pack.
Use MineBrush's Complementary Reimagined guide to understand the base family's goals or build a comparison. Do not enable both shaders at once, merge their archives, or copy settings between releases without checking which options still exist.
The feature and the tradeoff are inseparable
The project's defining feature is colored block lighting that casts sharp shadows. The creator explains that occasional sudden brightness changes are a side effect of the lighting system and cannot be removed completely without either hurting performance or removing sharp light-source shadows.
The documented escape hatch is to disable Per-Pixel Lighting in the Rethinking Voxels settings. That removes the sharp shadows produced by light sources. It is not a magic stability toggle that preserves the full signature effect; it deliberately changes the result you installed the pack to see.
Current releases require Iris
The project overview still displays Iris and OptiFine because historical builds exist for both. The creator's current note is narrower: Iris is required, while beta 18d and older versions also work on OptiFine. The selected r0.1-beta9 release itself lists Iris only.
That makes loader choice straightforward. Set up Iris for the exact Java build, prove an unshaded world first, and do not troubleshoot beta9 through OptiFine. MineBrush's Iris setup article covers the surrounding loader steps.
Install with a reversible baseline
- Create a separate Iris profile for one of beta9's listed Minecraft versions.
- Launch the profile without shaders and confirm chunks, dimensions, and resource packs load normally.
- Leave
rethinking-voxels_r0.1-beta9.zipcompressed and place it inshaderpacks. - Select Rethinking Voxels and load a copied test world or a familiar server area.
- Record Iris, Sodium, Minecraft, driver, GPU, resolution, render distance, resource packs, and the Per-Pixel Lighting state.
- Restart, repeat the same scene, and keep the unshaded option ready if a compile or lighting fault returns.
The shader runs on the client. It does not add server mechanics, world generation, or a server plugin. A server's mod policy remains independent from whether the ZIP technically loads.
Test the voxel-light behavior directly
Build a small room with redstone lamp or other bright vanilla sources, colored blocks, a doorway, stairs, and moving entities. Observe the light boundary while placing and removing sources, turning corners, opening the inventory, and moving between chunks. Repeat at daytime, night, and after teleporting away and back.
A useful test captures both the desired sharp shadow and the documented failure mode. If brightness jumps, note the exact trigger and whether disabling Per-Pixel Lighting prevents it. “Looks broken sometimes” is not enough for a reproducible report.
Creator test platforms set an evidence boundary
The developer says the shader is developed on Iris with AMD graphics on Linux and also tested with NVIDIA graphics on Linux. Other platforms may work, but platform-only bugs may take longer to catch. This is not evidence that every AMD or NVIDIA driver is supported, and it supplies no Intel, Apple, Windows, or macOS result.
For an unsupported or less-tested combination, keep the first run small. Capture the shader compile log, GPU model, driver, operating system, and exact beta filename before changing settings.
Measure stability before frame rate
The creator compares Rethinking Voxels favorably with path-tracing shaders, but MineBrush adopts no speed ranking. Different algorithms, presets, resolutions, drivers, and scenes make a copied comparison unreliable.
- Warm a repeatable route with several light sources and chunk boundaries.
- Lock resolution, render distance, time, weather, resource packs, and Per-Pixel Lighting.
- Record visual errors, compile messages, frame-time spikes, and input feel for at least two passes.
- Toggle only Per-Pixel Lighting, then repeat to expose its quality/stability tradeoff.
- Retest after a client restart before keeping the beta in a daily profile.
No benchmark or device test was produced for this article.
Resource packs can change light recognition
Rethinking Voxels identifies light sources and renders its colored output against the selected resources. A PBR pack, custom emissive textures, modded blocks, or a pack that changes light-source art can alter what you see without changing the shader code.
Start with vanilla resources, then add one material pack. If a specific source desaturates or lights the wrong area, capture its block identity, resource-pack name, shader settings, and the same scene without that pack. Beta9 reduces some false positives; it does not promise perfect detection for every modded light.
Troubleshooting beta9
| Symptom | Next useful action |
|---|---|
| Shader fails to compile | Verify r0.1-beta9, a supported Java build, and current Iris; save the full compile log before editing the ZIP. |
| Block light looks pixelated | Confirm the selected file is beta9, whose notes explicitly address pixelated block light. |
| A light appears washed out | Reproduce with vanilla resources and record the source type; beta9 fixes some desaturation and unknown-light false positives, not every case. |
| Brightness changes suddenly | Capture the trigger, then test with Per-Pixel Lighting off. The creator documents this as a system limitation. |
| Sharp light shadows disappear | Check Per-Pixel Lighting. Disabling it intentionally removes those sharp source shadows. |
| OptiFine will not load beta9 | Use Iris. OptiFine support is documented only for beta 18d and older, not the current beta9 file. |
| A modded lamp casts the wrong color | Test the same source without material packs and report the exact block/mod, since light detection can be source-specific. |
Update and rollback rules for a WIP shader
Preserve the last working ZIP, settings, Iris version, and a screenshot/log pair before updating. Read the changelog for fixes that match your issue; a newer beta can also change lighting assumptions. If a regression appears, restore the earlier shader file before rolling back Iris or the graphics driver.
Removing the shader is safe at the client layer: select OFF or another pack. It does not require deleting a world or Complementary Reimagined, because no separate base file was installed for beta9.
License and media boundary
Rethinking Voxels is governed by the Complementary Agreement 1.3. It permits normal gameplay and content creation and defines conditional modpack and modified-pack redistribution. The agreement also limits other redistribution. MineBrush therefore links to the creator and does not mirror the archive or reuse gallery screenshots.
No real beta9 ZIP, original MineBrush capture, or creator image was found locally. The current page cover is generated editorial art and is not evidence of voxel lighting.
Primary sources
- Rethinking Voxels project
- r0.1-beta9 release
- Complementary Agreement 1.3
- Complementary Reimagined project
Sources were rechecked August 24, 2026. This package records creator claims and explicit unknowns; it does not claim a tested lighting or performance result.

PLAYER QUESTIONS
Discussion
Include the exact edition, version and step when asking for help.