Tags
Creators
Details
Licensed CC-BY-NC-SA-4.0
Published last year
Updated last month
All versions
1.3.1
Release
CelestCombat Pro 1.3.17 months ago 399
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.x
Platforms
Bukkit
Folia
Paper
Purpur
Spigot
Changes
Add:
- Added configuration caching system to improve performance
- Added UXM Claims integration with runtime detection (no compile dependency)
- Added combat claim entry prevention
- Added PvP protection inside claims
- Added owner and trusted combat exceptions in claims
- Added teleport prevention into claims during combat
- Added per-world claim protection settings
- Added intelligent TTL caching for claim lookups
- Added advanced ender pearl glitch protection system
- Added micro-teleport exploit prevention
- Added barrier / bedrock / portal pearl protection
- Added tight-space teleport safety checks
- Added separate ender pearl cooldown system
- Added configurable event priority system
- Added dynamic event handler registration
- Added EventPriorityManager for caching and validating priorities
- Added /celestcombat eventpriority command to view current priorities
- Added Elytra combat restrictions (equip, shift-click, and glide prevention)
- Added automatic Elytra removal when combat starts
- Added CombatAPI method disconnectPlayerSafely(Player player)
- Added /celestcombat safeDisconnect <player> admin command
Fix:
- Fixed performance issues caused by repeated config lookups
- Fixed EssentialsX GUI command bypass
- Fixed Elytra being usable during combat
- Fixed ender pearl block-stuck teleport edge cases
- Fixed potential claim lookup performance issues
Improve:
- Improved plugin compatibility with other plugins using configurable event priorities
- Improved combat and teleport handling stability
- Improved item restriction handling during combat
- Improved combat start handling logic
- Improved overall plugin performance during player movement checks
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:Kp9Kt4QT:xe7CRQSz"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Kp9Kt4QT:xe7CRQSz"
}

