1.1.7+mc26.2
Compatibility
Required content
Changes
Just-Tiers 1.1.7 beta
PvPTiers replaces the discontinued MCTiers integration, and PvPHQ joins SubTiers and NovaTiers. This release supports Minecraft 1.21.10, 1.21.11, 26.1, 26.1.1, 26.1.2, 26.2 and 26.3, with a separate JAR for each version.
- Use PvPTiers in the former MCTiers yellow and PvPHQ in gray
#D2D2D2. - Enable or disable each site independently in configuration or with
/justtiers site <site> [true|false]. The old display-mode selector and/justtiers modecommand are replaced by these toggles. - With several sites enabled, show each site's best placement. With exactly one enabled, prefer its selected gamemode and fall back to its best placement. Disabling all four sites hides nametag tiers. Explicit player lookups still include all four sites.
- Support PvPHQ's 11 gamemodes and middle divisions, such as MT3. Middle divisions rank between high and low divisions of the same tier. Inactive placements are not treated as retired, and peak placements are ignored.
- Migrate existing MCTiers gamemodes and custom colors to PvPTiers. Old single-site display modes preserve that choice; the old all-sites mode enables all four.
- Update lookup rows, configuration previews, color palettes, icons and diagnostics for all four sites and 43 supported gamemodes.
- Add Minecraft 1.21.10 compatibility alongside the six existing targets.
Install the JAR for your exact Minecraft version with matching Fabric API and YACL. Minecraft 1.21.10 and 1.21.11 require Java 21 and YACL 3.8.2 or newer. Minecraft 26.x requires Java 25 and YACL 3.9.4 or newer, except 26.3 which requires YACL 3.9.7 or newer and Fabric Loader 0.19.5 or newer. Other targets require Fabric Loader 0.19 or newer. ModMenu remains optional. Server installation is unnecessary.
Optional dependencies
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:8zkz6d1C:JBNoC9ht"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:8zkz6d1C:JBNoC9ht"
}

