1.0.5+mc26.3
Compatibility
Required content
Changes
Chat Ping 1.0.5
- Only recognized messages from other players can trigger a notification.
- Server-formatted chat must have a recognized sender present in the client player list.
- Match results, victory notices, kill messages and unrecognized server notifications no longer trigger pings just because they contain your name.
- Your own messages remain silent, including player-head and rank prefixes.
- A real player mentioning your name while discussing a win still triggers a ping.
- Custom sound still uses Master Volume independently of UI volume.
- 51 automated mention and cooldown checks passed.
Client-side Fabric mod. Requires Fabric API. Mod Menu is optional for settings.
Compatibility: custom nicknames or unsupported chat layouts can be ignored rather than risk a false notification.
Optional dependencies
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:dGd6TKYt:1GvP3FhU"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:dGd6TKYt:1GvP3FhU"
}

