Tags
Creators
Details
Licensed LGPL-3.0-only
Published 4 years ago
All versions
Chat Patches
8.0-alpha.5+1.21.1-fabric
Alpha
8.0-alpha.5 for 1.21.1 Fabric9 months ago 124.2K
Compatibility
Minecraft: Java Edition
1.21–1.21.1
Platform
Fabric
Supported environments
Client-side
Required content
Any compatible version
Any compatible version
Changes
Chat Patches 8.0-alpha.5 for Minecraft 1.20.1-1.21.10 on Fabric, Quilt
- Chat log dumps can now be loaded in-game by renaming them to
chatlog.json. Note that this does not perfectly restore the original log, as most style data is lost - The chat input box will now be grayed out while the chat log is loading to prevent sent messages being moved to the end of chat history
- Now compatible with 1.21.9-10! (#269)
- Going forward, the
onlyInvasiveDraftingoption will be ignored and reflected as such in the config screen, as it's been implemented in vanilla
- Going forward, the
- Doesn't show the 'Hover Text' button in the context menu if there is none to show
- Now requires Placeholder API. Mod Menu also requires it since 9.2.0 (1.20.4) so this shouldn't be an issue; but <1.20.4 or on non-ModMenu installs, you will need to install it manually
- Dev notes:
- For IntelliJ users or anyone using an IDE with import optimization, YOU NOW MUST DISABLE IT BEFORE PROPOSING CHANGES. Stonecutter currently doesn't have a working fix, and typing the entire qualifier EVERYWHERE (especially for swaps) is simply unreadable. You may manually trigger optimizing IF you ensure all is well with the stonecutter directives BEFORE pushing changes, but the automatic system WILL DELETE THEM!!
- Updated the chat log to restore messages explicitly on the render thread, due to Minecraft's begging (crashing) over it - expect more issues to stem from this
Optional dependencies
Any compatible version
Any compatible version
Any compatible 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:yqCVgE2Z"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:MOqt4Z5n:yqCVgE2Z"
}

