All versions
1.1.2
Release
MCPvP Ranked 1.1.2last month 5
Compatibility
Minecraft: Java Edition
26.3
26.2
26.1.x
1.21.11
Platform
Fabric
Supported environments
Client-side
Changes
MCPVP Ranked 1.1.2 — Update Log
ELO rules
- Emerald and up: win ELO gains now scale with your win streak — +5 to +8 depending on streak length, jumping to +12 per win once you hit a 10-win streak.
- Netherite: flat +5 per win, no streak bonus.
- Diamond and up: losses are now much heavier — Diamond −25, Netherite −30 (up from −8).
- Team matches (anywhere more than one name is listed per side, or a "Team won the round" message) no longer affect ELO or placements at all.
Version lock
- The mod now sends its version with every request. The ranked database refuses to save results from anyone running an outdated version — old versions can no longer grind matches without counting.
- Players on an outdated version see an "update required" screen instead of the ranked menu.
Player profiles
- Click any player on the leaderboard, or search for them by name, to open their profile: full skin in the middle, per-kit ranks on either side, overall record and recent match history below.
- New
/statscommand opens your own profile the same way;/stats <player>opens anyone's.
Leaderboard
- Added a search bar.
- Filter buttons are now sized to fit their labels, so kits like "SpearMace" no longer get cut off.
Rank-up celebration
- Promotions now open a full-screen animated celebration (tier icon, ELO count-up, confetti) instead of just the small HUD banner. Toggle it off in Settings if you prefer the old banner.
Fixes
- mcpvp.com's ranked results no longer show the opponent as "Unknown" — the mod now identifies them from who's nearby during the match.
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:xwIsZd7D:yTPLLwV2"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:xwIsZd7D:yTPLLwV2"
}

