AFK Cloaking: This is done in response to Local Chat flawlessly reporting pilot presence. It dumbs down the interaction between pilots by outright telling all parties who is present. Without this crutch, use of sensors, strategy, and cooperation would be needed to fill the void.
What does it achieve?
It creates a flaw in the usual flow of cause and effect for life in many systems. Often, a neutral or hostile pilot is seen entering, and activity is suspended until they leave. There is trivial risk, as standard procedure often involves being ready to get safe in the time frame provided by this instant alarm. Hostile pilots who refuse to leave are subsequently hunted down.
When the "AFK Cloaking" pilot enters, he disrupts this process, by not leaving. Further, since this intel tool persistently shows him present, the default response of suspending activity is perpetually pushed as chosen reaction.
This devalues the intel tool, as it is now being used against the native PvE pilots instead of helping them.
If local were removed, sensors strategy and cooperation would be placed as valuable means of protecting PvE income assets.
It would also be pointless to AFK cloak, as noone would be aware of your presence while you were passive.

The problem:

My concern is that cloak players can let the ship there in the system floating, unscanable; while they go sleep, work, play other games or anything else. This, for me, is anything different from booting! The presence of the enemies ship in a system prevents careful people to keep their business in the system afraid of a attack or hot drop, things that a active player can do (and for active players there is no problem if he can be there in his PC for 24/7). However a player can leave his account logged in and cloaked in the system playing a passive role as if he is there to control the ship, but he is not there. Its the same as booting for me.

A solution:

Hi,

Am going to show a solution to a question i think is a big problem in this game: (not really sure if the idea is original in this forum, but it appears to be)

.

.

AFK Cloaking: This is done in response to Local Chat flawlessly reporting pilot presence. It dumbs down the interaction between pilots by outright telling all parties who is present. Without this crutch, use of sensors, strategy, and cooperation would be needed to fill the void.
What does it achieve?
It creates a flaw in the usual flow of cause and effect for life in many systems. Often, a neutral or hostile pilot is seen entering, and activity is suspended until they leave. There is trivial risk, as standard procedure often involves being ready to get safe in the time frame provided by this instant alarm. Hostile pilots who refuse to leave are subsequently hunted down.
When the "AFK Cloaking" pilot enters, he disrupts this process, by not leaving. Further, since this intel tool persistently shows him present, the default response of suspending activity is perpetually pushed as chosen reaction.
This devalues the intel tool, as it is now being used against the native PvE pilots instead of helping them.
If local were removed, sensors strategy and cooperation would be placed as valuable means of protecting PvE income assets.
It would also be pointless to AFK cloak, as noone would be aware of your presence while you were passive.

I shall try to explain a few details that are usually glossed over crudely, but hold the truth.

AFK Cloaking: This is done in response to Local Chat flawlessly reporting pilot presence. It dumbs down the interaction between pilots by outright telling all parties who is present. Without this crutch, use of sensors, strategy, and cooperation would be needed to fill the void.
What does it achieve?
It creates a flaw in the usual flow of cause and effect for life in many systems. Often, a neutral or hostile pilot is seen entering, and activity is suspended until they leave. There is trivial risk, as standard procedure often involves being ready to get safe in the time frame provided by this instant alarm. Hostile pilots who refuse to leave are subsequently hunted down.
When the "AFK Cloaking" pilot enters, he disrupts this process, by not leaving. Further, since this intel tool persistently shows him present, the default response of suspending activity is perpetually pushed as chosen reaction.
This devalues the intel tool, as it is now being used against the native PvE pilots instead of helping them.
If local were removed, sensors strategy and cooperation would be placed as valuable means of protecting PvE income assets.
It would also be pointless to AFK cloak, as noone would be aware of your presence while you were passive.
It is widely anticipated that any change to local which stopped free cloaking awareness would also include a means to hunt cloaked ships.

Summary: That free intel tool favored by so many can be used by the hunters too.

Hot Dropping: Bridging is intended to bypass reinforced blockades and travel time. Here, it has been fine tuned to avoid advertising the presence of a fleet to the free intel tool as well by delaying the easily recognizable population spike till the last possible moment. The intention is to deny the warning local provides, although it still reports the presence of the cyno boat enough to be associated with AFK Cloaking instead.
Quite simply, while PvE pilots would never resume regular activities with a hostile fleet present, they are sometimes willing to gamble over whether a cloaked vessel represents that level of threat at a given time.

Sorry about the length, but the mindless repetition of "AFK Cloaking is bad mmkay" sounds foolish.

Hi,

Am going to show a solution to a question i think is a big problem in this game: (not really sure if the idea is original in this forum, but it appears to be)

First:

I really have nothing against people using their cloak ship to sneak around and grab unaware people, have safe eyes for intel or any purpose a cloaker can accomplish.

The problem:

My concern is that cloak players can let the ship there in the system floating, unscanable; while they go sleep, work, play other games or anything else. This, for me, is anything different from booting! The presence of the enemies ship in a system prevents careful people to keep their business in the system afraid of a attack or hot drop, things that a active player can do (and for active players there is no problem if he can be there in his PC for 24/7). However a player can leave his account logged in and cloaked in the system playing a passive role as if he is there to control the ship, but he is not there. Its the same as booting for me.

A solution:

When a player cloak-¦, his ship starts to bleed a ion of some gas related to the ship race, (EX: Heliun for caldari, Xenon for galent, Radonium minmatar and Argoniun for ammar). If the ship remains x min time without warp to anywhere else in the system, that ion will accumulate to a threshold detectable by ions scan probes, so players can warp right on top of the cloaker if he goes afk or by mistake do not warp elsewhere in a given time. This way, afk cloakers can still doing his valid job while they are active and smart enough. And afk ones would be found with the probes.

The idea can be extended to find cloak fleets: when a lot of cloak ships are all together, the ion in space accumulates to the threshold limit faster, so cloak blobs would need to move faster or risk to be probed.

For EVE:

The solution i proposed intended to use current eve mechanics, new opportunities (hunt cloakers), news skills can be associated as well and prevent afk people to do passive **** (passive harassment of a system)

And, its really like StarTrek way to find things: : Spoke - deep field scans now

.