Links
Tags
Creators
Details
Licensed MIT
Published last year
Updated last month
All versions
2.1.3
Release
Attract to Chat – Mob Attraction by Chat Messages 2.1.3last month 34
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Fabric
Supported environments
Server-side
Client and server
Required content
Any compatible version
Changes
- Fixed: handheld Walkie-Talkie chat attracts mobs again on Walkie-Chat builds that ship no proximity callback (all current 1.3.x builds).
- Fixed: hostile mobs now attack and destroy Walkie Block stations; "signal lost" notification and block-target behaviors (creeper ignition, enderman teleport) work.
- Fixed: a hostile that is already standing near a Walkie Block stops marching to the message and tears that station apart instead; a creeper that gets close detonates it.
- Changed: a station destroyed by an attracted mob drops nothing, so a raid on a relay network costs the network, not a free item.
- Changed: mobs no longer delete a Walkie Block in one tick. Every hostile now chips it down with the game's own cracking progress (stages 3 → 6 → 9) — slimes by hopping on top of it, everyone else by working at it — and one mob works a station at a time, so a crowd takes turns and the progress carries over when the worker dies. Creeper stays the exception: its explosion ends the station outright.
- Fixed: plain chat beside a Walkie Block attracted nothing at all. ATC suppressed it while waiting for a relay that never arrives — Walkie-Chat's own nearby-active-block probe ignores frequency, so anyone standing by a powered station was invisible to the mobs.
- Changed: a Walkie Block is only a target when the voice really came through the walkie network — a held walkie tuned to the same frequency as that block. Otherwise every message means the player, and mobs stop wandering off to smash hardware nobody asked them to.
- Improved: the "signal lost" notice now arrives like a walkie message — the mod's own channel prefix and receive click, to tuned players only — and names what destroyed it.
- Fixed:
/atc walkiechat compat enable|disablegates the whole integration in both directions. - Fixed: 1.19.2 Forge attracted mobs from nothing at all — its chat listener was registered on an event the 1.19.2 Forge never fires. It listens to the real chat event now, like the other loaders.
- Fixed: 1.19.2 Fabric ignored every chat message while Walkie-Chat was installed — ATC listened to a Fabric API event that Walkie-Chat's own chat interception stops from ever firing. ATC now hooks the chat packet itself, before anything can intercept it.
- Fixed:
/atc walkiechat proximity range|capsbonusnow does something — the values had no caller at all, so the documented "reach of Walkie-Talkie voices" was decorative. They act as a floor over the range Walkie-Chat reports, on builds that expose that callback. - Fixed:
@aactually parses —/atc ignore add|remove @aand the new/atc trollmode add|remove @awildcard worked only after this; the name arguments wereword(), which silently rejects@. - Improved: the Walkie-Chat reflection path applies ignored-players, vocal-fatigue and anti-spam, and records stats/debug for relayed messages.
- Improved: canceled chat is still processed while the Walkie-Chat integration is on (Walkie-Chat cancels every message it re-routes); with the integration off, other mods' cancellations are respected.
- Improved: reflection resolves once at startup, warns once per missing capability, and
/atc statusreports the true integration state. - Note: 1.19.2 keeps conflict-free coexistence with Walkie-Chat (no integration API in those builds).
Optional dependencies
Unavailable 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:o7LRRWJo:F2eO1Jby"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:o7LRRWJo:F2eO1Jby"
}

