|
|
| Author |
Thread Statistics | Show CCP posts - 0 post(s) |
Induc
Amarr
   |
Posted - 2010.04.22 10:55:00 -
[1]
AFK cloaking is only a problem if YOU make it a problem.
|
Induc
Amarr
|
Posted - 2010.07.06 03:25:00 -
[2]
 Originally by: Voith
AFK Cloaking is broken and goes against everything Eve and real PvPers stand for: Risk.
It allows a person to assume no risk and to effect the game of others. If you like AFK cloaking you should go back to woW.
Affect the game of others? No, the only reason it affects you is because you let it affect you.
You talk about risk, when it's really you who's to scared to undock with a neutral in local. If you don't like AFK cloaking you're either a too big carebear to live in 0.0, or you're crying because the afk cloaker breaks your ratting macro.
Originally by: Innocent Murderer
How would that remove the cloaking problem? That would remove the ability to see the problem, not the actual problem itself. Congratulations, you're a dumbass. Or a troll. Or someone who makes a living off of using an imbalanced game mechanic. Or some combination of all three.
No, he actually has a point. The problem is not that you can't find someone cloaked at a safespot, the problem is that you know he's in the same system even if he's cloaked.
The afk cloakers exploit the fact that you know they're there, but you can't do anything about it.
|
Induc
Amarr
|
Posted - 2010.07.06 04:09:00 -
[3]
Originally by: Innocent Murderer
What is a con to adding a fuel requirement to a cloak? I'm still waiting for someone to explain how it could ruin things.
Where would you get it? NPC sell orders? Free or not?
However you decide to solve it will add yet one more thing I have to remember before I undock.
And what about wormholes? Do I have to find an exit to k-space every 16 hours because some whiny nullbears can't HTFU?
It's is just a simple case of "don't fix what ain't broken".
And of course you can almost never fight back when they attack, because they'll never uncloak and attack until they're sure they'll win. Just don't give them the opportunity.
|
Induc
Amarr
|
Posted - 2010.07.07 03:40:00 -
[4]
The way you describe it sounds like the your only concern with afk cloaking is that they're invulnerable and impossible to catch.
But how do they differ from someone logging in every few hours to check for targets and then logs off again?
After killing someone they can just warp between safespots until the aggression timer's away and then log out, impossible to catch. The only difference between them and afk cloakers is that you know when they're afk or not.
Originally by: Innocent Murderer
You have thus far failed to put forth any sort of drawback to adding a fuel requirement with a reasonable time limit.
You still haven't answered how solve the w-space problem. PI won't solve it. You can't expect everyone in w-space to have a POS and that the wh won't collapse behind them.
I can see why you would want a fuel requirement on prototype cloaks, but cov ops cloaks? Ships that can fit them have enough drawbacks as it is.
Also, 0.0 is completely risk free - as long as you dock up when someone appears in local.
|
Induc
Amarr
|
Posted - 2010.07.27 19:03:00 -
[5]
Originally by: Mackenna
The only meaningful difference is that in scenario 2, you are affecting the (often limited) game time of the people in system who want to engage you. Baiting someone who isn't there is a complete waste of time, after all.
But that is the whole point of afk cloaking, making sure you don't know if they're there or not. You can't say you're wasting your time baiting the "alleged" afk cloaker, because you have no idea if he's actually afk or just not stupid enough to take your bait.
The difference between scenario 1 and 2 is that in scenario 2 you get intel without any effort and in scenario 1 you actually need scouts and intel channels. And you can't be sure that the cloaker that entered your system has left unless you have scouts at every exit gate.
Also when you think about it, does it really make sense that you are searching for a cloaked ship in your system? He's cloaked right? So why should you know he's there? Removing local would give covert operations a whole new meaning...
|
|
|
| |
|