Links
Tags
Creators
Details
1.3.1
Compatibility
Required content
Changes
- Better Search Sorting: Search results are now sorted by relevance! Advancements that you're close to completing will appear at the top (sorted by progress percentage), while already completed ones move to the bottom.
- Search Optimizations: Search is now noticeably faster and uses memory much more efficiently.
- Fixed Icon Search: Searching by item icons was broken because it checked raw item IDs instead of display names. Now it searches by the item's actual hover name (including custom names and localized languages).
- Custom Icon Names Support: Creators can now set a custom name on an advancement's icon item. The search will find the advancement using this custom name, even if the text isn't in the advancement's title or description.
- Hide Advancements Option: Added support for a custom tag (
advancements_search:hide_mode) in custom_data: 1 — Hides the advancement if it's not completed yet (great for secret or custom advancements). 2 — Hides the advancement permanently from search results. - Improved Hover Cursor: Hovering over an advancement in the search list now changes your cursor to a click pointer to clearly show it's interactive.
- Smoother Highlight Animation: Clicking an advancement to locate it in the tab menu now triggers a smoother, longer, and softer flashing animation so it's much easier to spot.
- .. and Minecraft 26.3 Support!
--
Under the hood, the mod has been completely rewritten to use Lapis KSP — a custom mixin generator that lets us write mixins natively in Kotlin. Because of this, the mod now requires Fabric Language Kotlin. This transition is a huge milestone: it allowed us to roll out this update so quickly right after the new version released. Thanks to Kotlin and this new setup, future updates will be coming out much faster and without delays!
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:Ccho67RI:mFc7amLp"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Ccho67RI:mFc7amLp"
}

