[UPDATED RELEASE] Coyote's Run Mission

[davcefai]

I don't want to give away any spoilers but you shouldn't obey everything your partners tell you.

[davcefai]

I've completed the Coyote's Run mission. However on entering Laquused space the mission tries to start again!

The only Coyote related variable in my save file seems to be CoyoteCompletionCount which is set to one

Code: Select all

	<key>mission_CoyoteCompletionCount</key>
	<string>1</string>

Should I uninstall the mission or just avoid Laquused as there might be more Coyote goodness on the way?

Nice mission, author. I enjoyed it. Thanks.

[Cody]

Should I uninstall the mission or just avoid Laquused as there might be more Coyote goodness on the way?

Uninstall it* - you have completed the mission! Glad you enjoyed it! There is a sequel to the original tale, but no follow-on OXP.


*Unless you plan to visit Lago/Avernus Orbital again at some stage, in which case leave it be.

[Fatleaf]

but no follow-on OXP.

Well for now.........................................................

But the piece of equipment you get at a certain station requires you to have the OXP installed. So keep that in mind as to whether you want to use it or not.

[davcefai]

Well really all that is required is for the main script to honour the mission_CoyoteCompletionCount key.

Check if it is set to one and if so don't run the script. I haven't looked to see if it attempts to do this and might even try to do it myself when I have some time and inclination.

(Anybody who thinks that retirement means an empty, tranquil, even boring life had better not retire! The children still are evident in your life. The grandchildren can vacuum up any time you have left over from house maintenance, hobby woodworking, legal problems etc. (I'm not complaining, I LOVE being retired!) )

[Cody]

If memory serves, Okti left an option to immediately restart the mission - that's probably why it doesn't complete.

[Fatleaf]

Well it does 'complete' but it is always active. The counter is just for the players personal records to see how many times he has done the mission with the same commander. Leaving it active was to make things easier for the player to do the mission again without editing the save file.

If you ever find the mission offering to start again at the start planet all you have to do is ignore the instruction to cloak and the mission wont go any further. Just go about your normal business.

[davcefai]

Life being what it is, last night I was passing through Laquused again on an RSS mission. I was pounced on by a group of pirates AND a bunch of Thargoids.

Instinctively I cloaked to have a chance to orient myself. So the mission restarted! My fuel tank was automagically refilled and I jumped out to Reriveza, only to find the python there and the mission continuing.

So I edited the save file. I think the best bet will be to uninstall the OXP (losing the"special" piece of equipment which probably will not be of any future use). Alternatively I could edit the main script to exit at once. Could be fun playing with it.

[Fatleaf]

That sounds like you really have bad luck! Is this typical of the rest of your life?

I spend all of my time in the Seventh Octant (G7) so it never becomes an issue for me.

[davcefai]

Is this typical of the rest of your life?

Not typical, no, but at the moment in tune with a lot of other passing storms

Always look on the bright side of life!

https://www.youtube.com/watch?v=eTXiqKGFNso and wait for the song.

[vsfc]

G’Day Commanders!
I been running Coyote Run mission in Galaxy 5 and came across two problems.

1. Sahana keeps crashing into a station where she should dock on injectors, which basically stalls a mission as Sahana never gets docked and only edit of the save file to the next state number makes it to continue.
2. Main script file has no state 290, which has to be changed to 280. Occurs only in one place.

I haven’t completed the whole mission yet, so more reports may come if something. I am running 1.80 version of oolite at the moment.

Cheers,
VSFC

[Cody]

I vaguely remember something similar happening during the making/testing of the OXP. I can offer no help, I'm afraid - the OXP needs updating and Okti is MIA.