I thought about that as well but I'm not sure the backend plausibility of the current proposal, let alone tying modules into the mix I'd -love- for something like that to happen though, but Range Amplifiers would have to be overhauled because the 15% gain just isn't worth it on a suit with only a 15-20m scan range (talking a whole 3m gain from taking up an entire slot)

Started thinking...So we can't get rid of team shared passive scans because of a backend issue. Active scans are all the rage (hemmorhoid removals abundant) but it's sort of argumentative as to how to fix them. I'm thinking maybe instead of trying to tackle both of those from their sources we should try to hit it from a different angle.

I dunno if it's really possible but perhaps changing the Minimap range on a role basis could cause enough of an impact to make a difference here as it would effectively eliminate passive scan benefits on more offensive roles (since passive scan results don't show chevrons) and reduce the overall value of active scanners wholly.

I believe the Minimap range is around 100m, if I'm not mistaken. So using that as a base, perhaps:

Sentinel: 50m <------> Scout: 100m

This would institute that the 'heavier' (more combat focused) your role, the less range you have on your minimap and thusly more reliance on your actual eyes as to where you're finding your targets. A Sentinel with a 50m minimap range would only be able to see passive scan results from friendlies in his immediate area and active scan results outside of that range would only show on his screen as a chevron. He'd know the direction fo his targets, but not how far away they are.

I think this would put a much greater emphasis on role interaction with EWAR as a whole and impact a lot of the problem areas we see with both passive and active scans. Discuss?