Player Features and Ideas Discussion

My suggestion works only against AFK cloakers not against cloakers that camp and are at their keyboard ... at least once every 10 min.

It is still a nerf to a module that also comes with considerable downsides. So no. No need to nerf active players to get at inactive ones.

My preferred solution is remove local, put in the OA and let it put local back, but is also vulnerable to attack and hopefully hacking, and make cloaks scannable so long as an OA is anchored in system.

Game mechanics have to be plain and simple. Unless there is a good reason to add fluff, don't. We have enough timers as it is; and no-one running multiple accounts will go for this.

It's not just the cloaky eyes. It's my bathroom break. It's going over the kid's homework before resuming operations.

Reconnaissance work, aka "prolonged stealth operations behind enemy lines" requires that we can do "stuff" without constantly having to push a dead man's switch in an environment where neither docking nor safelogging are desirable.

When a recon does its job it is a problem? Why don't you ask us to enter a lockbreaker code for every ECM module activated, and a transponder ID for every sentry drone deployed? Traders and cyno alts will of course be subject to the same harassment I presume - auto logoffski?

No thanks.

I don't have to prove I'm not AFK because being AFK isn't against the rules. Please scroll up the thread to find numerous counters to deal with the situation, along with healthy debate pro and con. The long and short of it, is that even knowing the recon is there is already wrong. You can't fix that wrong by introducing another wrong. That'd be ... well ... even more wrongierst.

Let me guess... you're trying to solo rat? Within the repository of wisdom that is this thread are all the answers. 1 cloaker vs 1 ratter = no problem. 1 cloaker+cyno = a fleet vs 1 ratter = one dead ratter. One cyno fleet vs 1 defense fleet = gudfites. You have no defense fleet? Allow me to show you the nearest wormhole to Empire space.

Then there's a couple of pages on targeting delay, low sensor strength, the futility of regular roaming fleets countered by merely staying aligned, no cynoes in plexes, somebody also mentioned large jump drives in conjunction with the inability to warp to fleet members inside anoms ..... yup, that about covers it I guess.

Oh wait. If I recall correctly someone else brought up the concepts of "Two Way Street" and "deal with it".

(this, in a nutshell, what I've gathered thus far LOL)

After that we pretty much agreed local chat needs some tweaking before the cloak needs a tweak. Several suggestions were acceptable, granted; but timers, fuel, scanprobes, basically all ONE-SIDED nerfs were shot down relentlessly.

TL;DR - now you're up to speed comrade.

It's not the AFK-part that you hate. It's the uncertainty. You want perfect Intel about the dangers. Cloaking up in a system for a while breaks the perfect Intel from local and you feel like it's wrong that you cannot know for sure about the risks. You are well on your way to becoming a true nullbear! Congrats!

Have you ever actually used cloak-capable ships? Done any scouting? Wormholes?

And spending 15-20 minutes on the killboards will tell you when the cloaker has been active in the past, giving you a reasonable safety from getting dropped on.

In reality a lot of "anti cloack" said same as you: You want to be afk in a ship and be safe ? go in highsec no cloacky.
People want just a way to disrupt the perfect immunity of colloquy people, same as you with"counter local".

Add capacitor drawback to cloaking devices - reduce capacitor regeneration dramatically, perhaps by 50-90%, while the ship is cloaked., so that cloaked pilots either need to wait some time between warping or periodically cycle cloaks.

Deactivate or even completely offline cloaking devices if the ship drops to 0% capacitor while cloaked, so that long, or frequent warps risk disabling the cloak. Require the ship to be above 50% capacitor to initially activate cloak.

This reduces the possible threat posed by a cloaked ship, and opens the possibility to get some dscan intel.if they become active.again.

It will be balance the day who people can find colloquy people, They are the counter of local, ok perfect .... And they have no counter ? You see the problem, for me an afk in space must be findable and be kill. (an active people who use cloack can be stay cloack, but an afk it's same as if you afk in "intern markV" at one moment you must be kill :p )

So we can start to counter to perfect local the day who you lost information about rating in system ho they use perma camp: like Farming, mining etc ... Same as WH in fact.
Actually you have to many free intel for no WH area ... so it's already the counter of local, because enemy can know you are here with this informations.

Not the local : the free intel you have onramp like Dotlan with npc kill by instant ect. Yes in null you have a local, but you can't close you're gate, all people in universe can know you are here due to statistic of you're system. It's why you have a local.
So perma cloack are here to disrupt local if you want, but they need to be hunt if afk, like ALL kind of player. No incivility mechanic must be allowed. Be clocked actually mean be safe.