test content
What is the Arc Client?
Install Arc

Cloaking Device.... still bugged?

2»

Comments

  • Archived PostArchived Post Member Posts: 2,264,498 Arc User
    edited July 2011
    The fix for this issue is not as simple as it sounds. It involves touching every single map in the game, which is a ridiculously high number.

    That being said, we did it and the fix will be in the next tribble push.

    That made it sound like they had worked tirelessly and physically touched every last map in the game in order to correct the problem.

    Turns out it was an automated script... and one that may not have worked properly?

    Bah... never mind. I see an infraction coming my way if I say any more. :) Thanks for the "attempt" anyway, devs.
  • Archived PostArchived Post Member Posts: 2,264,498 Arc User
    edited July 2011
    If you could just stay cloaked you could basically just fly to a mission objective, use it, and leave without ever having to fight anything that might be there to protect it.

    this right there actually is something i very much LIKED.

    as a Federation Player i often tried to avoid combat if it was not required in the Quest Log.

    If it says kill 5/5 enemys -> clear orders to clean out the sector
    If it says scan 5/5 clickies -> but Romulans hang around in the sector, i try to stay out of range and only scan the clicky, with any luck i complete the objective without murdering and maybe even get 10 DXP.
    (that was mostly in Patrol mission)


    Of course as Fed you can allways use Mask Energy signature, which is often forgotten, but works under the same conditions as the cloak, so Mask Energy Signature suffers from the same issues as the Cloak.
  • Archived PostArchived Post Member Posts: 2,264,498 Arc User
    edited July 2011
    I'm really sick of it.

    After more then a half year they bring something out wich they call "fix" for a a broken game mechanic, and this doesnt fix anything.

    The cloak is still broken and obviously will stay broken intentionally.
    I never bought that "going through all maps" stuff, that would mean going through all of the "unlimitet" amount of exploration missions, not even speaking of foundy missions, wich is simply impossible and the cloak worked before. They simply had to remove the patch that broke it. And dont even try to tell me "you cant remove a patch that easy, they removed the WHOLE season 4 patch from tribble within less then an hour.

    Also: the explanation "it did not decloak WHEN it was supposed to"; well I'd say the 3 of 200 times the player gets a slightly unfair advantage is still better then BRAKING THE WHOLE CLOAK!!!

    There is NO reason ANY dialog shoukld EVER force to decloak. The game told me "I'm the captain", that would mean I DECIDE when I decloak.
    Iteracting with objects is another thing, when I decide to interact with an object I know it will drop the cloak, so thats my decision.
    But if anybody talking to me without giving me the option to prevent that, thats a broken mechanic, nothing else.

    But well.... whats left to say?
    Its not the only broken thing that will remain broken in the game.
    I had high hopes that season 4 will massivly inprove STO.
    It failed on EVERY level. Right now, I simply cant play. I cant even eqiop my bos at the right stations any more. Thats the kind of stuff that happens if patches go live that simply are not ready for the live server, the fact that almost ALL reportet bugs now have been reportet on Tribble too is prove enough for that.
    Whild the shooter mode is BASICLY fun, ground is a mix between FAR TO EASY, wich is no fun, and one shot deaths, wich also isnt fun.
    Instead of removing character based purchases for unreasonable high prices, like requestst towards BO and ship slots thousands of times, they even addet MORE character-only stuff into C-Store (Bank and Inventory slots).
    Things didnt get better, they got MUCH MUCH WORST.

    So, before I wanst a fan of people saying that, now I'm saying it myself: As soon as The old Republic starts its open beta, I'm gone for good. Cant be worst there then here. And until then, C-Store won't see any of my money any more.

    I just feel sorry for all the money and time I wastet with the disapointment called "Star Trek online".
  • Archived PostArchived Post Member Posts: 2,264,498 Arc User
    edited July 2011
    That made it sound like they had worked tirelessly and physically touched every last map in the game in order to correct the problem.

    Turns out it was an automated script... and one that may not have worked properly?

    Bah... never mind. I see an infraction coming my way if I say any more. :) Thanks for the "attempt" anyway, devs.

    Yeah, I am surprised to hear this too as it was described as if they had tirelessly gone through every single map and fixed it by hand. :confused:
  • Archived PostArchived Post Member Posts: 2,264,498 Arc User
    edited July 2011
    The patch notes weren't very clear here, let me elaborate.

    When the game was shipped, pop-up dialogs and informational inter-actables did not force ships that were cloaked to decloak. The only thing that would force you out of cloak were mission objective inter-actables.

    This was by design. If you could just stay cloaked you could basically just fly to a mission objective, use it, and leave without ever having to fight anything that might be there to protect it.

    Somewhere between Season 2 and Season 3 all pop-ups and informational inter-actables were reclassified in the Engine to all work off the same internal engine feature, prior to this change there were separate systems for each . This change was a good thing for those of us that use the tools daily because it simplified our work flow. However, it had the side effect of breaking people out of cloak whenever you use any inter-actable or get any pop-up etc...etc..

    There has been new tech added to this system as with the latest build that allows us to flag this stuff now on a case by case basis. We also ran a game wide "fix" script that should have caught most of these with Season 4.

    I'm sure that the script probably missed a bunch of edge cases as well, so just report them when you see them and we will crush them as we get the reports.

    Just so you know, on your clarifications, all popups are STILL decloaking ships as of last night, least for the Gx.
  • Archived PostArchived Post Member Posts: 2,264,498 Arc User
    edited July 2011
    Still happening for me too...

    Devs.. here is how you reproduce...

    1) Go into Ker'rat
    2) You get the initial popup telling you about the mission.. which I should be able to suppress after the 10 millionth time.
    3) cloak and stay cloaked
    4) wait until the decryption of the node phase completes.
    5) when the next phase of the missions begins, to destroy the repair hulks, you will decloak upon message popup
    6) Cloak again
    7) when all repair hulks are destroyed and mission completes you will decloak

    I believe these guys when they say that other maps are causing the same problems...

    I'm sorry, but there are only certain things that should caused a ship to decloak and they are listed here:

    http://memory-alpha.org/wiki/Cloaking_device under the "Penetrating the cloak" section.. in addition to the extras this game has introduced. I should NEVER be pulled out of a cloak for anything except for what is listed on this webpage and what the game intends as a Boff power to do so.

    Season 4 release notes say this:
    • Contacts and mini-contacts will no longer pull players out of cloak with the following exceptions.
    • If you are interacting with something you will still be pulled out of cloak.
    • We can still have a contact or mini-contact pull you out of cloak if we feel it benefits the mission!

    Sorry, I would order my boff to shutup rather than decloak me.

    The last item stinks.. basically, Cryptic is saying they can pull you out of cloak whenever they want. If Cryptic were my boff, I would discipline him/her for messing up an attack run by decloaking when he/she shouldn't.

    This messed up after Season 3 was deployed.

    Basically, and in summary, nothing was really fixed because the exceptions pretty much encompass all popups. This was very misleading by the person who wrote that release note!!!
  • Archived PostArchived Post Member Posts: 2,264,498 Arc User
    edited July 2011
    Well if the script didn't fix the problem... what DID it do?
  • Archived PostArchived Post Member Posts: 2,264,498 Arc User
    edited July 2011
    Good summary of the situation there TF.
  • Archived PostArchived Post Member Posts: 2,264,498 Arc User
    edited July 2011
    Iceroid wrote: »
    Actually, using the transporter did not force decloak.

    See ST 4 The Voyage Home

    Actually, I don't doubt you. Then again, the BoP has a cloak that would allow for it. The Defiant, however, had to decloak between Enterprise's (NCC-1701) old style sensor scans to transport someone. :p
  • Archived PostArchived Post Member Posts: 2,264,498 Arc User
    edited July 2011
    I'm not sure who told you this, but it wasn't anyone who works for Cryptic on the Content Team. There are exactly 3 people at Cryptic that know the history of the issue and I am one of them.

    I'll check again tomorrow and find out what's going on. I'm giving you the exact information that was given to me by the Programmer that "fixed" the issue. No one is trying to spin anything, no one is lying to you.

    Thank you. I feel better now. Carry on, then, and squish ze buggers. :)
  • Archived PostArchived Post Member Posts: 2,264,498 Arc User
    edited July 2011
    Back out the engine change. Special-case it for Cloaked Intentions. Try again later. Please.

    It's not even about this particular bug anymore. It's reversing a negative change in development philosophy that cropped up with the featured episodes. Adding cool new Items and effects for the FEs had unexpected, negative, global consequences; i.e., cloak, tractor mine, fighters. STO's been backsliding on the quality and trekiness that Season 2 delivered on.
  • Archived PostArchived Post Member Posts: 2,264,498 Arc User
    edited July 2011
    I have not had a single interaction with a Boff that has not pulled me out of cloak.
  • Archived PostArchived Post Member Posts: 2,264,498 Arc User
    edited July 2011
    I have been complaining about this since 01-11-11, the day they broke cloaking. I find this entire situation to be beyond pathetic & truely lame. What does it take to get through to these people? Fixing cloaking should be priority number 1, period. At this stage though, to expect any kind of quality from Crytic is downright ludicrous.
  • Archived PostArchived Post Member Posts: 2,264,498 Arc User
    edited July 2011
    Borthan wrote:
    I find this entire situation to be beyond pathetic & truely lame.

    i wouldn't say it like that, but agreed.
    the situation could have been handled more... uhm... professionally... and a lot earlier.
    Borthan wrote:
    Fixing cloaking should be priority number 1, period.

    actually... no
    fixing the Foundry (Missions) and getting the PvE + PvP Queue's to work again should have priority one
    and then... the cloak. (what good is a working cloak if half the game is not working ;P )
  • Archived PostArchived Post Member Posts: 2,264,498 Arc User
    edited July 2011
    Heya Fellows

    This is kinda annoying, like most people say, whats the point of having cloak if it gets disabled everytime you encounter an enemy or a hail.

    If this game is based on Star Trek, we should at least be able to use warp and sensors while cloaked as they do in DS9 and honestly, BO's should be able to talk to their captain without letting the ship delcoak :p.

    I think Cryptic should look over the cloaking procedures in this game 1 more time.
    I wouldnt mind see the cloak work properly on my ship again.


    "Let's sneak passed that Cardassian fleet... Captain, incoming hail, we decloaking.... Facepalm"
    This is just silly :rolleyes:


    //Freeman
  • Archived PostArchived Post Member Posts: 2,264,498 Arc User
    edited July 2011
    Sobekeus wrote: »
    Well if the script didn't fix the problem... what DID it do?

    Guesses:
    1) not run at all. At least not on the "real" mission data on tribble or holodeck.
    2) break mission difficulty.
    3) Found a cure to cancer and send the results to /dev/null
  • toralantoralan Member Posts: 17 Arc User
    edited July 2012
    I had hoped that this would be fixed in Season 6, but no dice. Maybe if the Federation players who own a refit Defiant class starship start complaining, they will start fixing it.
Sign In or Register to comment.