Player Features and Ideas Discussion

And local should not be invulnerable to attack. My view is that so long as that is the case, then AFK cloaking should absolutely remain. Dumbing down the game is just bad.

So... 288 pages and you guys have this all worked out, right?

C'mon guys, clearly CCP thinks that AFK cloaking is valid and isn't going to do anything about it.

It seens to be an equal tool for the stalker as much as it's an anti-stalking tool.

If you don't like someone cloaked, be vigilant, or cloak up yourself and mess with them. How nervous do you think they'd be if 20 members of a corp they are stalking are also 'in system', not in-dock, and can't be scanned down?

It's up to you to determine how you react. The tool is useable by anyone.

coz cake is gud.

I personally think you should have the ability to once a week have local go down...... either through sustained ECM or Physical attack like prior to an attack,
Exactly like our (My) forces initial actions, remove communications, remove logistics/re-supply, remove moral then remove the opposing force.
That way you provide a whole new game dynamic to be utilised. It could then be 'policed' by CCP to reduce total abuse and reduce knock on effect to (too many) innocents but would make for fun times... but it think that'a slightly off topic :)



(or knock it out but allow it to be repaired in game.........)

i'd use it for a system attack, or if that way inclined use it to go for a POS or just to give ultimate cover for piracy/covert ops.

as to physical actions against a comm's array, that could be 'policed' by local security or hired out to players to defend. And to prevent repeated attacks have CONCORD jump in to effect repairs and protect until it can be re-attacked at a suitable time period. Plus would make it a fleet operation to take it down, be it stealth bombers in a hit and run or bs's in a stand and slug it out job.

Just not a lone captain balckbeard in a frigate who wants to cause problems.

So once a week people call an "op" to take down the local when it's most convenient for them, so that you don't do it at the most inappropriate moment.

How the might of the strongest null coalition can be cowed into inactivity by a single grey name in the local channel?
That you're too scared to use your own sovereign territory because someone might shoot you?
Frankly, I doubt it. I doubt it very much.
Up to you if you want to use your space or not.

I'm going to post my original idea again since I still think it would work in solving the problem.

Require cloaks to use cap while activated at a slow rate and do not allow capacitors to recharge while cloaked.

This solves a couple issues. One, it prevents people from AFK'ing in space for long amounts of time in order to "cloaky camp" and prevent other players from enjoying the game. Second, It balances pvp in the game by reducing the benefit cloakers get when they burn off and cloak so that they can regen cap to come back in for another surprise attack in order to remain untouchable.

I see that at Page 288 there are still only two ideas...

1) Change Local to where it behaves like WH Space in Nullsec (You have to chat to show up)

2) Nerf Cloaks to where they cannot last permanently OR Develop a method for hunting cloaked ships


Personally I like both...as in do both. Remove active local in Null AND create a module/scanner that after some effort allows the pinpointing of cloaked ships. Active flyers will easily avoid this module if that's all they are trying to do (i.e. scouts).

AFK cloaking would cease to exist because A) Local stops the perception and B) The module acts as an intel creator and creates risk for cloaked pilots without destroying the effectiveness of their tactics - i.e. either you have a dedicated scout-finder in each system or you just accept the fact someone might be scouting you and now you REALLY don't know.

I think it creates a bit of a thrill for cloaky pilots (having roamed null myself just for the sake of seeing more of EVE) as well as puts to bed the whole nonsense of afk cloaking. These changes would also make covops more useful (blank local) while not rendering their potential targets totally defenseless (the module).

I'd see the module as acting something akin to a D-Scan, it can detect cloaks for certain in a small radius (say 2 AU) but it's ability to detect decreases with radius increase. At maximum (say 30), it only have a 10% chance of registering a cloaked vessel in system. As for actually scanning down a cloaked ship, the module would require you to narrow the scanner (like D-Scan) to increase strength. Once a cloaked ship is fully spotted by D-Scan, the hunter could warp to that ship and decloak it.

Keep in mind this would be quite difficult to do - so the cloaky is pretty safe unless actually AFK. Really, the module/scanner allows a hunter to potentially detect a covops attack by seeing multiple cloak signatures within a small band...hinting at a possible attack incoming.

Ultimate idea to stop AFK cloaky campers. The fact that they are AFK is the most annoying fact. Look at this CCP:
http://i.imgur.com/HdiLhS8.jpg
A certain corporation, has 1 pilot in each of these systems. They don't own the systems, in fact they are enemies with the people there. They have been there since 1 week at least (my knowledge). Is this the future of this game? Plex accounts just to park them in enemy territory - AFK. Pay to keep the enemy under constant threat with no danger to yourself. Or is this convenient to CCP?

It's not a system upgrade, because all null systems would need one. And if a system upgrade that can decloak ships exists, bombers for example will never be sure when it will be activated.

All cloaked ships should prove they are not AFK, using a reasonable time interval, like 10 min. If they don't - they get decloaked.

All cloak modules will ask a certain random letter/number to be entered at 20 min intervals, with 1 min timer. If it is not entered corectly, ship gets decloaked. No big deal, if the pilot is not AFK, he will just recloak. Also on activation of the module the letter/number must be entered, during a 1 min time interval. This is to prevent bots, a bot that is just pressing a key to look like he's not AFK. Also once the bot gets decloaked he can't just F1 and cloak back up, he will need to enter the key combo to cloak, or lose his cloak after 1 min.

It may look as an extreme solution, but this is required, unless CCP has some very good anti-bot software. And this targets only AFK cloakers. This threatening the enemy with no danger to yourself system, must go.

About non-AFK cloaky campers - it's their bussiness what they do with their time.