Tags
Creators
Details
Licensed MIT
Published last month
Updated 3 weeks ago
All versions
1.1.2-paper
Release
PvPIndex Battles 1.1.2 (Paper)3 weeks ago 34
Uploaded by
Compatibility
Minecraft: Java Edition
26.1.x
1.21.x
Platforms
Bukkit
Folia
Paper
Purpur
Spigot
Changes
Added
- Configurable
api.max_api_payload_byteslimit (default 5 MB) guarding outgoing battle submissions; oversized payloads are automatically trimmed before submission via the newBattlePayloadSizeGuard. - Battle submissions to the PvPIndex API are now gzip-compressed (
Content-Encoding: gzip), reducing bandwidth for large replay payloads. - Oversized submissions rejected by the API with HTTP 413 are automatically retried with replay frames stripped, instead of failing outright.
- New message key
queue.arena_teleport_failedshown when a match cannot start because the arena world was not ready.
Changed
- Split the monolithic
BattleServiceinto focused collaborators (BattleStartHandler,BattleEndHandler,BattleSubmissionFlow,BattleSubmissionRetryHandler,BattlePayloadBuilder,BattleStartSetupStore) for clearer separation of concerns and easier testing. - Extracted API request/compression helpers (
ApiRequestBuilder,CompressionService) shared by the Paper API client.
Fixed
- Arena teleport failures no longer strand players in survival with their kit.
BattleQueueServicenow checks the result of the arena teleport; on failure the match is aborted, both players' pre-battle state is restored, and queued players are automatically re-queued instead of being left in the arena template world wearing battle gear. - Arena world save race on cleanup: arena worlds now have autosave disabled immediately after creation, and their folders are deleted a few ticks after unload (with retries) instead of synchronously, preventing
NoSuchFileExceptiononraids.dat/level.datunder Multiverse and similar world-management plugins.
Optional dependencies
Any compatible version
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:oRvmxM8N:WnlRBs40"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:oRvmxM8N:WnlRBs40"
}

