Tags
Creators
Details
3.0.0+1.21
Compatibility
Required content
Changes
Major patch to finally bring Combat+ into the world of 1.21, this update completely rewrites literally everything that even remotely interacted with enchantments.
For obvious reasons, version 3.0.0 contains breaking changes for almost everything.
Brief Overview
Yes, this is the brief version...
Check Github for the full details.
Additions
- Combat+ Core now reveals LilyLib to dependent mods.
- LilyLib was already bundled in the jar, it's just made available now.
- LilyLib patch notes will be included in Combat+ patch notes.
- Added several new enchantment components types:
combat-plus:post_charged_attackcombat-plus:post_critical_attackcombat-plus:post_killcombat-plus:bonus_damage- So items that are not the primary weapon can increase damage too.
combat-plus:gamerule_damage- Damage dealt against players is modified by the new gamerule.
- This allows for world-based PvP balancing.
- New gamerule that modifies enchantment damage effectiveness against players.
- Extra Damage Enchantments and Extended Enchanting both had their seperate versions of this gamerule before. They have been moved into Combat+ now.
- Added a small library of common effects and conditions for enchantments.
- Added a new type of enchantment effect: Double Entity Effect
- This is used by the Combat+ components and allows for effects for consider two entities at once.
- Added two built-in resource packs:
- One provides Roman Numerals for enchantments with a level over 10 (up to 255).
- One replaces Roman Numerals for enchantment levels with plain numbers (up to 255).
- Vanilla Maces are considered melee weapons by Combat+.
- Added two new loot functions.
Changes
- Sharpness, Smite, Bane of Arthropods, and Fire Aspect are now overriden entirely by Combat+ Core to change their supported item tags.
- Previously a mixin was used to change the tags instead.
- Smite and Bane of Arthropods use the new
combat-plus:gamerule_damagecomponent.
- The enchantment types of Combat+ (Additional Damage, Offhand, Weapon Utility, Aspect) have been converted into enchantment tags.
- Combat+ Enchantment Helper methods have different parameters.
Removals
- The entire old enchanting system. :(
New Features From LilyLib
- Enchantment datagen provider
- DamageType datagen provider
- DamageType tag datagen provider
- Enchantment Containers
- Combines a registry key with an enchantment builder. Highly useful for eliminating code duplication if you need to bootstrap your enchantments.
- Also contains useful utility for getting registry entries of the enchantment.
- DamageType Containers
- Combines a registry key with a damage type. Highly useful for eliminating code duplication.
- Also has utility methods for generating damage sources.
- Fabric resource condition to only load certain things when in dev mode.
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| combatplus-core-3.0.0+1.21-sources.jar | Unknown | 118.97 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:7Mq5ZPPv"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:NbKFMiE7:7Mq5ZPPv"
}

