Links
Tags
Creators
Details
Licensed MIT
Published 2 months ago
Updated 3 weeks ago
All versions
1.0.3-fix1
Release
Chat Translation 1.0.3-fix13 months ago 76
Compatibility
Minecraft: Java Edition
26.2
Platform
Fabric
Supported environments
Client-side
Required content
Any compatible version
Changes
New Features
- Added translation feature for outgoing messages.
- Added independent target language setting for outgoing messages.
- Added toggle in Mod Menu to enable or disable outgoing translation.
- Added locale texts for Simplified Chinese, English, German, French, Japanese, and Korean.
Bug Fixes
- Fixed an issue where messages sent by the player would be translated again after being echoed back by the server.
- Fixed an issue where MyMemory incorrectly sent the error message "Please select two different languages" as a translation result.
- MyMemory's source language detection now uses server-side auto-detection instead of incorrectly defaulting to English.
- Fixed potential out-of-order issues when sending multiple messages in quick succession.
- Fixed an issue where messages could be lost after translation failures.
- Prevented translated messages from re-entering the outgoing translation pipeline to avoid circular processing.
Behavior Notes
- Outgoing translation is disabled by default.
- Default target language for outgoing messages is English.
- Commands starting with
/will not be translated. - If translation fails, the result is empty, placeholders are corrupted, or the message exceeds the chat length limit, the original message will be sent instead.
- The server echo of the current player's messages will be displayed directly without undergoing a second translation.
- URLs, player names, mentions, and formatting content will be preserved as much as possible.
Optional dependencies
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:OvYCO8RT:hPSh7DRB"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:OvYCO8RT:hPSh7DRB"
}

