2.6.2
Compatibility
Changes
2.6.2 - 2026-03-09
Fixed
Fixed a multiplayer/login crash caused by third-party mod interactions during Wildex mob-count/probe entity cleanup.
Wildex now uses a safer cleanup path for temporary probe/display entities so faulty discard hooks from other mods no longer break login, completion checks, or related preview logic.
Compatibility
Existing worlds are supported. No world/save data migration required. Safe update path from 2.6.1.
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:NiLz1hiU:3KECKxoZ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:NiLz1hiU:3KECKxoZ"
}

