Links
Tags
Creators
Details
All versions
2.7.2
Release
Wildex Bestiary 2.7.27 months ago 66
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Changes
2.7.2 - 2026-03-11
Changed
- Reworked Wildex right-panel data loading so expensive server-side info is now requested strictly on demand per active tab.
- Loot, Spawn, and Info/Misc data are no longer preloaded implicitly while just opening Wildex or rapidly cycling through mob entries.
- Added explicit loading states for lazy-loaded right-panel tabs so users can see that data is still being fetched.
- Added client-side retry windows for lazy-loaded tab requests so dropped/throttled requests do not leave tabs stuck in a permanent loading state.
- Reduced repeated progress/completion snapshot work in the server-side discovery flow to lower short hitch risk when many entries are unlocked in quick succession.
Fixed
- Fixed noticeable server/world lag spikes when opening Wildex for the first time in a fresh world and quickly switching through many mob entries.
- Fixed unnecessary breeding/taming extraction work being triggered just by selecting mobs, even when the
Infotab was not open. - Fixed cases where the
Loottab could remain onLoading loot data...indefinitely after rapid navigation. - Reduced short TPS/world lag spikes when multiple Wildex entries are discovered in rapid succession.
- Fixed Cobblemon variant labels in the Wildex mob list so Pokemon species/forms are shown with their proper names again instead of collapsing to generic tokens like
Normal.
Compatibility
- Existing worlds are supported.
- No world/save data migration required.
- Safe update path from
2.7.1. - Multiplayer-safe:
- discovery/progress flow remains server-authoritative
- lazy-loaded Wildex tab data is still requested and validated through the server
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:k1LXjX1s"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:NiLz1hiU:k1LXjX1s"
}

