Tags
Creators
Details
Licensed LGPL-2.1-only
Published 4 years ago
Updated 3 months ago
All versions
1.3.4-1.21.1-NeoForge-HF1
Release
Combatify 1.21.1 1.3.4 NeoForge HF15 months ago 736
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client-side
Server-side
Client and server
Required content
Any compatible version
Any compatible version
Any compatible version
Any compatible version
Changes
Changes:
- Tiered Shields have been redesigned, with some notable changes:
- Iron, Gold, and Diamond Shields now take Blocks of Coal, Blackstone, and Obsidian respectively to craft
- Iron, Gold, and Diamond Shields now provide 0.5 Shield Strength
- Copper Shields now take 1.1x disable time
- Iron, Gold, and Copper Shields now have higher base durability
- Golden Shields now take half the durability and have 0.8x disable time
combatify:extended_blocking_datacomponent had its fieldconsiders_bannerreplaced withbanner_damage_reductions- Has the same format as the damage reductions on
minecraft:blocks_attacks, however will be applied in addition when the shield has a banner
- Has the same format as the damage reductions on
- On 1.21.1,
combatify:blockerhas been altered to suit the new necessary functionalities for the tiered shields- Added the field
item_damage, matching the equivalent on theminecraft:blocks_attackscomponent in vanilla - Added the field
disable_cooldown_scale, scales the amount of disable time this blocking item will take
- Added the field
Config Changes:
- Nothing to see here
Fixes:
- Fixed pack format for built-in datapacks (no longer shows unsupported)
- Fixed creative block breaking being slow on 1.21.11
- Fixed durability taken by shields having an improper threshold
- Fixed shield banner recipe for tiered shields
Optional dependencies
Any compatible version
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:kRYhslBa:RpWSA3ld"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:kRYhslBa:RpWSA3ld"
}

