Player Features and Ideas Discussion

You are warping before whoever entered local has even loaded into the system. Once again I ask, what counters local.


It does matter. If you are having to be active once every 5 hours then that makes you active, they don't know when you reapplied the cloak so they assume you are active because they have to. This is why your idea is terrible, you are removing our only counter to local.


Doesn't matter what your opinion is, both are pvp by their very nature.


The only reason people AFK cloak is to get around the intel given by local and local isn't going away so it is very much needed.

Sonya
Yes, that is pretty much exactly what I am saying. Human error is part of the game and people do make mistakes.

This is one of the two factual downside to introducing a mechanism where a cloak has to be reloaded every 5 hours to function.

A afk cloaky camper may have every intention of returning to his computer within a 5 hour timeframe, but will occassionally not do so. Opening a window of vulnerability where the now uncloaked ship might be scanned down and caught unless skillfully positioned or fitted.

Play and counter play based on human error as a content provider. What is not to love?

You're missing (or ignoring) the point. Human error is the ONLY way ratters in null can be caught if AFK cloaking goes away. There is no in game counter to local for sov null. That's one part of why cloaking needs to stay as is.

Thats not a counter to local, the red still shows up in local the second they enter system. You being an idiot and paying no attention doesn't change this.


You AFK camp a system because they dock whenever you send something their way, there are no kills for that roaming gang anyway.


It makes a hell of a difference. It can take upwards of a week for people to get used to an AFK camper, they will not come out if they know you have to be active every 5 hours as they have no idea when you last activated your cloak.

PvE = Player vs environment

PvP = player vs player.

AFK cloaking is only used on players, thus PvP.

As for the last bit, how many times do people have to tell you AFK camping in only done to counter local.

Agreed. which is why cloaking can't be changed. Thanks for agreeing with me.

Thank you for sharing your opinion about it, but you are wrong. Right now, barring humarn error or the presence of a AFK-cloaker you have decided not to care about, you are 100% safe due to the 100% accurate intel given by local and intel-channels that are built around that (and sometimes even semi-automated). Now you want to make it even more safe for them?

Ah, Baltec, I see you've not skimmed the history. Let me help you where this will go with a brief recap.

Local has nothing to do with it, it is something else.

Soon to be followed by the "implicit threat"

Pretty soon after you'll be treated to nonsensical reasons why you're wrong, complete with validated proof.

There is also judicious handbags at dawn to be expected as claims are disproven.

Enjoy your stay.

--

We're being cloaky camped all the time right now and frankly it's just fine. People have standing fleets, support, collaboration. It works just fine.

Local gives advanced warning. You cannot "act" quick enough to circumvent that aspect of local. It is impossible. If I am in system and you jump in, I will see you in local while you are still in the jump/warp tunnel. You cannot do anything to get around this. Ever.

I don't come on the forums often so I don't know what all options have been offered. I just want to throw out an idea for consideration in case it hasn't been mentioned yet in the last 347 pages.

I have seen in some games where the game itself will have some mechanic for AFK check.

I am thinking the drifters and/or circadian seekers could provide a good platform for such a mechanic. You could say that they are interested in energy readings they get from cloaking for whatever reason. Having cloaks active in the system might have a x% chance to cause drifter/seeker activity to increase by z%. Further, there could be some attraction to the grid where a cloak is active. Once on the grid the drifters/seekers could perhaps begin seeking out the cause of the readings they are picking up from a cloak being active. Over a long period of time they could perhaps decloak someone who had kept direction and velocity constant for too long; this could be almost accidental simply decloaking by proximity. They may not even be interested in the actual cloaked ship but perhaps they mistook the readings for something else they were looking for.

As an example it could take a matter of hours for the drifters/seekers to be attracted to the grid where a cloak is active. It could perhaps take another hour for them to actually decloak someone who was not moving; perhaps it would take two hours to decloak someone who was maintaining a constant direction and velocity. Perhaps a change in either direction or velocity would set back the process by another hour or two.

Just to briefly go over some of the implications this could provide... AFK cloaking in a system where drifters/seekers are currently active could be more dangerous than systems where they are not present. It may not be possible to be thoroughly sure if they are in fact active in a system. So there is the possibility that you may have less time to AFK safely then you think. If drifters/seekers are on a grid there is a possibility they have been attracted by a cloak; especially if they behave oddly. You may even be able to guess where that cloak may be by observing the behavior of the drifters/seekers.

I do not follow how my idea brings us to where AFK cloaking is a counter to local.

I would be in favor of removing local. But that seems like a discussion for another thread.

I think my idea would work with or without local.