Tags
Creators
Details
2.4.0-beta-1
Compatibility
Changes
This update is long overdue and I apologize for that. It's mostly fixes with amethyst geodes.
Highlight fixes: (Please re-enable these options if you disabled them specifically for these issues):
Fixed furnace crackle playing the sound in empty furnaces
Fixed mesa shafts crashing servers.
Fix new boats being glitchy by making them a clientside controlled vehicle once more. (Thanks embeddedt!)
New boats can also break lily pads
Added a mixin to fix stepping from a lower block into a two block tall entrance (Thanks again embeddedt!!)
(No fix for stepping from lower blocks onto stairs/slabs yet)
Fixed some ore generation issues that would cause stuff like diorite, granite, and andesite to not generate exposed to air
Fixed an issue with the mod's entity replacer which caused enabling new boats over old boats to completely break some worlds.
Non-highlight fixes, and new features
Added amethyst geodes and the relating blocks, calcite, smooth basalt, amethyst clusters (split into two IDs), budding amethyst and amethyst blocks.
Amethyst geodes currently generate in a circle. The vanilla 1.17 code is highly complex and I wasn't able to port it. The size of the circle still varies though.
Several workstation blocks from 1.14 have been added although they don't do anything yet. Their item description clarifies that they are currently non-functioning.
Blast Furnace and Smoker no longer show in NEI when they're disabled
Mesa mineshafts no longer carve bubbles in blocks above them. (For regular mineshafts being fixed, see BugTorch)
Fixed berry bushes not consuming bone meal
Frost walker no longer generates ice over entities
Fly-sprinting actually works now
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:o56psTwz:PYVn83vA"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:o56psTwz:PYVn83vA"
}

