Tags
Creators
Details
0.3.2
Compatibility
Changes
✨ New Features
- Slider element (type: "slider")
Bind to numeric game options (fov, mouseSensitivity, soundVolume, musicVolume, etc.) with customizable track and handle textures.
- Cycle element (type: "cycle")
Toggle through enumerated options (graphicsMode, cloudStatus, particles, chatVisibility, narrator, mainHand, etc.) with left/right arrow textures.
- List element (type: "list")
Scrollable container with automatic vertical layout. Supports any child elements and panel switching via switch_panel action.
- Catalog element (type: "catalog")
Navigation menu for settings screens. Click items to switch content panels, with optional selected highlight style.
- Panel switching action (type: "switch_panel")
Dynamically replace list content at runtime. Specify target list ID and new content definition file.
- Automatic layout system
Child elements in lists/catalogs can omit position.y – they stack vertically with configurable item_spacing and padding.
- Slider & Cycle style files
Separate JSON style definitions for slider (track/handle textures) and cycle (background/arrow textures).
🔧 Improvements
- Expression system extended
Added containerWidth and containerHeight variables for child elements inside containers.
- Internal rendering optimizations
Updated to Minecraft 1.21.x & 26.1 .
- Action system enhancements
All actions now work consistently across all supported screens.
🐛 Fixes
-
Fixed ResourceLocation construction issues in mixins.
-
Fixed mouse event forwarding for scrollable containers.
-
Fixed graphics matrix push/pop method name changes.
⚠️ Notes
-
Slider and cycle styles must be placed in slider_styles/ and cycle_styles/ folders respectively.
-
List content files go in panels/ directory; catalog definitions in catalogs/.
-
Use switch_panel with target (list element ID) and content (panel definition identifier).
-
Press F3+T to reload resource packs after making JSON changes.
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:qE8FcmJP:rPKXxXAT"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:qE8FcmJP:rPKXxXAT"
}

