Posted 07 April 2014 - 02:36 PM
There seems to be a good deal of miscommunication when it comes to what ECM-nerf advocates what to achieve and what game systems are involved in this rebalancing. I’m going to do my best to lay out how changes would be made to targeting, ECM, BAP, NARC, TAG, LRMs, and SSRMs. In the descriptions below, it is always assumed that a friendly is carrying the ECM unless noted otherwise.
Friendly units within the ECM bubble will now be Line-of-Sight (LoS) targetable by any enemy and appear on their personal minimap. However, friendly units within that bubble that are targeted by LoS will no longer appear on the minimap or be targetable by other enemies that do not have LoS, etc. If an enemy doesn’t have adequate sensor range and LoS, a friendly within the bubble cannot be targeted regardless of whether or not other enemies have said LoS. Exceptions for TAG and NARC noted later.
Multiple ECMs do not stack. The only benefit to bringing more than one ECM is having more than one bubble.
ECM has no effects on enemy units within its 180 meter bubble that are in addition to the effects described elsewhere.
TAG and NARC no longer function when shot at a unit protected under the ECM bubble, regardless of whether they are applied to the ECM carrier or a protected unit. Period. NARC no long disables the ECM of an ECM carrier.
LRMs can no longer be fired indirectly without TAG or NARC, regardless of whether or not the mech to be fired upon can be targeted or the presence of ECM. LRM flight speed will be sped up accordingly to reflect that they are now primarily a direct-fire weapon. When a mech is targetable they will still lock on, but that lock cannot be made without the LRM carrier having personal LoS on the target. If LoS is broken, tracking is lost regardless of whether or not units friendly to the LRM carrier have LoS. If a unit is TAGged, it is valid for targeting and for LRM locks and indirect LRM fire until it is no longer TAGged. If a unit is NARCed, it is valid for targeting and for LRM locks and indirect LRM fire until the NARC is exhausted. LRM locking mechanism will be altered so that the crosshair must remain closer to the center of the targeting box to remain locked – sort of middlish is no longer enough. This is complex enough to warrant some examples:
1) An enemy LRM carrier crests a ridge and obtains personal LoS on a friendly mech without ECM cover. That enemy LRM carrier may target the friendly, lock, and fire. Missiles will track until the friendly mech breaks LoS with the LRM carrier.
2) An enemy LRM carrier crests a ridge and obtains personal LoS on a friendly mech without ECM cover that has been NARCed. That enemy LRM carrier may target the friendly, lock, and fire. Missiles will track until the NARC is exhausted regardless of LoS.
3) An enemy LRM carrier crests a ridge and obtains personal LoS on a friendly mech without ECM cover that is currently TAGged by another enemy mech. That enemy LRM carrier may target the friendly, lock, and fire. Missiles will track until the friendly is no longer TAGged. If the TAG ceases but the LRM carrier still has personal LoS, missiles will continue to track until that personal LoS is broken.
4) An enemy LRM carrier sits behind a ridge without personal LoS on a friendly mech without ECM cover. Another enemy mech crests the ridge, obtains personal LoS on the friendly mech, and targets it. The enemy LRM carrier may target the friendly, but it may not lock or fire upon it.
5) An enemy LRM carrier crests a ridge and obtains personal LoS on a friendly mech with ECM cover. That enemy LRM carrier may target the friendly, lock, and fire. Missiles will track until the friendly mech breaks LoS with the LRM carrier. Note that this is exactly the same as with no ECM (#1).
6) An enemy LRM carrier sits behind a ridge without personal LoS on a friendly mech with ECM cover. Another enemy mech crests the ridge, obtains personal LoS on the friendly mech, and targets it. The enemy LRM carrier may not target, lock, or fire upon the friendly mech. (no target sharing of targeting on ECM-protected friendlies)
7) An enemy LRM carrier sits behind a ridge without personal LoS on a friendly mech with ECM cover. Another enemy mech crests the ridge, obtains personal LoS on the friendly mech, targets and TAGs it. The enemy LRM carrier may not target, lock, or fire upon the friendly mech as long as it remains under ECM cover. If it exits ECM cover and is still TAGged, the enemy LRM carrier may fire upon it regardless of LoS (see #3). Note that whether or not the TAGging mech targets the friendly is irrelevant.
8) An enemy LRM carrier sits behind a ridge without personal LoS on a friendly mech with ECM cover. Another enemy mech crests the ridge, obtains personal LoS on the friendly mech, targets and NARCs it. The enemy LRM carrier may not target, lock, or fire upon the friendly mech as long as it remains under ECM cover. If it exits ECM cover and is still NARCed, the enemy LRM carrier may fire upon it regardless of LoS until the NARC is exhausted (see #2). Note that whether or not the NARCing mech targets or maintains LoS on the friendly is irrelevant.
9) Basically, LRMs cannot fire indirectly without TAG/NARC, ECM has no effect if the LRM carrier has personal LoS for direct fire, and it prevents TAG and NARC from allowing indirect LRM fire.
The Target Retention module will still allow targets to be retained but will no longer allow LRM locks to continue after the target has left LoS. Because TAGged and NARCed LRM targets are not directly subject to LoS restrictions to be valid for targeting or for LRM locks, they do not additionally interact with the Target Retention module in any way.
BAP will now extend sensor range by 35% and increase target acquisition speed by 35%, up from 25% each. This will make it more worth carrying. However, any friendly unit that is inside the ECM bubble is not subject to these increased detection ranges and speeds. This means that a unit inside the bubble that carries BAP will be able to target an enemy while the enemy carrying BAP will not be able to target them in return. Make note that, due to proposed changes in targeting and ECM/SSRM interaction, BAP no longer needs to interact with ECM at close ranges. BAP will still detect shutdown enemies at 120m or closer. BAP has no impact on the ability to target ECM-protected enemies within normal sensor range because within that range ECM does not prevent personal LoS targeting.
SSRMs can lock based on personal LoS or on shared targeting data from other units that have LoS. When you throw in ECM and the rest this means that if you acquire a lock on a light mech that runs behind a building, several things can happen. Note that even though the language is the same as for LRMs, SSRMs still do not have ballistic trajectories or fire indirectly, so defacto personal LoS is required.
1) An enemy SSRM carrier crests a ridge and obtains personal LoS on a friendly mech without ECM cover. That enemy SSRM carrier may target the friendly, lock, and fire. Missiles will track until the friendly mech breaks LoS with the SSRM carrier.
2) An enemy SSRM carrier crests a ridge and obtains personal LoS on a friendly mech without ECM cover. Another enemy mech also obtains personal LoS on the friendly mech and targets it. The enemy SSRM carrier may target, lock, and fire on the friendly mech as long as it remains in the personal LoS of either of the two enemy mechs.
3) An enemy SSRM carrier crests a ridge and obtains personal LoS on a friendly mech without ECM cover. Another enemy mech also obtains personal LoS on the friendly mech, targets, and NARCs it. The enemy SSRM carrier may target, lock, and fire on the friendly mech until NARC is exhausted regardless of LoS.
4) An enemy SSRM carrier crests a ridge and obtains personal LoS on a friendly mech with ECM cover. The enemy SSRM carrier may target, lock, and fire on the friendly mech until the friendly mech breaks LoS with the SSRM carrier. (exactly like #1)
5) An enemy SSRM carrier crests a ridge and obtains personal LoS on a friendly mech with ECM cover. Another enemy mech also obtains personal LoS on the friendly mech and targets it. The enemy SSRM carrier may target, lock, and fire on the friendly mech until it breaks LoS with the enemy SSRM carrier, regardless of whether or not the second enemy mech maintains LoS. (No target sharing of ECM-protected mechs).
6) An enemy SSRM carrier crests a ridge and obtains personal LoS on a friendly mech with ECM cover. Another enemy mech also obtains personal LoS on the friendly mech, targets, and NARCs it. The enemy SSRM carrier may target, lock, and fire on the friendly mech until it breaks LoS with the enemy SSRM carrier. If the friendly mech loses ECM cover before the NARC is exhausted, the enemy SSRM carrier may target and lock on the friendly mech regardless of LoS until the NARC is exhausted. (NARC doesn’t function under ECM, no target sharing of ECM-protected targets)
7) An enemy SSRM carrier crests a ridge and obtains personal LOS on a friendly mech with ECM cover. Another enemy mech also obtains personal LoS on the friendly mech, targets, and TAGs it. The enemy SSRM carrier may target, lock, and fire on the friendly mech until it breaks LoS with the enemy SSRM carrier, regardless of whether or not it remains TAGged. If the friendly mech loses ECM cover, the enemy SSRM carrier may target, lock, and fire on the friendly as long as an enemy mech maintains LoS with the friendly. Since TAG requires LoS by default, this is exactly like #2 after the friendly loses ECM cover.