These forums have been archived and are now read-only.

The new forums are live and can be found at https://forums.eveonline.com/

Player Features and Ideas Discussion

 
  • Topic is locked indefinitely.
 

Much Ado About AFK Cloaking

First post
Author
Alvatore DiMarco
Capricious Endeavours Ltd
#61 - 2013-06-17 00:38:13 UTC
I rather like lowsec. I'd probably live there if I weren't so absentminded and distracted all the time. There's a lot of stuff you have to always keep an eye on in lowsec if you don't want to become someone else's killmail.
Teckos Pech
Hogyoku
Goonswarm Federation
#62 - 2013-06-17 01:26:27 UTC
Black Dranzer wrote:
Somebody in this thread probably wrote:
An AFK cloaker is completely harmless.

So is a pilot in a pod or a shuttle, but we're still allowed to hunt and kill them.


You can't hunt the pilot docked in station or inside a POS. So your argument is not very good.

"The curious task of economics is to demonstrate to men how little they really know about what they imagine they can design."--Friedrich August von Hayek

8 Golden Rules for EVE Online

Dr Ted Kaper
Arondight
#63 - 2013-06-17 03:10:17 UTC
Local channel is your counter to cloaks, and you will always know they are there with local. Besides afk cloaked ships are not dangerous, only active cloak ships are! If you see a person in local and they aren't on d-scan you know they are cloaked and you should make sure that you have someone to help you if they decide to show up. Frankly Local alone is enough to put cloakers in their place, and if you live somewhere where people can kill you...than you should have something capable of giving you a scare ormaking you break a sweat, its supposed to be dangerous in low and null. The only people who can even honestly complain that cloaked ships are OP is those in WHs where local gives you nothing, but in WH space cloaks are an appreciated danger that makes WHs properly dangerous and scary. So all you low and null bears who hate cloak ships need to suck it up, if it bothers you too much move back to hi sec.
Dr Ted Kaper
Arondight
#64 - 2013-06-17 03:22:37 UTC
Mahpiya Luta wrote:
Because in contrast to you we dont fly phukkin drakes. Blink The worth of our ships go into multiple billions.

And you deserve to fly these, make enough isk to fly them, all the while being completely risk free? Your kidding right....that doesn'tsound broken at all...
Alvatore DiMarco
Capricious Endeavours Ltd
#65 - 2013-06-17 14:02:24 UTC
Features & Ideas: We Whip Our Dead Horses Back and Forthâ„¢

This joke was probably not funny the first time I said it.
Bakuhz
Banana-Republic.
Shadow Cartel
#66 - 2013-06-17 14:24:40 UTC
Dr Ted Kaper wrote:
Local channel is your counter to cloaks, and you will always know they are there with local. Besides afk cloaked ships are not dangerous, only active cloak ships are! If you see a person in local and they aren't on d-scan you know they are cloaked and you should make sure that you have someone to help you if they decide to show up. Frankly Local alone is enough to put cloakers in their place, and if you live somewhere where people can kill you...than you should have something capable of giving you a scare ormaking you break a sweat, its supposed to be dangerous in low and null. The only people who can even honestly complain that cloaked ships are OP is those in WHs where local gives you nothing, but in WH space cloaks are an appreciated danger that makes WHs properly dangerous and scary. So all you low and null bears who hate cloak ships need to suck it up, if it bothers you too much move back to hi sec.


my exact point

https://zkillboard.com/character/584042527/

Tchulen
Trumpets and Bookmarks
#67 - 2013-06-17 14:38:05 UTC
How about when someone who's flying a cloaked ship comes into your system and goes AFK the local chat channel disappears from everyone in system's clients?

This would solve your issue of AFK cloakers as you'd know darned well that there was actually an AFK cloaker in your system whilst also removing the free intel you get from local at the same time.

I believe this would balance the situation. You gain intel and lose intel. Balance.

What do you guys think? Lol
Alvatore DiMarco
Capricious Endeavours Ltd
#68 - 2013-06-17 14:45:42 UTC
Remove the ability to have onlined highslots in highsec. Remove local. Remove cloaks. Remove undocking in null and remove spaceships in WH. Remove lowsec altogether.

AFK cloaking fixed, along with myriad other problems.
Teckos Pech
Hogyoku
Goonswarm Federation
#69 - 2013-06-17 15:00:24 UTC
Tchulen wrote:
How about when someone who's flying a cloaked ship comes into your system and goes AFK the local chat channel disappears from everyone in system's clients?

This would solve your issue of AFK cloakers as you'd know darned well that there was actually an AFK cloaker in your system whilst also removing the free intel you get from local at the same time.

I believe this would balance the situation. You gain intel and lose intel. Balance.

What do you guys think? Lol


What, and face unacceptable risk? You sir are just being totally outlandish!

"The curious task of economics is to demonstrate to men how little they really know about what they imagine they can design."--Friedrich August von Hayek

8 Golden Rules for EVE Online

Tchulen
Trumpets and Bookmarks
#70 - 2013-06-17 15:17:04 UTC
Teckos Pech wrote:
What, and face unacceptable risk? You sir are just being totally outlandish!


But they'd know that there was an afk cloaky in system which is what they're after! What risk would it then be any more than being in a wormhole? The WH denizens seem perfectly happy with the situation they have so why not "solve" the afk cloaky "problem" some people perceive in this balanced and fair approach?

Shocked

I'm being shuper sherious.
Nikk Narrel
Moonlit Bonsai
#71 - 2013-06-17 15:39:00 UTC
Tchulen wrote:
Teckos Pech wrote:
What, and face unacceptable risk? You sir are just being totally outlandish!


But they'd know that there was an afk cloaky in system which is what they're after! What risk would it then be any more than being in a wormhole? The WH denizens seem perfectly happy with the situation they have so why not "solve" the afk cloaky "problem" some people perceive in this balanced and fair approach?

Shocked

I'm being shuper sherious.

I think this is the point where they suggest wormhole is safer because noone drops carriers onto them, or uses covert cynos somehow....

Because, when you're ratting or mining, that is what worries you.... someone dropping supers on you...
Gizznitt Malikite
Agony Unleashed
Agony Empire
#72 - 2013-06-17 15:44:42 UTC
Mahpiya Luta wrote:
There is this thing called 'afk camping' and two sides to the coin. First things first, it's within the rules of the game, it isn't cheating nor bug-using or what so ever. Cloaky modules are part of this game and have a right to exist. They make sense! So what's all the fuss about anyways? Well, being a system owner/renter in this game is also part of this game. You invest time, money and manpower to raise the military and industrial level and make this game running by producing, ratting, mining.

It's astounding that all someone (jerk) has to do, in order to destroy other players gameplay, is to sit in a cloaky ship at a savespot and leave his computer for good without even bothering about getting caught. This can't be the idea of this game. You might say: 'Well why dont you kill them when entering the system?' Because, there is a time for the game and there is a tme for real life and you can't have a guarded system 24/7.


It's astounding that all someone has to do, in order to destroy your game play, is to sit in a cloaky ship at a safe spot and leave his computer for good. That's simply pathetic! (Go to a system next door, rat in a fleet, etc, etc, etc)

Mahpiya Luta wrote:

Let's see what we got so far. Cloaky modules make sense and should definitly provide a high amount of savety to a cloaked pilot. Especially bombers, cover-ops and black-ops. On the other hand, having a computer running an alt in a cloaky ship with a cyno field gen fitted and nobody taking care of that alt. After days of not even looking how your cloaky alt is doing, you then suddenly decide to just hotdrop a whole fleet.

The way I see it, the problem isn't the cloak camping but the 'away from keyboard' claok camping. The solution therefore would be a game feature that doesnt destroy the savtey aspect of cloak modules but forces people to continously watch out for their cloaked alts in order for not getting caught and killed. If you dont watch for your alt, you then lose your ship and pod.

You're misguided. The issue isn't the "away from keyboard", but the "suddenly a hotdrop of a whole fleet".

Hotdrops are great at catching risk adverse gate campers that will pounce on a "single target", but their drawback is when a cloaky camper can bring in a pragmatically unscoutable and tedious to counter fleet on top of your ship.

AFK does nothing to harm you... as you can scout out and prep for any pilot(s) in local. You just can't reliably and pragmatically prep for the "suddenly spaceships" hotdrop on top of you. See why you are misguided!!!!

Mahpiya Luta wrote:

The newly added hacking minigame and a vague memory of a star trek sequal from many years ago when I used to watch those things, brought this idea of an scanning minigame to my mind. When scanning for cloaked ships in star trek you still had some fuzzy signatures which when reajusting your probe settings became more clear the more you ajusted them. So how about having to ajust some frequencies (ship signatures) everytime you hit the scan button (the smaller the probe radius the smaller the frequency scal gets) and get closer to the pinpointing? And how about if its different for any shiptype, which means if you already know what ship you're scanning for makes it easier because you have to ajust your scan for ladar (minmatar), radar (amarr), gravimetric (caldari) or magnetrometric (gallente) or maybe even bs, bc, frig, etc. The cloak pilot on the other hand should then be able to reajust his frequencies somehow or just plain by switching his cloaking device off and on again. This would make sure he can't leave his ship for good at some savespot and just go afk. Using a bot to reajust frequencies would then clearly be against the rules of the game.

Regards, M.L.


Huh? You really are addressing the wrong problem! In general, the best solution I've seen is "scanner probes" that take a long time to scan out the cloaky (60s cycle times or some difficult setup). However, this doesn't address the issue of "why" people afk cloak. AFK cloaking is the counter to "local chat" being used as an infallible, omniscient intel tool that allows you to operate in complete safety when living in "nullsec".

To summarize my points:
1.) AFK cloaking itself is not an issue. It's the ability to hotdrop an unscoutable fleet right on top of you that is unbalancing.
2.) AFK cloaking is the counter-action to the imbalanced intel tool known as local. Inhibiting afk cloaking without addressing the elephant (local chat) in the room is inappropriate and wrong!
Trii Seo
Goonswarm Federation
#73 - 2013-06-17 16:04:20 UTC
Thing with W-space is, ISK is literally dripping off the walls there. Which means risk vs. reward ratio is good: you make obscene amount of money at the cost of lack of local. If you're good at managing losses and profits from sleeper drops you'll actually end up in the green anyway. Why?

Simple: W-Space income is based on components exclusive to it. Their price is regulated by supply and demand, they're used to build T3 cruisers that are in high demand.

Price of loss remains the same in null/low, but there's less money to be earned. Money from ratting in nullsec does not come from drops, but from rat bounties regulated by CCP. If you simply ramp up the risk, null will just become unprofitable (it already barely is at times. The only market-based commodities are faction/deadspace/officer modules and exploration drops, the latter crashed in value because the risk was lowered to the point everyone rushed after them. The market was literally flooded.) and people will start farming ISK using hisec alts. (They already do with FW alts.)

Where's AFK cloaking in this? Everywhere. Targets for those people (black ops groups especially, gotta love a good ratter kill.) are ratters. Not even dedicated carebears - fleet grunts when they're not in a brawl and earning money will do nicely.

When hostiles enter the system, you always have a choice. POS/Dock/Safe or risking it and dscan-mashing. Maybe it's a pod, maybe a shuttle - or maybe, indeed, a pesky Arazu about to light a cyno. Most people will choose the former, and wisely - there isn't enough incentive to risk your ship.

So a hunter ship has to either move along or resort to AFK cloaking. Hope the other side is ballsy or desperate enough to risk it.

How to "fix" it? You can't by fixing cloak or local. Just can't.

- "no local null" does not work. It's big space, much bigger than wormholes, with fixed connections and local makes spotting fleets possible. Scouts report, fleets change course, fights happen. All is good.
- "no cloak null" won't work either. To put it short, removing (or nerfing to the point of effective removal) this entire element of the game (and a branch of specialization) would be like shoveling a third of the sand from the sandbox because someone peed on it and is now crying.

To "fix" it, CCP would have to look at the profitability of nullsec anomalies and income generated that way. I wish them luck on that endevour, because it sure as hell isn't easy.

Proud pilot of the Imperium

Arek'Jaalan: Heliograph

Tchulen
Trumpets and Bookmarks
#74 - 2013-06-17 16:05:17 UTC
Gizznitt Malikite wrote:
To summarize my points:
1.) AFK cloaking itself is not an issue. It's the ability to hotdrop an unscoutable fleet right on top of you that is unbalancing.
2.) AFK cloaking is the counter-action to the imbalanced intel tool known as local. Inhibiting afk cloaking without addressing the elephant (local chat) in the room is inappropriate and wrong!


Solution to 1) Stop any ship with a cov ops cloak from using a non cov-ops cyno. Now you can either get hot dropped by a cov ops fleet of paper thin ships which is fine or you can see the ship warping to you prior to being hot dropped. No more cov-ops cloaked ships sidling up to you and popping a titan bridge for a large fleet of combat ships. If you get caught, you weren't paying attention.

Teckos Pech
Hogyoku
Goonswarm Federation
#75 - 2013-06-17 16:13:19 UTC
Gizznitt Malikite wrote:


To summarize my points:
1.) AFK cloaking itself is not an issue. It's the ability to hotdrop an unscoutable fleet right on top of you that is unbalancing.
2.) AFK cloaking is the counter-action to the imbalanced intel tool known as local. Inhibiting afk cloaking without addressing the elephant (local chat) in the room is inappropriate and wrong!


Technically you could scout the surrounding systems that are in bridge range. For example, if I were ratting in DBRN in Fountain I'd look in a subset of systems in Aridia and Solitude (I doubt somebody would bring in a hostile titan into Fountain). I'd also check the in-game map to see if there are pilots building up in those systems.

You could do the same for BLOPs, but the number of systems does get larger and they can move around.

So technically such a fleet is scoutable. One could argue it is unreasonable to be looking for a BLOPs gang, but I'd argue if you have one in your space, finding them and trying to evict them is part and parcel of owning sov. Or you could opt to forgo such a tactic, but then complaining about it is rather absurd. You've made a choice, now live with it.

"The curious task of economics is to demonstrate to men how little they really know about what they imagine they can design."--Friedrich August von Hayek

8 Golden Rules for EVE Online

Gizznitt Malikite
Agony Unleashed
Agony Empire
#76 - 2013-06-17 16:25:50 UTC
Teckos Pech wrote:
Gizznitt Malikite wrote:


To summarize my points:
1.) AFK cloaking itself is not an issue. It's the ability to hotdrop an unscoutable fleet right on top of you that is unbalancing.
2.) AFK cloaking is the counter-action to the imbalanced intel tool known as local. Inhibiting afk cloaking without addressing the elephant (local chat) in the room is inappropriate and wrong!


Technically you could scout the surrounding systems that are in bridge range. For example, if I were ratting in DBRN in Fountain I'd look in a subset of systems in Aridia and Solitude (I doubt somebody would bring in a hostile titan into Fountain). I'd also check the in-game map to see if there are pilots building up in those systems.

You could do the same for BLOPs, but the number of systems does get larger and they can move around.

So technically such a fleet is scoutable. One could argue it is unreasonable to be looking for a BLOPs gang, but I'd argue if you have one in your space, finding them and trying to evict them is part and parcel of owning sov. Or you could opt to forgo such a tactic, but then complaining about it is rather absurd. You've made a choice, now live with it.


While you are "technically" right, this is anything but pragmatic!

The number of systems in bridge range of just about any system in EvE is 100-200 systems in total. While there are certain "areas" that far more likely, especially if you are deep within sov territory, it's tedious and unrealistic to monitor even the 10 most likely systems while you are out and about.
Gizznitt Malikite
Agony Unleashed
Agony Empire
#77 - 2013-06-17 16:34:34 UTC
Tchulen wrote:
Gizznitt Malikite wrote:
To summarize my points:
1.) AFK cloaking itself is not an issue. It's the ability to hotdrop an unscoutable fleet right on top of you that is unbalancing.
2.) AFK cloaking is the counter-action to the imbalanced intel tool known as local. Inhibiting afk cloaking without addressing the elephant (local chat) in the room is inappropriate and wrong!


Solution to 1) Stop any ship with a cov ops cloak from using a non cov-ops cyno. Now you can either get hot dropped by a cov ops fleet of paper thin ships which is fine or you can see the ship warping to you prior to being hot dropped. No more cov-ops cloaked ships sidling up to you and popping a titan bridge for a large fleet of combat ships. If you get caught, you weren't paying attention.



That's a possibility (although it invalidates one of the bonuses of the force recon).

There's a 30 second reactivation delay on lighting a cyno after your cyno shuts off. Perhaps have the cloak trigger the reactivation delay on the cyno, too...

I don't know what the best solution is, but it's important to recognize that afk cloaking complaints are generally akin to whining about the mouse in the room with elephants, when there shouldn't be elephants in the room to begin with!
Teckos Pech
Hogyoku
Goonswarm Federation
#78 - 2013-06-17 16:56:25 UTC
Gizznitt Malikite wrote:


While you are "technically" right, this is anything but pragmatic!

The number of systems in bridge range of just about any system in EvE is 100-200 systems in total. While there are certain "areas" that far more likely, especially if you are deep within sov territory, it's tedious and unrealistic to monitor even the 10 most likely systems while you are out and about.


True, but for a Titan, I don't think it will be moving around from system to system. The more likely case, it will have a POS and use that system. For regions with Sov, the Titan will most likely be outside the Sov systems (using the Fountain example, that limits the systems to some in Aridia, Solitude and Fountain core). So that puts it at 25ish or so systems. Much more doable than 100-200.

The BLOPs gang is considerably more difficul in that they can move around much more easily. This is where reporting hostiles in intel channels come in. Which is not unlike what Nikk, Mags and others have been talking about; intel you have to work for.

And to some extent this is beside the point since if you have an active BLOPs gang, you most likely have an active hunter and not an AFK cloaky. Granted, the hunter may have been AFK cloaking before the BLOPs gang goes active, but as others have pointed out this is due to the nature of local.

"The curious task of economics is to demonstrate to men how little they really know about what they imagine they can design."--Friedrich August von Hayek

8 Golden Rules for EVE Online

Onomerous
Caldari Black Hand
Caldari Tactical Operations Command
#79 - 2013-06-17 17:21:59 UTC
Gizznitt Malikite wrote:

To summarize my points:
1.) AFK cloaking itself is not an issue. It's the ability to hotdrop an unscoutable fleet right on top of you that is unbalancing.
2.) AFK cloaking is the counter-action to the imbalanced intel tool known as local. Inhibiting afk cloaking without addressing the elephant (local chat) in the room is inappropriate and wrong!



There is truth in those words. Most null sex players don't want to see some of it but it is not a simple, one-part problem... which means the solution isn't going to be simple either.

Although it is funny, "45 people have to dock up because of one afk cloaker". I love that quote. NS isn't quite as rough and bad-arse as we are led to believe?
Gizznitt Malikite
Agony Unleashed
Agony Empire
#80 - 2013-06-17 17:22:58 UTC
Teckos Pech wrote:
Gizznitt Malikite wrote:


While you are "technically" right, this is anything but pragmatic!

The number of systems in bridge range of just about any system in EvE is 100-200 systems in total. While there are certain "areas" that far more likely, especially if you are deep within sov territory, it's tedious and unrealistic to monitor even the 10 most likely systems while you are out and about.


True, but for a Titan, I don't think it will be moving around from system to system. The more likely case, it will have a POS and use that system. For regions with Sov, the Titan will most likely be outside the Sov systems (using the Fountain example, that limits the systems to some in Aridia, Solitude and Fountain core). So that puts it at 25ish or so systems. Much more doable than 100-200.

The BLOPs gang is considerably more difficul in that they can move around much more easily. This is where reporting hostiles in intel channels come in. Which is not unlike what Nikk, Mags and others have been talking about; intel you have to work for.

And to some extent this is beside the point since if you have an active BLOPs gang, you most likely have an active hunter and not an AFK cloaky. Granted, the hunter may have been AFK cloaking before the BLOPs gang goes active, but as others have pointed out this is due to the nature of local.


I concede it is possible, just not practical.