v1.1
Compatibility
Changes
E2EChat Update v1.1
A small update focused on security, stability, and command handling.
Fixes
- Fixed thread-safety issues with secure sessions and pending requests.
- Fixed an unnecessary encryption call in
/msg. - Fixed command interception occasionally failing in some setups.
- Fixed private message aliases not being filtered correctly from logs.
Improvements
- Improved async handling using concurrent collections.
- More reliable interception of
/msgand/secure. - Log filtering now covers all supported message aliases.
- Cleaned up internal code and improved Floodgate checks.
Added
-
Added support for standard Minecraft message aliases:
/tell/w/m/message
These aliases now work exactly the same as /msg and remain protected from server logging.
Notes
- No config changes required.
- No migration required.
- Fully backwards compatible.
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:D3muhOH4:AbZfnMQ9"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:D3muhOH4:AbZfnMQ9"
}
