3.8
Compatibility
Changes
- One jar now covers Minecraft 1.20.1 to 1.20.4
- Hammers, excavators and greataxes no longer depend on item tags, so they work way better in big modpacks
- 3x3 tools now only break what the tool can actually mine, based on the tool type and its tier
- Tools are much more durable now, and a full 3x3 only costs 4 durability instead of 9
- The greataxe now costs 1 durability per 3 logs instead of 1 per log
- Fixed the greataxe not being able to break a log when there were no leaves nearby
- Added a greataxe leaves option: break no leaves, only the ones touching the logs, or all the connected leaves
- Leaves placed by players are no longer broken by the greataxe
- Added an option to turn off break particles for 3x3 and greataxe
- Extra blocks broken by 3x3 and the greataxe now respect claim and protection mods
- Extra blocks now give XP, count for stats and use hunger like normal
- Added a built-in config screen: Mod Menu on Fabric, and the Config button on Forge (no need for Configured anymore)
- Config options for sneaking and max logs actually work now on Fabric
- Fixed item tags getting wiped when Advanced Netherite isn't installed
- Fixed the Advanced Netherite compat recipes not loading properly on Forge and Fabric
- Wooden and stone hammers now use the same recipe shape as the iron one
- Netherite tiers are now ordered iron, gold, emerald, diamond in the creative tab
- New stone tool textures
- Tools stop breaking extra blocks when they're about to break (Forge)
- The 3x3 no longer triggers if the block you hit isn't something the tool can mine (Forge)
- New logo, new icon, new creative tab title and Catalogue support (banner, icon and background)
- New license (All Rights Reserved with limited non-commercial permissions)
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:Y6IqsJxk:Dae9wHOg"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Y6IqsJxk:Dae9wHOg"
}

