Player Features and Ideas Discussion

LOL
No you sir are wrong. You are claiming a residents local is somehow more powerful that yours. It's not in any way shape or form. The fact that you can't act is NOT a local mechanic, it's a gate mechanic. If you don't gate, like the resident didn't, you can act as fast as they can. If they gate to you, they get the time it takes to finish gating.

And there are loads of these. When you warp onto a grid, I can start approaching you before you gain controls. When you undock, I can't do anything to you until you perform an action. That's just the way the game works, and no getting teary eyed and tantruming over how much you hate local will change that. Even if they implement an "effort based" local, the same thing would still happen.

But it does tell you they are there, exactly the same as the resident. My point being that it works the same for everyone. If a PvP player is in a system, and a PVE player jumps in, the roles are reversed but it's exactly the same.

The tears in this thread are that a miner/PVE player will run away when an enemy shows up. Replacing local with some effort based system will not change that. PVE players won't suddenly start engaging people, they'll still bounce as soon as there's a hint of a player in local. It will simply mean that those living in non sov held space, like NPC null or low, or smaller alliances will not be able to benefit from local. Because of course what null needs is more advantage for the largest alliances.

It's pretty amusing, though pretty tiring, that this thread is supposed to be about AFK cloaking and yet every time anyone tries to discuss that, Nikk and Teckos start crying about how they want to ruin null and score easy kills.

Yes, in that case the PvP player can act before the PVE player. The exact reverse of the other situation.

It's got nothing to do with butthurt. AFK cloakers put null systems out of action at no cost to the cloaker, with no risk, and with zero effort. I don't think people should be able to do that while AFK. If you want to actively cloak in a system and put it out of use, that's fine, but it does not add to the game to allow AFK players to do it 24/7.

Sigh...
This has been covered numerous times. I hate that people keep jumping in here, and raising things that they easily could have read about sever hundred times over in this very thread.
The issue is you can't see who's AFK and who's not. So treating anyone as AFK is a moronic idea. The whole "AFK people can't hurt anyone" has been discussed over and over, and it's one of the stupidest arguments going. The easiest way to see it, is:
If I was going on fire a gun at your chair where you sat, but you didn't know if it was loaded or not, and you had full control over staying in that chair or getting up, would you remain seated and risk getting shot in the head?
It's that same thing. It's simply not logical to remain in system with a cloaker when there are so many other systems to play in.

AFK cloaking exists to deny content for no reason, the AFK player gains no gameplay from it as they aren't there. It's counter productive to a game to deny content. I can;t understand why anybody supports that. Worse still, most people that support it whine to no end about other AFK activities like AFK miners, which takes considerably more actual play time.

Whatever it still conveys a distinct advantage on the person already in system. You know it and are just obfuscating.

And with undocking there is an invul timer so not at all equivalent. As for warping in again you can't do anything like target, etc. the pilot until the warp bubble collapses. Can you move, yeah but that is pretty damn trivial. Now if the pilot could not do anything for a full second after the warp bubble collapses that would be more comparable.

Really grasping at straws here.

It is not the exact reverse. If you see somebody in system who is not blue either when you log in or when the neutral/hostile enters system you have considerable advantage since you'll have time on your side.

Somebody jumping into a system looking for a target then time is not a luxury.

And AFK cloakers have costs, just not substantial ones.

Well if it isn't local giving the advantage then changing local should not be a problem because it conveys no advantage.

Kinda messed there didn't you?

Fuel would nerf active cloaking too. That you cannot handlean AFK cloaker is your problem, not the problem of everyone who uses cloaking devices.

Cloaking does not convey a one sided advantage now does it?

Neither does local. Your issue is with loading grid and with session changes, not with local. You mind dropping the "local" distraction and focusing on the issue of afk cloakies with cynos; because I think most of us could care less about a single "afk" cloaky without a cyno. And by "afk," I mean, all cloakies with cynos, because it doesn't even make sense to talk about afk unless the client implements an auto-logoff to reveal the "afk" and to separate the "afk" from the non-afk so a sudden return to the keyboard does not render the "afk" intel meaningless.

Let us proceed toward actually making progress on this topic. I think that my two suggestions bring us fairly close to a resolution, assuming that the op is interested in a real solution. 1) Auto-logoff after 30 minutes without keyboard or mouse input. 2) A cloaky ship may not fit both a cyno gen/covert cyno gen, and the disruption/scrambling module at the same time. Now discuss this with an eye to a real solution to this afk cloaky topic.