Tags
Creators
Details
Licensed Apache-2.0
Published last year
Updated 4 days ago
All versions
0.9.0-preview.2+26.3
Beta
Itematic 0.9.0 Preview 2 for 26.32 weeks ago 54
Compatibility
Minecraft: Java Edition
26.3
Platform
Fabric
Supported environments
Client and server
Changes
Itematic 0.9.0 Preview 2 for 26.3
13th of October 2026
This preview adds a new data-driven registry for item groups!

Changes
- Added data-driven item groups under the
item_groupdirectory in a data pack.
Item Groups
- A new registry for providing items for the Creative inventory.
- Format: A map with fields:
name: A text component. The name displayed when hovering over the group, as well as a title in all but the Survival Inventory group.icon: An item stack. The icon to display for the group.entries: An item group entry provider, list of item group entry providers, or hash-prefixed item group entry provider tag. The items to display in the group.
Example:
{
"entries": "#minecraft:building_blocks",
"icon": {
"id": "minecraft:bricks"
},
"name": {
"translate": "itemGroup.buildingBlocks"
}
}
- You can add your own item groups to the
#minecraft:creative_mode_groupstag to display them in the Creative inventory. - Any additional groups will be displayed on a separate page, and only ten groups from the tag will be displayed at once.
- If no item stacks are available in an item group, it won't display the group and later groups will be moved earlier in the list.
- The following groups are always in the same place:
- Operator Utilities (
minecraft:op_blocks) - Search Items (
minecraft:search) - Saved Hotbars (
minecraft:hotbar) - Survival Inventory (
minecraft:inventory)
- Operator Utilities (
- If any of these are removed with a data pack filter, they will no longer display in the Creative inventory.
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:ZclAAHfk:vVk8tJIx"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ZclAAHfk:vVk8tJIx"
}

