Links
Tags
Creators
Details
All versions
26.1-r1.0-fabric
Release
Combat Reborn 26.1-r1.0-fabric4 months ago 46
Compatibility
Minecraft: Java Edition
26.1.x
Platform
Fabric
Supported environments
Client and server
Required content
Changes
- 26.1 port
It is recommended you delete your existing weapon / armor configs when updating, in order to have the intended, up-to-date experience.
What's New
- 26.1 port
- critical damage attribute & tooltip
- additional improvements
Added
- Critical Damage Boost attribute
- Charge Damage Boost attribute
- critical damage tooltip (shown when holding shift by default)
Changed
- excess hunger from eating now overflows into saturation
- armor scaling now uses a linear formula by default
- duplicate attribute tooltips are now merged
- axes have +1 Critical Damage Boost by default
- updated default weapon / armor configs
- Cleaving now increases Critical Damage Boost per level, rather than base damage
- removed duplicate Quiver loot entries in Jungle Temple chests
Config
- in-game General config screen is now shown on NeoForge
- added
hunger_overflowboolean tohunger - added
tooltipscategory -
critical_tooltipenum accepts either SHIFT, ALWAYS or NONE to determine how the custom critical damage tooltip should be displayed
-
merge_attributesboolean allows the toggling of attribute tooltip merging
Integration
- End Reborn Netherite integration now works by providing
end_reborn:netherite_item_pathin configs, which overwrite vanilla / other mod path values when End Reborn is installed and End Reborn Netherite integration is enabled
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:b3L9JgTp:W4hvT3sx"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:b3L9JgTp:W4hvT3sx"
}



