Tags
Creators
Details
Licensed Apache-2.0
Published 11 months ago
Updated 2 weeks ago
All versions
0.8.0-preview.2+26.1
Beta
Itematic 0.8.0 Preview 2 for 26.13 weeks ago 15
Compatibility
Minecraft: Java Edition
26.1.x
Platform
Fabric
Supported environments
Client and server
Changes
Itematic 0.8.0 Preview 2 for 26.1
15th of September 2026
This preview improves unloadable items and fixes related bugs.
For a few more details regarding the new future you can look at the roadmap to 26.x!
Changes
Items
- Unknown items now use a model instead of being rendered as-is.
- This model is built-in and thus cannot be overridden.
- This makes them more consistent with the way they are rendered and with other models and also makes them work automatically instead of needing special overrides.
- This means that they no longer face the camera in certain places.
- Item stacks with unloadable items can now properly stack up to their current stack size.
- For example, a stack of 30 will use 30 as its max stack size until the count is modified, such as by splitting the stack in half, in which case it will be 15 for both item stacks.
- This prevents them from being accidentally destroyed.
- This also means that the item stack can still be moved around without snapping to a single item, while at the same time it prevents a player from accidentally overflowing item stack counts.
- This is the case because the game cannot be certain about the actual max stack size; The item doesn't exist after all!
- Unloadable item stacks now display their count where appropriate, just like normal item stacks.

Fixes
- Picking container blocks with unloadable items now creates an item stack correctly.
- Unloadable item stacks now no longer incorrectly match with empty stacks in certain places.
- Unloadable item stacks now no longer snap to a single item when moved around in an 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:Q3bSkhnR"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ZclAAHfk:Q3bSkhnR"
}

