Tags
Creators
Details
Licensed LGPL-3.0-only
Published 4 years ago
Updated last month
All versions
Chat Patches
8.0-alpha.8+1.21.11-fabric
Alpha
8.0-alpha.8 for 1.21.11 Fabric4 months ago 148.7K
Compatibility
Minecraft: Java Edition
1.21.11
Platform
Fabric
Supported environments
Client-side
Required content
Any compatible version
Any compatible version
Changes
Chat Patches 8.0-alpha.8 for Minecraft 1.20.1–26.1 on Fabric, Quilt
- Updated to 26.1! Like always with recent Minecraft drops, A LOT has changed under the hood, so be on the lookout for bugs!
- Requires Fabric Loader 0.18.0+ going forward
- Added another Band-Aid patch for #252, again thanks to SkyNotTheLimit!
- Added the Delete button to the context menu! When clicked it displays a warning forcing you to confirm or cancel the operation, because message deletion cannot be undone. The burn item sound will play when a message is successfully deleted as an extra indicator something happened. To be clear this is purely client side, nothing is actually deleted from the server chat
- Fixed non-vanilla messages formatted like vanilla ones having an extra space between the name and message (#233)
- Mostly fixed Chat Heads'
BEFORE_NAMEsetting not working with Chat Patches on 1.21.9+, thanks mostly to Fourmisain! (#285 + #297, and likely #233 too!) - Fixed a 1.21.10 crash from right-clicking to open the context menu (#298)
- Error and info toasts are now pushed on the render thread (#302)
- Fixed the duplicate counter not working with
counterCheckStyleenabled (#258)- Note: historically the duplicate counter suffers from bad edge-cases, so if yours doesn't work with specific messages please report them un... (trimmed)
Optional dependencies
Any compatible version
Any compatible version
Known incompatibilities
Any version
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:4TNAPaVq"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:MOqt4Z5n:4TNAPaVq"
}

