Links
Tags
Creators
Details
1.3.6+fabric-1.21.10
Compatibility
Changes
CodxLib 1.3.6
This file is for Fabric 1.21.10. It requires Fabric Loader 0.17.0 or newer — exactly what Fabric API already needs on 1.21.10, so CodxLib adds no restriction of its own.
Update notices no longer link to a download page. The codx mods are published on both Modrinth and CurseForge, and a notice that pointed at one of them was sending roughly half of you to a store you don't use.
The notice is now simply:
[OneBlock] Update available: 3.3.1 (current 3.2.0)
Update from wherever you installed the mod — your launcher, CurseForge, or Modrinth.
No API changes.
For players / server admins
- No more clickable link in the update message. Nothing else about the notice changed: it still appears on the server console at startup, and in chat for operators (or in single-player).
- The version number is now shown plainly —
3.3.1instead of3.3.1+26.1.2-neoforge. The trailing part named the build the file came from; with no file being offered it added nothing, and naming a loader in a message that isn't handing you a download was the confusing bit. - This affects every codx mod that uses CodxLib's update checker — OneBlock, CleanHUD, QuickCraft, Reflex, Health-hud, EnhancedTooltips, Chunky-Extended, ElytraPlus. You only need to update CodxLib; the mods themselves are unchanged.
- CodxLib is now on CurseForge as well as Modrinth, so you can install it from whichever you already use. The two carry identical files.
- Nothing else changed:
/codxlib versions,/codxlib help, and the rest behave exactly as in 1.3.5.
For developers (consumer mods)
- No API changes.
codx.codxlib.api.*is unchanged from 1.3.5, so there is nothing to adjust in your code or yourcodxlibversion range. UpdateChecker.updateAvailableMessage(mod, latest)keeps its signature but no longer appendsCodxNotify.link(...). If you render thatComponentyourself, expect a plain line with no click handler.- Modrinth is still the only endpoint queried — it remains the source of truth for
"is there something newer", including the per-loader filter added in 1.3.5. Dropping
the link is purely about not advertising one store over the other, so
ModInfo.modrinthSlug()is still required and still used for the query. CodxNotify.link(...)itself is unchanged and still available for your own messages.
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:6oyMM4yX:INcWc7Bc"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:6oyMM4yX:INcWc7Bc"
}

