Links
Tags
Creators
Details
v1.6.1
Compatibility
Required content
Changes
Republish of 1.6.0 for the Modrinth pipeline. The mod itself is unchanged — if you already run 1.6.0 from the GitHub release, there is nothing new here.
1.6.0's Modrinth upload served the sources jar: the publish workflow picked .release.assets[0], and the sources jar happened to be listed first. The workflow now takes the first .jar that is not a -sources or -dev jar, and uploads it under its own name instead of release-asset.jar.
A release event reads its workflow from the tag it fires on, and v1.6.0 predates that fix — so re-firing it would have repeated the same upload. This tag carries the fix.
Requirements
- Minecraft 26.3
- Java 25+
- Fabric Loader 0.19.5+ and Fabric API
Full Changelog: https://github.com/paraf0x/mc_chat_tabs/compare/v1.6.0...v1.6.1
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:iRIAQEuO:4W1Al1XY"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:iRIAQEuO:4W1Al1XY"
}

