v2.4.1+mc26.2
Compatibility
Changes
Bug fix update and some improvements.
Bugs:
-
Fixed a bug with the villager bell trade (specifically for armorers) where there was a price inconsistency when using demand mitigation, making the emerald purchase appear ghosted or inaccessible with high demand.
-
Fixed a bug in the update checker where external components were missing, causing the download option to always be available even when the current version of the mod was installed.
Improvements:
- Demand mitigation has been improved and is now more consistent using decimals.
Explanations:
Demand mitigation has a base cap, and some trades have a base price. Unlike discounts, it works completely differently from any base calculation. The base price influences the demand increase. The lower the base price, the less noticeable the mitigation. If you want total consistency for demand, turn it off completely so there’s no demand increase.
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:Yf8KPA8u:AyEVJtaI"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Yf8KPA8u:AyEVJtaI"
}

