
CelestCombat
ArchivedA simple plugin that tags players in PvP and kills those who disconnect to prevent combat logging.
15.9Kdownloads
15followers
15.9Kdownloads
15followers
CelestCombat has been archived. CelestCombat will not receive any further updates unless the author decides to unarchive the project.
Tags
Creators
Details
Licensed GPL-3.0-only
Published last year
Updated last year
All versions
1.0.9
Release
v1.0.9last year 14.2K
Uploaded by
Compatibility
Minecraft: Java Edition
1.21β1.21.5
Platforms
Folia
Paper
Purpur
Changes
CelestCombat - Version v1.0.9
π‘οΈ New Features
- GriefPrevention Integration: Added comprehensive barrier system for GriefPrevention claims
- Configurable barrier materials and detection radius
- Permission-based bypass system with multiple access levels
- Customizable push-back force for claim boundaries
- Per-World Configuration: Both WorldGuard and GriefPrevention protections now support per-world enable/disable settings
- Granular control over which worlds have protection active
- Improved server performance by disabling protection in unused worlds
β‘ Performance Improvements
- WorldGuard Barrier Optimization: Significantly improved WorldGuard barrier performance
- Reduced CPU overhead during barrier detection
- More efficient boundary checking algorithms
- Smoother player experience when approaching protected zones
π Bug Fixes
- Fixed potential memory leaks in barrier detection systems
- Resolved edge cases where barriers could appear in wrong locations
- Improved error handling for invalid world configurations
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:sJEHxBdW:AK4LHivS"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:sJEHxBdW:AK4LHivS"
}
