Tags
Creators
Details
8.0-alpha.10+26.1.2-fabric
Compatibility
Required content
Changes
Chat Patches 8.0-alpha.10 for Minecraft 1.20.1, 1.21.1+5, 1.21.8–26.2 on Fabric, Quilt
-
Published builds now come with signatures
and checksums! This means you can verify the integrity of Chat Patches builds (and ensure they haven't been tampered with)! See the README for more info! Currently only available on Modrinth. -
The placeholder (
$) intimeFormatis now optional (#277) -
Prevents vanilla's command history from being loaded if the chat log is enabled (#300)
- Note: I wrote this a while ago but couldn't publish it due to dependency requirements, so lmk if you find any issues!!
-
Added an updated
ko_krtranslation thanks to ettip in #317! (I have no idea why the original translation was removed) -
Increase max compact chat distance to 50 (#319)
-
Partially implemented #323 (fix for a Feather-related crash)
-
Fixed the chat un-scrolling after deleting a message when
contextDeletionWarningwas enabled -
Added a toggle for the message deletion sizzle sound
-
Known issues:
- Entering an invalid value to a config option will falsely log a "Value mismatch! Reset to binding's getter" error
- Modrinth (and apparently the buildscript) doesn't support uploading checksum files yet, despite the capability existing now
-
Dev notes:
- Added Fletching Table as a dependency, which primarily allows for versionable mixins (needed for #300 and the future implementation of
- #109 on 1.21.11+)
Optional dependencies
Known incompatibilities
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| chatpatches-8.0-alpha.10+26.1.2-fabric.jar.asc | Signature file | 273 bytes |
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:WkegsqJ8"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:MOqt4Z5n:WkegsqJ8"
}

