Tags
Creators
Details
1.0.0
Compatibility
Changes
CelestCombat
A comprehensive combat management plugin for Minecraft servers specializing in PvP environments.
Requirements
- Minecraft Version: 1.21 - 1.21.4
- Server Software: Paper, Purpur, Folia
- Java Version: 21+
Optional Dependencies
- WorldGuard - For safe zone integration and region protection
- GriefPrevention - For claim-based protection systems
Installation
- Download the latest release from Modrinth
- Place the
.jarfile in your server'spluginsfolder - Restart your server
- Configure the plugin in
plugins/CelestCombat/config.yml - Reload with
/cc reload
Commands
| Command | Permission | Description |
|---|---|---|
/cc help |
celestcombat.command.use |
Display command help |
/cc reload |
celestcombat.command.use |
Reload plugin configuration |
/cc tag <player1> [player2] |
celestcombat.command.use |
Manually tag players in combat |
/cc removetag <player/world/all> |
celestcombat.command.use |
Remove combat tags |
Aliases: /cc, /combat, /celestcombat
Permissions
| Permission | Default | Description |
|---|---|---|
celestcombat.command.use |
OP | Access to all plugin commands |
celestcombat.update.notify |
OP | Receive update notifications |
celestcombat.bypass.tag |
false | Bypass combat tagging |
Building
git clone https://github.com/ptthanh02/CelestCombat.git
cd CelestCombat
./gradlew build
The compiled JAR will be available in build/libs/
Contributing
- Fork the repository
- Create a feature branch
- Make your changes
- Test thoroughly
- Submit a pull request
Support
- Issues & Bug Reports: GitHub Issues
- Discord Community: Join our Discord
Statistics
License
This project is licensed under the CC BY-NC-SA 4.0 License - see the LICENSE file for details.
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:4GvKVgg3:PggApEBv"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:4GvKVgg3:PggApEBv"
}

