I just don't see what the problem with this d-scan immunity is. I don't fly combat recons so I'm not gaining anything from this, so I don't have a horse in the "must have" race. I'm just not seeing any problem with this being used against me. If I sit in a plex I'm going to need a scout or be ready and aligned if I want to be "safe", and frankly why would I want that if I'm in a plex?
Could someone explain exactly why this is a bad change?
It makes protecting a wormhole system more time-consuming/tedious. In smaller systems, you can find one or two spots that will let you d-scan pretty much everything. Granted, it doesn't spot cloaks, but in order for that cloaked ship to steal your resources (i.e. mine, harvest or run sites), they have to decloak. With d-scan immune combat recons, they can be in a site, and you won't even know they're there: no local, no d-scan. The only way to even know they're there is to go into the site itself and/or have someone do nothing but site parked, cloaked off every wormhole.
They'll become the defacto tackle in wormholes. Site the DPS safely outside, send in a Lachesis (or, worse, a Lachesis and any other combat recon) to tackle, and the DPS squad has plenty of time to jump in and warp to the victim.
Similar issues apply to faction warfare. You won't be able to check complexes on d-scan. You'll have to go in, slide the gate and visually verify whether there's a recon in there. And you'll have to use a combat recon to do, otherwise, the recon in the site will see it coming and just move.
Unlike the Mobile Scan Inhibitor that PYRE used in Arnstur, you at least knew
something was there. You didn't know what, but you knew something was there.
Like Ashley said, it's gimmicky. Yeah, it gives combat recons a reason to be used. I know there generally wasn't a reason to take Rook over a Falcon, unless your pilot couldn't use a cov-ops cloak. All it's doing is putting in an arms race/escalation.