KubeJS Studio
If you have ever written a KubeJS script, you know the rhythm: edit a file, reload, scroll through the log, fix a typo, repeat. KubeJS Studio changes that rhythm. It is an in-game front end for KubeJS that puts a full workspace inside Minecraft, so you can build recipes, tags, loot tables, item properties and registry entries without ever leaving the game window. Press K and you are there.
This is not a separate project format or a wrapper that locks your work away. Studio writes plain files under kubejs/: scripts, datapack JSON, lang files and models. There is nothing to export, and everything it generates keeps working even if you remove the mod later. KubeJS Studio for Minecraft is a client-side authoring tool, so it never has to go on a server.
Supported Versions and Loaders
Compatibility is deliberately narrow and well tested. KubeJS Studio runs on Minecraft 1.21.1 with NeoForge 21.1.216 or newer and Java 21, and on Minecraft 1.20.1 with Forge 47 or newer and Java 17. Both builds require KubeJS, and the Forge 1.20.1 build also needs Kotlin for Forge 4.11 or above. LDLib2 is bundled inside the jar, which is why the NeoForge floor sits higher than the loader baseline.
Optional integrations unlock extra convenience. Create adds hand-built forms for its processing recipes, including heated mixing and sequenced assembly. JEI or EMI add an Edit button directly on their recipe screens in singleplayer creative mode, jumping straight into Studio with that recipe selected.
How to Install KubeJS Studio
Installation follows the standard mod workflow. Drop the jar into your mods folder alongside KubeJS and the required loader dependencies, then launch the game. Open a singleplayer world before using the browsers, because the recipe, tag and loot catalogs read live data from the running server. If you prefer a smoother path, the foxygame.net launcher handles KubeJS Studio as a one-click install from its add-on catalog, matching the correct build to your loader and Minecraft version automatically.
GUI or Code, Your Call
Studio does both, and you can switch whenever you like, or use both at once. If you have never written a KubeJS script, start with the five visual tabs. Pick a recipe, a tag, a loot table or an item, change it with real item slots and normal fields, then hit Queue. Studio shows you exactly what it is going to write before it touches anything.
The Visual Tabs
- Recipes: Every loaded recipe is browsable and filterable by mod, type or item. Override, disable, duplicate or start blank. Vanilla crafting, cooking, stonecutting and smithing have hand-built forms, as do Create, Farmer's Delight, Ars Nouveau and common Mekanism machine types. Other types get a flat form generated from the KubeJS recipe schema, with raw JSON as the fallback.
- Tags: Pick a registry, find the tag, add or remove members. Additions and removals show inline against live contents so you can see the diff before queueing. This is the quick way to get modded items into
#minecraft:planksor#c:ingots/copper. - Loot: Real loot tables edited in place as a tree of pools and entries, with typed forms for conditions and functions: tool checks, random chance, Fortune bonuses, explosion decay, names, lore and nested logic.
- Properties: Base stats no recipe or tag can touch, from stack size and durability to hardness, light level and mining tier. Studio writes the matching modification script.
- Create: New items, blocks and fluids without touching a startup script, using version-correct builder types.
The Code Editor
If you already write KubeJS, the Files tab is a proper editor. Completion, hover docs and error checking are built from the running instance, not from a typings file that went stale two updates ago. Type event.recipes. and the list is the recipe types loaded in that pack, mods included. Diagnostics flag unknown members, misspelled ids, argument mismatches and events used from the wrong script type, and KubeJS console errors land on the offending line.
Nothing in the visual tabs writes straight to disk. Changes collect in a pending list, and Apply shows a diff, keeps a .bak of the previous version and reloads afterwards. Recipe, tag and loot changes can be written as KubeJS scripts or datapack JSON, per change. Eighteen built-in themes, a searchable settings dialog and rebindable shortcuts round out the workspace.
Final Thoughts
KubeJS Studio removes the guesswork from pack authoring. Whether you want a visual recipe builder or a context-aware script editor, it delivers both inside Minecraft, with plain output files you fully own. Download KubeJS Studio, open a world and press K.