I played this mission today on a new character. Last time I played it, was a few months ago. Today, though, I noticed that the two locations to perform the Orbital Strike were missing. I haven't been able to find any news about them being removed.
Did I miss something, is this a bug, did Cryptic pull this thinking we wouldn't notice, what gives?
0
Comments
The thing is, there are quite a few things in the Romulan segment of the storyline (for feds) that seem to be different but could simply be down to my own faulty human memory because its been such a long time since I did these missions.
That being said, I do know Cryptic does change things in the storyline missions and they don't do much announcing for it. I rarely read patch notes of course so they might mention it there. *Chuckle.* One such thing is when T'Nae started actually talking with an actual voice rather than it being simply all text like it was back when I last did it.
They botched the Azura mission too. Once, if you were a science captain, you could rescue all of the Azura's crew and they all looked uniquely different and had different medical problems your captain temporarily fixed. You saw them in all the cut scenes where you beamed them out, then yourself out and they were physically there when you transported into your transporter room at the end.
Now of course all the 'extra' crewmembers you save as a sci captain are identical and none of them show up during the final rescue cutscenes. Only the two crewmembers that you pick up in the Azura engine room from Captain Brott show up in the cutscenes.
Similarly they botched another early mission as well where B'Vat lures you to a 'secret' base and locks you inside and sets a self destruct even slower than Hakeev's one in "Mine Enemy." The fed Captain had to shoot the doors open to run back to a point where your crew could transport you aboard.
Now, B'Vat doesn't lock you in, yet his gloating 'victory speech' about luring you into a trap hasn't been changed. So um... what trap exactly? The whole mission no longer makes sense....
Oh wait we were talking about the missing orbital strikes bit in "Cutting the Cord." Lol, yeah, let's just say Cryptic has done a lot of editing missions and often most players have no idea about it until they play the mission again on a new toon.
Jo Cox 22.6.1974 - 16.6.2016
Assuming that whatever glitch ailed me, also caused your issues, the location from where I shoot doesn't seem to be the trigger. I've played the mission probably over a hundred times (23 captains on my main account, 2 alt accounts, various replays and assists of other players, call me an addict if you must), and I generally just barge in and start shooting, never had the issue before. Just FYI.
Good luck fixing that one. You can run a debug / logging build ten times and it have it work properly every time.
RIP KDF and PvP 2014-07-17 Season 9.5 - Death by Dev
My character Tsin'xing
Get the Forums Enhancement Extension!
That bug is even worse on the console version as it happens very frequently. Anyway, I never saw the orbital strikes in the console version of the mission, and I did look for them in the usual spots. I think I found one, but it wasn't glowing.