MineBrush local downloads

Choose the file that matches your Minecraft version and mod loader. Each link opens the separate MineBrush download page before DLE serves the attached file.

• Prepare download → — Minecraft 26.2
• Corresponding source and license bundle
• LGPL-3.0 license

MineBrush reviewed the official release records and attachment structure. This exact build was not independently launched in a Minecraft runtime; use a backup and match the listed game version, loader, and dependencies.

What Bobby actually does

Bobby is a client-side Minecraft Java mod by Johni0702 and contributors. When a multiplayer server sends a chunk to your client, Bobby can store that chunk under .minecraft/.bobby. If you later move far enough away that the server stops sending the chunk, Bobby can render its cached copy. The result is a longer visible horizon made from terrain you have already received.

That distinction matters. Bobby does not increase the server's view distance, simulation distance, entity tracking range, or ticking area. Cached terrain is a local visual record, not a live copy of the server. It cannot show an unexplored build, a new player, a changed block, or another update until the server sends current data again.

Choose the exact download

• Resource: Bobby
• Release: 5.2.15+mc26.2
• Minecraft: Java Edition 26.2
• Loader: Fabric
• Environment: client only
• Official version ID: KLiFVFju
• File: bobby-5.2.15+mc26.2.jar, 867,357 bytes

The exact JAR declares Minecraft ~26.2 and Fabric Loader >=0.18.4. It does not declare Fabric API, Cloth Config, Mod Menu, or Sodium as a required external mod file. Do not add a random API just because another Fabric mod needs it, and do not use this JAR in Forge, NeoForge, or Bedrock Edition.

Version 5.2.15 is more than a routine version label. Its creator changelog says it fixes a path-safety issue where a malicious server could overwrite a local world if it could guess the name. MineBrush therefore does not recommend downgrading to 5.2.14 for a Minecraft 26.2 profile.

Install Bobby on Fabric

1. Create a separate Minecraft Java 26.2 instance and launch vanilla 26.2 once.
2. Install Fabric Loader 0.18.4 or newer for that same instance. The tagged source used Loader 0.19.3 during its build, but the released JAR's enforceable minimum is 0.18.4.
3. Close the game and place bobby-5.2.15+mc26.2.jar intact in the active instance's mods folder. Do not unzip or rename its extension.
4. Launch the Fabric profile, join a disposable or familiar server, move through several chunks, disconnect, reconnect, and check the same horizon.
5. Restart the client and repeat the check before trusting the setup in a main modpack.

If your launcher manages separate instances, use its Open Folder command. Copying the file to a global .minecraft/mods folder will not affect an instance that uses a different game directory.

Optional integrations without dependency confusion

Bobby works without three integrations that players often mistake for requirements:

• Cloth Config API: suggested at version 26.2.155 or a compatible release. It supplies the configuration UI plumbing.
• Mod Menu: suggested at version 20.0.0-beta.3 or a compatible release. Used with Cloth Config, it gives you an in-game route to Bobby's settings.
• Sodium: optional, but Bobby's Max Render Distance setting requires Sodium. The exact JAR rejects Sodium older than 0.6.0.

Without Cloth Config and Mod Menu, Bobby still loads and writes config/bobby.conf. The creator source says this file is watched and automatically reloaded when changed. Keep a copy before hand-editing it, use plain values, and change one setting at a time.

Settings that matter

• Enabled: master switch for Bobby.
• Dynamic World Management: separates and can later reconcile caches on servers that use several identically named worlds. Leave it off unless the server topology needs it.
• Disable Block Entities: enabled by default. It avoids loading ticking block entities such as chests in fake chunks.
• Taint Fake Chunks: darkens cached chunks so you can distinguish them from live server chunks.
• Chunk Unload Delay: defaults to 60 seconds and delays unloading outside the current view distance. It does not carry across dimensions.
• Cleanup Unused Regions: defaults to -1, which disables automatic age-based cleanup. 0 cleans after every disconnect; a positive value is a retention period in days.
• Max Render Distance: defaults to 32 and requires Sodium when used to raise the configurable ceiling.
• Singleplayer Server View Distance: defaults to 0, meaning disabled. A nonzero value makes Bobby useful in single-player by overriding the integrated server's view distance and needs a re-login to enable or disable.

Start at defaults. A very large visible horizon can increase disk reads, memory use, upload work to the GPU, and the amount of geometry on screen. Raise distance gradually and compare frame time while standing at the same location. Bobby is not a guaranteed FPS optimization.

Cache location, disk use, and privacy

Multiplayer cache data lives under .minecraft/.bobby for a default instance. A launcher with a custom game directory stores it inside that instance instead. The cache grows as servers send more terrain, so long exploration sessions across several servers can use meaningful disk space.

Use Bobby's cleanup setting or archive old instance data deliberately. Do not share the .bobby folder casually: it can contain cached terrain from places you explored and may expose information about private builds or server routes. Close Minecraft before moving or restoring cache folders, and copy the entire working folder rather than merging unknown files into it.

What cached chunks can and cannot show

• Can show: the last terrain state the server sent to your client.
• Cannot show: unexplored terrain or remote changes that the server has not resent.
• May look stale: builds, doors, redstone, fluids, block entities, and other details can change while their cached copy remains outside live view distance.
• Does not tick: a cached chunk is not a second simulation and cannot keep farms, mobs, or machines running.

If a distant structure looks wrong, move close enough for the server to send the current chunk. Judge correctness after the live chunk replaces the cached view, not while the old visual record is still displayed.

Optional single-player fallback world

The creator documents an advanced feature that can load chunks from an existing single-player world even when the multiplayer server has never sent them. To use it, the folder of the source world—not its in-game display name—must be renamed to bobby-fallback.

Treat this as an expert workflow. Work on a copy, not the only copy of a world. The fallback must match the intended terrain closely enough to be useful, and an old-format world may need optimization from Minecraft's Singleplayer menu. A visually plausible fallback is not authoritative server data.

Dynamic multi-world servers and commands

Proxy networks and servers with identically named worlds can confuse a simple one-cache-per-name model. Bobby's Dynamic World Management starts a new local cache on a world change and can merge caches when enough terrain appears similar. The creator warns that flat worlds may require more movement before the match becomes clear and that an older mixed cache may need cleanup.

The exact release registers client commands under /bobby, including /bobby worlds, /bobby worlds full, /bobby worlds create, /bobby worlds merge <source> <target>, and /bobby upgrade. Do not merge cache IDs from guesswork. List them, back up the entire cache, and use merge only when you can identify source and target.

A repeatable five-minute verification route

1. Start a clean Fabric 26.2 instance with Bobby only.
2. Join a server whose rules allow client render-distance tools and note the server-rendered boundary.
3. Walk a straight route long enough to receive several chunks, then return and increase the client render distance modestly.
4. Disconnect, reconnect, and confirm that previously received terrain appears beyond the current live boundary.
5. Change one block close enough to be live, walk away, then return and confirm the server refreshes it.
6. Restart the client and verify the cache persists, with no new loader warning.
7. Check disk growth under the instance's .bobby folder and set a cleanup policy you understand.

Repeat with Sodium, Cloth Config, and Mod Menu only after the base route passes. Then add the rest of the modpack in small groups. That order separates a Bobby issue from a renderer, UI, or broad pack conflict.

Fix common Bobby problems

• “Incompatible Minecraft version”: use the exact 26.2 file in a 26.2 instance. A similar-looking 26.1 or 1.21.11 build is not interchangeable.
• Game opens but Bobby is absent: confirm the active instance directory, Fabric profile, and intact JAR location.
• No in-game config button: Bobby can still run. Add compatible Cloth Config and Mod Menu only if you want the screen.
• Render-distance slider will not go above 32: the Bobby setting that raises the maximum requires compatible Sodium. Do not use Sodium older than 0.6.0.
• Distant terrain is outdated: cached chunks show the last state received. Move within the server's current view distance to obtain fresh data.
• Disk use keeps growing: back up the cache, set a positive cleanup age, or remove old per-instance cache data while Minecraft is closed.
• Old chunks disappear after a Minecraft update: preserve the cache and run /bobby upgrade only on a backup-aware current setup; the conversion can take time.
• Wrong world appears on a proxy network: stop exploring, preserve all caches, enable and validate Dynamic World Management in a copy before merging anything.
• Frame time becomes worse: lower render distance, keep block entities disabled in fake chunks, and compare the same route without shaders or other render mods.

Update, remove, or roll back safely

Before updating, copy the working instance, config/bobby.conf, and the complete .bobby cache. Replace the old Bobby JAR instead of leaving two versions in mods. Launch a disposable route, reconnect, restart, and only then use the main profile.

To remove Bobby, close Minecraft, remove its JAR, and keep the cache until the unmodded profile has launched correctly. Cached files are local; removing them should not change the remote server. Delete them later only when you are certain rollback is no longer needed.

Download safety, license, and source

The exact JAR and tagged source declare GNU LGPL version 3 or later. Any MineBrush-hosted binary must be accompanied by the full GPL and LGPL notices and the exact corresponding source archive for tag v5.2.15+mc26.2, commit 47868a67f24f2dc2670cbbb22fd3e3363cb152a1. Keep the creator filename and credit intact. Use the normal DLE attachment button so the player reaches MineBrush's separate download page rather than a raw file URL.

Official sources checked

• Bobby on Modrinth — creator-owned project and current release route.
• Bobby source repository — code, tagged source, changelog, settings, commands, and license.
• Bobby issue tracker — current known problems and reproducible reports.

Continue with the right setup

Use the MineBrush Fabric installation guide before touching a main instance. If you want Bobby's extended slider ceiling, compare the Sodium setup guide. For the optional in-game settings route, use the Mod Menu guide.

Quick answer

For Minecraft Java 26.2, install bobby-5.2.15+mc26.2.jar on the Fabric client with Loader 0.18.4 or newer. It re-renders chunks your server already sent and stores them locally; it does not load or simulate unexplored terrain. Begin with defaults, protect the cache, use 5.2.15 for the security fix, and add optional UI or Sodium integrations only after the clean profile passes.

MineBrush local downloads

Each link opens the separate MineBrush download page before DLE serves the attached file.

• ReplayMod 2.6.27 — Fabric
• ReplayMod corresponding source
• GPL-3.0-or-later license

MineBrush reviewed the official release records and attachment structure. This exact build was not independently launched in a Minecraft runtime; use a backup and match the listed game version, loader, and dependencies.

ReplayMod records Minecraft Java sessions as replay data that you can reopen, pause, scrub through and film from a free camera. Instead of trying to fly perfectly while screen recording, you can play first, then build a smooth camera path afterward. The 2.6.27 release has a dedicated Fabric build for Minecraft 26.2.

Download ReplayMod 2.6.27 for Minecraft 26.2

Do not use this JAR on Minecraft 1.21.1, 1.21.11 or 26.1. ReplayMod publishes separate files for those game lines. The 26.2 filename is part of the compatibility check, not decoration.

What ReplayMod can do

• record singleplayer and multiplayer sessions from the client;
• open saved replay files in a dedicated viewer;
• move a free camera through the recorded world;
• pause, change replay speed and jump to another time;
• mark useful moments while recording;
• create position and time keyframes for cinematic paths;
• render normal, stereoscopic or 360-degree output;
• export video or image sequences through FFmpeg.

Install ReplayMod

1. Back up the profile and any existing replay folder.
2. Install Fabric Loader for Minecraft 26.2. MineBrush's Fabric mod guide covers a clean profile.
3. Download replaymod-26.2-2.6.27.jar from the card above.
4. Place the JAR in that profile's mods folder without unzipping it.
5. Launch Minecraft and confirm that Replay Viewer appears on the main menu.
6. Before a long session, record a two-minute disposable world and confirm it saves and opens.

ReplayMod is client-side. The official documentation says it should not be installed on the server. You can record your client perspective on a normal compatible server, subject to that server's rules and any privacy expectations for other players.

Record the first replay

1. Open ReplayMod settings and confirm automatic recording is enabled.
2. Join a world or server. Look for the recording message/indicator.
3. Press M during an interesting moment to add an event marker.
4. Leave the world normally when finished.
5. Wait for the replay-saving message to complete before closing the launcher or killing Java.
6. Open Replay Viewer, choose the new recording and load it.

Navigate a replay

Inside a replay, use the movement keys to fly like a spectator and the mouse wheel to adjust camera speed. The replay controls let you pause time, change playback speed and move the replay cursor. A large jump—especially backward—can take longer because the replay state must be reconstructed.

Right-clicking a visible entity can start spectating it; use the normal sneak key to leave that view. Keybinds can be changed in Minecraft controls, so check the active profile before assuming a documented default is broken.

Build a simple camera path

1. Move the camera to the opening shot.
2. Place the keyframe-timeline cursor at the start and add a position keyframe.
3. Move the timeline cursor forward, fly to the second camera position and add another position keyframe.
4. Add a third point only after the two-point move looks clean.
5. Use path preview to inspect framing and whether the curve clips through blocks.
6. Add time keyframes when the replay action must advance or pause during the camera move.
7. Preview the complete path before opening render settings.

Position keyframes control where the camera travels. Time keyframes control what moment in the replay is shown while it travels. Mixing them up is the classic reason a camera moves beautifully across the wrong ten seconds.

Install FFmpeg for video export

ReplayMod's official documentation requires FFmpeg for video rendering. Use the installation route for your operating system and prefer official or OS-maintained packages. On Windows, ReplayMod's docs explain that ffmpeg.exe can be placed inside the active instance's Minecraft directory. On macOS or Linux, an OS package manager can install FFmpeg and expose it on the system path.

Alternative launchers keep separate instance directories. Installing FFmpeg under a global .minecraft folder does not help if ReplayMod is running in another instance and cannot find the executable.

Render a safe first clip

1. Create and preview a short camera path.
2. Choose the normal/default rendering method.
3. Start with 1280×720 or 1920×1080 rather than a giant 4K/360 job.
4. Use an MP4 default-quality preset for the first test.
5. Pick a short output filename and a folder with plenty of free space.
6. Render ten seconds, play the result, then scale resolution, frame rate or quality.

Where replay files live and how to protect them

ReplayMod stores recordings inside the active Minecraft instance rather than in a cloud account. The exact folder follows the launcher instance, so use Replay Viewer to identify the right profile before copying or deleting files. Back up irreplaceable replays before trimming, renaming in bulk, migrating launchers or updating the mod.

A replay can also contain player names, chat or server activity captured by the client. Review the material and respect server rules and other players before publishing it.

Fix: no replay was recorded

• Confirm the Replay Viewer exists; otherwise the JAR did not load in this profile.
• Check that recording is enabled in ReplayMod settings.
• Make sure the game was closed normally and replay saving had time to finish.
• Check the current instance folder, not another launcher's global directory.
• Review the latest log for write-permission, disk-space or compatibility errors.
• Test without shaders and unrelated camera/render mods before retrying a valuable session.

Fix: ReplayMod cannot find FFmpeg

• Confirm FFmpeg runs on the operating system outside Minecraft.
• Verify that the executable is inside the active instance or available on the system path.
• Check custom command settings for a stale path copied from another computer.
• Avoid spaces and unusual characters in the first test output path.
• Restart the launcher after changing environment paths.

Fix: rendering crashes or produces a black video

• Render a ten-second 720p default-quality clip before retrying the large project.
• Disable shaders, custom render injectors and incompatible camera mods for one test.
• Update the GPU driver and confirm Minecraft can render the replay normally.
• Check free disk space for both temporary frames and the final video.
• Use a standard MP4 preset before experimenting with custom FFmpeg arguments.
• Keep the replay backup before trying repairs; corruption recovery is not guaranteed.

Creator, source and license

ReplayMod is developed by the ReplayMod contributors and released under the GNU General Public License version 3 or later. MineBrush stores the unmodified creator JAR together with corresponding source and license materials for the exact mirrored build.

• Official Modrinth project
• Official ReplayMod documentation
• Official source repository
• Official FFmpeg downloads
• Download corresponding ReplayMod source
• Read the included GPL license

ReplayMod is a community project and is not an official Mojang or Microsoft product. MineBrush is not affiliated with the creator.

MineBrush local downloads

Choose the file that matches your Minecraft version and mod loader. Each link opens the separate MineBrush download page before DLE serves the attached file.

• EMI 1.1.24 — Fabric / Quilt — Minecraft 1.21.1
• EMI 1.1.24 — NeoForge — Minecraft 1.21.1
• Fabric API 0.116.15 — required on Fabric / Quilt
• EMI corresponding source
• EMI MIT license

MineBrush reviewed the official release records and attachment structure. This exact build was not independently launched in a Minecraft runtime; use a backup and match the listed game version, loader, and dependencies.

Quick answer: EMI 1.1.24 is a client-required item and recipe viewer for Minecraft Java 1.21.1. Choose emi-1.1.24+1.21.1+fabric.jar for Fabric or Quilt, or emi-1.1.24+1.21.1+neoforge.jar for NeoForge. Do not put the Fabric file into NeoForge, and do not use the 1.20.1 Forge build in Minecraft 1.21.1. The exact Fabric file also declares Fabric API as required. MineBrush verified the creator records and the embedded manifests, but has not yet completed clean-profile runtime tests.

Exact EMI 1.1.24 files for Minecraft 1.21.1

Both are creator-published Release-channel files dated May 13, 2026. Modrinth marks EMI as required on the client and optional on the server. That means every player who wants the interface needs the mod in their client profile. A server-side copy is not a substitute for the client mod.

The Fabric/Quilt and NeoForge version records list no downloadable Modrinth dependencies, but the file itself is more precise: its fabric.mod.json requires Fabric Loader 0.13.1 or newer and the Fabric API module. The NeoForge file's embedded metadata requires NeoForge. This is why MineBrush checks the archive manifest rather than relying only on the project summary.

What EMI actually does

EMI adds a searchable item index around inventory screens and connects items to their recipes and uses. Its value goes beyond a basic “how do I craft this?” panel:

• Recipes and uses: open the ways to create an item or the recipes that consume it.
• Favorites: pin items and recipes to the opposite sidebar for quick access.
• Craftable mode: narrow the interface to recipes your current inventory can make.
• Recipe trees: break a complex target into crafting steps, base materials, and expected leftovers.
• Recipe-tree crafting: track how many steps remain and expose synthetic favorites for those steps.
• Smart tags: represent ingredient groups such as planks as a meaningful group instead of an unexplained rotating item.
• Recipe defaults: choose which route a tree should use when multiple recipes can create the same output.
• Quick crafting: move available ingredients into supported recipe handlers.
• Runtime JEI compatibility: EMI can run beside JEI, share recipes provided through JEI integrations, and hide JEI's interface.

EMI does not add survival items, make every recipe craftable, or create missing recipes by itself. A mod's recipes must exist and be exposed through a supported integration. Quick crafting also needs the right ingredients and a compatible handler; it is not an automatic resource generator.

What changed in 1.1.24

The 1.1.24 release is a small stability update rather than a feature overhaul. The creator adjusted empty mixin-notification logging, fixed inconsistent crashes related to mixin order—reported mainly on older Fabric 1.19.2 and 1.20.1 profiles—and fixed duplicate application of self-mutation mixins. Those fixes do not prove compatibility with every 1.21.1 modpack, so keep a rollback copy of the previous working profile.

Choose the right loader file

1. Open your launcher profile and read the Minecraft version. It must be exactly 1.21.1 for the files in this guide.
2. Read the installed loader name: Fabric, Quilt, or NeoForge.
3. For Fabric or Quilt, use the filename ending in +fabric.jar and install the compatible Fabric API.
4. For NeoForge, use the filename ending in +neoforge.jar.
5. If the profile says Forge, stop. The exact 1.21.1 release matrix reviewed here has no Forge variant.

Do not rename a Fabric file to “neoforge,” combine the two JARs, or keep both variants in the same mods folder. The loader reads code and metadata inside the archive; changing the visible filename cannot convert it.

Install EMI on Fabric or Quilt

1. Create a separate Minecraft 1.21.1 Fabric or Quilt test profile.
2. Install the appropriate loader and Fabric API for that profile.
3. Close Minecraft and the launcher instance before changing files.
4. Open the instance's own mods folder, not a different global installation.
5. Add emi-1.1.24+1.21.1+fabric.jar as a file. Do not extract it.
6. Start the profile and confirm EMI appears in the loaded-mod list or inventory interface.
7. Open a disposable world, open inventory, search for an item, and test one recipe and one use.

If the loader reports a missing fabric dependency, that refers to Fabric API. Installing a different EMI build will not solve that message. Match Fabric API to Minecraft 1.21.1 and the exact profile.

Install EMI on NeoForge

1. Create a separate Minecraft 1.21.1 NeoForge test profile.
2. Close the game, then open that instance's mods folder.
3. Add emi-1.1.24+1.21.1+neoforge.jar without extracting or renaming it.
4. Remove any Fabric, Quilt, Forge, older EMI, or duplicate EMI file from this test profile.
5. Launch, confirm EMI is recognized, and prove the inventory index and one recipe in a test world.

The embedded NeoForge manifest carries a permissive lower-bound declaration, but the file record itself is specifically for Minecraft 1.21.1. Use a NeoForge 1.21.1 profile; do not treat that lower bound as permission to run the file on a different Minecraft line.

Default controls that matter

EMI keeps its bindings in its own configuration. The exact 1.21 branch source defines these defaults:

If a shortcut opens another mod's screen or does nothing, change it in EMI's own config interface. Do not assume the vanilla Controls screen contains every EMI bind. Also remember that mouse actions are context-sensitive: left-clicking an ordinary inventory slot is not the same as left-clicking an EMI entry or recipe control.

Find an item and read its recipes

1. Open inventory and select the sidebar page that contains the item index.
2. Press Ctrl+F or click the search field.
3. Search by a clear part of the item name. EMI can also be configured to include tooltip text, mod names, and tags.
4. Hover an item and press R for recipes.
5. Press U for uses.
6. Check the workstation shown by the recipe. A shaped crafting recipe, furnace recipe, and modded machine recipe are not interchangeable.
7. If several routes exist, inspect each tab before choosing a default for a recipe tree.

Search behavior is configurable. In the exact branch source, tooltip searching is enabled by default, while automatic mod-name and tag searching are disabled by default. If results seem too broad or too narrow, inspect EMI search settings before assuming items are missing.

Use favorites and craftable mode

Hover an item and press A to pin it. Favorites are useful for repeated materials, but recipe favorites are more powerful: they can preserve a specific recipe route and participate in quick crafting. If a favorite appears but cannot craft, verify the workstation, recipe handler, ingredient alternatives, and quantities.

Craftable mode focuses on recipes EMI believes the current inventory can satisfy. Treat it as a planning filter, not a guarantee. Ingredients can be locked in another container, a machine can require energy or fluid, or an integration can expose a recipe without supporting automatic filling. Test one vanilla recipe first to separate a broken install from a mod-specific handler gap.

Build and use a recipe tree

A recipe tree answers a different question from a normal recipe screen: “What are all the steps and base materials for this final target?” It can calculate intermediate crafts, leftovers, and alternate recipe choices.

1. Open the target item's recipe.
2. Use the recipe-tree button if it is visible. The exact source enables recipe-tree controls by default; unbound tree shortcuts can remain unset.
3. Review the selected recipe for every ingredient with alternatives.
4. Set a preferred default when the tree chooses an unwanted production route.
5. Read the base-cost total before gathering materials.
6. Use synthetic favorites or step tracking only after the tree's choices look correct.
7. Recalculate after changing recipe defaults or adding/removing integration mods.

A tree is only as complete as the recipes registered in the current profile. If a mod hides a machine recipe from EMI, the calculated cost can stop early or choose another route.

EMI with JEI: when and why

The creator documents runtime JEI compatibility: install JEI beside EMI, and EMI can consume recipes supplied through JEI while JEI's interface is hidden. This is useful when a mod exposes recipes only through JEI integration.

JEI is optional, not a base EMI dependency. Add it only to solve a verified integration gap, match it to Minecraft 1.21.1 and the correct loader, and test the pair in a copy of the profile. If recipes disappear after adding JEI, compare logs and test EMI alone before adding more compatibility add-ons.

Client and server expectations

Official metadata says the client is required and the server is optional. For an ordinary server, install EMI on the player's client to get the interface. A server may carry EMI for a controlled modpack or integration profile, but that does not make the item panel appear for clients without EMI.

On multiplayer, recipe visibility can still depend on the server's mod list, data packs, configuration, permissions, and recipe synchronization. Do not use cheat-mode item actions unless the world or server rules allow them. EMI's configuration has cheat actions, but the default cheat behavior and actual permission outcome depend on game mode and context.

Troubleshooting by symptom

Update without wrecking a modpack

1. Copy the entire launcher instance, including mods, configs, saves, and logs.
2. Record Minecraft, loader, EMI, Fabric API if applicable, JEI if present, and integration-mod versions.
3. Remove the old EMI JAR; do not leave both versions in the folder.
4. Add one exact new loader-matched file.
5. Launch a disposable world and test index, search, R/U, favorite, one quick craft, and one recipe tree.
6. Open the real world only after the copy passes.

For rollback, close the game, restore the previous JAR and matching dependency set, then restore the copied config if the new version rewrote it. Never delete the known-good instance until the updated profile has survived a full restart.

Download and license

EMI is MIT-licensed, and the creator repository's license permits redistribution when the copyright and permission notice is included. MineBrush can host the two exact JARs as separate DLE attachments only after same-day source recheck, archive and security inspection, exact manifest comparison, clean-profile runtime tests, and inclusion of the MIT notice. The download button must open MineBrush's separate DLE download page—not a raw file URL.

Until those gates pass, use the official EMI project on Modrinth. Never package Fabric API or JEI inside an “EMI bundle.” Each dependency or optional compatibility mod needs its own official source, license review, version match, and attachment decision.

Frequently asked questions

Is EMI available for Minecraft 1.21.1 Forge?

Not in the exact 1.1.24 release set reviewed here. Minecraft 1.21.1 has Fabric/Quilt and NeoForge files. The Forge 1.1.24 file targets Minecraft 1.20.1.

Does EMI need Fabric API?

The exact Fabric/Quilt JAR declares the Fabric API module as required. The creator also describes standard Fabric/Quilt APIs as the only dependency family for that route.

Does EMI need JEI?

No. JEI is optional. Run it beside EMI only when you need recipes supplied through a JEI integration; EMI can hide JEI's interface while sharing those recipes.

Can I install EMI only on the server?

No, not if you want the interface. Official metadata marks the client as required and the server as optional.

What keys show recipes and uses?

In the exact 1.21 source defaults, R shows recipes and U shows uses. Left- and right-click also work in supported EMI contexts.

How do I hide or restore EMI?

The default visibility toggle is Ctrl+O. You can also confirm that EMI is enabled and that the index sidebar page is selected.

How do I favorite an item?

Hover the item in a supported EMI screen and press A. The favorite appears on the sidebar opposite the recipe index.

Why does R open another mod?

The key is conflicting. Change the binding in EMI's own configuration; not every EMI bind is managed through Minecraft's vanilla Controls screen.

Why are some recipes missing?

Confirm that the recipe exists in the current mod/version and that an EMI integration exposes it. If the mod relies on JEI integration, a matching JEI install beside EMI may supply it.

Does EMI let me cheat in items?

EMI has configurable cheat actions, but game mode, permissions, and server rules control whether they can work. Recipe viewing itself does not grant items.

Can I use the Fabric JAR on Quilt?

The exact Modrinth version lists Fabric and Quilt. Use a Quilt profile capable of its Fabric API dependency and test the exact combination before adding it to a large pack.

Can I keep EMI and JEI interfaces visible together?

The creator's documented runtime compatibility intentionally hides JEI while sharing recipes. Treat EMI as the visible interface in that setup.

Where is EMI's config?

Use the EMI config button or configuration screen in the interface. The exact source enables that button by default. Back up the instance before editing config files manually.

Does EMI improve FPS?

EMI is a recipe and item viewer, not a performance mod. Its batched UI renderer may be faster, but the source warns that it can conflict with shaders or other mods.

Is EMI a Bedrock add-on?

No. It is a Minecraft Java mod distributed as loader-specific .jar files.

Bottom line

EMI is most useful when the article and download route keep the exact profile clear: Minecraft 1.21.1, EMI 1.1.24, then either Fabric/Quilt plus Fabric API or NeoForge. Once installed, learn R, U, A, search, favorites, craftable mode, and recipe trees before adding JEI or more integrations. If a feature fails, reproduce it with one vanilla recipe and one clean profile first. Browse MineBrush's Minecraft Java mods or follow the Fabric installation checklist for the loader-and-dependency workflow.

MineBrush local downloads

Choose the file that matches your Minecraft version and mod loader. Each link opens the separate MineBrush download page before DLE serves the attached file.

• Storage Drawers 19.1.1 — NeoForge — Minecraft 1.21.10
• Corresponding source snapshot
• MIT license
• Build notice

MineBrush reviewed the official release records and attachment structure. This exact build was not independently launched in a Minecraft runtime; use a backup and match the listed game version, loader, and dependencies.

Storage Drawers is built for high-volume materials you want to recognize and move quickly. Instead of opening a chest and searching slots, you see the stored item on the drawer face and use direct clicks to deposit or withdraw it. Drawer blocks trade variety per block for clean bulk storage, then upgrades and controllers let the system grow with a base or factory.

How drawer controls work

• Right-click: inserts the held stack when the drawer accepts that item.
• Double right-click: deposits matching items from your inventory into the drawer.
• Left-click: removes one item.
• Shift + left-click: removes a full stack.
• Shift + right-click with an empty hand: opens the drawer interface used for detailed management in current branches.

Test these controls before building a wall around the system. A keybind or interaction mod can intercept clicks, and a server may change behavior through configuration.

Pick the right drawer

Drawer layouts hold different numbers of item types and assign capacity accordingly. A one-slot drawer is ideal for a bulk material such as cobblestone. Multi-slot drawers fit families of items such as logs, crops, or mob drops. Compacting and framed options, when present in the selected build, serve different organizational or visual jobs. Use the in-game recipe data for exact recipes and capacity values because configs and branches can change them.

Requirements and installation

• Minecraft Java Edition 1.21.10.
• A matching NeoForge loader build.
• StorageDrawers-neoforge-1.21.10-19.1.1.jar.

1. Back up important worlds, then close Minecraft and the launcher.
2. Create or select a Minecraft 1.21.10 NeoForge instance and run it once.
3. Open that instance's mods folder.
4. Add the exact NeoForge JAR and remove older or wrong-loader Storage Drawers files.
5. Launch and verify version 19.1.1 in the installed-mod list before opening a valuable world.

The exact JAR declares no additional required mod and contains no nested library JAR. Historical instructions for Minecraft 1.8–1.12 mention Chameleon and should not be carried into this 1.21.10 setup.

Dedicated-server setup

1. Stop the server and back up its world, configs, and mod list.
2. Confirm Minecraft 1.21.10 and a compatible NeoForge version.
3. Put the same Storage Drawers 19.1.1 JAR in the server mods folder.
4. Install the same content build on every client.
5. Start the server and check the latest log before placing drawers in the main world.

Use a disposable test area to verify deposits, withdrawals, upgrades, controller range, chunk boundaries, and automation under the server's actual configuration.

Upgrade guide

The official project description lists a broad upgrade set. Availability, tier values, and recipes must be confirmed in the selected build.

• Capacity upgrades: increase how much a drawer can store.
• One-stack downgrade: limits capacity when a small buffer is preferable.
• Void upgrade: destroys overflow after the drawer is full. Use it only for materials you are willing to lose.
• Redstone upgrade: exposes fill information to redstone systems.
• Fill-level indicator: makes capacity easier to read visually.
• Hopper upgrade: adds item-transfer behavior appropriate to automated systems.
• Magnet upgrade: pulls eligible nearby item entities according to its rules and range.
• Illumination upgrade: adds a light-emitting role to the drawer.
• Conversion and balanced-fill upgrades: adjust capacity conversion or how multi-slot drawers accept items.
• Portability and creative upgrades: cover specialized movement or unlimited-capacity workflows; review tooltips and server rules before use.

Never add a void upgrade to a production line until overflow behavior is tested with a harmless item. Filters, locks, upgrades, and automation order can determine what gets destroyed.

Drawer Controller basics

A Drawer Controller provides a central interaction point for a connected drawer network. Players can deposit matching inventory items through the controller, and compatible automation or storage systems can treat the controller as the network access point. Exact range, connection rules, trim behavior, and chunk-loading behavior depend on the selected version and configuration.

1. Build a small group of drawers and add known test items.
2. Place and connect the controller according to current tooltips and recipe data.
3. Test manual bulk deposit at the controller.
4. Test input and output with one hopper or pipe before connecting a full factory.
5. Cross a chunk boundary deliberately and verify the result after a server restart.

Framed drawers and appearance

Framed drawers can be styled using block materials supported by the current recipe or interface. Capture the exact interaction in the selected build before publishing a step-by-step recipe. Resource packs can change textures without changing storage logic, while shader or rendering mods can affect labels and icons.

Automation and storage-network integration

The project describes controller integration with systems such as Applied Energistics 2 and Refined Storage. Treat this as supported project intent, not a guarantee for every combination of versions. Match all mods to Minecraft 1.21.10, test import and export limits, define storage priorities, and protect against loops. A drawer with a void upgrade can silently delete items if a network routes overflow into it.

Common problems and fixes

Right-click does not deposit

Confirm the drawer is unlocked or assigned correctly, the held item matches, and capacity is available. Test with an empty hand and a basic item. Temporarily disable interaction/keybind mods and compare behavior on a clean profile.

Shift-right-click UI is missing or invisible

Verify the control, empty-hand requirement, and client version. Test without shaders, custom GUI packs, or rendering mods. An older official issue reported an invisible shift-right interface on an earlier 1.21.1 build; use that only as an isolation clue, not proof of a 19.1.1 bug.

The controller cannot see a drawer

Check connection blocks, controller range, chunk boundaries, locked states, and whether both chunks are loaded. Reduce the network to the controller and one adjacent drawer, then expand one block at a time.

A pipe will not insert or extract

Test the same side with a vanilla hopper, verify side and filter rules, then check the automation mod's compatibility for these exact versions. Older issue reports describe automation edge cases, including void/discard behavior, but do not establish a defect in this release.

The game crashes after an update

Keep only one Storage Drawers JAR, confirm Minecraft and NeoForge compatibility, and read the first meaningful error in latest.log or the crash report. Restore the backup if the updated build changes registries or saved data unexpectedly.

Safe updates and removal

Back up the world and configuration. Read the exact upstream changelog, remove the old JAR, and test the new build on a copy. Before uninstalling, empty drawers and remove Storage Drawers blocks where practical. Removing a content mod can delete its blocks, items, upgrades, and stored inventory from saved data.

Official download and source

Verify the selected record on the official Storage Drawers file page. Code and license information are available in the official source repository. MineBrush has acquired and statically verified the exact CurseForge JAR, pinned source, and MIT notices, but has not malware-scanned or runtime-tested it.

Quick answers

How do I deposit everything that matches? Double right-click the drawer.

How do I take a stack? Shift + left-click the drawer face.

Can one controller connect unlimited drawers? Do not assume that. Range and connection rules belong to the exact build/configuration and should be tested.

Is the local download ready? The local bundle passes identity, checksum, metadata, source, and MIT-notice checks. Keep it disabled on the live site until approved malware scanning, clean client/server launch, and staging QA pass.

MineBrush local downloads

Choose the file that matches your Minecraft version and mod loader. Each link opens the separate MineBrush download page before DLE serves the attached file.

• Comforts 16.0.0+26.2 — NeoForge
• Comforts source JAR
• Comforts exact source snapshot
• Embedded SpectreLib source
• Comforts LGPL-3.0 license
• SpectreLib LGPL-2.1 license
• Bundled notices

MineBrush reviewed the official release records and attachment structure. This exact build was not independently launched in a Minecraft runtime; use a backup and match the listed game version, loader, and dependencies.

Comforts is a focused utility mod for players who explore far from home, travel between bases, or want more control over the sleep cycle. It adds sleeping bags that do not replace your existing spawn point and hammocks that can advance daytime to night. Both item families come in 16 Minecraft dye colors.

What sleeping bags and hammocks do

• Sleeping bag: provides portable sleep without setting a new respawn point. Your normal bed remains the place you return after death.
• Hammock: provides the opposite time-shift use case, allowing daytime to advance toward night when its world and configuration conditions are met.
• Colors: both families are available in the standard 16 dye colors, which is useful for player kits or team storage.
• Configuration: server owners can adjust behavior such as auto-use, the Well Rested effect, sleepiness, hammock-at-night behavior, break chance, debuffs, and insulated sleeping bags.

Comforts does not replace Minecraft beds. Keep a bed at a safe base if you need to establish a respawn point.

Requirements

• Minecraft Java Edition 26.2.
• A NeoForge build made for Minecraft 26.2.
• comforts-neoforge-16.0.0+26.2.jar.

The exact JAR declares no separate required library mod. It embeds SpectreLib 0.22.0+26.2 through JarJar, so players should not add a second SpectreLib download for this build. Do not copy dependency advice from a different Minecraft version or loader.

Install Comforts on a client

1. Back up important worlds and close Minecraft and the launcher.
2. Create or select a clean Minecraft 26.2 NeoForge profile.
3. Run that profile once, then close the game.
4. Open the profile's mods folder. This must be the instance folder used by the selected launcher, not automatically the global Minecraft folder.
5. Add the exact Comforts NeoForge JAR. Remove older Comforts copies and any Fabric or Forge variant.
6. Start the game and confirm Comforts appears in the installed-mod list before loading a valuable world.

Install Comforts on a server

1. Stop the server and back up its world, configuration, and mod list.
2. Verify that the server uses Minecraft 26.2 and the matching NeoForge generation.
3. Place the same Comforts version in the server's mods folder.
4. Install the matching build on every connecting client.
5. Start the server, review the latest log for dependency or registry errors, then test with a temporary sleeping bag and hammock away from the main base.

Keep client, server, Minecraft version, loader family, and mod version aligned. A client-only installation is not a reliable multiplayer setup for content that adds blocks, items, and sleep behavior.

Crafting and using the items

The official project description identifies wool as part of the sleeping-item crafting path. Exact recipe layouts can change between mod and Minecraft versions, so use the recipe viewer in the installed 26.2 profile or inspect the current data recipes instead of relying on an old screenshot. After crafting, place the item where there is enough space and interact with it under the time and safety rules allowed by the world and server configuration.

If the item looks usable but sleep does not begin, first check the time of day, nearby threats, obstruction, dimension rules, and server sleep settings. Then check Comforts configuration and any other mod that changes time, beds, player pose, weather, or sleeping.

Configuration that is worth checking

• Auto-Use Sleeping Bag: controls convenience behavior around deploying or using the bag.
• Well Rested and Sleepiness Factor: affect the mod's rest-related mechanics when enabled.
• Hammocks at Night: changes when hammock use is accepted.
• Break chance and debuffs: can make portable sleep safer or more survival-oriented.
• Insulated sleeping bags: affects the insulated variant behavior where present in the selected build.

Configuration ownership can differ between client and server. In multiplayer, treat the server configuration as authoritative and restart when a setting says a restart is required.

Common problems and fixes

The game reports an incompatible mod or will not launch

Confirm all four identifiers: Minecraft 26.2, NeoForge, Comforts 16.0.0+26.2, and one Comforts JAR only. If the log names a missing dependency, use the dependency version listed for this exact file rather than guessing.

The sleeping bag does not work

Test in a normal Overworld area at the appropriate time with open space and no hostile mobs nearby. Check the server's sleep percentage and other sleep-changing mods. Official issue reports have documented compatibility problems with some realistic-sleep and world/time mods; those reports do not prove a universal bug in 16.0.0+26.2, but they make a clean-profile test especially useful.

The hammock does not skip the day

Check the current hammock time rules and server configuration. Remove obstruction, try a default Overworld test, and temporarily isolate mods that alter time or weather. Compare the result with Comforts alone before reporting it.

The item renders strangely or leaves an invisible object

Update the graphics stack and reproduce with Comforts and its confirmed requirements only. An older official report mentioned an invisible armor-stand-like artifact in a specific modpack. Treat that as a compatibility clue, not a confirmed defect in this release.

It works in single-player but not on the server

Compare client and server mod lists, exact filenames, loader versions, configurations, and logs. Confirm that both sides use the same Comforts build. Test without plugins or mods that rewrite sleep votes, dimensions, time, or player pose.

Safe updating and removal

Back up first. Read the official changelog, match the new file to the same Minecraft and loader family, and remove the old JAR instead of keeping two versions. Before removing Comforts from a world, pick up its placed blocks and items where practical, then test a copy of the world. Removing content mods can delete their blocks and items from saved data.

Download and source

Verify the selected build on the official Comforts file 8303507 page and use the official source repository for code and license information. MineBrush has acquired and statically verified the exact JAR plus corresponding Comforts/SpectreLib source and LGPL notices, but has not malware-scanned or runtime-tested it.

Quick answers

Does a sleeping bag reset my spawn? No. Preserving the existing spawn point is its defining use case.

Can I use the Fabric file on NeoForge? No. Download the file built for the loader in your profile.

Does the server need Comforts? Yes for the multiplayer setup covered here; keep the same content version on the server and clients.

Why is the local download unavailable? Binary identity, checksums, corresponding source, and LGPL notices pass offline QA. The approved malware scan, clean client/server launch, and live staging checks still must pass.

MineBrush local downloads

Each link opens the separate MineBrush download page before DLE serves the attached file.

• e4mc 6.2.1 — Fabric
• e4mc 6.2.1 — NeoForge
• Fabric API 0.158.0
• e4mc source JAR
• MIT license

MineBrush reviewed the official release records and attachment structure. This exact build was not independently launched in a Minecraft runtime; use a backup and match the listed game version, loader, and dependencies.

e4mc lets a Minecraft Java host expose an Open to LAN world through a temporary public address. It creates a reverse tunnel through the e4mc relay, so you do not have to open a router port or ask friends to join your home network. The host installs the mod; guests normally connect with a vanilla client by entering the address e4mc displays.

Download e4mc 6.2.1 for Minecraft 26.2

Use the Fabric modern build for Minecraft 26.2. The separate non-modern Fabric file targets the long 1.18–1.21.11 compatibility line and is not the correct 26.2 download. NeoForge users need the NeoForge JAR and should not add Fabric API.

What e4mc does—and what it does not do

• creates a temporary public hostname for a local Open to LAN session;
• tunnels Minecraft traffic through the e4mc relay instead of router port forwarding;
• lets ordinary guests join without installing e4mc;
• works from the host's normal singleplayer world flow;
• does not turn the world into a permanent 24/7 server;
• does not keep the world online after the host closes it;
• does not provide MineBrush-hosted relay infrastructure or an uptime guarantee;
• does not replace backups, moderation or access decisions.

Install e4mc on Fabric

1. Back up the world and create a separate Minecraft 26.2 profile.
2. Install Fabric Loader. MineBrush's Fabric installation guide covers profile and dependency matching.
3. Download e4mc-fabric-6.2.1-modern.jar and Fabric API from the cards above.
4. Place both JARs in that profile's mods folder without unzipping them.
5. Launch once and confirm that e4mc loaded before opening the important world.

Install e4mc on NeoForge

1. Install NeoForge for Minecraft 26.2 in its own launcher profile.
2. Download e4mc-neoforge-6.2.1.jar.
3. Place the JAR in the profile's mods folder. Do not add the Fabric JAR or Fabric API.
4. Launch and confirm the mod appears in the startup log or mod list.

Host a world with e4mc

1. Open the copied singleplayer world on the computer that will host the session.
2. Pause and choose Open to LAN.
3. Choose the intended game mode and whether commands are allowed, then start the LAN world.
4. Wait for e4mc to display a public domain alongside the local port message.
5. Copy the domain exactly. Do not add the local 192.168… address; remote friends cannot use it.
6. Send the public domain privately to the invited players.
7. Keep the world open while everyone plays. Closing the world ends the host session.

How friends join

1. Use Minecraft Java on the same compatible game version as the host.
2. Open Multiplayer and choose Direct Connection or Add Server.
3. Paste the complete e4mc domain displayed by the host.
4. Join while the host's world and LAN session are still open.

Guests do not normally need e4mc because they connect to a public address like any other Java server. They may still need the host's gameplay mods if the world uses a modpack with required client/server content. e4mc solves network reachability; it does not make mismatched modpacks compatible.

Security and privacy checklist

• Use a copied world for the first session.
• Share the address in a private message, not a public post or stream overlay.
• Invite only players you trust with that world.
• Do not expose personal files, launcher logs or desktop notifications while streaming.
• Remember that Minecraft traffic is relayed through third-party e4mc infrastructure.
• Close the world when the session ends and confirm that the public address no longer accepts connections.
• Use a real dedicated server with documented access controls when the world must stay online or serve a larger community.

Fix: no public e4mc address appears

• Confirm that e4mc loaded and that you selected Open to LAN, not only opened the pause menu.
• Check that the correct modern Fabric or NeoForge file is in the active profile.
• Fabric users should confirm that Fabric API is present and compatible.
• Review the latest log for e4mc connection, DNS or relay errors.
• Temporarily test without a VPN, restrictive proxy or network filter that may block the relay connection.
• Check the project's current status/issues; an external relay outage cannot be fixed by reinstalling the JAR.

Fix: a friend cannot connect

• Send the address again as plain text and remove spaces or punctuation copied from chat.
• Verify that the host's world is still open and the LAN session has not ended.
• Match the Minecraft version. A network tunnel cannot fix an outdated client/server protocol.
• If the world is modded, match every required mod and configuration on the joining client.
• Have one player test from a different network to separate a guest-side firewall issue from the host setup.
• Read the host log while the guest attempts to join; a visible handshake or disconnect reason is more useful than “it doesn't work.”

e4mc versus port forwarding, a VPN and a dedicated server

Creator, source and license

e4mc is developed by vgskye and contributors and released under the MIT License. Its client mod and relay source are publicly documented by the project. MineBrush stores the original unmodified release files listed above with their source and license references.

• Official Modrinth project
• Official service site
• Official mod source
• Download source material
• Read the included MIT license

e4mc is a community project and is not an official Mojang or Microsoft service. MineBrush is not affiliated with the creator or relay operator.

MineBrush local downloads

Each link opens the separate MineBrush download page before DLE serves the attached file.

• Controlify 3.4.1 universal JAR
• Fabric API 0.158.0
• YACL 3.9.6 — Fabric
• YACL 3.9.6 — NeoForge
• Controlify corresponding source
• LGPL license

MineBrush reviewed the official release records and attachment structure. This exact build was not independently launched in a Minecraft runtime; use a backup and match the listed game version, loader, and dependencies.

Controlify adds full controller input to Minecraft Java Edition: gameplay, inventories, chat, menus and modded screens. It can identify common controllers, show matching button glyphs, remap vanilla and modded actions, and expose hardware features such as rumble or gyro when the controller, connection, operating system and driver support them.

Controlify 3.4.1 download for Minecraft 26.2

The Controlify JAR is universal, but YACL is not. Pick the YACL file that matches the loader in your profile. Do not put both YACL builds in one mods folder.

What Controlify actually supports

• controller movement, camera, combat and normal gameplay actions;
• inventory and menu navigation with a controller-friendly cursor;
• per-controller bindings, sensitivity and deadzone settings;
• automatic glyphs and default layouts for recognized devices;
• button guides and an on-screen keyboard;
• a configurable radial menu for actions that do not deserve a permanent button;
• standard rumble and controller-specific features when exposed by the driver;
• gyro aiming, flick stick and adaptive triggers on supported hardware;
• modded GUI and keybind compatibility through Controlify's integration APIs.

How to install Controlify on Fabric

1. Back up the profile and its options.txt before changing input mods.
2. Install Fabric Loader for Minecraft 26.2. MineBrush's Fabric install guide covers the clean profile setup.
3. Download Controlify, Fabric API and YACL for Fabric from the cards above.
4. Place all three JARs in that profile's mods folder. Do not unzip them.
5. Launch the profile and confirm that all three appear in the mod list or startup log.
6. Connect the controller before opening the Controlify settings page for the first calibration.

How to install Controlify on NeoForge

1. Install NeoForge for Minecraft 26.2 in a separate launcher profile.
2. Download the same universal Controlify JAR and YACL for NeoForge.
3. Place those two JARs in the NeoForge profile's mods folder.
4. Do not add Fabric API or the Fabric YACL JAR to the NeoForge folder.
5. Launch once and confirm that the controller is detected before adding other input-remapping mods.

First-run controller setup

1. Use USB for the first test when possible. It removes Bluetooth pairing and battery state from the troubleshooting stack.
2. Open Controlify's controller settings and choose the detected device.
3. Let the automatic deadzone calibration finish with the sticks at rest.
4. Check movement, camera, jump, inventory and pause before changing bindings.
5. Adjust look sensitivity in small steps. A giant jump makes aim feel snappy but hides whether the deadzone is wrong.
6. Open an inventory and verify cursor movement, quick-move and drop actions.
7. Only then configure gyro, radial actions, vibration intensity and controller-specific extras.

Controller support: what “supported” means

Controlify uses SDL3 for cross-platform controller input. A common gamepad will usually expose sticks, buttons, triggers and a D-pad, but extra features are not guaranteed. Rumble, gyro, touchpad clicks, paddles, battery reporting, HD haptics and adaptive triggers can change with the exact controller model, USB versus Bluetooth, operating system and driver.

For example, the official compatibility table distinguishes DualSense USB and Bluetooth because HD haptics are not available in every Bluetooth combination. Treat the model and connection as part of the setup, not as trivia.

Use Controlify on multiplayer servers

Controlify is a client-side input mod. The official documentation says a normal server does not need Controlify installed. By default, stick movement is translated into keyboard-like WASD input because some anti-cheat systems reject full analogue movement. A server can explicitly allow analogue input, and trusted servers can be added to the local whitelist.

If a server flags movement, return to the default keyboard-like mode before assuming the entire mod is incompatible. Input comfort should never require bypassing a server's rules or anti-cheat policy.

Fix: Controlify does not detect the controller

• Reconnect by USB and confirm the operating system sees button input.
• Close Steam Input, DS4Windows or another remapper for one clean test; two input layers can hide or duplicate the device.
• Restart Minecraft after changing the connection mode.
• Confirm the exact Controlify, Minecraft, loader and YACL versions.
• Test with only Controlify and its required dependencies before restoring other input mods.
• On Linux, verify device permissions and the current controller driver rather than running the launcher as root.
• When reporting a bug, include controller model, USB/Bluetooth, operating system, loader and the startup log.

Fix: double inputs or spinning camera

Double actions usually mean two layers are converting the same controller into game input. Disable external remappers, launcher controller profiles or a second controller mod one at a time. A drifting or spinning camera is more likely a deadzone/calibration problem: place the controller flat, recalibrate with untouched sticks, then increase the affected stick's deadzone slightly.

Fix: rumble, gyro or glyphs are wrong

• Rumble missing: test USB, confirm the driver exposes rumble, and make sure that vibration source is enabled in Controlify.
• Gyro missing: verify that the exact device/connection/OS combination exposes gyro; not every Bluetooth or XInput mode does.
• Wrong glyphs: reselect the controller identity or remove a glyph resource pack for one test.
• Modded screen awkward: use virtual mouse mode or check whether that mod has explicit Controlify integration.

Steam Deck notes

Controlify supports Steam Deck, but avoid stacking a complex Steam Input layout on top of Controlify until the native setup works. Start with a simple gamepad-style layout, confirm that Controlify identifies the device, then add Deck-specific shortcuts. Desktop-mode overlays and game-mode input can behave differently, so record which mode you tested.

Creator, source and license

Controlify is developed by isXander and contributors and released under the GNU Lesser General Public License version 3 or later. MineBrush distributes the unmodified creator file with the corresponding source and license materials for the exact mirrored build.

• Official Modrinth project
• Official Controlify documentation
• Official source repository
• Download corresponding source
• Read the included LGPL license

Controlify is a community mod and is not an official Mojang or Microsoft product. MineBrush is not affiliated with the creator.

MineBrush local downloads

Choose the file that matches your Minecraft version and mod loader. Each link opens the separate MineBrush download page before DLE serves the attached file.

• KubeJS 2101.7.2 build 374 — Minecraft 1.21.1 NeoForge
• Rhino 2101.2.7 build 85 — required dependency
• KubeJS corresponding source
• Rhino corresponding source
• KubeJS LGPL-3.0 license
• Rhino MPL-2.0 license

MineBrush reviewed the official release records and attachment structure. This exact build was not independently launched in a Minecraft runtime; use a backup and match the listed game version, loader, and dependencies.

KubeJS is a Minecraft scripting platform for modpack creators and server administrators. It can change recipes and tags, register custom content, react to server and client events, customize world generation, and provide integrations with other mods. Its jаvascript is executed by the Kube-mods fork of Rhino.

Required files

The selected KubeJS JAR itself is the dependency truth source. Its NeoForge metadata marks Rhino required and Better Advanced Tooltips optional. It also embeds BAT build.1, Tiny Java Server build.33, and Animated GIF Lib 1.7. Do not add an external BAT JAR merely because a project-wide relation page labels it differently.

Install KubeJS

1. Back up the instance or server, world, configs, datapacks, and existing kubejs directory.
2. Create or select a Minecraft 1.21.1 NeoForge profile and launch it once.
3. Add the two exact JARs to the correct mods folder.
4. Remove Forge/Fabric, other Minecraft branches, old duplicates, and any incompatible Architectury-era instructions.
5. Launch once. KubeJS should generate a kubejs folder with examples and a README.
6. Stop the game/server and commit that clean generated folder to version control before editing scripts.

For multiplayer, align the server and client mod set according to the scripts and content used. Server scripts are server-authoritative, but registered content or client scripts may require matching client resources/mods.

Choose the correct script folder

A file in the wrong folder may never run, run on the wrong side, or run too late for the registry it tries to change. Check the current wiki page for every event or API used.

Security: treat scripts as administrator code

Do not paste an unreviewed KubeJS script into a production server. KubeJS can modify recipes, tags, loot, world behavior, commands, and event handling. Its plugin system can expose Java bindings, and the project documentation describes native Java type access through Java.loadClass with built-in and addon-supplied class filters. That is not a promise of a complete security sandbox.

• Accept scripts only from a trusted, attributable source and review every line and included file.
• Reject obfuscated/minified scripts, remote loaders, encoded payloads, unexplained Java class access, or code that reads/writes outside the intended KubeJS/world data paths.
• Never store tokens, passwords, API keys, RCON credentials, or personal data in scripts or a public repository.
• Test with a disposable offline server account and a copy of the world.
• Run the server process with least filesystem/network privileges available; do not run it as an administrator/root user.
• Use version control, signed/approved changes, peer review, and a rollback tag for every script deployment.
• Audit addon mods: a KubeJS plugin can add bindings or change class-filter exposure.

A safe first recipe script

Begin with a tiny recipe change from the current 1.21.1 wiki syntax, in a disposable profile. Do not copy an old onEvent example without confirming the branch. The general workflow is:

1. Create one clearly named file under server_scripts.
2. Change one test recipe using the current documented event/API.
3. Start or reload and read the KubeJS/server log for syntax and event errors.
4. Confirm the recipe in a recipe viewer and crafting test.
5. Restart the whole server and verify persistence before adding more changes.

Recipes, tags, loot, and mod integrations

KubeJS supports normal datapack recipe types by default. More complicated mod recipes may require an addon or an exact recipe schema. Match the addon to Minecraft, loader, KubeJS, and target-mod versions. Never assume a KubeJS Create or KubeJS Mekanism addon build supports the newest Core merely because the names match.

Recipe or tag removal can break progression, quests, loot, and automation. Search references before deleting an ID, test existing saves, and keep a changelog for pack users.

Startup content and world generation

New registries and some world-generation changes require startup or world restart and may affect saved data. Adding an item ID and later renaming/removing it can create missing registry entries in existing worlds. Worldgen scripts should be tested in newly generated chunks and a copy of an existing world. Never run experimental worldgen on the only backup.

Reload versus restart

A successful reload does not prove a clean restart. Event listeners can duplicate, registry changes may not reload, and client/server state may diverge. For production acceptance, test: clean start, reload where documented, player reconnect, full server stop/start, and client restart.

Read errors efficiently

1. Open the KubeJS log and latest.log.
2. Find the first error naming your script path and line number.
3. Check brackets, quotes, commas, resource IDs, event names, and folder/side.
4. Disable all but the failing file, then reduce it to the smallest reproducible block.
5. Confirm the example belongs to KubeJS 2101/1.21.1, not an older branch.
6. Restore the last version-control commit if the production server is affected.

Common installation failures

Missing Rhino

Install a Rhino build in the required [2101.2.7-build.81,) range; this package selects stable build.85. Do not add Architectury from an older tutorial because the selected metadata does not require it.

Rhino version mismatch

Use the latest stable Rhino compiled for the matching 2101/Minecraft branch that file 8715199 accepts. Reject a 2001/1.20.1 Rhino JAR and confirm the range in KubeJS metadata.

The script loads but nothing happens

Check folder, event side, resource ID, event timing, and whether a full restart is required. Confirm the target mod and any integration addon loaded.

Commands or events behave differently after reload

Test a clean restart and check current open issues for the exact KubeJS build. An older official issue reported multi-level command registration trouble on an earlier 2101 build; use it only as a regression clue, not proof that build 374 has the same defect.

Backups and deployment

Version the entire KubeJS directory, configs, datapacks, mod list, and world schema together. Deploy to staging first. Make a world backup while the server is stopped, review the diff, run syntax/start/reload/restart tests, then deploy the identical approved commit. Keep a tested rollback that includes both scripts and mod versions.

Official downloads, source, and local mirror

Use the official KubeJS file record, Rhino file record, KubeJS wiki, and source repository. KubeJS build 374 is tied to release commit 6d3c30db6a1504ac81f3c0a833bcf6427d0a6b21; Rhino build.85 is tied to 2d95ef41d02cbaf82e72f2ee0e21a03f5d34557a. MineBrush captured both commit archives, both published source JARs, the licenses, and source for all three embedded libraries. A local mirror may open only when the exact two runtime files and the full source/notice bundle pass staging, malware, and runtime QA together.

Quick answers

Is Rhino optional? No. It is a required KubeJS dependency.

Is Better Advanced Tooltips required? No. The selected JAR marks it optional and already embeds build.1.

Can I reload every script? No. Registries and worldgen can require full game/world restarts.

Are downloaded scripts safe? Not by default. Review and test them as administrator-controlled code.

MineBrush local downloads

Choose the file that matches your Minecraft version and mod loader. Each link opens the separate MineBrush download page before DLE serves the attached file.

• Mekanism Core 10.7.19.85 — required; Minecraft 1.21.1 NeoForge
• Mekanism Generators 10.7.19.85 — optional module; requires Core
• Mekanism Tools 10.7.19.85 — optional module; requires Core
• Mekanism Additions 10.7.19.85 — optional module; requires Core
• Corresponding source — exact version
• MIT license

MineBrush reviewed the official release records and attachment structure. This exact build was not independently launched in a Minecraft runtime; use a backup and match the listed game version, loader, and dependencies.

Mekanism is a broad technology mod rather than one machine or one progression tree. Its core covers power storage and transfer, processing machines and factories, item/fluid/chemical transport, gases and chemicals, digital storage, mining tools, equipment, and complex multiblocks. Official optional modules expand power generation, tools and armor, or miscellaneous content.

Core and modules: install only what you need

All four files are built from the same official repository and release version. The simplest player install is Core only. Add Generators only when its generation systems are wanted; never download a module merely because another guide includes it.

Requirements and installation

• Minecraft Java Edition 1.21.1.
• A matching NeoForge loader build.
• Java 21 for the normal Minecraft 1.21.1 environment.
• Mekanism Core 10.7.19.85, plus only identically versioned optional modules.

1. Back up important worlds, configs, and the current mod list.
2. Create or select a clean Minecraft 1.21.1 NeoForge instance and launch it once.
3. Add Core to that instance's mods folder.
4. Add Generators, Tools, or Additions only if needed, checking the full filename for 1.21.1-10.7.19.85.
5. Remove Forge builds, other Minecraft branches, and duplicate old modules.
6. Launch and confirm every Mekanism module reports the same version before loading a valuable world.

Dedicated-server setup

1. Stop and back up the server.
2. Install the same Core and optional module filenames on the server and all clients.
3. Start once to generate configs, then review logs for module/version mismatch.
4. Adjust server configuration before players build production machinery.
5. Test energy, transport, factories, chunks, restarts, and permissions in a disposable area.

Mekanism stores machines, inventories, chemicals, networks, and multiblock state in the world. Treat updates and removals as world migrations, not cosmetic mod swaps.

A practical first-hour route

1. Use the recipe viewer for exact 10.7.19.85 recipes and identify basic crafting components.
2. Choose an early power source available in Core or the installed Generators module.
3. Build an energy buffer and connect one basic processing machine.
4. Learn machine side configuration before automating input and output.
5. Add upgrades only after the power system can support the increased demand.
6. Expand into factories, gas/chemical chains, ore processing, digital mining, or QIO after the basic line survives a restart.

Power: generation, storage, and transfer

Generators produces power; energy cubes buffer it; cables and machine sides move it. Exact output, capacity, and consumption depend on version and configuration. Measure the actual installed profile rather than copying numbers from an older wiki page or modpack.

When a machine will not charge, verify that the source is running, the cable connects to an enabled energy side, the receiving machine accepts energy on that face, and the network is not saturated. Test the same source with one machine and one cable before debugging a full factory.

Machine sides and auto-eject

Mekanism machines can assign faces for item, fluid, chemical, and energy input/output. The colors and tabs visible depend on the machine. Configure one resource type at a time, enable auto-eject only when the target inventory is ready, and avoid loops that send an output back into its own input.

If a pipe connects but nothing moves, confirm the correct resource type, side mode, pull/push behavior, redstone control, filter, and destination capacity.

Factories and upgrades

Factories scale supported operations across multiple processing slots. Tier installers and upgrade systems allow machines to grow, but speed upgrades can sharply increase energy demand. Energy upgrades improve efficiency/capacity behavior according to the machine. Install upgrades gradually and watch the power buffer under sustained load.

Ore processing without wasting the base

Mekanism supports progressively more complex processing chains. Higher multiplication is not automatically better: it costs machines, chemicals, space, power, and maintenance. Start with a reliable low-tier line, then expand only when inputs and energy are stable. MineBrush's separate offline `JAVA-006 R2` package contains the detailed 2x/3x/4x decision intent; this resource page should link to that guide if it becomes live instead of duplicating the full walkthrough.

Gases, chemicals, and pressurized tubes

Chemical systems are not ordinary fluid systems. Use the transport and tank type specified by the machine UI/recipe documentation. Check side configuration and chemical identity before assuming a pipe bug. Breaking or moving a machine with stored chemicals can be dangerous or destructive; empty systems safely in a test copy first.

Radiation safety

Some advanced Mekanism systems can involve radioactive materials and contamination. Do not build them in a main base without understanding storage, waste handling, chunk loading, protection, and emergency recovery for this exact server configuration. Back up before testing. Never claim a generic “remove the block” action cleans a contaminated world.

Digital Miner and QIO

The Digital Miner can select blocks based on configured filters and area rules; QIO provides a digital storage system. Both can affect server load and valuable inventories. Define narrow filters, respect claims and world borders, set chunk behavior deliberately, test redstone control, and verify storage/export priorities. Do not run an unbounded mining or item-routing experiment in the main world.

Common crashes and fixes

Module version mismatch

Compare every Mekanism filename. Core, Generators, Tools, and Additions must all end in 1.21.1-10.7.19.85. Remove the mismatched JAR; do not rename it to look compatible.

Missing Mekanism dependency

An optional module requires Core. Install matching Core or remove the module. Do not satisfy a 10.7.19 module with 10.7.18 Core.

Machine or pipe stopped after an update

Check side configuration, redstone control, transport filters, saved chemicals, and logs. Reproduce the smallest machine-to-machine connection in a copied world.

Server TPS falls around a factory

Profile before blaming one block. Reduce active machines, transport loops, broad Digital Miner searches, always-loaded chunks, and rapid cross-mod transfers one variable at a time. No performance number is claimed by this package.

Safe updates and removal

Back up worlds and configs. Stop all processing, empty hazardous or valuable buffers where practical, capture the module list, and update Core/modules as one version-locked set. Test the copy through a complete restart. Before uninstalling, dismantle Mekanism content and networks safely; removing the mod can delete machines, inventories, chemicals, and saved data.

Official downloads, source, and mirror boundary

Use the official exact records for Core 7904058, Generators 7904061, Tools 7904062, and Additions 7904060. The official source release covers the same version and pins commit a00109e4856fd38b9c5b3dd7f22ce4a59cd65a80. All selected modules are MIT-labeled, but MineBrush must inspect and clear each exact JAR independently before mirroring it.

Quick answers

Do I need all four files? No. Core is the baseline; the other modules are optional.

Can Generators 10.7.18 run with Core 10.7.19? Do not mix them. Use 10.7.19.85 for both.

Why is my machine not moving items? Check item-side configuration, auto-eject, redstone state, destination capacity, and transport pull/push rules.

Can MineBrush mirror the module bundle now? Not until every file is independently acquired, hashed, scanned, metadata-checked, and license/asset reviewed.

MineBrush local downloads

Choose the file that matches your Minecraft version and mod loader. Each link opens the separate MineBrush download page before DLE serves the attached file.

• GeckoLib 5.5.3 — NeoForge — Minecraft 26.2
• GeckoLib corresponding source
• MIT license

MineBrush reviewed the official release records and attachment structure. This exact build was not independently launched in a Minecraft runtime; use a backup and match the listed game version, loader, and dependencies.

GeckoLib is a library that other mods use to render and animate entities, blocks, items, armor, and more. It supports complex 3D keyframe animations, many easing types, concurrent animations, and sound, particle, and event keyframes. Installing GeckoLib alone usually does not add a new creature, machine, menu, or progression system; the visible content comes from the mod that requires it.

When you actually need GeckoLib

Install it when a mod's official dependency list, loader error, or bundled modpack requires GeckoLib. The dependent mod decides the acceptable GeckoLib and Minecraft range. A page that merely says “requires GeckoLib” is not permission to download the newest file for a different Minecraft branch.

• If the dependent mod targets Minecraft 26.2 NeoForge and accepts GeckoLib 5.5.3, use the file in this guide.
• If it targets 1.21.1, 26.1.2, Forge, or Fabric, select that exact branch instead.
• If a modpack already includes GeckoLib, do not add a second copy unless the pack author instructs you to update it.

Requirements

• Minecraft Java Edition 26.2.
• A NeoForge loader build compatible with Minecraft 26.2.
• geckolib-neoforge-26.2-5.5.3.jar.
• At least one dependent mod that explicitly supports this GeckoLib line, unless you are building or testing a mod.

No separate runtime mod dependency was established for the selected NeoForge JAR from the captured official evidence. The exact JAR metadata remains authoritative and must be inspected before the local attachment is approved.

Install GeckoLib on a client

1. Back up important worlds and close Minecraft and the launcher.
2. Create or select a Minecraft 26.2 NeoForge instance.
3. Run that empty loader profile once, then close it.
4. Open the instance-specific mods folder.
5. Add the exact GeckoLib NeoForge JAR and the compatible dependent mod.
6. Remove GeckoLib files for Fabric, Forge, another Minecraft version, or an older duplicate.
7. Launch and verify both GeckoLib 5.5.3 and the dependent mod in the loaded-mod list before opening a valuable world.

Install it on a server

The project is marked for client and server. In practice, follow the dependent mod's environment requirements: if that content mod belongs on both sides, install the matching GeckoLib build on both sides too.

1. Stop the server and back up world, configs, and the mod list.
2. Verify Minecraft 26.2 and a compatible NeoForge build.
3. Install the same GeckoLib 5.5.3 JAR and compatible dependent-mod version on the server.
4. Align the client files with the server requirements.
5. Start the server and read the first dependency or version-range error before changing files.

How version matching works

Match four things: Minecraft version, loader family, GeckoLib major/release, and the dependent mod's accepted range. GeckoLib 5 introduced major API and asset-path changes for modern Minecraft branches, including moving GeckoLib assets into GeckoLib-specific model and animation directories. Those developer-facing changes mean a mod compiled for GeckoLib 4 cannot be assumed to run on GeckoLib 5 merely because both JARs load under NeoForge.

For players, the safest source of truth is the dependent mod's exact release page and the dependency range in its JAR metadata. For developers, use the official GeckoLib 5 installation and migration documentation for the selected Minecraft branch.

Fix “GeckoLib is missing”

1. Confirm GeckoLib is in the active instance's mods folder, not a different launcher profile.
2. Confirm the filename says NeoForge and Minecraft 26.2.
3. Check that the dependent mod accepts GeckoLib 5.5.3.
4. Remove duplicate or nested copies.
5. Read the loader's requested version range. Do not replace it with “latest” unless latest fits the range.

Fix a wrong-loader or wrong-Minecraft crash

A Fabric or Forge GeckoLib JAR does not become compatible when placed in a NeoForge folder. Likewise, 1.21.1 and 26.1.2 builds do not belong in a 26.2 instance. Check the first relevant exception in latest.log or the crash report and compare every filename. Exit code 1 is only the launcher summary.

Fix broken, frozen, or invisible animations

First confirm that the game launches with GeckoLib and the dependent mod only. Then check resource packs, shaders, renderer replacements, entity-culling mods, camera mods, and custom models one group at a time. GeckoLib 5.5.3's official changelog describes a vanilla armor rotation fix for GeckoLib entities; that does not guarantee every third-party animation is fixed.

If the log names a missing model, texture, or animation JSON, report that path to the dependent mod author. GeckoLib can load animation resources, but it cannot repair a resource the content mod did not package or referenced incorrectly.

Fix a dedicated-server startup failure

Compare server and client environments, then isolate GeckoLib plus one dependent mod. A client-only content mod should not be forced onto a server merely because GeckoLib supports servers. Conversely, a content mod that registers entities or blocks generally needs its required library on the server. The dependent mod's official environment and metadata decide.

Safe updates

Update the dependent mod and GeckoLib as a tested pair. Back up the instance, read both changelogs, remove the old JAR rather than leaving two copies, and test a world copy. A library update can change rendering or resource behavior even when it adds no standalone world content.

For mod developers

The official GeckoLib wiki provides separate player-independent setup and migration documentation. GeckoLib 5 uses modern render-state patterns and changed packages and asset locations from GeckoLib 4. Do not paste a GeckoLib 4 tutorial into a GeckoLib 5 project. Use the official installation page for the loader and the official GeckoLib 5 changes page before porting code or assets.

Official download, source, and local mirror

Use the official GeckoLib NeoForge 5.5.3 file record. Source and documentation are in the official repository and official wiki; the pinned release source commit is 05048071ce4801969237ffdca0b73223e986d94d. The project is MIT-licensed, but MineBrush must still verify the exact JAR, embedded notices, third-party bytes, and packaged asset licensing before enabling a local attachment.

Quick answers

Does GeckoLib add mobs? No. It supplies animation/rendering systems used by other mods.

Can I use the Fabric file on NeoForge? No.

Should the server install it? Follow the dependent mod. For a mod installed on both sides, use the matching GeckoLib build on both sides.

Why is local download disabled? File ID, exact bytes/hash, scan, JAR metadata, MIT notice, and asset/component review are incomplete.