1.20.1-2.3.9
Compatibility
Changes
Natural Progression Changelog (1.20.1)
2.3.9
I've been super busy with work lately, so further updates are on an as-needed basis or unless someone provides a PR for a fix or requested feature, like this one! Thanks for understanding ❤️
Fixed:
- Pebbles not generating anywhere except for underwater.
- Thank you to kaiser_czar for this PR which fixed this issue.
2.3.8
Fixed:
- Not being able to break Wood/Stone using the right tool.
- "This tool is too brittle to use" tooltip showing on tools when ToolNeutering is disabled
Changed:
- Improved the layout and readability of the Config File
- Internal refactors to deduplicate the code that is responsible for checking if a block can be broken and handling damaging the player & cancelling the break progress
2.3.7
Added:
- Options to Disable Wood & Stone Punching damage
Fixed:
- Jade incompatibility, causing damage when just looking at wood or stone with a bare hand
- Twig placement being inconsistent and being able to replace non-solid blocks
2.3.6
Added:
- Ported over the config option for the "Incorrect Tool" damage - thank you Saereth!
- Config option to control the Knapping mechanic entirely
Fixed:
- Some of the Create Pebbles having a Missing Texture
2.3.5
Initial Port to 1.20.1 and Neo
Added:
- Support for Bamboo & Cherry Wood in Sawing/Axing Recipes
Changed:
- If you were using the
makeGroundBlocksHarderfeature, the blocks that are considered "ground" are now determined via the Block tagnatprog:earthy_blocks - If you were using the ability to require tools to break all wood-based blocks, you will now need to add every
single block to the tag
natprog:woods_requiring_toolbecause Mojang decided to remove a fundamental component of Blocks that has been there since before I started modding in Beta 1.7.3 😡 - Same as above, but for the requirement of a pickaxe-adjacent tool to mine stone-based blocks
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:VkVpYDxO:KK4OZz0e"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:VkVpYDxO:KK4OZz0e"
}

