In dev blog #20 they have stated that they are fixing the decloak problem so we will no longer drop out of cloak every time a bridge officer sneezes!!!
"We also updated several Cardassian and Borg themed episodes for inclusion in the Klingon?s storyline. New dialog options were added to make them feel more in-line with the Empire?s goals, and an effort was made to make many parts of the game friendlier to cloaked ships! Yes, that?s right; we can now take steps to ensure that your First Officer doesn?t pull your ship out of cloak just to tell you that nothing can be found on the scanners. It?s a slow and involved process to make all the Klingon missions ?cloak friendly,? so give us some time. It?s one aspect of the game we will continue to improve upon in the future."
In dev blog #20 they have stated that they are fixing the decloak problem so we will no longer drop out of cloak every time a bridge officer sneezes!!!
"We also updated several Cardassian and Borg themed episodes for inclusion in the Klingon?s storyline. New dialog options were added to make them feel more in-line with the Empire?s goals, and an effort was made to make many parts of the game friendlier to cloaked ships! Yes, that?s right; we can now take steps to ensure that your First Officer doesn?t pull your ship out of cloak just to tell you that nothing can be found on the scanners. It?s a slow and involved process to make all the Klingon missions ?cloak friendly,? so give us some time. It?s one aspect of the game we will continue to improve upon in the future."
WOOOO!!
Unfortunately, not all of the instances will be fixed in the near future. :P
reH, QaH nuv'e' SuvmeH!
Edit: Bah, I wish Bing was more accurate... when I translated "Still, this will help us against our foes!" into Klingon (producing the above text) and back, I got "to Help people, always".
So much for using the Klingon language in appropriate places. :mad:
Infinite possibilities have implications that could not be completely understood if you turned this entire universe into a giant supercomputer.
It's funny how this was first a huge bug, then Stahl said it was "working as intended" and now its back to being a bug that's been fixed.....
Aside from that i'm wondering just what all they did that makes the missions more cloak friendly aside from that. Unless it's like every thing else they advertised in which case it's just that and they're trying to make it sound like something it's not.... To make it even worse is that Fed and Klingon cloaks are only being fixed so the romulan crowd doesn't get angry.
I wonder if the "cloak friendly" missions (if it's even that) will apply to feds with cloaks as well?
It's funny how this was first a huge bug, then Stahl said it was "working as intended" and now its back to being a bug that's been fixed.....
This.
Either way Cryptic has lost a lot more credibility (as if they had much to begin with). This is something they should have done well over 2 years ago. They will not get praise for this, nor should they deserve it. The opinion of everyone should be "about time!" but also remain skeptical.
Can't think of a developer except a few that has betrayed the trust of their customers as much as Cryptic has yet gotten away with it.
Having played the KDF content on tribble, I can say for certain that they are fixing it
That being said, quite a few of the missios in the game will still have the bug, but it I'd say they are at least half way there
Play my missions on Holodeck! Return of Ja'Dok Series (6 Part Series) Enemy of the Exile Series (4 Part Series) Task Force Ja'Dok Series (3 Part Series)
Funny how it has gone from ''working as intended'' according to certain Cryptic staff to a bug all of a sudden. Its almost like some kind of big event like the Romulan faction triggered this... oh wait. I think a lot of vet KDF called this.
As previously noted, this must be done on a case-by-case basis. That means that it is simpler to build a mission from the ground up with this function, than to go back to an older mission and retrofit it. (Not that this stopped me when I was retrofitting the Cardassian missions to make them accessible to Klingons.) Naturally, this means that the new content will be more likely to have this feature, not because it's just for Romulans, but simply because doing it from the start in new missions was simpler to do.
The fact that interactions drop your ship out of cloak works as designed in that this is what the engine is programmed to do. The base engine, unless you specifically build around it, flags that when any kind of interaction happens -- talking to a bridge officer, scanning a mission objective, whatever -- it will interrupt the cloak power. So, it is "working as designed" in that it does exactly what the engine is built to do. Brandon might call it a "bug" inasmuch as people complain about it, but it's not a "bug" in the sense that this is not the engine behaving in some way that it shouldn't, or some code not doing what we meant for it to do. It is doing exactly what the code is programmed to do, and working around that requires specific time and functionality changes from the designers.
So working as designed doesn't necessarily mean it's working the way you wish it did, just that it's working the way it was built to originally, aye?
Basically, as far as I'm reading
'Working as intended', as far as the engine was designed to do, but not as the devs planned to keep. So it's still a bug because many players are annoyed with it.
In short, really another miscommunication, it seems
Was named Trek17.
Been playing STO since Open Beta, and have never regarded anything as worse than 'meh', if only due to personal standards.
'Working as intended', as far as the engine was designed to do, but not as the devs planned to keep. So it's still a bug because many players are annoyed with it.
In short, really another miscommunication, it seems
It's literally the difference between "working as designed" and "working as intended".
:eek::cool:
Formerly Known as Protector from June 2008 to June 20, 2012
Please enable us to buy a token with Zen to faction change a 25th Century FED to a TOS FED.
'Working as intended', as far as the engine was designed to do, but not as the devs planned to keep. So it's still a bug because many players are annoyed with it.
In short, really another miscommunication, it seems
Just because your annoyed with something does NOT mean its a bug.
For instance I am annoyed with the perma KB with the secondary sword strike. Its not a bug its just annoying.
Just because your annoyed with something does NOT mean its a bug.
For instance I am annoyed with the perma KB with the secondary sword strike. Its not a bug its just annoying.
Uh, I never said I was annoyed with popups decloaking Klingon (and now Romulan) ships; just that it annoyed many others. And there have been a lot of requests that it be fixed, like many other 'bugs'.
It may not technically be a bug, but that doesn't mean we can't call it that, for convenience.
Was named Trek17.
Been playing STO since Open Beta, and have never regarded anything as worse than 'meh', if only due to personal standards.
Yeah, and why has there be so much talking? Give me the mission briefing and I will shoot up things. Talk, talk, talk , all the time .... shut up.
The other day I missed some loot again, while hitting the interaction key to pick things up, a guy in a pop screen appears telling me to warp out ... bang, gone.
Side note. I do often the 2800 missions to get the Jem set, but I really get frustrated while doing Boldly they rode of Kurland. Every step you take, Kurland here, ok you took a step, be careful now, put your other feet forward and take the next step. It should be renamed. Boldly they rode and never stopped blathering.
As previously noted, this must be done on a case-by-case basis. That means that it is simpler to build a mission from the ground up with this function, than to go back to an older mission and retrofit it. (Not that this stopped me when I was retrofitting the Cardassian missions to make them accessible to Klingons.) Naturally, this means that the new content will be more likely to have this feature, not because it's just for Romulans, but simply because doing it from the start in new missions was simpler to do.
The fact that interactions drop your ship out of cloak works as designed in that this is what the engine is programmed to do. The base engine, unless you specifically build around it, flags that when any kind of interaction happens -- talking to a bridge officer, scanning a mission objective, whatever -- it will interrupt the cloak power. So, it is "working as designed" in that it does exactly what the engine is built to do. Brandon might call it a "bug" inasmuch as people complain about it, but it's not a "bug" in the sense that this is not the engine behaving in some way that it shouldn't, or some code not doing what we meant for it to do. It is doing exactly what the code is programmed to do, and working around that requires specific time and functionality changes from the designers.
As a software engineer myself, I can completely understand this distinction. But just because it is NOT a bug in the literal / technical sense does not mean it is working as intended. I think from the perspective of a player and feature it is NOT working as intended and essentially is a bug because it gets in the way of us playing the game naturally. It also makes no sense in terms of cannon / story / logic or game mechanics. All of this is true despite the code doing exactly what is supposed to be doing.
The difference is one of design / implementation. Let's chalk this up to a design bug that should have been dealt with long ago.
"With the first link, the chain is forged. The first speech censored, the first thought forbidden, the first freedom denied, chains us all irrevocably."
And I can confirm it works, at least currently on Tribble I was playing that two-part Orion mission plotline (the ones currently just before "Alpha"), and I was scanning their bases for clues, cloaked. (btw, scanning no longer decloaks you either, far as I can tell)
An enemy came to get revenge, with one of those overly-big popups...
Before, during, and after the popup, my ship stayed cloaked. I enjoyed it
Was named Trek17.
Been playing STO since Open Beta, and have never regarded anything as worse than 'meh', if only due to personal standards.
Either way Cryptic has lost a lot more credibility (as if they had much to begin with). This is something they should have done well over 2 years ago. They will not get praise for this, nor should they deserve it. The opinion of everyone should be "about time!" but also remain skeptical.
Can't think of a developer except a few that has betrayed the trust of their customers as much as Cryptic has yet gotten away with it.
Interesting... it must be due to the number of feds that will now have cloaked ships and will complain.. but TRIBBLE everyone who has been complaining since January 2011 when the bug was released eh? In any case... it is about time!
I AM NOT A FAN OF PWE!!!!
MEMBER SINCE JANUARY 2010
The fact that interactions drop your ship out of cloak works as designed in that this is what the engine is programmed to do.
The game engine can be programmed to do that (and DO IT) all you want ... but that does not resolve the fact that the resulting BEHAVIOR is neither EXPECTED nor even DESIRED. It is that latter point that causes the "disconnect" on turns of phrase like Working As Intended ... because use of the term immediately calls into question what the Intended BEHAVIOR is supposed to be, and if it doesn't align with Expectation (or Desired Results) then you've got a problem that needs to be fixed. Most players view issues that need to be fixed as BUGS rather than "features" of gameplay.
The better question to ask in this case is why the game engine was programmed with this particular bias in it in the first place? Seems that the smarter play would have been to design interactions to NOT drop cloak in the first place, and then have specific circumstances in missions that would do so as a consequence of specific actions involving interactions (ie. dropping cloak is a deliberate STORY driven consideration, rather than an automagic "game engine" driven bias). Which in turn begs the question of why Cryptic isn't addressing this issue at the game engine level FIRST so as to "reverse the bias" involved in this issue, since it would seem (to lay people like us outside the company code base) to be the simpler and easier solution.
In dev blog #20 they have stated that they are fixing the decloak problem so we will no longer drop out of cloak every time a bridge officer sneezes!!!
"We also updated several Cardassian and Borg themed episodes for inclusion in the Klingon?s storyline. New dialog options were added to make them feel more in-line with the Empire?s goals, and an effort was made to make many parts of the game friendlier to cloaked ships! Yes, that?s right; we can now take steps to ensure that your First Officer doesn?t pull your ship out of cloak just to tell you that nothing can be found on the scanners. It?s a slow and involved process to make all the Klingon missions ?cloak friendly,? so give us some time. It?s one aspect of the game we will continue to improve upon in the future."
WOOOO!!
Hopefully they're fixing that for ALL cloaking ships.
The game ahs TWO cloak heavy factions now, I doubt the ROmulans like being booted into view because they're getting a status update ont eh repairs to deck fours grav plating.
Comments
Unfortunately, not all of the instances will be fixed in the near future. :P
reH, QaH nuv'e' SuvmeH!
Edit: Bah, I wish Bing was more accurate... when I translated "Still, this will help us against our foes!" into Klingon (producing the above text) and back, I got "to Help people, always".
So much for using the Klingon language in appropriate places. :mad:
Infinite possibilities have implications that could not be completely understood if you turned this entire universe into a giant supercomputer.
Oh well, at least it's getting done.
It's cool to see that Bing added Klingon to the translation matrix, just sorry they didn't do it so it accounts for sentence structure.
Seems like a lot of the old problems like this are finally getting addressed. Hopefully AutoNav pathing will be next across the board.
Not sure how it is with you Klingons, but on the Fed side autonav pathing sucks.
I wonder how many Klingon first officers were killed for sneezing while cloaked? lol
Aside from that i'm wondering just what all they did that makes the missions more cloak friendly aside from that. Unless it's like every thing else they advertised in which case it's just that and they're trying to make it sound like something it's not.... To make it even worse is that Fed and Klingon cloaks are only being fixed so the romulan crowd doesn't get angry.
I wonder if the "cloak friendly" missions (if it's even that) will apply to feds with cloaks as well?
This.
Either way Cryptic has lost a lot more credibility (as if they had much to begin with). This is something they should have done well over 2 years ago. They will not get praise for this, nor should they deserve it. The opinion of everyone should be "about time!" but also remain skeptical.
Can't think of a developer except a few that has betrayed the trust of their customers as much as Cryptic has yet gotten away with it.
What Cryptic should consider before releasing anything.
Yeah, some of our content has pretty wonky autonav pathing.
That being said, quite a few of the missios in the game will still have the bug, but it I'd say they are at least half way there
Return of Ja'Dok Series (6 Part Series)
Enemy of the Exile Series (4 Part Series)
Task Force Ja'Dok Series (3 Part Series)
The fact that interactions drop your ship out of cloak works as designed in that this is what the engine is programmed to do. The base engine, unless you specifically build around it, flags that when any kind of interaction happens -- talking to a bridge officer, scanning a mission objective, whatever -- it will interrupt the cloak power. So, it is "working as designed" in that it does exactly what the engine is built to do. Brandon might call it a "bug" inasmuch as people complain about it, but it's not a "bug" in the sense that this is not the engine behaving in some way that it shouldn't, or some code not doing what we meant for it to do. It is doing exactly what the code is programmed to do, and working around that requires specific time and functionality changes from the designers.
So working as designed doesn't necessarily mean it's working the way you wish it did, just that it's working the way it was built to originally, aye?
'Working as intended', as far as the engine was designed to do, but not as the devs planned to keep. So it's still a bug because many players are annoyed with it.
In short, really another miscommunication, it seems
Been playing STO since Open Beta, and have never regarded anything as worse than 'meh', if only due to personal standards.
It's literally the difference between "working as designed" and "working as intended".
:eek::cool:
Please enable us to buy a token with Zen to faction change a 25th Century FED to a TOS FED.
Just because your annoyed with something does NOT mean its a bug.
For instance I am annoyed with the perma KB with the secondary sword strike. Its not a bug its just annoying.
It may not technically be a bug, but that doesn't mean we can't call it that, for convenience.
Been playing STO since Open Beta, and have never regarded anything as worse than 'meh', if only due to personal standards.
That and there was a point that it never did it, like for the first year of the game. So most people assumed it was a bug and not done on purpose.
The other day I missed some loot again, while hitting the interaction key to pick things up, a guy in a pop screen appears telling me to warp out ... bang, gone.
Side note. I do often the 2800 missions to get the Jem set, but I really get frustrated while doing Boldly they rode of Kurland. Every step you take, Kurland here, ok you took a step, be careful now, put your other feet forward and take the next step. It should be renamed. Boldly they rode and never stopped blathering.
easy there space puppy
system Lord Baal is dead
simple...get a human boff, name it Kurland...hmmm...and dismiss lol
Or execute for incompetence.
As a software engineer myself, I can completely understand this distinction. But just because it is NOT a bug in the literal / technical sense does not mean it is working as intended. I think from the perspective of a player and feature it is NOT working as intended and essentially is a bug because it gets in the way of us playing the game naturally. It also makes no sense in terms of cannon / story / logic or game mechanics. All of this is true despite the code doing exactly what is supposed to be doing.
The difference is one of design / implementation. Let's chalk this up to a design bug that should have been dealt with long ago.
- Judge Aaron Satie
R.I.P
system Lord Baal is dead
Like the rudder, bolts and anti-flooding designs on the Titanic.
Working as intended... until it sinks (player support).
Now that the majority of the player base wants to play a romulan faction its not working as intended?
Which is it?
An enemy came to get revenge, with one of those overly-big popups...
Before, during, and after the popup, my ship stayed cloaked. I enjoyed it
Been playing STO since Open Beta, and have never regarded anything as worse than 'meh', if only due to personal standards.
Interesting... it must be due to the number of feds that will now have cloaked ships and will complain.. but TRIBBLE everyone who has been complaining since January 2011 when the bug was released eh? In any case... it is about time!
I AM NOT A FAN OF PWE!!!!
MEMBER SINCE JANUARY 2010
The game engine can be programmed to do that (and DO IT) all you want ... but that does not resolve the fact that the resulting BEHAVIOR is neither EXPECTED nor even DESIRED. It is that latter point that causes the "disconnect" on turns of phrase like Working As Intended ... because use of the term immediately calls into question what the Intended BEHAVIOR is supposed to be, and if it doesn't align with Expectation (or Desired Results) then you've got a problem that needs to be fixed. Most players view issues that need to be fixed as BUGS rather than "features" of gameplay.
The better question to ask in this case is why the game engine was programmed with this particular bias in it in the first place? Seems that the smarter play would have been to design interactions to NOT drop cloak in the first place, and then have specific circumstances in missions that would do so as a consequence of specific actions involving interactions (ie. dropping cloak is a deliberate STORY driven consideration, rather than an automagic "game engine" driven bias). Which in turn begs the question of why Cryptic isn't addressing this issue at the game engine level FIRST so as to "reverse the bias" involved in this issue, since it would seem (to lay people like us outside the company code base) to be the simpler and easier solution.
Protonic Kool-Aid Down The Drain Cruiser
Immortal BOff Skills combo for Ground
Hopefully they're fixing that for ALL cloaking ships.
The game ahs TWO cloak heavy factions now, I doubt the ROmulans like being booted into view because they're getting a status update ont eh repairs to deck fours grav plating.