Pastel’s purpose is a soft, colorful image with pink, blue, and yellow preset palettes, clear starry skies, and approachable quick settings. Choose it for that palette-driven mood, not because an old project description says it runs on low-end or integrated graphics. MineBrush has no benchmark for your hardware.

Match Pastel Shaders 1.200

Do not read “Universal” as support for every later Minecraft build. Version 1.200 specifically fixed a loading issue with Iris 1.7 on Minecraft 1.21. The official project has not published a release labeled for 1.21.1–1.21.11 or 26.x.

Pastel is a palette choice first

The project presents three preset directions: pinkish, blueish, and yellowish. Its broader visual pitch is a near-vanilla atmosphere with clear starry skies, sunsets, and sunrises. Quick settings provide an easier first layer, while advanced controls allow deeper customization.

Pastel is described as the visual opposite sibling of Insanity and is based on BSL. That relationship does not make the packs interchangeable:

• Choose Pastel for bright color direction, gentle sky mood, and a friendly palette workflow.
• Choose Insanity when the intentional goal is horror atmosphere and darkness.
• Choose a current actively maintained shader when your Minecraft build is newer than Pastel’s listed 1.21 ceiling.

MineBrush ID156 owns Insanity. ID30 owns generic Iris installation. This page stays with Pastel’s color presets, maintenance boundary, and gameplay readability.

Install only on a listed build

1. Create a separate Java profile for Minecraft 1.21 or another explicitly listed version.
2. Install a compatible Iris or OptiFine build and launch once without a shader.
3. Download version ID w3Pxx3b4 from the creator-controlled versions page.
4. Place Pastel-Shaders-Universal-v1.200.zip in that profile’s shaderpacks folder without extracting it.
5. Select Pastel, keep the defaults for the first route, and disable unrelated PBR or visual packs.

If you use Minecraft 26.x, stop here. A file working accidentally on an unlabeled version would not create official support, and it would not justify publishing compatibility claims.

Compare the three palettes in useful scenes

Create five repeatable viewpoints: a material wall at noon, a village or colorful build, a forest, a water edge at sunset, and a torch-lit interior. Lock resolution, render distance, loader, resource packs, time, weather, and camera positions.

1. Capture the default palette with no manual color changes.
2. Switch to the pink preset and inspect white blocks, skin tones, foliage, fire, and redstone indicators.
3. Repeat with blue and yellow, using the same world clock and exposure.
4. Choose the palette that preserves gameplay-critical color differences, not only the prettiest sunset.
5. Change one quick setting, replay the route, and save the first stable profile.

Readability failures are palette evidence

Treat performance language as unverified

The creator calls Pastel performant and mentions modern low-end GPUs and integrated graphics. The page supplies no device matrix that can predict your resolution, driver, loader, render distance, modpack, or thermal behavior. Benchmark the entire same-camera route after warm-up and report frame time, low-frame behavior, and visible correctness.

MineBrush has not downloaded or run version 1.200. Exact Iris/OptiFine parity, later-game compatibility, FPS, memory, temperature, battery, recording behavior, and every preset result remain unknown.

Rights and support boundary

Pastel Shaders is labeled All Rights Reserved. The current project exposes no source repository or issue tracker. Do not mirror its ZIP or creator gallery, publish modified builds, or infer redistribution rights from its relationship to BSL or Insanity.

• Pastel Shaders project
• Official Pastel versions
• Pastel Shaders 1.200
• Creator-uploaded CurseForge file record

Download boundary: MineBrush does not host Pastel-Shaders-Universal-v1.200.zip. Use the official project route and keep version ID w3Pxx3b4 with the file record.

That makes Mellow useful for players who want to art-direct atmosphere without turning every session into a cinematic showcase. The creator’s “easy on your computer” language is a design goal, not a MineBrush performance result. Test the exact release on your own GPU and keep frame-time measurements tied to the settings that produced them.

Match Mellow 3.3

The broad release labels need one important qualification: the creator says only Minecraft 1.17 and newer are currently tested. Earlier labeled versions may or may not work. The creator recommends current Iris with custom-uniform support; OptiFine is described as mostly working but having small bugs.

Choose Mellow by the controls you will use

• Color schemes: start with the preset closest to your preferred mood instead of forcing one profile across every biome.
• Fog: use the extensive fog system to shape depth, then verify that paths, mobs, and landmarks remain readable.
• Clouds: version 3.3 adds a Blocky style alongside the existing choices.
• Shadows: compare lightmap- and shadowmap-based approaches in the same scene; they are design alternatives, not a guaranteed fast/slow switch for every computer.
• Color grading: saturation, exposure, balance, and adjustable colors can rescue a scene or crush important detail when several move together.

Mellow’s page also names Distant Horizons, Voxy, and Colorwheel under broad mod compatibility. That is creator-stated scope, not proof for every version combination. Add those systems only after the shader works alone.

Use the supported loader route honestly

1. Duplicate a Java profile for the exact Minecraft build you want to test.
2. Install a compatible Iris release; use OptiFine only with the creator’s stated small-bug caveat.
3. Launch once without a shader and confirm the world and shader menu work.
4. Download version ID y6zWED9s from the creator-controlled versions page.
5. Place Mellow Shader v3.3.zip in the active profile’s shaderpacks folder without extracting it.
6. Select Mellow and test its defaults before restoring other rendering mods or PBR packs.

Modern Nvidia, AMD, and Intel GPUs on Windows and Linux are listed by the creator. Mac behavior is explicitly uncertain. These are source statements, not a minimum-spec chart or a promise for every driver.

Build a painterly acceptance route

Use a known world with five checkpoints: a bright build, a forest edge, a foggy long view, water at sunset, and a dark interior. Fix resolution, render distance, time, weather, resource packs, loader, driver, and camera positions.

1. Run Mellow’s default look and note where important blocks or silhouettes lose contrast.
2. Choose one color scheme and repeat the route.
3. Adjust fog until distant depth feels intentional without hiding navigation.
4. Compare one cloud style and one shadow method at a time.
5. Change color grading last, then revisit daylight, interiors, Nether, and End.

Version 3.3 also changes POM on rectangular block faces, makes third-person handheld lighting player-centered on Iris, adds dynamic image sharpening for the Fabulous profile, lowers daytime brightness, and includes small bloom, shadow, and lighting optimizations. Treat each as a release-note claim until you reproduce it with the exact feature enabled.

Troubleshoot the affected layer

Measure before calling it lightweight

Record GPU, driver, operating system, Minecraft build, loader and version, Mellow release, resolution, render distance, resource packs, mods, profile, changed options, warm-up, route, and sample duration. Compare frame-time stability, low-frame behavior, and visual correctness—not just average FPS.

MineBrush has not downloaded or run the 3.3 ZIP. We have no verified FPS, memory, thermal, battery, startup, device, Distant Horizons, Voxy, Colorwheel, POM, or Mac result.

Source and license

Mellow is labeled MIT and links a creator-controlled Codeberg source repository and issue tracker. Keep the original attribution and license notice with any permitted redistribution or modification. Creator gallery images are separate media assets; the code license should not be assumed to grant unrelated image rights.

• Mellow project
• Official Mellow versions
• Mellow 3.3 release
• Creator source repository
• Mellow issue tracker

Download boundary: MineBrush does not mirror the shader ZIP or creator gallery. Use the creator versions page and record version ID y6zWED9s.

Use the exact 1.3.8 release boundary

The version tags are creator metadata, not a MineBrush launch result. Match the Minecraft version and loader first, then use the official version page rather than assuming the newest file fits an older profile.

Choose Iris unless the exact profile requires another path

A platform tag is not loader parity. Do not publish one compatibility badge that hides the release note's OptiFine limitation.

Separate the shader from the material pack

Super Duper Vanilla includes iPBR settings and release 1.3.8 updates iPBR handling for newer Minecraft resources. The shader can render without a PBR resource pack, but its material response can change when normal, specular, or emissive data is present.

1. Start with the default resource pack and record the shader, loader, Minecraft version, and settings.
2. Add one iPBR-compatible material pack and keep the shader settings unchanged.
3. Check reflective blocks, wet surfaces, emissive textures, foliage, and transparent materials.
4. If an artifact appears, remove the material pack before attributing it to the shader.

No specific PBR pack is a declared dependency of release 1.3.8.

Test Distant Horizons as its own rendering route

The 1.3.8 changelog describes Distant Horizons support as completed and says Distant Horizons shadows were removed to correct their behavior. That is a release statement, not a guarantee for every Distant Horizons, Iris, GPU, or Minecraft combination.

• Confirm the normal near terrain first, with Distant Horizons disabled.
• Enable Distant Horizons and inspect the transition between regular chunks and LOD terrain.
• Check sunrise, sunset, fog, water horizons, and fast travel for seams or exposure jumps.
• Do not diagnose missing distant shadows as a broken local shadow setting without reading the 1.3.8 release note.

Evaluate the intended visual direction

The project borrows an art-direction idea; it does not recreate a released official Super Duper Graphics Pack, because that Mojang project was canceled.

Troubleshoot by feature boundary

Official project, release, and license

Open the official Super Duper Vanilla release list.

• Super Duper Vanilla project and setup notes
• Super Duper Vanilla 1.3.8 release record

The FlameRender Studios License permits personal use and content creation but does not grant unrestricted standalone redistribution. Use the official release page; do not mirror the ZIP.

Source check: August 24, 2026. MineBrush did not test the shader, iPBR materials, Distant Horizons, or any loader combination.

Start from the exact 9.5d release record

The project page describes testing across broad Minecraft, GPU, and operating-system families while explicitly withholding a guarantee for every model. The release tags are creator metadata, not a MineBrush hardware or runtime result.

Choose the loader before choosing effects

Do not move a settings file between Iris and OptiFine and call the results equivalent. Loader builds, shader-menu defaults, driver behavior, and supported options can differ.

Build an effect budget instead of trusting the name

Record a baseline that another player can reproduce

1. Record Minecraft, Iris or OptiFine, MakeUp 9.5d, GPU, driver, resolution, render distance, resource packs, and selected preset.
2. Use one repeatable route containing open terrain, foliage, water, a cave, weather, and a fast camera turn.
3. Start with the expensive or comfort-sensitive effects disabled.
4. Capture frame time and visual notes after the route is stable; do not compare a chunk-loading pass with a warmed pass.
5. Add one effect group, repeat the same route, and keep only changes whose cost and appearance the player accepts.

This procedure produces a local decision. It does not justify an FPS range, “low-end” label, universal preset recommendation, or cross-device performance promise.

Use the same scenes for visual acceptance

• Daylight lake: water edges, reflections, underwater visibility, and bright-surface clipping.
• Night: torch readability, hostile-mob visibility, auto-exposure, and dark-block detail.
• Cave: shadow noise, held-light behavior if used, and ore readability.
• Nether and End: dimension-specific sky, fog, emissive surfaces, and portal readability.
• Fast motion: TAA history, motion blur, sharpening halos, and foliage shimmer.

Troubleshoot by loader and effect

Official project, release, and source

Open the official MakeUp release list.

• MakeUp Ultra Fast project and settings guidance
• MakeUp 9.5d release record
• Creator source repository
• Creator issue tracker

Source check: August 24, 2026. MineBrush does not mirror the ZIP and did not measure its performance or image output.

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

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

1. Create a separate Iris profile for one of beta9's listed Minecraft versions.
2. Launch the profile without shaders and confirm chunks, dimensions, and resource packs load normally.
3. Leave rethinking-voxels_r0.1-beta9.zip compressed and place it in shaderpacks.
4. Select Rethinking Voxels and load a copied test world or a familiar server area.
5. Record Iris, Sodium, Minecraft, driver, GPU, resolution, render distance, resource packs, and the Per-Pixel Lighting state.
6. 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.

1. Warm a repeatable route with several light sources and chunk boundaries.
2. Lock resolution, render distance, time, weather, resource packs, and Per-Pixel Lighting.
3. Record visual errors, compile messages, frame-time spikes, and input feel for at least two passes.
4. Toggle only Per-Pixel Lighting, then repeat to expose its quality/stability tradeoff.
5. 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

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.

Solas 3.7b is built for atmosphere: colored light, volumetric skies, dramatic dimensions, stylized water, and configurable post-processing. It can load through Iris or OptiFine, but the two paths do not expose the same visuals. If custom skies and colored block light are central to the look, begin with Iris.

Verified release record

• Release: Solas Shader 3.7b.
• Modrinth version ID: KcfQaN5J.
• Filename: Solas Shader V3.7b.zip.
• Game labels: Java 26.2, 26.1.x, and every major family from 1.21.x back through 1.12.x.
• Platforms: Iris and OptiFine.
• 3.7b change: small fixes for Intel Arc.
• Rights label: All Rights Reserved.

The Intel Arc note does not identify a tested model, driver, or fixed symptom. It is a release-note fact, not a guarantee for all Arc systems.

The Solas look is more than colored torches

The creator's feature list combines several render systems: colored block lighting and real-time shadows; 3D clouds, crepuscular rays, fireflies, Nether smoke, and an End protoplanetary disk; aurora, Milky Way, nebula, black hole, and rainbows; water waves, caustics, absorption, and refraction; plus tonemapping, bloom, lens flare, chromatic aberration, depth of field, motion blur, and tilt-shift.

That makes the pack a deliberate fantasy grade. Evaluate it in motion and in ordinary survival spaces. A gallery-ready End sky may be impressive while a torch-lit stairwell, rainy forest, or underwater route exposes the settings that decide whether the shader is comfortable to play.

Iris is the complete route

Solas lists both Iris and OptiFine, yet the creator marks Iris as preferred and states that custom skyboxes and colored block lighting are not supported on OptiFine. Those missing features change the pack's identity, not just an advanced checkbox. An OptiFine screenshot should not be used to promise the Iris result or vice versa.

Use MineBrush's Iris guide for loader installation. Solas stays zipped in the shaderpacks folder. It is client-side presentation; the release does not provide a server module.

Install in a controlled profile

1. Match a current Iris or OptiFine build to the exact Java version.
2. Launch without a shader and confirm the world, renderer, and resource packs load correctly.
3. Place Solas Shader V3.7b.zip in that profile's shaderpacks directory.
4. Select Solas, leave its settings unchanged, and revisit a familiar daytime scene.
5. Check a cave, rain, water, Nether smoke, and an End view before saving a personal preset.
6. Add PBR materials or distant-terrain mods one at a time after the base shader survives a restart.

Do not mix a loader migration, graphics-driver update, shader update, and new PBR pack in one test. When four variables move, a visual regression has no clear owner.

Integrated PBR and external PBR are separate decisions

Solas advertises an integrated PBR resource pack for some emissive textures, reflective materials, and generated normals. It also supports external LabPBR and OldPBR/SEUS PBR formats. The creator instructs players to enable PBR Resourcepack in shader settings for external material packs.

Begin with Solas alone so the built-in contribution is visible. Then enable one suitable material pack and compare a metal, a rough block, glass or water, and an emissive surface. If only one material family works, inspect the resource pack's maps before changing the shader.

Choose effects by gameplay cost, not by spectacle

The creator describes a moderate performance cost, but that phrase is not a benchmark and has no fixed hardware target. Build your preset around the scenes you actually play:

• Volumetrics: check fog, clouds, rays, Nether smoke, and End atmosphere at your normal render distance.
• Post-processing: motion blur, depth of field, chromatic aberration, and lens flare can reduce clarity even when frame rate is acceptable.
• Water: compare the surface, underwater visibility, shorelines, and caustics without changing the resource pack.
• Colored lighting: use Iris and a room with distinct sources; make sure cave shadows do not hide hazards.
• Subsurface scattering: inspect supported foliage or blocks at noon and sunset rather than assuming every material participates.

Voxy and Distant Horizons are listed, not universally certified

The Solas page names both projects under mod compatibility. The selected release does not publish a complete matrix of every Minecraft, loader, distant-world mod, GPU, and Solas setting. Test one distant renderer at a time from a fixed overlook. Move across the near/far transition, change weather, and watch the horizon through a day/night cycle.

If lighting breaks only beyond normal chunks, save the Solas preset and reproduce with the distant mod removed. If the problem remains in ordinary chunks, return to the loader-only baseline. This distinction matters more than a generic “compatible” label.

Intel Arc deserves a targeted check

Because 3.7b specifically mentions Intel Arc, an Arc user should record GPU model and driver, then inspect the effects most likely to reveal shader errors: colored lights, reflections, clouds, volumetric rays, water, and PBR materials. A successful title screen is not enough.

MineBrush did not run this route. No Intel, NVIDIA, AMD, macOS, Windows, or Linux result is claimed.

Make a repeatable performance record

1. Choose a saved route with a village or build, water, foliage, a cave entrance, and a busy sky.
2. Lock resolution, render distance, entity distance, weather, time, and resource packs.
3. Capture a no-shader pass, then Solas defaults, then one modified setting group.
4. Record average frame time, noticeable spikes, image artifacts, and input feel.
5. Repeat after a full restart before declaring the preset stable.

Do not copy a recommended FPS value from another GPU. The useful result is the exact tuple that remains playable on your machine.

Troubleshooting map

Updates, removal, and rights

Save the current ZIP, loader version, driver, resource-pack list, and exported setting values before updating. Confirm the new file against the creator's version page, then repeat the same dimension and PBR checks. To remove Solas, select OFF or another shader; do not delete the loader while diagnosing a shader-only problem.

Solas is labeled All Rights Reserved. MineBrush does not mirror the archive or import gallery images. The current page cover is generated editorial artwork, not a verified Solas screenshot.

Creator records

• Solas Shader project
• Solas Shader 3.7b release
• Creator-linked source repository

Sources were checked August 24, 2026. No archive, creator image, or hardware result was stored by MineBrush.

Photon v1.3b rebuilds Minecraft's sky, water, weather, fog, shadows, reflections, and ambient light without aiming for a full path-traced presentation. Use Iris when you want the complete feature path, especially voxel colored lighting. Use the official file record and judge the shader on your own repeatable scene rather than somebody else's FPS number.

Current release at a glance

Version labels are creator metadata, not proof that every loader build, graphics driver, and Minecraft patch behaves identically. The archive was not run by MineBrush.

What Photon is trying to deliver

The project describes a gameplay-focused, semi-realistic style. Its feature list spans multilayer clouds, changing weather skies, volumetric fog, water, screen-space reflections, variable soft shadows, GTAO ambient occlusion, camera effects, anti-aliasing and sharpening options, temporal upscaling, and LabPBR materials.

That scope makes Photon a whole rendering profile rather than a single lighting toggle. A useful evaluation asks whether caves remain legible, rain still supports navigation, water boundaries are readable, and the sky treatment fits long survival sessions. A dramatic sunrise alone is not enough.

Iris and OptiFine are not feature-equivalent

Both loaders appear on the v1.3b record, but the creator recommends Iris and says voxel colored lighting works only there. Photon exposes that lighting through its Ultra profile. If colored lamps or emissive blocks are the reason you want Photon, choose a current Iris setup first; do not assume the OptiFine listing includes the same renderer path.

MineBrush's Iris setup guide covers the loader layer. Photon itself remains a ZIP placed in the shaderpacks folder. It does not belong in the mods directory and it does not add a server plugin.

Hardware boundary: Apple Metal is a stop sign

The creator lists NVIDIA, AMD, and Intel GPU vendors, then explicitly marks Apple GPUs using Metal as incompatible. That is stronger than “not tested.” Do not publish an Apple-silicon workaround as supported unless the creator changes this boundary. Translation layers, unofficial patches, or a screenshot from one Mac do not establish support.

No minimum GPU, driver, VRAM, resolution, or target frame rate is guaranteed on the project page. A vendor name is not a performance tier.

Clean installation path

1. Choose the exact Minecraft build and install a current compatible Iris or OptiFine release.
2. Launch once with no shader to confirm that the loader reaches a playable world.
3. Keep photon_v1.3b.zip intact in the profile's shaderpacks folder.
4. Select Photon from the shader menu and begin with its unchanged defaults.
5. Restart the client, revisit the same scene, and record Minecraft, loader, Photon, driver, resolution, and render distance.
6. Add a PBR pack, Voxy, Distant Horizons, or a settings preset only after the base result is stable.

The shader is a client renderer. A server or Realm does not need the ZIP for one player to use it, though server rules and client-mod policies remain separate decisions.

Build a useful settings baseline

Start with visual correctness, then change one high-impact system at a time. For Photon, the most informative groups are render resolution or temporal upscaling, volumetric clouds and fog, reflections, shadows, ambient occlusion, post-processing, and voxel colored lighting.

• Upscaling: the creator says advanced temporal upscaling is disabled by default. Enabling it is a quality/performance trade, not an automatic boost.
• Ultra colored lighting: test it only on Iris and compare a room with several differently colored light sources.
• Reflections: inspect water edges, transparent surfaces, and objects leaving the screen, where screen-space methods can reveal limits.
• Camera effects: depth of field and motion blur may help screenshots but reduce gameplay clarity for some players.
• Clouds and fog: test rain, mountains, caves, and Nether sightlines before keeping a dramatic preset.

Voxy and Distant Horizons need their own acceptance pass

Photon lists both projects as compatible. That does not identify every supported combination of Photon, Iris, distant terrain mod, Minecraft, and GPU driver. Enable one distant-world system at a time. Use a ridge or tower where near chunks, distant geometry, water, clouds, and fog meet, then watch for a lighting seam while moving and after teleporting.

Record whether the issue disappears with the distant-world mod disabled, with Photon disabled, or after a clean shader reload. That separation produces a useful bug report and avoids blaming the last component installed.

LabPBR is material input, not a built-in result

Photon advertises full LabPBR resource-pack support. You still need a material resource pack that supplies the relevant maps. Test the shader first with vanilla resources, then add one documented LabPBR pack and inspect a small set of metal, rough, emissive, and wet surfaces.

Do not use the MineBrush cover as a material screenshot. It is generated editorial art and cannot show which Photon settings or resource pack produced an effect.

A benchmark that belongs to your PC

1. Save a 60–90 second route through the same loaded area.
2. Fix resolution, render distance, simulation distance, weather, time, and loader.
3. Warm the route once, then measure a no-shader pass and the unchanged Photon profile.
4. Change one setting group and repeat at least twice.
5. Keep the preset only if image quality, input response, and low-frame behavior remain acceptable.

No such run was performed for this article. Photon's “Low,” “Medium,” or “High” tags and its upscaling feature are not MineBrush FPS data.

Troubleshooting

Update, rollback, and rights

Keep the last working shader ZIP and settings file until a new release survives the same weather, cave, water, and distant-terrain checks. Roll back Photon before changing the loader or driver so only one variable moves.

Photon uses a custom license. It permits normal use, commercial screenshots and video, personal modification, and some redistribution under stated conditions, while restricting monetized-platform redistribution and paid copies without permission. MineBrush does not mirror the file; use the creator's release page and read the license for any modpack or redistribution decision.

Creator sources checked

• Photon Shaders project
• Photon v1.3b release
• Photon Shaders License Agreement

Sources were checked August 24, 2026. No Photon archive, creator screenshot, or runtime result was retained in this offline package.

Build the first playable profile around visual clarity. Start with the creator defaults, turn off camera effects if they interfere with movement, and only then decide how much shadow, volumetric, water, and material detail your exact system can hold.

Match BSL Shaders 10.1.3

The creator lists both Iris and OptiFine. That platform label does not prove every loader build, modded renderer, GPU driver, or resource-pack stack. The shader runs on the client; a server does not install it to produce the image for players.

Know what makes BSL distinct

CaptTatsu describes BSL as bright, colorful, and distinct. Its listed core features include real-time shadows, volumetric light, ambient occlusion, bloom, customizable clouds and water, and built-in anti-aliasing. Optional effects include depth of field, motion blur, specular and normal mapping, cel shading, and world curvature.

Those groups give BSL its range, but they solve different problems:

• Shadows and ambient occlusion define shape and contact around blocks.
• Volumetric light and bloom shape the atmosphere but can wash out bright builds if pushed too far.
• Cloud and water controls change the sky and traversal scenes players see constantly.
• Depth of field and motion blur are camera-style effects; they can suit captures while making normal play less readable.
• Specular and normal mapping need compatible material data from a resource pack. BSL cannot invent correct PBR maps for every texture.

Generic Iris installation belongs in MineBrush ID30. Complementary Unbound selection belongs in ID149. This page owns BSL’s effect hierarchy, first settings baseline, and creator-specific rights boundary.

Install the ZIP intact

If Iris is not already working in this profile, follow our Iris setup guide first, then return here for the BSL-specific ZIP and settings.

1. Duplicate the Java profile you intend to use.
2. Install a compatible Iris or OptiFine build for that exact Minecraft version.
3. Download BSL version ID hIibTfxn from the creator-controlled release page.
4. Place BSL_v10.1.3.zip in .minecraft/shaderpacks without extracting it.
5. Launch Minecraft, open Video Settings, enter the Shaders/Shader Packs menu, and select BSL.
6. Leave unrelated visual mods and PBR packs off until the base route is stable.

If the pack does not appear, check the active instance’s folder before reinstalling anything. Multi-instance launchers often use a profile directory that is not the global .minecraft folder.

Start with play clarity, then add the look

Use one world with a sunny exterior, dense foliage, a torch-lit interior, water, glass, rain, Nether lava, and an End scene. Fix the resolution, render distance, simulation distance, loader, resource packs, driver, weather, and camera path.

1. Select BSL and preserve the untouched default as the rollback point.
2. Disable depth of field and motion blur for the first gameplay pass if either makes movement or targeting harder.
3. Check block edges, hostile mobs, dropped items, particles, glass, water surfaces, and UI overlays.
4. Record frame time across the whole route after a warm-up pass.
5. Change one effect group and repeat before moving to the next.

There is no honest universal “best BSL setting.” A 1080p survival route, a 4K screenshot, and a modded base with animated machinery are different workloads. Save separate gameplay and capture presets if both matter.

Tune the symptom you can reproduce

Benchmark a full route, not a screenshot

For each change, record Minecraft version, BSL version ID, loader and version, GPU and driver, resolution, render and simulation distance, resource packs, mods, preset, changed options, warm-up, sample duration, and the route. Compare frame-time consistency and visible correctness alongside average FPS.

MineBrush has not downloaded or run BSL 10.1.3. We have no FPS, low-frame, memory, startup, device, or visual-result measurement for this release. Creator compatibility labels and feature descriptions are not performance guarantees.

Update without losing the known-good preset

Keep the previous ZIP and exported or documented settings outside the active folder. Update in a duplicate profile, verify the version ID and original filename, then replay the same scene route before removing the old build. If the image or timing changes unexpectedly, restore the full old tuple rather than mixing a new shader with unidentified old settings.

Rights and official sources

BSL is labeled All Rights Reserved. CaptTatsu explicitly allows using the shader for screenshots and videos and modifying it for personal use. The creator forbids redistribution without permission, claiming or renaming the pack, and monetized URL shorteners. Publishing a heavily modified version also requires permission.

• BSL Shaders project
• Official BSL versions
• BSL 10.1.3 release
• CaptTatsu’s BSL site

Download boundary: do not mirror BSL_v10.1.3.zip. Send players to a creator-controlled versions page and keep the exact release tuple with any local test record.

Choose Unbound because its starting image fits your world, then build a measured baseline around the exact GPU, resolution, render distance, loader, and Minecraft version you use. “Potato” through “Ultra” are creator profile names, not universal hardware tiers.

Match Complementary Unbound r5.8.1

The official manual route recommends Iris, while the current release metadata also lists OptiFine. Keep the shader ZIP intact in the profile’s shaderpacks folder. A dedicated server does not need the file to render one player’s local image.

Unbound or Reimagined?

The creator says both downloads belong to the same Complementary shader system and differ only in their default settings. Unbound starts less restricted and aims at a more realistic image. Reimagined starts closer to Minecraft’s recognizable visual language. Both can be customized in Shader Options: Unbound can use blocky clouds, and Reimagined can use realistic water.

That makes the selection practical:

• Start with Unbound if realistic sky, water, lighting, and atmospheric defaults are the result you want to tune from.
• Start with Reimagined if preserving the blocky Minecraft identity is the stronger priority.
• Do not install both and assume their names represent different rendering engines. Compare the defaults in the same scene first.

MineBrush ID34 owns the separate Complementary Reimagined decision and settings page. ID30 owns generic Iris installation. This page stays focused on selecting and baselining Unbound.

Install the manual route

New to the loader? Complete the Iris setup guide before placing the shader ZIP, then return to this release-specific baseline.

1. Create or duplicate a Java profile for the exact Minecraft build you plan to use.
2. Install a compatible Iris build, or use the creator-listed OptiFine route.
3. Launch once and open the Shaderpacks/Shaders screen in Video Settings.
4. Open the profile’s shaderpacks folder from that screen.
5. Place ComplementaryUnbound_r5.8.1.zip in the folder without extracting it.
6. Return to the game, refresh the list if needed, and select Complementary.

The official Complementary installer is another creator-supported route and installs Complementary with Iris. If you use it, record what it installed instead of mixing its output with a second manual loader and guessing which copy is active.

Build a baseline before chasing a preset

Use a small route through one known world: a bright outdoor build, leaf-heavy terrain, water, a dark interior, the Nether, and the End. Lock the Minecraft build, loader version, GPU driver, screen resolution, render distance, simulation distance, resource packs, time of day, weather, and camera positions.

1. Start with Unbound’s default settings and let the world finish loading.
2. Record frame-time behavior across the whole route, not one peak FPS number.
3. Check gameplay clarity: ores, hostile mobs, dropped items, glass, water edges, particles, and UI overlays.
4. Change one group—shadows, volumetrics, clouds, water, reflections, or profile—then repeat.
5. Save the first stable setup as a named baseline before testing another group.

The creator provides profiles from Potato through Ultra. These are convenient starting configurations. They cannot tell you which profile is “safe” for a laptop, GPU family, modpack, or recording target without measurements from that exact system.

Decide which cost is worth keeping

What r5.8.1 does and does not prove

The creator’s r5.8 notes describe Voxy support work, Distant Horizons-related improvements, rewritten light shafts, End-atmosphere changes, precipitation texture handling, reflections, customization, and performance improvements on higher settings. These are release-note claims, not a MineBrush runtime verification for every mod combination.

MineBrush has not downloaded the ZIP, run Voxy or Distant Horizons, measured frame time, or verified visual results on a device. Treat the current loader and game labels as creator metadata. Recheck the official release page before moving a live profile to a newer build.

Custom license and source boundary

The project uses the Complementary Agreement. Normal gameplay and content creation are allowed. Redistribution is limited to the agreement’s stated modpack or substantially modified-pack cases and conditions; ordinary mirroring is not allowed. The agreement also says its terms apply to the version containing that exact agreement, so inspect the license shipped with the release you use.

• Complementary Unbound project
• Official Unbound versions
• Complementary Unbound r5.8.1
• Official style and download guide
• Complementary Agreement 1.3

Download boundary: MineBrush does not mirror the shader ZIP or creator gallery. Use the creator’s page, keep the file intact, and record version ID VMHXIk50.

Iris lets Minecraft Java load modern shader packs without turning setup into guesswork. The key is to match four things—the Minecraft version, mod loader, Iris build, and Sodium dependency—before you touch graphics settings. This guide covers the official installer, manual Fabric and NeoForge installs, shader-pack placement, performance tuning, and the most common failure points.

Quick answer: what you need

• Minecraft Java Edition. Iris is not a Bedrock, Marketplace, RTX, or Vibrant Visuals add-on.
• A supported loader. Fabric is supported from Minecraft 1.16.5 forward; NeoForge support starts at 1.21.1. Forge is not supported.
• Iris and Sodium for the same branch. The official installer handles both. Manual installs require the Sodium version listed by the exact Iris release.
• A separate shader pack. Iris is the loader, not the visual pack itself.
• A clean baseline. Launch the correct profile once before adding a shader pack so you know whether a problem comes from the loader or the pack.

Iris is client-side. You normally do not install it on a Minecraft server, and you can join a server without asking every other player to use the same shader pack.

Choose the right Minecraft and loader branch

Do not download whichever file has the biggest version number. Iris releases are tied to specific Minecraft branches, and the newest Iris number is not automatically the correct file for the newest game branch.

These are dated examples, not a permanent “latest version” promise. Before installing, open the exact release page and verify its Minecraft version, loader, and required Sodium dependency. Distribution sites may label Fabric files for Quilt, but the current Iris FAQ does not present Quilt as a separate officially supported loader. Treat Quilt as a compatibility case, not a guaranteed first-choice route.

Option 1: use the official Iris Installer

The installer is the simplest route for a normal Minecraft Launcher profile because it installs Iris and Sodium together.

1. Open the official Iris download page.
2. Download the installer offered by the project. Windows users can use the EXE route when available; the universal JAR route requires a working Java runtime.
3. Close Minecraft and the launcher instance you plan to modify.
4. Run the installer, choose the exact Minecraft version you want, and install the new profile.
5. Open the Minecraft Launcher and confirm that the Iris profile is selected.
6. Launch once with no shader pack active. Open Video Settings and make sure the profile reaches the menu and a test world normally.

If the installer does not offer your exact Minecraft version, stop there. Do not choose a nearby branch and hope it works; use a matching manual release or stay on the profile that already works.

Option 2: install Iris manually

Manual installation makes sense for an existing Fabric or NeoForge profile, a controlled modpack, or a launcher instance with its own game directory.

1. Confirm the profile's exact Minecraft version and loader.
2. Download the matching Iris file from the project's Modrinth versions page or creator-owned CurseForge project.
3. Open that Iris release's dependency list and download the exact required Sodium build for the same Minecraft version and loader.
4. Place both intact .jar files in that profile's mods folder.
5. Remove conflicting copies of Iris, Sodium, or another loader variant before launch.
6. Launch the intended profile once before adding a shader pack.

The default Minecraft Launcher locations are %APPDATA%\.minecraft\mods on Windows, ~/Library/Application Support/minecraft/mods on macOS, and ~/.minecraft/mods on Linux. Third-party launchers and separate instances can use a completely different game directory, so follow the path shown by that instance instead of blindly using the default.

Do not mix Fabric and NeoForge files. Do not add Fabric API unless another mod in your profile actually requires it; the selected Iris release is the authority for its own dependencies.

Add a shader pack

A shader pack is separate from Iris and Sodium. Get it from the pack creator's official project page, then keep its archive in the shader-pack location—not in mods or resourcepacks.

1. Launch the Iris-enabled profile.
2. Open Options → Video Settings → Shader Packs.
3. Use Open Shader Pack Folder, or drag the pack into the shader-pack screen if that control is available.
4. Keep a correctly packaged pack as a ZIP, or use a folder that directly contains its shaders directory.
5. Select one pack, apply it, and wait for shader compilation to finish.

If the pack does not appear, check the active profile's game directory first. A common mistake is placing the ZIP in the default .minecraft folder while the launcher is using a separate instance.

Start with a performance baseline

Shader performance depends heavily on the pack, preset, resolution, render distance, GPU, driver, and the rest of the mod stack. Iris cannot promise a specific FPS increase or make every shader pack lightweight.

• Load a world you know with shaders disabled and note how it feels.
• Enable one shader pack on its low or medium preset.
• Test the same location, time of day, render distance, and screen resolution.
• Lower shadow quality and render distance before disabling every visual feature.
• Change one setting at a time. If your FPS gets wrecked, you want to know which change did it.

For screenshots or build showcases, save the exact Minecraft, loader, Iris, Sodium, and shader-pack versions with the project. That makes the setup reproducible instead of relying on a preset name that may change later.

Fix the problems players hit most often

The Shader Packs button is missing

You probably launched the wrong profile, installed the wrong loader build, or have a startup conflict. Recheck the launcher profile, Minecraft version, Iris file, and Sodium dependency before reinstalling everything.

The pack is not listed

Confirm that the file is inside the active instance's shaderpacks folder. Check that it is a ZIP or folder with a top-level shaders directory. A pack placed in mods or resourcepacks will not work as an Iris shader pack.

Minecraft crashes on launch

Remove obvious renderer conflicts first. Iris documentation identifies OptiFine, Canvas, and Vulkan renderer mods as incompatible. Also check for mixed Fabric and NeoForge files, duplicate Iris or Sodium JARs, and a Sodium version that does not match the selected Iris release.

The world is black, flickering, or visually broken

Disable the shader pack and confirm that the base Iris profile still renders normally. Then test a current pack version and update the graphics driver from the GPU vendor. Some packs have known limitations: Continuum/Focal Engine packs are not supported, Chronos 4.x is listed as problematic, and SEUS PTGI HRR 3 can have issues with motion blur enabled.

Distant Horizons, Voxy, or Nvidium behaves differently

Distant Horizons and Voxy need shader packs that explicitly support them. Nvidium can remain installed, but it disables itself while shaders are active. Do not assume every performance mod stays active in the same rendering path.

A resource pack stops working with shaders

Resource packs that replace custom core shaders cannot run at the same time as an active shader pack. Test the resource pack with shaders disabled to separate the two issues.

Update Iris without breaking a working profile

1. Back up important worlds and note the current working file names.
2. Check the exact Minecraft and loader branch before downloading.
3. Replace Iris and its matched Sodium dependency together.
4. Remove old duplicates instead of leaving several versions in mods.
5. Launch once with shaders disabled, then test one known pack.

If a new game release does not yet have a matching Iris build, keep the working profile. Updating Minecraft first and troubleshooting the renderer later is the fastest way to turn one change into five unknowns.

Official project and support links

• Iris official website — supported loaders, graphics guidance, and project documentation.
• Official Iris Installer — the recommended installer route.
• Iris versions on Modrinth — exact game, loader, release, and dependency records.
• MineBrush Fabric installation checklist — profile, loader, dependency, and backup basics.

Source check: August 24, 2026. MineBrush is independent from Mojang, IrisShaders, FabricMC, NeoForged, Modrinth, CurseForge, and shader-pack creators. MineBrush does not mirror Iris, Sodium, installer, or shader-pack files.