We all know about the dialog box causing cloaked ship to break cloak at the most inopportune moments (i.e., BOFF tells Captain that ship is on sensors and the ship decloaks when your about to do an ambush... no loud conversation on bridge )

Well, the one lousy effect of the dialog box that is now irritating me is the freeze my ship at the wrong location situation. Yesterday I was dominating a D'derx in my Sovereign/Regent cruiser and went in to take him down with a Metron gas pass. I just dropped the gas and was about to move away when the enemy ship hit zero and started to explode. That was when the dialog box came up and froze me right next to the enemy ship... as it was exploding. I tried to get rid of the dialog box as fast as I could, but was still caught up in the combination of exploding metron gas and D'derx. My ship survived with 25% hull, but I should have actually sailed away with no damage.

The dialog box is not our friend (neither FED or KDF); how about making the dialog box a non-interactive part of the game. It is possible to give information without affecting cloak or movement. If your going to freeze or foil us with dialog boxes then do the same to the enemy NPCs... that is all.

There is an option in the main menu to disable the 'stop ship when dialogue box appears'. I tend to just hit R quickly to engage full impulse without clearing the dialogue box if I need to keep moving when it happens, since I'm usually navigating anyway at the time and my fingers are over the throttle.

I did not know that!

This changes everything! (Well, not everything, but you know.)

I just press 'F' to acknowledge the message and make it go away. Still doesn't deal with the decloaking, which starts a 20 second timer. Of course, it's all 'working as intended'. It's not a bug or mistake, it's a 'feature'.

Yay! I'm helpful!


It's a shame there isn't something like that for cloaking as well. I don't see how that could be a feature. It was something about skipping story content in missions? But surely if they are mission objectives anyway, you would have to decloak to engage them? Or you could just fly a large loop and go around them the long way, without cloaking. Same effect.

Has anyone at cryptic EVER named a single specific instance/mission where a still cloaked ship causes the mission to break or leads to an exploit?

About the only missions that even get close to circumventing anything are those scan 5 things missions that feature NPC enemies. But those are not part of the objective and couldn't break anyhing, so that leaves the "problem" of breezing through the mission where it is supposed to cost you time to get the reward *cough*one-click-foundry-mission*cough*.

Ok, this is Fed side only, not a lot of cloaks here anyway.

What about Klingon side? Which mission lets you complete it cloaked if not for dialog box decloaking?

Wait, I can think of one... If you are cloaked and reach a waypoint your enemy decloaks himself and threatens you. Why would he do that if you remain cloaked yourself? makes no sense, because he shouldn't know you are there.

So the problem is not the dialog box, but the waypoint. You reach it cloaked it breaks the story logic. But that can be adjusted by having your Boffs inform you, that they suspect there is a cloaked ship around and they want to actively scan for it with a high energy beam or something.
That of course decloaks you IF you are hidden and also triggers the NPC.

But Cryptic has no control over stories in foundry missions right? So there would only be any possible exploit in foundry missions by cloaks? *cough*one-click-foundry-mission*cough*.
Since when is the decloak bug in game and when did Cryptic develop the Foundry again? Could there be a connection?

that's all fine and dandy. make story missions decloak you. but what about Ker'rat? where the story really doesn't matter and all we wanna do is shoot at each other. dialog box is nerfing the cloaking. and the "working as intended" response is their way of saying "we don't really care enough to devote the man power to fix this "minor" inconvienence" in other words "deal with it until we can higher more/smarter devs"

sorry devs, truth hurts sometimes.