Links
Tags
Creators
Details
Licensed MIT
Published 5 months ago
Updated last month
All versions
1.8.3+fabric.1.21.1
Release
AMI 1.8.3 (Fabric 1.21.1)3 months ago 3
Compatibility
Minecraft: Java Edition
1.21.1
Platform
Fabric
Supported environments
Client and server
Required content
Any compatible version
Changes
1.8.3 - 2026-08-07
Added
- Added
/ami dump pokemon-coverage, writing pack-author/player-facing Cobblemon species coverage as JSON, CSV, and HTML underami_dumps/pokemon_coverage/.
Fixed
- Prewarmed AMI's cached result view ahead of a survival/creative gamemode switch made while the inventory is closed, instead of rebuilding it synchronously the next time the inventory opens. Fixes a stall/hang on opening the inventory shortly after a gamemode switch on large modpacks with limited heap headroom (e.g. Steam Deck).
- Made craftable filtering use the active recipe viewer and the current container state, so JEI/EMI craftable results stay accurate across open inventories.
- Fixed AMI config and panel-content dropdowns (e.g. "AMI Mode") not opening when clicked — the earlier Forge-compatibility click-ABI rename left the initial open click falling through to a no-op default handler instead of the popup logic.
- Centered AMI config row labels and controls vertically within their rows; they previously used fixed offsets that left them sitting low relative to their labels.
- Preserved EMI fluid tooltip names when AMI is layered over external recipe screens.
- Fixed JEI's ingredient list, bookmarks, and search bar sometimes still drawing alongside AMI when a pack's installed JEI build is newer than AMI's own JEI version — JEI's overlay draw methods are now targeted by name rather than by a version-pinned class reference, so suppression survives JEI renaming or splitting its internal rendering methods across releases.
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:XcP1830k"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:QOM56zjQ:XcP1830k"
}

