Forums » Bugs

Beginner "Explore the universe mission" stalls

May 31, 2008 cms3 link
I'm currently on a trial account. I did all the training missions except the one that is titled something like "Explore the Universe" where you travel with a capital ship on its run. I started this mission and made it through the first jump, but then nothing happened. I attempted flying close to both the capital ship and the other escort ships. I attempted sending messages directly to each of these as well in the chat window (I know these were automated rather than player ships, but was hoping this would cause some sort of response to either trigger the next step in the mission or at least a response to let me know something was happening) but nothing happened. After waiting several minutes I aborted the mission and returned to the station to try something else. I reviewed the chat logs which contained the communications from the other (automated) ships in the group, but didn't see anything that gave me a clue as to what I could have done differently to keep the mission from stalling.
Jun 22, 2008 Winter Owl link
I've attempted this same mission three times without success. The first time everything seemed to work correctly until I was instructed to return to the original sector. After jumping there, I got a "XML error: unclosed channel".

I aborted the mission, rejoined channel 100, then accepted the mission again. This time I experienced what the original poster described: the NPC ships weren't talking. Abort the mission, reaccept for round three.

The third time through was identical to the first. "XML error: unclosed channel" at the same point in the mission.

Edit: I accepted the missions in Arta Caelestis, but I don't remember at what station, and don't see that information in my mission log. Maybe I'm missing it somehow.
Jun 22, 2008 Daare link
Same. Trial account. Completed mission "Explore the Universe" and returned to home station when the console popped up with "XML error: unclosed channel".
Jun 23, 2008 incarnate link
Sorry, fixed this.

I made some changes on Fri night that added some additional text, which apparently broke Ray's XML parser. Anyway, it should be fine now. Thanks for the reports.