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

The new forums are live and can be found at

Player Features and Ideas Discussion

  • Topic is locked indefinitely.
Previous page12

Cloak deactivation delay

Komi Toran
Caldari State
#21 - 2014-11-22 04:04:49 UTC
Jenn aSide wrote:
My thoughts are that you should not be asking people to correct your mistakes. ANY request of a devloper that is based on them fixing a mistake you made is a bad request by default.

This is not the OP's fault: this is a case of the UI lying to the OP, saying the module is not active when it is.

Side note which is just an interesting mechanic I've run into re: cloaks and gates:

If you land on a gate while cloaked using the "Jump" option, if you don't land towards the gate in that 2.5 km arrival bubble, you won't jump through immediately. Instead, your ship decloaks and you spend a server tick or two approaching the gate before jumping. To counter this, you can decloak just before you're out of decell, and you'll jump through immediately. HOWEVER, if you do this, you will then have a cooldown on your cloak which you wouldn't have had otherwise.
Verity Sovereign
Sebiestor Tribe
Minmatar Republic
#22 - 2014-11-22 09:04:24 UTC
See this thread:

When a UI change would comletely fix the issue,I submit that the UI was the issue.
King Fu Hostile
Descendant Command
#23 - 2014-11-22 10:10:52 UTC
Only thing they need to fix about cloak (and other modules) is the visual for active state- the faint green glow around the module is simply too weak, and often gets completely hidden by nebulas / gas clouds.

About the double-click - if you click the cloak too early after a jump, you get a notification. If you don't get a notification, your click was successful and clicking again is your own mistake.
Ralph King-Griffin
New Eden Tech Support
#24 - 2014-11-22 10:52:08 UTC
baltec1 wrote:

Ui has nothing to do with it, the issue is between the chair and the keyboard.

exactly this, having lost a legion to the stated "problem" in the op i still think of it as my own dam fault because (wait for it) ... it was my own dam fault.

lesson learned, sp lost, never made that particular mistake again

we always need room for pilot error and this is a great one ,

no problem here whatsoever.
CaCi-A 001Me
Covert Support and Logistics
#25 - 2014-11-22 21:12:08 UTC
baltec1 wrote:
Its a simple answer to a player made problem.

no, it's not. it's a wannabe witty remark, that is in fact just trollish and neither constructive nor does it show the reasons why you are against the OP's idea, which you obviously seem to be.
i also fail to see how the client beeing unable to give the correct information about whether the cloak is already active or not, due to lag or server tick or whatever, is a player made problem.

i don't play real life, the balancing sucks!

A Big Enough Lever
#26 - 2014-11-22 22:51:46 UTC
Major Trant wrote:
I can understand the need to drop the cloak immediately on command. However, as the OP says, there is no vital need, where you would want to drop the cloak within, say, 3 seconds of raising it.

I would suggest a simple halt on the ability to switch off the cloak within 3 seconds of starting it. Thus allowing the button to be mashed as you break the gate cloak. But no message to the user, the last thing you want to deal with is a message when you have jumped into a gate camp.

Edit: I would further suggest that during those 3 seconds, you have the reload emote circling the cloak icon. Which would alleviate the problem of not being sure whether the cloak has started up or not.

This seems a valid workaround - particularly if it was a client setting - that could be toggled - then those who say 'just don't misclick' can leave it off and get caught in the odd gatecamp - and those who acknowledge the need will use it - and likely die a little less than they did before;

everyone happy?

For posting an idea into F&I: come up with idea, try and think how people could abuse this, try to fix your idea - loop the process until you can't see how it could be abused, then post to the forums to let us figure out how to abuse it..... If your idea can be abused, it [u]WILL[/u] be.

Paranoid Loyd
#27 - 2014-11-22 23:34:08 UTC  |  Edited by: Paranoid Loyd
Jenn aSide wrote:
I've lost ships to misclicking on a cloak in low sec (my ship decloaked before it could warp). That's the cost for getting overly excited (I call it "premature De-cloak-ulation"). The 'cure' is slowing down, being precise in what you do, and accepting that when you fail it was YOU that failed, it wasn't the game.
You lost your ship because you were caught in a situation that made you tense up and do things you normally wouldn't do in a calm situation. Learn to control your emotions and you will learn to click when and where appropriate. If you clicked the button you clicked it. Sometimes there is lag, but if you clicked the button there is no need to click it again.
Also, as mentioned by Omnathious Deninard using hotkeys to activate the cloak will remove this mistake.

My loot scooper on occasion (although it is rare) will need to deactivate his cloak within a few seconds of cloaking, so I for one strongly disagree with adding a delay to it.

"There is only one authority in this game, and that my friend is violence. The supreme authority upon which all other authority is derived." ISD Max Trix

Fix the Prospect!

Previous page12