26.2.1
Compatibility
Changes
βοΈ Stability Update
This update focuses on modern compatibility, bug fixes, and performance improvements while preserving the original gameplay and plugin structure. No commands, configurations, or core mechanics were changed.
π Bug Fixes β Updated deprecated AsyncPlayerChatEvent to AsyncChatEvent (Adventure API) for modern Paper/Purpur compatibility. β Replaced deprecated new URL(String) with URI.create().toURL() for Java 20+ compatibility. β Migrated deprecated ActionBar API to player.sendActionBar(). β Replaced deprecated Title API with the Adventure showTitle() system. β Updated deprecated getMaxHealth() calls to the modern Attribute API. β Fixed /clan aceitar, where clan invitations were not being stored correctly. β Fixed a NullPointerException in /clan info when the clan leader was offline. β Fixed a member list substring error that could cause unexpected exceptions. β‘ Performance Improvements π SQLite now uses Write-Ahead Logging (WAL) for faster concurrent database access. π Clan saving now runs inside atomic database transactions, ensuring data consistency. π Implemented efficient UPSERT (ON CONFLICT DO UPDATE) operations. π Added database indexes for Kills, ELO, and XP, significantly improving ranking performance. π All database operations now use try-with-resources, preventing resource leaks. π KDR rankings are calculated directly in SQL instead of loading every player into memory. β Preserved Features
Everything that players and server owners expect remains exactly the same:
β Original package and class structure. β Original plugin.yml, commands, permissions, and aliases. β Original config.yml with no configuration changes. β Complete PvP system. β Combat Tag. β Clan system. β Betting system. β Rankings. β SentenΓ§a system. β OvO system. β Auto-save. β PlaceholderAPI support. β Update Checker. π₯ Compatibility
Fully compatible with:
β Purpur 26.2 (Build 2608) and newer β Previous Purpur versions β Modern Paper servers β Java 21+
This release is primarily a maintenance and optimization update, improving stability, compatibility, and database performance while keeping the plugin's original behavior completely intact.
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:AntFvWBZ:w8S7h4Rw"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:AntFvWBZ:w8S7h4Rw"
}

