Tags
Creators
Details
All versions
4.0.0+1.21.5
Release
4.0.0+1.21.52 years ago 17.3K
Compatibility
Minecraft: Java Edition
1.21.5–1.21.8
Platforms
Fabric
Quilt
Supported environments
Client and server
Required content
Any compatible version
Changes
Major update to make the library compatible with 1.21.5
Additions
- New item data components:
combat-plus:melee_weapon- Holds two floats, weapon damage and offhand damage.
- All Melee and Dual weapons are expected to use this data component.
- Combat+ mods can use this component to acquire damage values for callbacks (interface values from MeleeWeapon should always be preferred).
combat-plus:cooldown_group- Takes an identifier and sets what group the item should use when on cooldown.
combat-plus:max_use_time- Determines how many ticks an item can be used for.
- This component was moved from Dual Swords.
- New enchantment component type: data component enchantment effects!
- Enchantments can grant temporary data components to items.
- The component is added when the item is enchanted and lost when the enchantment is removed.
- Currently supports:
- Cooldown Group
- Max Use Time
- Blocks Attacks
- New attribute: Protection Effectiveness
- Treated as a multiplier, this determines how effective protection enchantments are on the entity.
- Default value of 1 (normal effectiveness).
Changes
- Callbacks for blocking attacks now accept a damage source instead of the attacking entity.
Bugfixes
- Tridents are no longer unbreakable with KeepLoyaltyTridents.
- When using
KeepLoyaltyTridents, only tridents with Loyalty will go on cooldown.
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| combatplus-core-4.0.0+1.21.5-sources.jar | Unknown | 146.78 KiB |
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:NbKFMiE7:GcuSa4i9"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:NbKFMiE7:GcuSa4i9"
}

