I would say it doesn't make that much difference for hacking role. A minja like me alway take risk to get kill by other scout when hack.

At least, it could prevent a pro to Amarr scout who 24/7 cloak with powerful wall-hack.

+ 1 to codebreakers in highs. I would love to use them but it's just foolish on an Amarr suit. Scout needs range enhancers, all of them need armor modules. Lame!

Or, you can just check your surroundings before hacking like everyone else does.

I feared this would happen,... we have to wait and see if it actually has happened.

My opinions about cloaking are negative, but I have respect for cloak-use ONLY where it benefits you true scout players.
The majority of us victims get angry at all Scout suits and Cloak equipment solely due to the in-game misdemeanors of a small minority of abusers/exploiters. We don't distinguish the annoying cloak-shotties from true Scout players---and that's VERY unfortunate.

It's also dangerous---I really didn't want to see ANY tweaks or changes to the current "cloaks" , unless it acknowledges the TWO categories of cloak-users, and target only the group CCP wants to go after.

You have my compassion, guys. You're going to have to keep getting it out there that YOU are different from the cloak-run-n-gun pranksters---otherwise, the devs are going to be gradually persuaded to make changes that will colaterally hurt you.
"Cloak changes" are DANGEROUS.

I agree.

Too many necessary LS modules to use some helpful ones.

I can't add a codebreaker when I need Damps...

I though the same about CB on H until I realize that Gal scout would turn to be a better option for hacking if it's on H.

Considering Gal scout with 2 Damp, 1-2Kat, 2CodeBewak will has similar run speed and hack speed with Min but way better on ewar.

BTW, I'm not sure what race r u running mostly?

I am wholeheartedly behind changing the cloak in ways that fix problems. I am 100% behind the cloak delay since they will have sprint bug fixed.

What I hate more than anything is when they see a problem, and then make an overly broad "fix" that affects other roles, like hackers, who were never OP to begin with.

The only caveat being, if they have exhausted all other possibilities and having to make those sacrifices are for the good of the game as a whole. I don't think that they have exhausted the other possible fixes.

Bullseye! I don't really like their nerf either, the cloak delay will heard knife more than shotgun,but just have to bare with it.

I actually disagree. I get shotgunned to the face too often. I don't knife from cloak enough for it to be a problem. Plus I don't really think its terribly fair. I would have even supported a 1 second delay. They can't see me when I am running behind them anyways.

Knifers have been hit really hard by the Sprint Glitch. I think when you add the cloak delay and the sprint glitch fix together, we will come out on top.

The change I hate the most is the 85% reduction to scan radius. If sharing passive scans while cloaked were an issue, I would rather they just remove shared passives. I have been against those for a year since I first found out they were implemented.

-cut-
15% of that is 4.5 m, which would likely round to 5.

A word of caution on math and CCP. In particular with CCP and Dust514.

They use the MSFT round-down/truncate at .5 tradition. While it is not the fault of MSFT it is the default math library option with many of their applications and libraries.

Thus 4.5 will be either 4.5 or 4, never 5. The best hope here is that Dust keeps many values in floating point so 4.5 is most likely 4.5, otherwise we would never see a Merc running about with 0,0 health. Which means they have 0.1 armor and 0.0 shield, or some such combination. It is just displayed as integers, aka Zero, Zero.