Yes I understand why people AFK Cloak. But in my suggestion, the cloaked vessel is removed from local, therefore they can hunt the BOTs or scared ZeroSecers because local will be blue. Residents will have to keep an eye on local, and pay attention when people come into the system, or drop cloak to scan etc.
This forces zero sec residents to actually pay attention and gather their own intel, protect the system they are claiming is ‘theirs’.
As the cloaker (in my suggestion) is denied local/scanning/Dscan they will have to drop cloak occasionally to get intel for themselves, this gives residents the chance to notice them, and gather their own intel. Someone appears in Local, start DScanning, get an understanding of where they are in system…
You can even have your defense ships cloaked nearby, the cloaker will have no knowledge of them, spring your own trap.
The issue with having a tool to ‘Find’ cloaks, it that everything I ever see being suggested is straight up nerf or outright breaks cloaks. If you can suggest something that does not nerf cloaks, or give someone instant intel that there is a cloaked vessel somewhere in system, then that would be a good start.
A solution that does not involved Structures or arrays.
So there has been a problem in Eve that has persisted for many years.
Cloaky camping, the act of sitting cloaked in a system for hours at a time, some times AFK, sometimes not.
Cloaky Camping adversely affects game play in several ways:
While many suggestions have been put forward, nothing has yet been done about this and i feel it’s about time something is.
The main issue that needs to be addressed is the act of sitting in one spot cloaked for many hours at a time usually AFK, or with little to no input from the user, allowing a single person with dozens of alts to maintain a presence across great swaths of space with very little effort or input.
Or to put it another way, a cloaky camper requires attention only 1-5% of the time it is in a system, where as any counter to this potential threat requires constant attention 100% of the time.
The advantage goes to the group who is taking none of the risk as opposed to the group who is trying to live in, operate out of, and maintain sov in the area.
I feel it would be wrong to adversely affect those who are legitimately at their computer for one reason or another, evading hunting parties, etc, so i suggest the following:
First the things that will not be changed:
Now for the changes:
Prototype: Can hold 4800 charges (4.8m3), with a 30% signature radius reduction, and a 60 second reload time.
Improved: Can hold 5400 charges (5.4m3), with a 50% signature radius reduction, and a 45 second reload time.
Covert Ops: Can hold 7200 charges (7.2m3), with a 95% signature radius reduction, and a 30 second reload time.
Faction: Can hold 10800 charges (10.8m3), with a 99% signature radius reduction, and a 3 second reload time. (Can only be fitted to a Battleship class hull or larger.)
Officer: Can hold 14400 charges (14.4m3), with a 99.95% signature radius reduction, and a 1 second reload time. (Can only be fit to a capital class hull or larger.)
These charges increase the racial signal strength of the ship they are fitted to by 1,000% while the cloaking device is active.
The signature radius reduction inherent to the module itself means that a ship does not necessarily have to have the correct racial charge loaded, or any charge at all, to have their signature radius reduced, but they will not receive the sensor strength bonus without the specific charge.
The aim of these changes is to make it possible to probe down ships which are maintaining an AFK presence in a system, while making it possible to continue to evade hostiles and maintain a cloaked presence in system with a small amount of input from the account holder.
All your problems are solved by removing local.
When are these whingers going to realise that CCP obviously approves of cloaky camping, and isn’t about to do anything to nerf it ? This thread alone has been going for nearly 3 years, and cloaky camping is still with us…
5 years, actually. It’s just a continuation of the thread on the old forums, which itself was a response to constantly closing redundant whiny threads the decade before that.
CCP hasn’t done anything about cloaking camping for the past 15 years because it simply isn’t a problem to anyone but the imbeciles who have no business being in nullsec in the first place.
Cloaky camping doesn’t cause those things, the ability to see that local isn’t blue does.
The problem isn’t cloaking at all, it’s players being unwilling to operate in systems that aren’t 100% safe.
This isn’t a result of game mechanics, it’s human psychology and you cannot patch human psychology.
-1. I didn’t even bother reading your proposal because you’re trying to fix a non-issue, just like people have been trying to fix this particular non-issue for a decade or more.
Please see my update.
Or to put it another way, a cloaky camper requires attention only 1-5% of the time it is in a system, where as any counter to this potential threat requires constant attention 100% of the time.
The advantage goes to the group who is taking none of the risk as opposed to the group who is trying to live in, operate out of, and maintain sov in the area.
Your update doesn’t change anything. The problem has always been local.
Honestly it has never made sense that a truly covert ops ship can’t be covert as they show up in local. The whole issue of afk cloaky players is the fact that they can sit cloaked but also be visible in local. If they weren’t visible they wouldn’t need to spend hours cloaked in system.
Honestly in the same vein it has never made sense why concord bothers to offer local services to 0.0 space. It makes sense in high and low, where they maintain some level of empire control, but not 0.0. Local should be a service offered by some SOV structure that must be maintained, and defended.
Unless you’ve found a way to patch human psychology, whatever you proposed, updated or not, won’t change anything.
Gotta love nullbears. The most risk averse players in the game. Scared to death to undock because of an unknown in their system. Meanwhile, high and low sec players run the risk of getting ganked every second of every day, yet they still undock and go about their business…
Why ? Your update was every bit as stupid and pointless as your original post.
Not AFK Cloaking… you are taking about active cloaking here.
Cloak fuel has been suggested MANY times, and is not a solution, this severely nerfs active cloak playstyles as well.
Again, nothing original about this, and CONGRATULATIONS you have instantly broken all of WH Space.
One click of your probes and you know how many cloaked vessels are in the system.
Nothing here but huge cloak nerfs and giving nullbears even more instant intel so they can hide from any of this “potential content” you are touting.
I’ve been making that suggestion for years. Good luck with that ever happening. This is Eve, common sense has no place here.
*runs from room laughing*
STOP your killing me 
Being a pixel coward and being AFRAID to undock are not game problems!
GROW A PAIR!!
It’s only pixels 
As someone who has pitched radical ideas myself and gotten blapped for it, I can appreciate how strongly you feel about this. However, I must agree with everyone else on a number of points:
Focus on counters for AFK cloaks, of which there is no shortage - there is no need to change the mechanics themselves over this.
I think cloak means one has to produce less signals as possible. How comes you can launch a d-scan radar and stay cloaked? Using d-scan must drop your cloak, so you have to re-cloak yourself, IMHO.
There’s an official tears thread for cloaks.
It acts like Probe scan which can be done when cloaked, but probe launch requires ship to be uncloaked.
Exactly my point.