Tags
Creators
Details
Licensed LGPL-3.0-only
Published 4 years ago
Updated last month
All versions
Chat Patches
202.6.3
Release
202.6.33 years ago 5,117
Compatibility
Minecraft: Java Edition
1.20.2
Platforms
Fabric
Quilt
Supported environments
Client-side
Required content
Changes
Chat Patches 202.6.3 for Minecraft 1.20.2 on Fabric, Quilt
- Should be compatible with Quilt again! (requires Loader 0.23.0+)
- Note that Chat Patches still isn't developed directly for Quilt, issues may still arise
- Added the
counterCheckStyleoption, which controls checking style data when condensing duplicate messages (#144) - Added the
chatNameColoroption, which overrides the color of playernames in vanilla chat messages. (#133) - Removed MoreChatHistory as incompatible, due to MixinExtra's compatibility injectors! (it's actually been compatible for a while, but I forgot to remove it)
- Dev info:
- Overhauled the publishing system for CurseForge and Modrinth, revived the GitHub Releases channel, and added a webhook to the Discord server to automatically post new releases! Now only uses modmuss50-publish-plugin, which is much cleaner and easier to use
- Moved most volatile Gradle variables to
gradle.propertiesto make it easier to change them - "Synced" some parts of the
build.gradlefile with the fabric-example-mod template to fix old warnings and keep it up to date - Added two specific methods to
StringTextUtilsfor use with dupe counter methods, to work with the newcounterCheckStyleoption - Removed the weird returning message reconstruction segment from
ChatUtils#getCondensedMessage(Text, int)because it was actually unnecessary! - Added some uncertain notes about certain aspects of the dupe counter process
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:MOqt4Z5n:LPwnOOhD"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:MOqt4Z5n:LPwnOOhD"
}



