All versions
2.6.1
Release
Wildex Bestiary 2.6.14 months ago 28
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Changes
2.6.1 - 2026-03-08
Added
- Added a new common config option
excludedVariantMobIds- only affects Wildex variant probing/subentries and does not hide the mob itself from Wildex
- Added client/server sync for
excludedVariantMobIdsso variant exclusions stay server-authoritative in multiplayer.
Changed
- Reworked Pedestal hologram rendering for better compatibility with complex modded renderers.
- AzureLib-based mobs now use a dedicated compatibility path instead of the old generic vertex-wrapping approach.
- Preview/Pedestal entity creation now normalizes more display-only entity state before rendering, improving presentation for some modded mobs.
- Variant exclusion matching now uses the same normalized ID filter logic as other Wildex mob filters.
Fixed
- Fixed a client crash caused by rendering certain modded mobs as Pedestal holograms:
- affected stacks included combinations such as AzureLib / TravelersLib / Sodium / Iris
- the crash was caused by the old vertex-consumer wrapping approach in the hologram renderer
- Fixed multiple Pedestal hologram rendering issues:
- reduced Z-fighting between hologram passes
- reduced unstable color flicker between blue hologram layers
- stopped hologram-only idle animation playback for displayed mobs
- improved hologram cone visibility
- Fixed AzureLib hologram side/transparency artifacts where large body surfaces could appear partially see-through.
- Fixed Jurassic Saga and similar growth-driven mobs rendering too small in Wildex/preview creation paths by preparing display entities in a stable adult/render-ready state.
- Fixed repeated variant cache invalidation when reopening Wildex:
- server config sync now only clears variant caches when synced values actually changed
Compatibility
- Existing worlds are supported.
- No world/save data migration required.
- Multiplayer-safe:
- discovery/progress flow remains server-authoritative
- new variant exclusion config is synced from the server to clients
- Safe update path from 2.6.0
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:P8DuNriu"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:NiLz1hiU:P8DuNriu"
}

