Tags
Creators
Details
All versions
1.1.0-26.1
Release
RevivalPVP 1.1.0-26.15 months ago 20
Compatibility
Minecraft: Java Edition
26.1.x
Platform
Fabric
Supported environments
Client-side
Changes
1.1.0 - Dynamic Kit Catalog
Added
- Potions kit in the hub picker: classic 1.8 PotPVP style. Iron sword + iron armor + splash heals/harm/strength + golden apples + cobwebs.
-
- Axe kit in the hub picker: netherite shield-breaker. Sharpness IV netherite axe + heavy armor + totem offhand + iron sword backup.
-
- Dynamic kit catalog: kits are now loaded from the backend on hub open. Future kit additions and rebalances no longer require updating the mod. ### Changed
-
- Kit metadata (icon, display name, description, default loadout preview) is now fetched from the backend instead of being hardcoded into the mod. - Hub kit row scrolls horizontally to fit the growing kit list (currently 11 visible kits).
-
- 3D loadout viewer now reflects the per-slot variants that the backend serves, so customize-loadout previews stay accurate after server-side rebalancing.
-
Server-side improvements rolling out in the same window These apply to everyone on RevivalPVP regardless of mod version, listed here so the patch-notes feel complete:
-
- Trident kit Riptide now triggers on dry land in duels, with a 5-second cooldown and an action-bar "Riptide ready in Xs" indicator.
-
- Each duelist gets a per-arena WorldBorder at duel start, preventing pearls and Riptide dashes from leaving the arena slot.
-
Compatibility
-
- Minecraft 26.1 (Fabric Loader 0.18.6+, Fabric API 0.145.4+26.1.1).
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:MYXmY3av:Km2iNXgn"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:MYXmY3av:Km2iNXgn"
}

