Tags
Creators
Details
All versions
1.1.0+neoforge-1.21.1
Release
KubeJS Studio 1.1.0 (NeoForge 1.21.1)6 hours ago 16
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Required content
Any compatible version
Changes
Minecraft 26.1
- Studio now has a NeoForge 26.1 build, alongside the existing NeoForge 1.21.1 and Forge 1.20.1 ones. It needs Java 25 and LDLib2 26.1.2.37 or newer
- EMI has no 26.1 release yet, so the EMI edit button is absent on that build only. JEI and REI are still picked up
Added
- Recipe conflict finder. It groups recipes that fight over the same inputs so you can see which one actually wins, and the groups collapse and expand
- Item usages view. Pick an item and see every recipe that consumes or produces it, without leaving Studio
- Bulk recipe operations. Filter with a regex, review the full match list, and remove or disable the lot in one queued change
- Typed component editor on 1.21.1. Item components get real forms instead of raw JSON, component ids complete and validate in the editor, and loot
set_componentsopens the same editor - Attribute modifiers. The Properties tab lists an item's attribute stats and lets you edit modifiers as an open ended list, written through KubeJS
- Embers Text API integration. Studio highlights and completes ETA markup inside string literals, previews the rendered result inline in the editor, and previews ETA fonts in Settings
- Tooltip line editor. Add tooltip lines with per line placement, reorder them by their drag handle, and watch a live preview that resizes and wraps long lines
- SNBT editing on recipe item inputs and outputs, so NBT sensitive ingredients are editable in the form instead of falling back to raw JSON
- Slot dragging. Drag an ingredient across slots to copy it or fill several at once, and right drag across slots to clear them
- Disk autosave for unsaved buffers. Close the game with a dirty file open and it comes back
- A Studio GUI scale setting, independent of Minecraft's, plus a separate UI font size setting
- Panel snap resistance and an overlay split mode for the main layout
- Queued operations can be reopened and edited from the dock instead of being cancelled and redone
- The loot browser filters tables by category
- The item picker and the recipe frame show your player inventory
- Workspace tabs stay alive across GUI closes
Changed
- New recipe, tag and loot changes now default to being written as KubeJS scripts rather than datapack JSON. The per change toggle is unchanged, and so is anything you already queued
- The editor's text shadow is off by default and its current line highlight is on
- On 1.21.1 recipe JSON is captured raw from the reload instead of being re encoded through its codec, so fields Studio has no form for survive a round trip untouched
- UI arrows are drawn as vectors, so they stay sharp at any GUI scale
Fixed
- NBT ingredients on Forge, unsaved buffer loss, and pending queue changes not surviving a restart
- The Studio window no longer stops filling the screen when the GUI scale changes, and scale changes are clamped to the screen and applied when Settings closes
- Queued mining tag operations replace each other instead of stacking up
- Queued tag and loot edits reopen through the deep link constructor, so the right row is selected
- Editor source text stays verbatim when Embers Text is installed, and caret positions stay honest under the inline preview
- Appearance settings apply even when a file buffer is unsaved
- The item usages dialog stays open while its item picker is up
- Recipe tool dialogs open over the whole screen instead of being clipped to a panel
- Result components are editable from the result slot
Optional dependencies
Any compatible version
Any compatible version
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:Hg4Bm0qD:mLwGzPMS"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Hg4Bm0qD:mLwGzPMS"
}

