Credits answer who contributed. A license or written permission answers what you may do with someone else's work. Those are different records, and a clean publishing workflow keeps both attached to every borrowed dependency before a project is released.

Build the source record before publication

Create one entry for each third-party texture, model, sound, script, library, map component, reference asset, or collaborator contribution. Record:

• the project or asset name;
• the creator or rights holder exactly as the source identifies them;
• the creator-controlled source URL;
• the exact license name and link, or the written-permission record;
• the version or dated source state you used;
• any changes you made;
• where the material appears in your release;
• any notice, attribution, share-alike, or distribution condition that still needs review.

A homepage link or a creator name by itself is not a complete license record. Preserve the exact source that governs the version you used, and recheck it before a new release.

Separate three permission states

Use a fail-closed status for each dependency:

1. License identified: the governing text is linked and its conditions have been reviewed for the planned use.
2. Direct permission recorded: the rights holder supplied permission that covers the planned use, and the record states its scope.
3. Permission unresolved: the source is missing, the license is unclear, or the planned use is outside the documented terms.

The third state is a stop signal. Do not replace it with “credit to the owner,” a search-result link, or an assumption that free access means free reuse. Remove or replace the dependency until the rights state is clear.

Write credits that can be audited

Group credits by function so a player or reviewer can trace them: building, code, textures, models, audio, testing, translation, and other contributions. Use the contributor's requested public name when known. Link to the creator-controlled source, not a repost or download mirror.

If a dependency was modified, say what changed without implying that you own the original. If different files use different terms, keep separate entries. A single project-wide license label should not hide asset-specific conditions.

Keep release notes and the rights record together

When a dependency changes, update its source, version, modification note, and permission state in the same revision. If a creator removes a page or changes a license, do not silently carry the old claim forward. Preserve the prior audit record and make a new release decision from the evidence that still applies.

The current Minecraft EULA distinguishes original creator work from Minecraft-owned content and directs creators to current Usage Guidelines. It provides a general official boundary only; it is not individualized legal advice and does not grant permission for third-party material.

Final disclosure gate

Do not publish until every dependency has an identified source, a resolved permission state, accurate credit, and a record of modifications. This page owns the disclosure workflow. Portfolio selection, project storytelling, and presentation order belong to the separate portfolio guide.

A strong Minecraft portfolio helps a reviewer understand what you made, why you made it, and which decisions were yours. It is more than a gallery of finished screenshots. The useful part is the context around each project: the goal, your role, the constraints, the result, and what you would improve next.

Choose projects that prove different skills

Start with a small, deliberate set of work instead of every build or experiment you have saved. Pick projects that show different kinds of judgment. A world build might demonstrate composition and navigation. A resource or tool might demonstrate a technical workflow. A collaborative project might demonstrate planning and communication.

Do not claim work simply because you appeared in it or helped publish it. State your contribution in plain language. If you designed the layout but another creator handled commands, modeling, textures, or testing, say so. Reviewers should be able to separate the team result from your individual role.

Give every project a compact context card

For each selected project, answer the same practical questions:

• What problem, player experience, or creative goal did the project address?
• Was it made for Java Edition, Bedrock Edition, or a clearly named toolchain?
• What part did you personally plan, build, write, test, or coordinate?
• Which constraints shaped the result, such as device limits, a deadline, accessibility, or multiplayer use?
• What evidence can a reviewer inspect at the creator-controlled source?
• Is the project current, archived, experimental, or no longer maintained?

These are editorial prompts, not proof of compatibility or quality. Keep version, performance, download, and gameplay claims tied to their own current source or test record.

Show decisions, not only outcomes

Use material you own or have permission to publish to explain one or two decisions inside each project. You might compare an early layout with the final route, explain why a palette changed, or describe how player feedback altered the scope. The point is to reveal your process without turning the page into a step-by-step installation guide or a technical claim you cannot support.

Link to the creator-controlled project page when a reviewer needs the current release or full project record. Do not rehost files, copy another creator's gallery, or treat a public link as permission to reuse its media.

Keep the rights boundary visible

The current Minecraft EULA distinguishes original creator work from Minecraft-owned content and points creators to current Usage Guidelines. That is a general official rights boundary, not individualized legal advice and not permission for any third-party asset.

This portfolio page should identify your work and provide context. Detailed source attribution, permission, and license-record keeping belong to the separate credits and licensing workflow, not inside every project narrative.

Final portfolio review

Before sharing the portfolio, check that every project has a clear purpose, an honest role statement, an edition or toolchain boundary, a current source route, and only media you may publish. Remove duplicated projects that prove the same skill. Keep the strongest example and use the saved space to explain the decisions behind it.

Minecraft Java memory optimization

FerriteCore is designed to reduce Minecraft's memory use, not to guarantee a specific FPS gain or prevent every crash. Install the file for your exact Minecraft version and loader, then compare the same profile and world after an identical warm-up period.

Choose a FerriteCore version on Modrinth

Download FerriteCore 9.0.0

MineBrush attached the unmodified creator-published 9.0.0 files downloaded from Modrinth. Select only the loader used by your profile. The MIT notice is included beside the files; check the creator versions page for later builds and older Minecraft releases.

Who should consider FerriteCore?

FerriteCore is most relevant when a Java profile, modpack, or dedicated server uses more RAM than expected. It can be useful on both clients and servers. It is not a substitute for finding a memory leak, allocating a sensible heap, removing duplicate mods, or fixing an incompatible Java version.

Match the file before installing

Install FerriteCore

1. Back up the launcher instance, configuration, and any world used for testing.
2. Close Minecraft or stop the server completely.
3. Download the file from the creator's official versions page and verify the Minecraft and loader labels.
4. Move the single .jar into that instance's mods folder without unzipping it.
5. Start the matching loader profile and verify the mod loads without an early error.

How to measure RAM use fairly

Memory readings move constantly, so one number is not enough. Use the same profile, Java build, JVM arguments, maximum heap, window state, world copy, route, view distance, resource packs, and test duration.

1. Restart the computer or close unrelated heavy applications if they would distort both runs.
2. Launch the baseline profile without FerriteCore, open the same world, follow the same route, and wait the same number of minutes.
3. Record the configured maximum heap separately from used heap and total process memory.
4. Close the game, add FerriteCore, and repeat the exact sequence.
5. Run each condition more than once. Compare the range and median rather than the best single result.

What to check besides the RAM number

• Startup completes without loader or mixin errors.
• The same world saves, exits, and reopens normally.
• Menus, model loading, chunk travel, and resource reloads behave as before.
• The operating system is not swapping memory to disk during either test.
• A lower used-heap reading does not come with new crashes or broken visuals.

Troubleshooting

• Crash before the title screen: verify loader, Minecraft version, Java version, and duplicate jars.
• No obvious memory change: repeat after the same warm-up and workload; a small vanilla profile may show less visible benefit than a large modpack.
• Conflict appears in a modpack: test FerriteCore with the loader, then add groups of mods until the conflict returns.
• Memory still climbs: capture a reproducible timeline and inspect logs or a heap profile; FerriteCore cannot fix every leak.

Update or roll back

Stop the profile, keep the previous jar outside the mods folder, add one replacement, and repeat the same world-open, save, exit, and restart checks. If the result regresses, restore the known-good file and the matching backup. Avoid changing FerriteCore, Java flags, and other optimization mods in the same test.

Bottom line

FerriteCore is a focused memory optimization, so evaluate it with memory evidence and stability checks—not a vague promise that Minecraft will become faster. MineBrush verified the current creator pages and license but did not benchmark every device, server, modpack, or world.

Sources checked

• FerriteCore versions on Modrinth
• FerriteCore 9.0.0 Fabric release record
• FerriteCore source repository

Minecraft Java performance mod

Lithium optimizes Minecraft game logic; it is not a shader, texture pack, or graphics driver. Install the build that matches both your Minecraft version and mod loader, then test a copied world under the same conditions. A higher FPS counter alone does not prove Lithium is working because its main target is simulation work such as entity, block, and world logic.

Choose a Lithium version on Modrinth

Download Lithium 0.25.3 for Minecraft 26.2

MineBrush attached the unmodified creator-published release files downloaded from Modrinth. Choose only the loader used by your profile. The LGPL license is included beside the files; the creator versions page remains the authority for newer or older builds.

Choose the right Lithium file

Install Lithium without mixing profiles

1. Close Minecraft and your launcher.
2. Open the instance that contains the matching Fabric or NeoForge loader. Do not use the global game folder if your launcher keeps separate instances.
3. Place the single Lithium .jar in that instance's mods folder. Do not unzip it.
4. Start the same loader profile and confirm Lithium appears in the latest log or your loader's mod list.
5. Open a copy of a known world before touching the only save you care about.

For a dedicated server, stop the server before changing the mods folder and keep the previous jar outside that folder. The official Lithium repository says clients are not required to install Lithium simply because the server uses it, but every wider modpack still needs its own compatibility test.

What Lithium can improve — and what it does not promise

Lithium is built to reduce the cost of game-logic work while preserving vanilla behavior. That can matter when a world is busy with entities, block updates, chunk activity, redstone, farms, or server ticks. It does not replace Sodium, a GPU driver, more RAM, a faster network connection, or a fix for a broken mod.

• Good measurement: the same world copy, route, entity count, render settings, view distance, Java build, JVM flags, and warm-up time.
• Useful server signal: tick time or MSPT during a repeatable workload, not only the player FPS counter.
• Useful client signal: frame-time consistency while the same simulation is running, alongside the game log.
• Weak evidence: one screenshot taken in different locations or immediately after startup.

A 10-minute stability test

1. Back up the profile and world.
2. Run the baseline without Lithium and record startup, memory, frame-time or tick-time observations.
3. Add only Lithium and repeat the same route.
4. Exercise redstone clocks, mob farms, portals, chunk borders, scheduled block ticks, saving, quitting, and reopening.
5. Check the log for mixin, loader, or compatibility warnings before adding another optimization mod.

If Minecraft crashes after adding Lithium

• Confirm the jar matches the loader and Minecraft version shown in the launcher profile.
• Remove duplicate Lithium jars and old versions from the same mods folder.
• Test Lithium alone with the loader, then restore other mods in small groups.
• Read the first meaningful error in latest.log or the crash report; the last mod name on screen is not always the cause.
• Reproduce the issue without Lithium in the same world copy before reporting a compatibility bug.

Update or remove Lithium safely

Stop the game or server, back up the world and configuration, remove the old Lithium jar, and add one matching replacement. If you roll back, restore the known-good jar and repeat the save/restart test. Never keep two Lithium versions active at the same time.

Bottom line

Use Lithium when game-logic performance is the problem and you can test it with a repeatable workload. Match Minecraft and loader first, change one component at a time, and keep the previous profile ready. MineBrush verified the creator-controlled release information but did not run every modpack, server, world, or hardware combination.

Sources checked

• Lithium versions on Modrinth
• CaffeineMC Lithium repository and installation notes
• Lithium support policy

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.

What Xaero’s Minimap is good at

A minimap is most useful when it removes small navigation friction without taking over the screen. Xaero’s Minimap keeps a compact view of nearby terrain available while you build, explore or travel between bases. Its waypoint system is the practical centre of the experience: mark a portal, a village, a project or a safe route, then keep those locations separate between worlds and dimensions.

The project offers more than one visual preference: map size, zoom, position, shape and colour modes can all be adjusted. Start small. A map that is too large or too busy becomes another interface competing with the game.

A calm first setup

If you also need a persistent full-screen record of explored terrain, add Xaero’s World Map as a separate companion after the minimap is stable.

1. Install the release for your exact game version and loader. The official project provides builds for Fabric, Forge, NeoForge and Quilt.
2. Open the settings before your first long session. Choose a corner that does not obscure your hotbar, quest UI or other mods.
3. Create only useful waypoints. Give them names that still make sense in a month: “Nether portal — east” is better than “base 2”.
4. Test in a familiar world. Check zoom and terrain shading while you already know where you are.

MineBrush recommendation: keep map information readable before adding more information. Navigation is faster when every marker has a purpose.

Waypoints without creating visual noise

Waypoints are powerful because they turn a personal world into a legible network of places. Use a short naming convention and reserve colours for categories: one for home, another for portals, a third for projects. If a marker has done its job, hide it rather than keeping a permanent row of symbols on the horizon.

For multiplayer, ask whether shared coordinate displays fit the server’s rules. Some communities welcome free navigation; others prefer exploration, PvP or event rules that limit radar and cave information.

Full edition and fair-play edition

The project also publishes a separate fair-play edition. Its purpose is simple: make the tool more suitable for competitive play where cave maps and entity radar would create an advantage. Pick the edition that matches the server you are joining, rather than trying to make one set of defaults fit every community.

Server owner notes

The official project documents server-side controls for how particular minimap features are available. If you operate a server, explain your minimap policy near the rules and test it with the exact loader and version your players use. Clear expectations work better than surprising players after they have already built a workflow around a map.

Where to download safely

Use the official Xaero’s Minimap page below. Select a release whose Minecraft version and loader match your instance, then keep the download page bookmarked for updates. Avoid random mirrors: release notes and compatibility information belong with the official project.

Editorial note

The cover on this page is an original MineBrush editorial illustration about navigation and exploration. It is not an official Xaero’s Minimap screenshot or project asset. MineBrush links to the official project for the current files and technical details.

Official and creator sources

• Creator project: xaeros minimap

These links identify the official or creator-controlled evidence checked on August 28, 2026. MineBrush has not treated an unverified runtime result, device outcome, or third-party configuration as guaranteed.

Sodium replaces parts of Minecraft: Java Edition's client renderer. Its job is rendering performance and frame-time stability—not server tick speed, networking, world generation, or memory tuning by itself.

For Minecraft 26.2, the latest creator-listed stable release checked on August 28, 2026 is Sodium 0.9.1 for both Fabric and NeoForge. The newer 0.9.2-alpha.4 files are testing builds. Start with stable unless you specifically need an alpha change and can report a reproducible renderer issue.

Choose the exact Sodium file

The exact 0.9.1 records declare no required project dependencies. That does not mean a Fabric or NeoForge profile can launch without its loader. Install the loader first, then use only the Sodium file made for that loader.

Do not put Fabric and NeoForge Sodium files in the same instance. Sodium is client-side; a dedicated server does not need this renderer mod.

Stable versus alpha

The creator also publishes 0.9.2-alpha.4 for Minecraft 26.2. Its release note asks players to test a new terrain-buffer allocation system and report frame-rate stability issues. That is a testing request, not a promise that alpha is faster or safer on every PC.

If you test alpha, clone the working profile, keep the 0.9.1 JAR and config, and change only Sodium. The Fabric alpha record and the matching NeoForge entry must remain clearly labeled alpha. Never overwrite a stable modpack profile just to chase an unmeasured improvement.

Install Sodium safely

1. Confirm the profile says Minecraft 26.2 and identify its loader.
2. Close Minecraft and the launcher process that owns the instance.
3. Back up the profile or create a copy for testing.
4. Remove duplicate or wrong-loader Sodium files from the active mods folder.
5. Add the exact stable Fabric or NeoForge JAR.
6. Launch to the title screen, open Video Settings, then load a copied world.
7. Save, close, reopen, and repeat the same short route before adding shaders or renderer extensions.

MineBrush has not launched these files. This is an evidence-bounded install and comparison procedure based on the creator records.

Start with a clean renderer baseline

Use default Sodium settings first. Disable shaders and third-party resource packs for the initial pass. Record resolution, fullscreen state, graphics preset, render distance, simulation distance, frame-rate cap, GPU, driver, and every renderer add-on.

Walk the same route twice. The first pass can include shader compilation or chunk loading that the second pass does not. Compare frame-time feel and visible rendering errors separately from the average FPS number. A higher peak FPS does not help if the profile produces broken geometry or repeated stalls.

Fix a crash before the title screen

• Verify Minecraft is exactly 26.2.
• Confirm the loader matches the JAR filename.
• Remove duplicate Sodium files.
• Test Sodium alone in a copy of the profile before restoring Iris, option-menu extensions, culling mods, or shader packs.
• Keep the first complete exception and mod list; do not report only “exit code 1.”

Fix missing blocks, flicker, or broken item models

Reproduce the same scene with shaders and resource packs disabled. Reset one Sodium option at a time rather than deleting the whole profile. If the issue disappears only when another renderer add-on is removed, record both exact versions and report the smallest working and failing pair.

Do not install a model-fix mod built for another Minecraft version as a blind repair. A screenshot can show the symptom, but the profile tuple and reproducible scene identify where to investigate.

Measure the right bottleneck

Sodium handles client rendering. If frame time is stable but redstone, mobs, or server actions are slow, use a logic/tick investigation. Choose Lithium for logic and tick optimization, not rendering.

If the problem is heap pressure or unusually high memory use, keep that as a separate experiment. Use FerriteCore only for the memory-use branch. Adding three optimization mods at once makes it impossible to tell which change helped or broke the profile.

Update or roll back without losing the baseline

Keep the working JAR, config, and short benchmark route. Update Sodium without changing Minecraft, loader, driver, shader pack, or resolution in the same pass. If the new build regresses, restore the previous JAR and config together and repeat the route.

Sodium FAQ

Does a server need Sodium?

No. The creator lists Sodium as client-side and unsupported on the server.

Should I install 0.9.1 or 0.9.2-alpha.4?

Use 0.9.1 for the stable Minecraft 26.2 route. Use alpha only in a copied testing profile when you need its changes and can tolerate regressions.

Does Sodium guarantee more FPS?

No. The project is designed to improve renderer performance, but the creator states that results vary by hardware and software. MineBrush has not benchmarked this tuple.

Can I combine the Fabric and NeoForge files?

No. Use exactly one JAR for the loader in the active profile.

Creator, license, and sources

Sodium is maintained by CaffeineMC and its current project license is Polyform Shield 1.0.0. That license must not be treated like MIT or another permissive license. Use the creator-owned Sodium project, its version list, and the official wiki. MineBrush does not mirror the JAR or creator media in this rewrite package.

Distant Horizons adds a level-of-detail (LOD) layer for simplified terrain beyond Minecraft’s normal render distance. It can make faraway land visible, but it does not make one file compatible with every game version, loader, shader, server, or graphics setup.

Choose one exact game and loader tuple

The selected version ID is gBf0SaV1. Its primary file is DistantHorizons-3.2.0-b-26.2-fabric-neoforge.jar, listed at 29,705,395 bytes. Those are creator-published metadata values, not a MineBrush artifact inspection.

The creator’s loader note says Minecraft 1.20.6 and newer use combined Fabric/NeoForge files, while 1.20.4 and older use combined Fabric/Forge files. These are separate release families. Do not install the current 26.2 file in 1.21.11, and do not treat an older Forge label as current NeoForge support.

Know which layer you are tuning

Minecraft still renders nearby normal chunks. Distant Horizons builds and displays a simplified distant representation beyond that area. Changing vanilla render distance, Distant Horizons distance, LOD quality, generation, and shader settings affects different parts of the scene.

Start low enough that you can recognize each change. A huge distance number is not automatically a better setup: terrain quality, build time, processor load, graphics memory, storage, and visual seams can all become the limiting factor. The project markets a low-cost long-distance view, but MineBrush has no controlled benchmark for your hardware.

Client-only and server-assisted play are different

The project marks both client and server installation as optional. The creator says a client-only installation can save LODs between sessions as you explore. In the client-plus-server mode, a server running Distant Horizons can send LOD data to connected users who also run the mod when distant generation is enabled on the server.

A client-only result does not prove server delivery. A server component does not replace the compatible client mod. Proxies, plugins, permissions, bandwidth, world-generation mods, and hosting limits remain separate variables that were not tested here.

Check the 26.2 beta’s graphics boundaries

The 3.2.0-b release notes raise the minimum OpenGL version from 3.2 to 3.3. They also add LOD textures for the base Distant Horizons renderer, while stating that Iris shaders render those LODs untextured in this release. The notes say the Auto rendering engine no longer crashes merely because Iris is present, but explicitly selecting Blaze3D can still crash because Iris does not support that path.

Those statements belong only to the checked 26.2 beta. They are not a blanket promise for every Iris version, shader pack, graphics API, or older Distant Horizons release. If shaders matter, record the exact Iris release, shader pack and preset, Distant Horizons rendering engine, GPU, driver, and world scene.

Install in a disposable profile first

1. Confirm the launcher profile is Minecraft Java 26.2.
2. Confirm the profile uses Fabric or NeoForge. Do not place the same JAR in a Forge profile.
3. Open the creator’s versions page and select version ID gBf0SaV1.
4. Place the JAR in that profile’s mods folder and start with shaders and unrelated renderer mods disabled.
5. Use a disposable profile or copied world. Reach a familiar location before raising LOD distance or CPU load.
6. Change one Distant Horizons setting at a time and keep the last-known-good profile configuration.

For a general Fabric installation route, use the MineBrush Fabric mods guide. This page owns the Distant Horizons release, LOD, side, and shader boundaries.

Run a small acceptance route

1. Launch the profile and confirm it reaches the menu without a loader error.
2. Open a familiar test world and wait in one known location.
3. Confirm normal nearby chunks first, then observe whether distant LODs appear.
4. Save, exit, restart, and revisit the same view before claiming that LOD data persists.
5. If multiplayer matters, record client-only behavior separately from a deliberately configured Distant Horizons server.
6. If shaders matter, repeat the exact route first without a shader, then with one exact Iris and shader-pack tuple.

Troubleshoot the first failed boundary

Performance remains hardware-specific

Do not copy a creator screenshot’s distance or another player’s memory allocation into your profile and call it safe. A useful comparison needs the same hardware, Java runtime, Minecraft and mod tuple, world, camera route, vanilla and LOD settings, shader state, warm-up, and repeated measurements.

Without that controlled tuple, FPS, frame time, RAM, VRAM, server tick cost, bandwidth, and latency remain unknown. Lowering one setting is a diagnostic step, not a guaranteed fix.

Creator-controlled sources

• Distant Horizons project
• Distant Horizons 3.2.0-b for Minecraft 26.2
• Official versions list
• Creator-linked source repository
• Distant Horizons wiki

Rights and evidence: The software is labeled LGPL-3.0-only. That label does not establish reusable rights for every icon, gallery image, screenshot, logo, or video. MineBrush has no local creator JAR or original screenshot for this article and should link to the official versions route rather than mirror files.

A Fabric install works when the whole profile agrees: Minecraft version, loader, mod file, dependencies, instance folder, and client/server scope. Get that tuple right once and most “the mod does nothing” problems disappear before launch.

Quick answer

Create or select a separate Minecraft Java profile, install Fabric Loader for the exact game version, and launch that Fabric profile once. Download a mod release that explicitly supports both that Minecraft version and Fabric, add every required dependency for the same version, and place the intact .jar files in that profile's mods folder. Start with one mod plus its dependencies, use a disposable world, and read the first loader error before swapping files.

Write down the compatibility tuple

Do not choose a file from the project title alone. A single project page can contain multiple game versions, loaders, and release channels. Open the exact file entry and record:

Fabric's player documentation says mods must target Java Edition, the Minecraft version you intend to play, and Fabric rather than another loader. It also notes that the majority of mods require Fabric API. “Majority” is not “every”: the exact mod release decides which libraries are required.

Install Fabric Loader for the official launcher

1. Run the intended vanilla version first. Reach the title screen and close both Minecraft and the launcher. This separates a base-game problem from a loader problem.
2. Use the installer from Fabric's official site. Choose the same Minecraft version you recorded. With the official launcher, keep Create Profile selected.
3. Follow the OS-specific Fabric page. Fabric documents a Windows installer route and universal .jar routes for macOS and Linux. Do not copy an operating-system workaround from an unrelated launcher.
4. Select the new Fabric profile and launch it once. Reach the menu, then close the game. At this point you have proved only that the loader profile opens—not that a mod works.

Prism Launcher, the Modrinth App, CurseForge, and other launchers can manage loaders per instance. Use that launcher's current instance controls instead of mixing its folders with the official launcher's global directory.

Add the mod and its real dependencies

1. Open the creator's release page and filter for the exact Minecraft version and Fabric.
2. Read the dependency and environment fields on that exact file.
3. Download required libraries from their official project pages in compatible branches.
4. Keep normal mod files as .jar files. Do not extract them or rename another loader's build.
5. Open the active instance's mods folder and add one mod plus only its required libraries.

Default mods-folder locations

Those are the default locations listed in Fabric's installing-mods guide. A custom Game Directory or launcher instance overrides them. If Fabric starts but the mod is absent, verify the running profile's directory before downloading anything again.

Use a three-check first launch

1. Menu: the Fabric profile opens without a loader dependency or conflict error.
2. Feature: the mod's documented client feature or test action is present. A Mods menu appears only when the stack includes a mod that supplies one.
3. Save cycle: a disposable world opens, saves, closes, and reopens without a new error.

A successful title screen is not enough for a world-changing mod. Keep the first test separate from your main save, especially when a project adds blocks, items, entities, dimensions, or world generation.

Read the first useful error

When sharing a crash report, remove account tokens, personal paths, IP addresses, and unrelated logs. Preserve the first clear loader requirement and the exact filenames; “latest” is not a reproducible version.

Client and server scope matters

A cosmetic client mod may not belong on a server. A gameplay mod may require the same mod and dependency versions on both sides. A server utility can have a different deployment rule. Use the creator's environment statement for the exact release; do not infer side requirements from another mod in the same category.

Update or remove with a rollback point

Before updating: back up the world and copy the working instance. Replace the old JAR instead of leaving two releases together. Recheck dependencies and launch a copied world first.

Before removing: read the creator's uninstall notes. Removing a client-only interface mod is not the same as removing content stored in a world. If the mod adds blocks, items, entities, dimensions, or generated data, keep the complete backup and test removal on a copy.

FAQ

Does every Fabric mod need Fabric API?

No. Fabric's documentation says the majority do, but the dependency list on the exact mod release is authoritative.

Can I put a Forge or NeoForge mod in Fabric?

Not unless that exact file also explicitly supports Fabric. The same project name and Minecraft version do not make loader builds interchangeable.

Should I unzip the mod JAR?

Normal Fabric mod JARs stay intact in the mods folder. Only open an outer bundle when the creator clearly identifies separate files inside it.

Why does the launcher open without my mod?

The most useful first check is the active instance path. Then confirm the file is for Fabric, the exact Minecraft version, and the correct client/server environment.

What this guide does not verify

MineBrush checked Fabric's current player documentation but did not download or run an installer, mod, dependency, client, or server for this rewrite. Compatibility, configuration, world persistence, networking, conflicts, and performance remain specific to the exact versioned stack.

Official sources checked

• Fabric Documentation: Installing Mods
• Fabric Documentation: Installing Fabric on Windows
• Fabric Documentation: Installing Fabric on macOS
• Fabric Documentation: Installing Fabric on Linux
• Fabric's official installer page

When your profile is ready, browse Minecraft Java mods. Keep resource packs on their separate Java resource-pack workflow.

A resource pack can change Minecraft's textures, models, sounds, fonts, and interface without using a mod loader. The install is quick; choosing the correct file and proving that it works in your actual profile is the part worth doing carefully.

Quick answer

For Minecraft Java Edition, download the resource-pack ZIP from the creator's official page, keep the ZIP intact, launch the Java profile you plan to use, and open Options → Resource Packs → Open Resource Pack Folder. Put the ZIP in the folder that Minecraft opens, return to the Resource Packs screen, and enable it. Read compatibility warnings, set the order intentionally, and test the pack in a familiar copied world.

Check the file before Minecraft loads it

A polished screenshot does not tell you whether a pack belongs in your profile. Make these checks on the exact release page before downloading:

Keep the original filename until the pack is working. Do not turn a Bedrock package, mod JAR, shader pack, or random ZIP into a Java resource pack by renaming its extension.

Install the pack in the active Java profile

1. Launch the intended Java version once. Reach the title screen, then open Options → Resource Packs. This makes the game—not a guessed filesystem path—identify the active profile.
2. Select Open Resource Pack Folder. Mojang's published Java workflow uses this in-game route and places the downloaded ZIP in the folder that opens.
3. Move the creator-supplied ZIP into that folder. Keep it zipped unless the creator clearly says the download is an outer bundle containing a separate installable pack.
4. Return to the Resource Packs screen. If the new entry does not appear, leave and reopen the screen before changing anything else.
5. Enable the pack and read any warning. A version warning is a compatibility signal, not a promise that the pack will fail or work completely.
6. Let Minecraft finish reloading. Large or high-resolution packs may take longer. Avoid repeated clicks or a forced shutdown while resources are reloading.

Use pack order as a controlled test

When several selected packs change the same asset, the order affects the result. Start with the main pack alone. Then add one focused overlay—such as a GUI, crosshair, or item layer—and inspect what changed. If the wrong texture wins, move only that overlay, reload, and compare again.

This one-change-at-a-time rule is much faster than rearranging five packs at once. It also tells you whether an incomplete look is caused by the pack itself, a deliberate overlay, or another selected pack.

Run a useful first test

Do not judge a pack from one screenshot or a five-second spawn check. Open a copied world you know well and walk the same short route after each change:

• daylight terrain with common blocks and foliage;
• water, glass, particles, and several light levels;
• inventory, crafting, chest, signs, and readable text;
• held items, armor, one or two familiar mobs, and the pause menu;
• the same movement route while watching frame pacing, not only the FPS counter.

High resolution, animation, custom models, and companion features can increase memory or GPU load. The label on a pack cannot predict performance on your computer, so compare the same scene before and after enabling it.

Fix the common failure first

Update or remove without losing the working setup

For an update: keep the last working ZIP outside the active folder until the new version passes the same comparison route. Disable the old entry, place the new file, confirm the pack order, and check whether the creator changed requirements or coverage.

For removal: move the pack back to Available or remove its ZIP while Minecraft is closed. A normal resource pack changes presentation rather than world blocks, but companion mods, data packs, and custom server requirements are separate systems. Review those separately before opening an important save.

Compatibility changes with Minecraft releases

Mojang's Java 26.2 release notes declare Resource Pack version 88.0. That number is useful as a concrete reminder that pack metadata moves with the game; it is not a universal version for every Java release. Match the pack to the version you are actually launching instead of copying a number from an unrelated guide.

FAQ

Should I unzip a Java resource pack?

Usually no: Mojang's published install workflow places the ZIP in the Resource Pack Folder. Open an outer download only when the creator clearly says it contains several separately labeled packs or documentation.

Can an older pack still work?

Sometimes parts of it may load, but a warning cannot tell you which renamed, removed, or newly added assets are missing. Use a creator release made for your version when one exists.

Can I use several packs together?

Yes, but prove the base pack first. Add overlays one at a time and record the order so you can reproduce or undo the result.

Why does the pack look different from its screenshots?

The screenshots may use another version, shader, companion mod, pack order, lighting setup, or optional file. Recheck the creator's caption and requirements instead of assuming the ZIP includes every visible effect.

What this guide does not verify

MineBrush checked official installation and release documentation for this rewrite but did not download or run a specific third-party pack. Compatibility, visuals, accessibility, load order, performance, and multiplayer behavior remain specific to the exact pack, Minecraft version, hardware, and selected stack.

Official sources checked

• Minecraft.net: Java resource-pack folder workflow
• Minecraft Java Edition 26.2 release notes
• Minecraft Help: supported Java Edition desktop platforms

Browse Java resource packs or continue with the Iris shader setup guide when the effect you want is lighting rather than texture replacement.