KubeJS JEI: Customize Just Enough Items with KubeJS

KubeJS JEI lets you create custom JEI recipe pages, hide or re-show items, and hot-reload configs for Minecraft. A must-have for modpack developers!

Download kubejei for Minecraft 1.21.1

Original name: kubejei

Minecraft: 1.21.1

Loaders: NeoForge

FileVersionLoaderSize
kubejei-1.0.0.jar1.21.1NeoForge29 КБDownload

KubeJS JEI

If you have ever built a modpack, you know that Just Enough Items (JEI) is the backbone of how players discover recipes. But vanilla JEI only shows what mods register, and sometimes that is not enough. KubeJS JEI bridges that gap by letting you customize JEI entirely through KubeJS scripts, no Java required. Whether you want to add brand-new recipe display entries, hide clutter, or expose JEI's texture resources for custom pages, this add-on gives you direct control over the recipe viewer your players rely on every session.

What KubeJS JEI Actually Does

At its core, KubeJS JEI is a scripting bridge. It hooks into JEI's API and surfaces that functionality through KubeJS, so pack authors can shape the recipe browser with the same event-driven workflow they already use for recipes, tags, and loot. The current feature set covers the tasks modpack developers ask for most often:

  • Creating new JEI recipe display entries so custom machines and processes appear in the recipe browser.
  • Hiding specified items from JEI when they are technical or unobtainable.
  • Re-showing items that another mod or script has hidden, giving you fine-grained override control.
  • Exposing JEI's texture resources so custom recipe pages can match the vanilla JEI look.
  • Providing the /kubejei reload command for hot-reloading JEI configurations without restarting the game.

That reload command deserves special mention. Anyone who has iterated on recipe layouts knows the pain of quitting to the main menu after every tweak. With /kubejei reload, you adjust your script, run the command, and see the result immediately. It is a small feature that saves hours during development.

Supported Versions and Loaders

KubeJS JEI is built for modern Minecraft, with support centered on Minecraft 1.20.1 and 1.21.x on the NeoForge loader, matching the current KubeJS release line. Because KubeJS itself has moved its primary development to NeoForge, this add-on follows suit, and older Forge builds of KubeJS may not be compatible. Before you download KubeJS JEI, confirm that your KubeJS and JEI versions line up with the add-on's release notes, since mismatched versions are the most common cause of scripts silently failing to register.

How to Install KubeJS JEI

Installation is straightforward if you already run a KubeJS pack:

  • Install KubeJS and JEI for your target Minecraft version and loader.
  • Place the KubeJS JEI jar in your mods folder alongside them.
  • Launch the game once to generate the plugin, then write your scripts in the KubeJS client_scripts or server_scripts directory as appropriate.
  • Use /kubejei reload in-game to apply changes on the fly.

If you would rather skip manual file management, the foxygame.net launcher bundles KubeJS JEI in its add-on catalog and handles version matching automatically, so the correct build lands in your instance with a single click and stays updated between sessions.

Practical Uses for Pack Developers

The most common use case is hiding junk. Technical blocks, placeholder items, and intermediate crafting components often flood JEI and bury the entries players actually need. A few lines of script can remove them from the index entirely. The reverse is just as valuable: if a datapack adds an item that JEI never indexes, you can re-show it and attach a proper recipe page.

Custom recipe displays are where the add-on shines for expert packs. Gate a machine behind a quest, then create a JEI page that explains the process with the mod's own textures. Because KubeJS JEI exposes JEI's texture resources, your custom pages inherit the familiar slot and arrow styling instead of looking bolted on. The author's wiki includes example code for each feature, and copying a working example is usually faster than reading API docs.

Tips for Cleaner Scripts

Keep hide and show logic in one script file per mod to avoid conflicts, and comment every entry with the reason it exists. When two scripts touch the same item, the load order decides the winner, and undocumented overrides become debugging nightmares months later. Test with /kubejei reload after each batch of changes rather than writing everything at once.

Final Thoughts

KubeJS JEI fills a gap that vanilla JEI intentionally leaves open: full script-level control over what players see in the recipe browser. For modpack authors on NeoForge running Minecraft 1.20.1 or 1.21.x, it turns JEI from a fixed reference into a design surface. Grab the matching build, keep your KubeJS and JEI versions aligned, and let your scripts do the rest.