Links
Tags
Creators
Details
Licensed MIT
Published 5 months ago
Updated last month
All versions
1.7.1+neoforge.1.21.1
Release
AMI 1.7.1 (NeoForge 1.21.1)4 months ago 103
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Changes
1.7.1 - 2026-06-17
Changed
- Item icons in the grid and tree views now render through Minecraft's normal item rendering path, improving visual consistency with inventory icons.
- AMI's tooltip additions (stats, quest evidence, hints) now append to the end of the vanilla item tooltip rather than replacing it, so other mods' tooltip lines are preserved.
- Tooltip event priority changed to
LOWESTon Forge and NeoForge so AMI's lines always appear after other mods. - Entity icon atlas cache misses now show a placeholder instead of falling through to a live render, preventing flicker during atlas bake.
- Entity icon disk hydration, GPU bake scheduling, and 3D render-state setup were reworked to reduce cold-start warmup cost and avoid per-frame render-state churn while icons are prepared.
- Added a cross-loader entity icon render-policy guard so unsupported render paths fail closed instead of attempting unstable live rendering.
- Fabric overlay toggle and keybind ownership now follow the same visibility/input policy used on Forge and NeoForge, including config-screen and recipe-viewer edge cases.
- Added mod icon, homepage, source, and issue tracker links to all loader metadata files (Fabric, Forge, NeoForge).
Fixed
- Removed three broken EMI mixin inject targets (
mouseMoved,charTyped,tick) that no longer exist in EMI 1.1.24, fixing a mixin resolution error on startup. - Mod name is now always shown on item tooltips in AMI results, whether or not JEI/EMI is present to add it. Duplicate mod name lines from other mods are deduplicated.
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:QOM56zjQ:Q5ixLFuS"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:QOM56zjQ:Q5ixLFuS"
}

