Links
Tags
Creators
Details
2.1.2
Compatibility
Changes
Attract to Chat 2.1.2 for Minecraft 1.20.1 — optional Walkie-Chat integration: proximity chat, walkie block stations and hostile mob attacks.
- Optional Walkie-Chat integration, on by default and toggleable in-game with
/atc walkiechat on|off(or thewalkieChatCompatoption). Requires Walkie-Chat 1.3.2 or newer. - Mobs are attracted to proximity chat spoken through Walkie-Chat, using the effective range Walkie-Chat already resolved;
walkieChatProximityRange(default 15) andwalkieChatProximityCapsBonus(default 10) shape the result. - Hostile mobs that reach an active Walkie Block station destroy it, and every player tuned to its frequency receives a "signal lost" notification in their own language.
- Chat spoken through a handheld walkie or next to an active Walkie Block is routed by Walkie-Chat and is no longer double-processed by the engine.
/atc statusreports the Walkie-Chat compatibility state when the mod is present.- Investigation particles are now a personal choice: the old server-wide switch is gone and each player opts in with
/atc client particles enable|disable. Existing configs migrate automatically. - Forge: chat handling now listens at the lowest priority and receives canceled events, so attraction keeps working with Walkie-Chat installed.
- Attraction dedupe guard: a message relayed by Walkie-Chat through both its broadcast helper and the block relay attracts mobs only once. The guard keys on message identity and is cleared on server stop, so world reloads never leave it stuck and different messages are never swallowed.
Fabric requires Fabric API 0.92.7 or newer. Java 17 is required. Client installation is optional.
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:o7LRRWJo:qKgzf2MF"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:o7LRRWJo:qKgzf2MF"
}

