Trident Down bug? **SPOILERS**

dave · Post by **dave** » Tue Feb 05, 2008 10:05 pm

Hello,

I've been playing the Trident Down mission and got to the stage where I confronted the ATU at Dicebe where then they threatened me with imprisonment if I didnt work for them.

I then delivered their equipement to Raceedat before returning to Dicebe. I was then asked to rescue the ambassador from the Astromine Colony but at the same time, all my kills have disappeared so I'm now Harmless with 0 kills and my saves are showing as nil instead of my commander name.

Has anyone an idea why this has happened?

I'm running v1.65 and 0.5 of Trident Down.

Thanks

Hoopy · Post by **Hoopy** » Wed Feb 06, 2008 8:28 am

Sometimes after a long playng session (many hours) I had a similar sounding problem after saving.

What happened was that a bug caused the save game to be marked as 'strict' mode. Since the save game had things like Q-bombs in it the game rejected it as not 'strict' mode so loaded the default commander jameson, 0 kills, harmless etc.

So check that you're still at Dicebe.

OTOH you say the commander name is 'nil' so maybe it's nothing to do with that...

I expect that the author of trident down (ramirez I think) will want to see the relevant bit of your save file. (Load it in a text editor and copy any lines with 'trident' in them and post them here.)

dave · Post by **dave** » Wed Feb 06, 2008 5:26 pm

Hi Hoopy. Thanks for the update. I am still at Dicebe.

Here's the only reference to Trident that I can find in my save file...

<key>Trident_Down</key>
<string>Rescue the Dicebean ambassador from the

hmmm. I'm no expert but that doesnt look too good to me!

By the way, I do still have all my credits, ship and equipment.

Hoopy · Post by **Hoopy** » Thu Feb 07, 2008 9:15 am

that's the bit that sets the text you see on the F5 string. There should be another bit which tells the OXP where you've got to. If it's missing then something has gone pretty badly wrong somewhere! I'm guessing you did something the OXP didn't expect so it's cleared the setting and not put the new value in...

Commander McLane · Post by **Commander McLane** » Thu Feb 07, 2008 9:51 am

If the game set itself to strict mode, isn't it more likely that something went wrong in that process?

Anyway, it looks bad. Probably not fixable?

Hoopy · Post by **Hoopy** » Thu Feb 07, 2008 10:20 am

I think the strict mode thing i suffered from is a red herring in this case.

I'm guessing it will fixable by adding the mission variable for Trident Down and trying again. Without digging through the script.plist I've no idea what the variable should be though. And Dave is playing a different branch in the OXP to me so I can't even guess.

Ramirez · Post by **Ramirez** » Thu Feb 07, 2008 10:43 am

Hi Dave

The mission variable you need for this bit is mission_trident_down ATURESCUE; alternatively if you want to make sure the change has taken effect properly, use WEAPONSDELIVERED and wait for the Dicebe debriefing to pop up again.
If need be just find an existing variable in the save file, copy and paste and amend as necessary.

dave · Post by **dave** » Thu Feb 07, 2008 5:32 pm

Thanks for the replies everyone.

Unforunately the bit I posted above is the last part of the save file. There's nothing else at all there.

I did have four outstanding UPS missions which have also disappeared from the F5 F5 screen.

Also, the save game files are still saved with my commander name, Allen.oolite-save but when loaded my name appears as "nil"

Commander McLane · Post by **Commander McLane** » Fri Feb 08, 2008 7:06 am

A quick question: How many save files do you have in your save file folder?

There is a long standing bug in Oolite that causes it to corrupt save files when there are more than a handful of them in your folder.

You will be safest when the number of commanders you have saved does not exceed 7 or 8. (You may place the rest of them into a sub-folder, though, if you want to keep them.)

dave · Post by **dave** » Fri Feb 08, 2008 8:21 am

I only have two saved commanders so its definitely not that.

Hoopy · Post by **Hoopy** » Fri Feb 08, 2008 9:11 am

The bug i mentioned earlier is the same a Commander McLane's - I'd forgotten that it was caused by the number of saves and not by the amount of playing.

I must just save every 15 mins on average so 2 hours play gives 8 saves and then I get the problem.

dave · Post by **dave** » Fri Feb 08, 2008 5:09 pm

Another thing I forgot to mention was that I've also lost my Supercobra and now have a Cobra MkIII again. Sorry that i've put the info on here in dribs and drabs - i've not managed to spend much time playing it since the crash.

Looks like I'll be starting again from scratch!

Hoopy · Post by **Hoopy** » Fri Feb 08, 2008 9:23 pm

no need to start from scratch, it'll be easy to take a new savegame and change your ship. you can then buy all the kit you used to have and set the credits to the right amount.

Oolite Bulletins

Trident Down bug? SPOILERS

Trident Down bug? SPOILERS