Tags
Creators
Details
Licensed GPL-3.0-only
Published 2 years ago
Updated last year
All versions
1.0.7
Release
v1.0.7last year 230
Compatibility
Minecraft: Java Edition
1.21–1.21.5
Platforms
Folia
Paper
Purpur
Changes
CelestCombat v1.0.7 - Update Log
🆕 New Features
Enhanced WorldGuard Safezone Protection
- Client-Side Barriers: Barriers are now entirely client-side for improved server performance
- Selective Visibility: Only combatants see barriers - other players can pass through without issues
- Configurable Barrier Blocks: Customize barrier materials to match your server theme
Complete Trident Management System
- Trident Cooldowns: Full cooldown system with per-world configuration
- Combat Timer Integration: Optional combat timer refresh when trident lands
- World-Specific Bans: Restrict trident usage in specific worlds
New Administrative Commands
/celestcombat removeTag <player>- Remove a player from combat/celestcombat removeTagWorld <world>- Remove all players from combat in a world/celestcombat removeTagAll- Remove all players from combat server-wide- Console Support: All commands can now be executed from console
🔧 Improvements
Simplified Permissions
- Unified Structure: All command permissions merged into
celestcombat.command.use - Easier Management: Single permission node for all administrative functions
Enhanced Multi-World Support
- Better Compatibility: Improved integration with Multiverse-Core and Worlds plugins
- Per-World Settings: More granular control over world-specific configurations
📋 Configuration Updates
New configuration options have been added for:
- Trident management settings
- Enhanced WorldGuard barrier customization
- Debug mode toggle
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:2skx3Jm5"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:sJEHxBdW:2skx3Jm5"
}

