Tags
Creators
Details
1.0.5
Compatibility
Changes
Celest Combat - Update Log
Version 1.0.5 (May 2025)
Bug Fixes
- WorldGuard Integration: Improved barrier system to prevent players from entering protected regions without visible barrier blocks - now more accurate and less intrusive
- Folia Compatibility: Resolved a scheduler conflict that prevented kill reward commands from executing properly
New Features
- Command Control System: Added a whitelist mode for commands during combat
- Players can now switch between blacklist mode (blocked commands) and whitelist mode (allowed commands)
- Provides more flexibility for server configurations
Kill Reward System Improvements
-
Global Cooldown: Added option for a server-wide kill reward cooldown that affects all players
- New
use_global_cooldownsetting in the configuration - When enabled, any kill will trigger a cooldown for all kill rewards across the server
- New
-
Permission-Based Cooldowns: Added support for permission-specific cooldown durations
- Configure different cooldown times based on player permissions
- Permission format:
celestcombat.cooldown.[group](e.g.,celestcombat.cooldown.vip) - Custom groups include VIP, MVP, and Elite with respective cooldowns of 12h, 6h, and 3h
Notes for Server Administrators
- The new whitelist mode for commands provides greater flexibility for controlling which commands can be used during combat
- When upgrading, review your cooldown settings as the new global cooldown option may change behavior if enabled
- Permission-based cooldowns allow for rewarding premium players with faster cooldown times
For any issues or feedback, please report them on our GitHub repository or Discord server.
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:ZQTLeXAM"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:sJEHxBdW:ZQTLeXAM"
}

