Player Features and Ideas Discussion

Well, since I enjoy going to effort, and reward indexes would increase to match, I would do well.

But then, I want to mine in null, not high sec.

Which is why I suggest the combined changes as follows:
Cloaked ships cannot view local, or be seen in local

Fleet ships can use spotter modules and detect cloaked ships, as detailed:
https://forums.eveonline.com/default.aspx?g=posts&m=2668453#post2668453

This can be through probes, or directly on grid overview.

Oh, not at all.

In fact, you are one of the few in assuming I want AFK cloakers to be nerfed.

I want them to be able to get kills, and have PvE players like myself need to compete in order to survive.

Always being able to avoid fights, with trivial effort, frankly is boring the real null miners to tears.

(And yes, those that could deal with all the other effects involved already moved to a wh, where roughing it really happens)

I would like to point out that this is actually not true for stealth bombers. How would this system affect them?

Also though the other ships may not be able to fire immediately, they can activate a cyno from cloak status. This is what the vast majority of the fuss is about. How does this get addressed.

Everything else about this is fine. Just those 2 issues specifically.

...

And also maybe star map statistics. But that's another debate.

If they use bombs then yeah, doesn't matter. Stealth bombers also come in torpedo and cyno flavors too.

The cyno can be used "while" cloaked, it does however bring the ship out of cloak uppon use. Yes I know this is just seems like nitpicking at words but the implications are changed completely.

Being able to use modules and in the case of the bomber targeting and engaging while being cloaked are a big deal. If this change does get implement then in the case of the SB it would be paramount to removing local entirely. One cyno SB or a gang of SBs could fly from system to system totally undetected with unchecked force projection and would be able to gank anyone at will. They would not show up in the new local until they were already engaging a target if not after its long dead depending on the delay.

This is the problem you were trying to avoid in the first place was it not? Allowing cloaks to be in system without being detected while also allowing locals to go about their business without fear of a camper. Or was it just a "CovertOps" remove local thread disguised by pretending to be impartial or "a 3rd side of the arguement"?

Another bad post with carebear OP.

What I'm saying is: The reason this (afk cloaking vs local) isn't a large enough issue to warrent immediate action is because of player interaction. If regions were fighting eachother instead of blue donuted then neighbors would more than likely be camping eachother constantly making it mostly impossible to perform any isk making activity. But thanks to the "blue donut" mentality of null and the ability to claim oceans of sov there is a physical barrier between hostile groups. Causing them to have to go far out of their way to mess with each other. Infact you could consider the huge sov fields an effect of the campy stuff. The larger your buffer between you and your enemies, the safer you'll be. God forbid your home system is in blops bridge range from a hostile system. How much ratting/mining do you think would be going on there?

As for local, yeah its balanced in a way now. Cloaks (covert ops especially) are not. Local gives intel away freely to anyone/everyone. Cloaks on the otherhand can probe, d-scan and visually see other ships where as other ships cannot probe,dscan or see them.

Maybe make a module or ship that can dscan cloaked ships. This would make a cloak hunter viable but also require very high player skill to be successful. Also could delay dscan recalibration on the ship/module so you can't just spam it constantly. Also instead of the shiptype/name it could just say "cloak field" so friendly cloakers might misslead you and you inadvertantly uncloak them while they're afk.

Seems like the least change possible to do something about it. And its easy enough to avoid detection if you're at your keyboard. Also seems funny if you screw over your corp/alliance mates and get them killed. (Accidentily or intentionally) :)

Uhhh, Erutpar Ambient, that reply seems to be drawing from a different thread than this.... miss-post?

Its all related.

One affects the other affects another.

Basically what I'm saying is if you implement this change it will give covert ops cloaks too much power and utility.

Edit: maybe it was the wrong thread, who knows. Lol postin from my cell phone :p

The way to get rid of AFK cloaks is to require the cloak operator to actually be at their keyboard. Put a cycle timer on cloaks, 10 minutes with a 30 to 15 seconds variable cooldown. Variable meaning it could take 30 seconds to reactivate or 15, or any time in between. Someone afk could simply set up a keyboard macro to click their cloak button every 10 minutes and 31 seconds you say? If they are afk and someone is actively probing for them they will get a delayed sensor signal every cycle. Over a few cycles the prober could eventually lock and and get a warp in at which point the AFK pvper would become vulnerable to attack. The non-afk pvper would simply warp somewhere every 30 minutes and avoid all the efforts of the prober. All of a sudden you solve all these problems without creating any new ones for people playing the game CCP intended *CCP has stated their intentions that ONLY people that are actually at their keyboards should be able to have an affect on other players*. If you would rather be able to not show up in local to be able to sneak up easily on people, go play in wormholes.