1.14.1
Compatibility
Required content
Changes
For Minecraft 1.21.11 (Fabric, client-side). Drop mclabs-addons-1.14.1.jar into your mods folder alongside Fabric API. Mod Menu and Cloth Config are now both optional — add them only if you want the Mod Menu settings screen.
A maintenance release: the mod no longer drags in a dependency it barely used, no longer turns away perfectly good Fabric Loader versions, and will fail with a readable message instead of a crash if you run it on the wrong Minecraft version.
Added
- The "update available" chat notice is now clickable. When a newer version is found on join, clicking anywhere on the line opens that release's Modrinth page in your browser, where the download button and its changelog are — no more hunting for the mod page yourself. Hovering shows "Click to download" first, and Minecraft still asks for confirmation before opening any link.
Changed
- Cloth Config is no longer required to install the mod. It was only ever used to draw the Mod Menu settings screen, while the in-game HUD editor (
;) is where everything is actually configured — so it is now an optional dependency. Without it the mod runs normally and Mod Menu just shows no settings button; install it if you want that screen. - The mod now runs on older Fabric Loader versions. The requirement dropped from 0.19.2 to 0.17.3 (what Fabric API itself asks for) — nothing in the mod ever needed a newer loader, so anyone who hadn't updated theirs was being turned away for no reason.
- The Minecraft version requirement is now exactly 1.21.11 instead of "1.21.11 or any later 1.21.x". The mod hooks into internals that move between versions, so on a future 1.21.12 you now get a clear "requires Minecraft 1.21.11" message at launch instead of a crash.
Full changelog: https://github.com/Jade-Cod/mclabs-addons/compare/v1.14.0...v1.14.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:LsX98dA1"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:W09tZtbv:LsX98dA1"
}

