Page 1 of 1

CSC mission bug

Posted: Mon Oct 01, 2007 3:47 am
by Fossaman
So, I got an unknown hostile mission, turns out to be a phobos. I die valiantly in defense of the commonwealth. My insurance claim gets processed, and I head back to the CSC, which tells me I have a mission in progress. I scamper back to where I saw the phobos, and pursue it to the stargate, where it gates out and gives me a 'mission complete!' message. I return to the CSC, where I get a standard mission succesful, you lost x many wingmen, etc. message.

This seems bugged to me.

Posted: Tue Oct 02, 2007 1:57 am
by (name here)
this happened to me, all ships involved with a player when he dies gate out.

Posted: Tue Oct 02, 2007 2:35 am
by george moromisato
You're right, this is definitely a bug. I'll fix this in a future release.

Thanks as always!

Posted: Tue Oct 02, 2007 6:12 am
by FAD
Staying inline with the CSC missions; Get the escort refugees from gate 1 to gate 2 successfully, then return to the carrier for the atta boy and get the next mission...it repeats another scenario of babysitting the refugees to the 2nd gate again. No biggie.
But... remember we have those previous wingmen on their way to gate out and with the new ones chasing you to meet up with the next batch of refugees at gate 1, then all of a sudden there's a "Mission Successful!" message before even reaching the gate! No new refugees anywhere!

So I return to the carrier feeling guilty for being credited or even promoted for a mission that never happened. Then several seconds later a message states that the refugees have arrived!?! OK, so here I am hovering near the carrier while all those helpless freighters are way out there trudging along toward gate 2. Being the good Samaritan that I am, I hurry off to help them gate out only to find the remains of an Ares easy-kill.
Yeah, sure, can't help but to loot all the wrecks but still... Something has gone adrift with this mission and I think it could have something to do with the previous wingmen gating out and triggering the "Success" code while the current mission is in session, maybe?
Any ideas or reasons why this happens?