Tags
Creators
Details
26.1-8.0.1
Compatibility
Changes
Port recipe scan efficiencies from 1.21: Replace per-item recipe scans with a lazy bulk index. Eliminates long hangs on first login in very large modpacks. Pre-resolve all food nutrients on ServerStartedEvent and ship the entire cache to clients in one bulk packet on join (and after /reload), so JEI/REI/EMI tooltip indexing no longer triggers a flood of per-item sync requests. Adds cycle detection and client-side packet de-duplication for safety; bumps the network protocol version to 2.4.
Adjust recipe recursion algorithm to search more deeply and not cache results for non-food items when reached near the end of the recursion budget.
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:OECzAr94:Ef1r7FhU"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:OECzAr94:Ef1r7FhU"
}

