All versions
2.7.0
Release
Wildex Bestiary 2.7.04 months ago 39
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Changes
2.7.0 - 2026-03-10
Added
- Added a new Wildex mob-list filter menu:
- Friendly
- Neutral
- Hostile
- Tameable
- Added per-player persistence for Wildex list filter state:
- stored server-side
- restored after closing/reopening Wildex
- restored after relog/server restart
- Added per-player persistence for the
Show only discoveredtoggle. - Added optional Accessorify compatibility for spyglass discovery/overlay behavior:
- Wildex now supports spyglasses equipped through Accessorify accessory slots
- spyglass mob labels and discovery progress can work when using Accessorify's dedicated spyglass hotkey
- Added dedicated client/server sync for Accessorify spyglass usage state.
- Added new localized labels/tooltips for the new filter UI in English and German.
Changed
- Reworked the left-side mob list filtering flow so Wildex can combine:
- search query
- discovered-only toggle
- aggression filters
- tameable filter
- Reworked the filter UI from simple inline toggles into a dedicated expandable filter control.
- Improved filter button visuals and theme-specific presentation across Wildex themes.
- Added aggression/tameable caching for the mob index to keep the new filters responsive.
- Improved aggression classification reuse so index/filter logic and header extraction stay consistent.
Compatibility
- Existing worlds are supported.
- No world/save data migration required.
- Safe update path from
2.6.2. - Multiplayer-safe:
- filter/discovered-only state is stored server-side per player
- Accessorify support remains optional and only activates when the mod is present
- Important:
- client and server should run the same Wildex version for
2.7.0, because the Wildex player UI-state packet format was expanded.
- client and server should run the same Wildex version for
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:GVFemSLn"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:NiLz1hiU:GVFemSLn"
}

