Tags
Creators
Details
1.0.0+mc1.21.11
Compatibility
Changes
1.0.0 — Initial Release
We are excited to announce the first public release of Evolution Tiers Tagger, a client-side Minecraft mod for both Fabric and NeoForge that brings Evolution Tiers competitive rankings directly into your game.
Tier Display Player tiers are now visible above their heads in the world and in the tab list, prepended to their username. Each tier label such as HT1, HT2, LT1, LT2, LT3, and Unranked is rendered in its official Evolution Tiers color, making it instantly recognizable at a glance. Retired players are marked with an R prefix (e.g. RHT1) to distinguish them from currently active competitors.
Peak Tier Optionally display a player's peak tier in brackets next to their current tier (e.g. HT2 (peak: HT1)), giving you a fuller picture of a player's competitive history and how they have trended over time.
Gamemode Support The mod supports all Evolution Tiers gamemodes. You can cycle through them using a configurable keybind and the display will update instantly across all visible players. A fallback option is available to show a player's highest ranking across all gamemodes if they are unranked in your currently selected one.
Player Search A built-in search screen lets you look up any player by their in-game name and view their full Evolution Tiers profile, including all gamemode rankings, region, total points, rank title, and last tested date.
Performance All API requests run in the background without blocking the game. Player data is cached for the duration of your session so repeat lookups are instant and network usage is kept to a minimum.
Configuration A full config screen gives you complete control over tier colors, display toggles, the API endpoint, and all behavior options so you can tailor the mod to exactly how you want it to look and function.
Platform Support
- Fabric (fabric-loader 0.16+)
- Minecraft 1.21.x
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:XCyvF8t3:ffH078Z3"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:XCyvF8t3:ffH078Z3"
}
