Tags
Creators
Details
Licensed MIT
Published 9 months ago
Updated 4 months ago
All versions
2.2
Release
ChatReply 2.24 months ago 446
Compatibility
Minecraft: Java Edition
1.21.x
Platform
Fabric
Supported environments
Client-side
Required content
Any compatible version
Changes
Official ChatReply Version 2.2
What's New?
- YACL Configuration: The old custom config flow has been replaced entirely by YetAnotherConfigLib (YACL).
- Mod Menu Integration: You can now open the configuration directly from your Fabric Mods screen.
- Recall Menu Screen: Pressing the C keybind now opens a dedicated recall menu screen.
- Keybind Interface: Added a dedicated ChatReply keybind menu screen, complete with a jump/filter helper that instantly focuses on ChatReply-related binds.
- Overhauled Commands: Redesigned the
/chatreplycommand flow:/chatreply help/chatreply status/chatreply toggle/chatreply config(reliably opens the config UI via a client-thread-safe screen open)- Note:
setmessage,setresponse,senddelay, andstopsenddelayremain completely unchanged.
- Command Cleanup: Running the root
/chatreplycommand no longer dumps the status block into your chat. - Interval Hardening: Added strict validation for scheduled intervals. The minimum interval is now enforced at 10 seconds, and invalid values are automatically sanitized on save.
- Stability Fixes: Fixed a crash path in custom screens by removing blur-based background calls and replacing them with a safe, translucent fill. Added YACL screen mixin support to improve background readability tuning.
Requirements
- Minecraft 1.21.1 – 1.21.11
- Fabric Loader 0.15+
- Fabric API
- YetAnotherConfigLib (Yacl) Correspondent with your minecraft version.
Example Images:

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:elQNnDre:eREup9m3"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:elQNnDre:eREup9m3"
}



