Tags
Creators
Details
0.16.4+1.18.2
Compatibility
Required content
Changes
0.16.4
Changes
Increased Banglum vein sizes.
Increased Midas Gold drops.
Nether Banglum Ores explode less frequently when Silk Touch + Efficiency/Fortune is used.
Nether Banglum Chunk drops happen more frequently when lucky.
Reduced Midas Gold Discard Chance.
Improved the effect Luck has on Midas Gold bartering.
Increased Durasteel yield from full ores when using a Tier 3 Forge Controller.
Improved Bronze tool textures.
Reduced Orichalcum Hammer mining speed by 10%.
Increased the chance of Carmot spawning in caves (Discard Chance 25% -> 12.5%).
Increased the healing from a Carmot Block in a Carmot Staff (2.5 Hearts -> 5 Hearts).
Reduced the cooldown of the Carmot Block healing ability (700 ticks -> 480 ticks).
Increased the attack speed of a Carmot Staff with a Netherite Block (0.6 -> 0.7).
Increased the range of small AoE Carmot Staff abilities.
Reduced the levels of the following abilities:
- Holy (For anyone wondering, Holy is just extra levels of Smite): 4 -> 3
- Natural Fire Protection: 2 -> 1
- Natural Feather Falling: 4 -> 3
Re-worked Carmot Shield
- You now gain more shield per armor piece, 4 -> 5
- The ability description has been updated to reflect this.
- Increased shield recharge rate
- Improved the rendering of the shield
- The shield now goes on a 2.5 second (50 tick) cooldown whenever you take damage
- The Particle trail will no longer show on players if the shield has 0 health
Fixes
Fixed an issue where Natural Armor Enchants would not apply correctly.
Fixed an issue where breaking blocks with Hammers would not respect the player.
Fixed an issue where Banglum Ores are not triggered by the Orichalcum Hammer.
Fixed a server crash related to a missing sound effect when using a Runite Block powered Carmot Staff.
Optional dependencies
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:bAWzYNRd:Kwa7yQEQ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:bAWzYNRd:Kwa7yQEQ"
}

