Tags
Creators
Details
1.0.3
Compatibility
Changes
⚔️ CelestCombat - Version 1.0.3
🛠️ Bug Fixes
-
🌀 Reload Command
- Fixed an issue where changes in the config file wouldn't apply after using
/celestcombat reload.
- Fixed an issue where changes in the config file wouldn't apply after using
-
🪖 Elytra Restriction
- Fixed bug won't allowing players to equip a chestplate when Elytra usage was blocked in combat.
-
🎁 Kill Reward Duplication
- Fixed a duplication bug causing kill reward commands to trigger multiple times under specific conditions.
✨ New Features & Improvements
-
🧊 Flight Permission During Combat
- Introduced a new permission to allow specific players to fly even while in combat.
# Permission: celestcombat.combat.fly # Description: Allows players to fly while in combat # Default: op -
🛑 Admin Kick/Ban Protection
- Players kicked or banned by server staff will no longer be punished for combat logging.
combat: exempt_admin_kick: true -
🔒 Toggleable Item Restrictions
- Item restrictions during combat can now be toggled on/off in the config.
item_restrictions: enabled: true -
🧭 Per-World Ender Pearl Cooldowns
- Customize ender pearl cooldowns per world, both in and out of combat.
enderpearl_cooldown: enabled: true duration: 10s in_combat_only: true worlds: minigames: false -
🧱 Custom Barrier Block
- You can now customize the block used for the WorldGuard safezone barrier.
safezone_barrier: block: RED_STAINED_GLASS_PANE -
🌐 Custom Language System
- You can now add your own custom language folder for personalized messages.
# For custom languages: # 1. Create a new folder in the language directory # 2. Use en_US/messages.yml as a template # 3. Modify messages.yml as needed # 4. Set 'language' in config to your custom folder name # ⚠️ Do not modify default language files directly!
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:gLMqbX8S"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:sJEHxBdW:gLMqbX8S"
}

