Player Features and Ideas Discussion

if I click 2x to armor repairer, same happens as to cloak.
if I click 2x to shield booster, same happens as to cloak.
if I click 2x to damage control, same happens as to cloak.
if I click 2x to shield hardener, same happens as to cloak.
if I click 2x to armor hardener, same happens as to cloak.
if I click 2x to any other active module, same happens as to cloak.

so why again, should cloak be a special module???

Cloak is a special module because it is simply on or off, so the accidental double click immediately shuts the cloak off, where as the rest of the modules you listed have a cycle time.

Im not saying I agree or disagree with the OP, but this is why I always use my F1 key for the cloak, it greatly reduces the chance of a double taping the key.

This is blatantly not true. Everyone of those module will cycle for 10-30 seconds first before switching down and then you can immediately restart them. With a cloak, it switches down immediately, then there is a reactivation delay of up to 30 seconds.

I agree with the OP. The emote complicates the issue too, it pulse once per second, related to the server tick. Thus when you first click it, it could be full second before you see the emote, before even considering any lag. So when you are going from a gate cloak to the onboard cloak, it is not immediately obvious that you have made the crossover. You are left having to delay clicking the onboard cloak for a second to make absolutely sure you are clear of the gate cloak. Not something you want to do when you have jumped into an insta-lock gate camp. In that situation you could end up clicking too early or mashing the button a second time, thinking it hasn't engaged. I too have been killed making that mistake under those circumstances.

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.

I don't think you get it:

1. You have jumped into an insta lock gate camp.
2. You break gate cloak and click the onboard cloak
3. In the first second, you see nothing happening other than the gate cloak dropping.

Have you clicked too early, or are you just unlucky with the server tick and a bit of lag? Remember you are decloaking into an insta lock gate camp.

Never happened to me, must be a new bug or something.

a problem stemming from the UI

DId you argue against the addition of the visible weapons timers and cooldown timers too?

A 1 second delay for all modules would be fine actually.

Not because of pilot error (which is great) but because of lag (which is less great).


For example, it sometimes happens to me that i click on prop mod, because of lag it doesn't immediately show that it's activated, so I click on it again and end up deactivating it.

Yes, it will cycle anyway, but at the end of the cycle it will auto turn off and I have to remember to turn it back on again. No big deal, but slightly annoying if you're PVPing and concentrated on several other things.

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

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.

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.

As one who experiences lags due to a poor internet connection on a consistent basis I understand the OP all to well.
Is it to much to ask that the emote around the cloak icon actually gives an indication that it has been activated in the same way that virtually every other module does?

It was asked why should the cloak be given something special that no other module has.
I would turn that around and ask why should the cloak be special in that it does not have the same thing that the other modules do?