1.16.1
Compatibility
Required content
Changes
Prestige bars track your sales again, and Sunken Treasure clears itself. MCLabs changed the message it prints when you sell chems, and 1.16.0 stopped recognising it, so the bars only moved when you ran /prestige progress. This also fixes the Sunken Treasure row that stayed on screen after the last barrel was found.
Download the jar matching your Minecraft version:
- Minecraft 1.21.11:
mclabs-addons-1.16.1-mc1.21.11.jar - Minecraft 26.2:
mclabs-addons-1.16.1-mc26.2.jar
Fixed
- Selling a single raw chem now moves your prestige bars. A sale that earns progress for just one raw chem prints the amount in the line itself (
Earned 104 prestige progress for Cactium.), and its hover only says "Click to see progress". Prestige tracking has only ever understood the other form,Earned prestige progress for Cactium and Potatium.with each chem's amount in the hover, which is what compound chems and sales of several raw chems print. So single raw chem sales have gone uncounted since tracking arrived in 1.15.0, and the bars only caught up when you ran/prestige progress. Both forms are read now. - The Sunken Treasure row goes away when a wave is over. The last barrel of a wave is announced as
has found the final treasure! All sunken treasures have been found!instead of "0 left", so the row stayed at "1 left" until you restarted. That line clears it now, and a wave with no treasure news for an hour (the Fishing Weekend ending with barrels still hidden, say) disappears on its own. /fwclears a leftover Sunken Treasure row during any weekend event. It only recognised the Fishing Weekend menu, so opening/fwduring a Farm Weekend did nothing. Any weekend menu with no treasure in it now clears the row.
Full changelog: https://github.com/Jade-Cod/mclabs-addons/compare/v1.16.0...v1.16.1
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:W09tZtbv:GqJw9pKc"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:W09tZtbv:GqJw9pKc"
}

