i don't believe the current implementation where it projects a "bubble" effect stealthing nearby mechs is appropriate.
If you consider the fluff and the "real world" ECM comparisons, then ECM disruption is caused by broad-band interference (noise) generated by the ECM source (in this case, the ECM carrying mech).
This interference in hindsight makes the broadcaster extremely visible (in terms of the receiving end knowing that someone is jamming and therefore someone is "out there") but today, we see ecm working in the opposite, it makes things "quiet". i.e. there is a complete absence of information.
In other words, the current ECM module is functioning more as a STEALTH BUBBLE instead of a jamming device.
ideally, ecm should function (compared to real world examples) as such:
ECM equipped mech enable an ECM module, and starts putting out lots of noise, however, the noise has a range (say 200m). Enemy AND friendly mechs inside this ECM range should be "Jammed" and unable to use/see sensor data due to the broadband interference. Mechs being Jammed should very clearly be aware that they are inside an ECM interference zone. Mechs outside the effective "jam" zone on the other hand should have an EXTREMELY clear notification that something is out there making lots of noise (in other words, a big red fuzzy blip).
there's also a slight problem with the ECCM implementation
ECCM works by filtering and/or ignoring the noise and allowing the ECCM equipped mech to "burn through" the jamming and overpower the noise. it shouldn't magically "cancel" ECM. it currently works as a counter-jamming device (ECM within range of ECCM gets "canceled") which doesn't make a whole lot of sense either.
ideally ECCM should work a little more like this:
ECCM equipped mech finds itself inside a jamming field (within 200m of an ECM enabled mech). ECCM equipped mech enables ECCM module and is now able to detect previously "jammed" signals while inside the ECM bubble. Mechs without ECCM shouldn't benefit at all unless they can receive data from the ECCM equipped mech (say via C3?).
What this means to gameplay:
ECM shouldn't be a magic stealth bubble. nothing in ECM indicates it should be working as a stealth bubble signal black hole that just eats radar/sensor data. ECM should affect PROXIMITY targets (friend and foe) and not targets 1000m across a map outside of ECM range.
ECCM shouldn't be a magic anti-ECM that benefits an entire team. it should enable an ECCM equipped mech to burn through ECM while being jammed (i.e. for example maybe while within 120m of the jamming source.)
But most of all, the part that is completely counter-intuitive and disconcerting, is the STEALTH BUBBLE effect of ECM today.
If you want a good explanation of a what an in-game ECM implementation that adheres more to "real world" type ECM engagements feel free to check out the EVE implementation of ECM and how ECM and ECCM work in the EVE universe. In EVE ECM is a tool used actively against a searching party, not passively to "stealth" people around you.
Edited by Noodlesoup, 05 December 2012 - 05:47 PM.