All versions
2.7.3
Release
Wildex Bestiary 2.7.34 months ago 251
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Changes
2.7.3 - 2026-03-15
Added
- Added a small animated variant-probing status indicator next to the Wildex Entries counter while background mob variant detection is still running.
- Added a hover tooltip for the new variant-probing indicator so players can see that Wildex is still processing mob variants in the background.
Changed
- Reworked Wildex mob-list variant support detection so opening Wildex no longer runs the full variant discovery path just to decide whether a mob entry can expand.
- Wildex now uses a lightweight variant-support fast-path for the mob list and only performs full variant option discovery when variant entries are actually expanded/requested.
- Reworked the client-side mob index so the base Wildex mob list is reused from cache instead of being rebuilt from scratch every time the screen is reopened.
- Reduced unnecessary display-state normalization work during lightweight mob-index/support checks by avoiding the heavier preview/pedestal entity preparation path where it is not needed.
- Refined multiplayer server-config refresh behavior so Wildex only rebuilds the mob list and invalidates variant caches when list-relevant variant settings actually changed.
Fixed
- Reduced the short client hitch that could occur when opening Wildex in large modpacks with many mob-adding mods.
- Reduced additional Wildex reopen hitching caused by repeated mob-list/index rebuild work.
- Reduced avoidable variant-probe churn during multiplayer config sync so Wildex openings stay smoother while preserving server-authoritative variant settings.
Compatibility
- Existing worlds are supported.
- No world/save data migration required.
- Safe update path from 2.7.2
- Multiplayer-safe:
- variant exclusions remain server-authoritative
- full variant discovery still runs when variant entries are actually requested
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:jRMKaaFO"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:NiLz1hiU:jRMKaaFO"
}

