You can just imagine if this happened in the TV series' star trek

Sisko and co go through the wormhole, cloak the ship, and do some reconn

One of the bridge officers (Nog in this case ) accidently speaks to the captain, causing the ship to decloak right inside dominion territory.

Why on earth does our ship decloak when a bridge officer speaks to us? It makes no sense at all.

Yeah I made similar thread on Klingon gameplay about this. It's quite stupid dropping the cloak because the bridge officer is reporting to you.


Who gave the order to drop shield and or to come to full stop anyway?

You can disable the ship from stopping when a BO talks to you in the controls, I found that recently, which is a start, but it makes you wonder what they were thinking when they designed the game to do both, by default.

Another one is, why you can't cloak while at warp?

Hehe, probably the same thing they were thinking before Autofire. /doublefacepalm But honestly there was a time I read everything my BO said and it saved me from backtracking. Now, nah.

Regardless... uhm, I've barely ever used cloaks and I could swear there was a patch months and months ago that addressed improper decloaking. Has it regressed or could I be imagining patch notes that don't affect me?

At warp? Wouldn't that be purely cosmetic during animations and sector space? From a PVE point of view my understanding was almost no missions should warp you into a firefight without prep time.

But they do. At least if we count the exploration missions.

Not to mention the ambushes people setup in pvp space zones

I've only entered one pvp encounter by accident and as soon as I arrived, I was met with a mine field and two federation players using escorts.

this is a known bug...since...i cant remember when, but its a long long time now. So one of the oldest bugs in the game, along some others.

Welcome to STO

I think it's been close to a year now since this bug was introduced to the game.

They didn't design the game to de-cloak you when a BO talks to you (way back at launch it didn't happen). Its a bug that was introduced about six months after launch (from memory), Cryptic have said it will take too much effort to fix it, as apparently they have to change something on every map to stop it happening, so they instead issued a patch note to say its now fixed and have since ignored it (although it never was actually fixed).

It seems to be a re-occuring theme to solving issues for them......