2.6.0
Compatibility
Changes
2.6.0 - 2026-03-05
At this point, I have implemented all features I wanted to see in Wildex for now, so I am starting the port to newer versions (1.21.11) to be better prepared for the next update drop. If issues appear, the 1.21.1 version will of course still receive bug-fix updates.
Added
- Wildex Pedestal Block: Place a Wildex on the pedestal to show a rotating hologram of discovered mobs. The hologram can be turned off via redstone. The inserted Wildex is owner-protected in multiplayer.
- Wildex Analyzer Block: Insert an item and power it with redstone to run an analysis (~10 seconds). The inserted item must be one of the mob's Wildex loot items: if it can unlock a new Wildex entry, the item is consumed; otherwise the item is dropped back out with feedback.
- Models/Textures: Added custom block models/textures for Wildex Pedestal and Wildex Analyzer.
- Advancements: Added dedicated recipe unlock advancements.
- UI Sounds: Added interface sound effects.
- Admin Commands: New discovery management:
/wildex discover add <player> <mob_id>/wildex discover remove <player> <mob_id>
Changed
- Variant Labels: Shown as compact names (e.g., Blue) instead of generic Variant N (blue) labels.
- Header UI: The right header now appends the selected variant to the mob name (e.g., Sheep (Blue)).
- Stats Tab: Now shows attack damage split by difficulty as Damage (E/N/H) (Easy/Normal/Hard).
- Variant Probing: * Extended setter matching (setX, setXByKey, setXKey) for broader mod compatibility.
- Improved ResourceKey/ResourceLocation token handling for stable variant IDs.
- Remains client-preview scoped to keep multiplayer behavior safe.
Fixed
- Aether: Fixed Moa variants not being detected by Wildex variant discovery.
- UI Alignment: Fixed Share screen player-dropdown arrow alignment so the indicator sits correctly inside the dropdown box.
Compatibility
- Existing worlds: Supported.
- Migration: No world/save data migration required.
- Multiplayer-safe: Server-authoritative discovery/progress flow remains intact.
- Update path: Safe from 2.5.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:b5MY20xY"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:NiLz1hiU:b5MY20xY"
}

