persistent.sfs CONTRACT_FINISHED vs ?

[Trann]

I'm wondering if anyone knows how the data that drives the checkbox is stored?

I'm finding the count doesn't map directly to the CONTRACT_FINISHED entries.

Thanks.

EDIT: updated to 'answered'.

Edited September 4, 2014 by Trann

[Alshain]

I believe it does a check to see that all PARAM states are marked complete but the contract state is not marked FINISHED.

[Trann]

In walking through things, all CONTRACT_FINISHED entries have "state = Completed" and the nested PARAMs have "state = Complete" while all CONTRACT entries have either "state = Offered" or "state = Accepted".

I'm sure CONTRACT gets changed to CONTRACT_FINISHED when appropriate which makes sense.

The issue I see is that there are 22 finished contracts in the persistent.sfs file while there are 29 checks in the GUI. I suspect a mod is clobbering the completed contracts somehow so I'm trying to figure out what I can search for in the file (and in backups of the file) to discover the mismatch.

...

But this is all academic. If no one knows, that's fine, too.

[DeMatt]

CONTRACT_FINISHED entries are your stored completed contracts. If you go into Mission Control and click on the "Archives" tab, you'll see them listed there.

The checkmarks you've pictured in your screenshot are messages from completing contracts. Most contracts only generate one message when you complete them; the exception is the "Explore Mun"-type contract, which has four separately-completed objectives, each of which generates its own message. Certain mods (e.g. DebRefund or StageRecovery) also create messages; I daresay KSP itself will create more messages itself as more functionality gets added.

If you look at the bottom of your persistent.sfs, you'll find a block labeled MESSAGESYSTEM, with MESSAGE sub-blocks inside. That's where your "29 checks" are stored.

[Trann]

Multiple objectives! :doh:

I'll tweak my script and recheck/recount the numbers. I'm betting that's it.

[Trann]

The MESSAGESYSTEM block is where it's at. Inside were messages with "Contract Complete" vs "Contract Parameter Complete". A count of the former matches the number of CONTRACT_FINISHED entries; adding the latter accounts for the number of overall checkmarks displayed in the GUI (29).

Thanks muchly.

And for the sake of sharing...

Searching for the PARAM "state = Complete" gives a much higher number because its sub-PARAMs are conditions that must be met before the test can be considered a success. For example, a part test might have

PARAM
{
 name = PartTest
 PARAM
 {
  name = ReachDestination
 }
 PARAM
 {
  name = ReachSituation
 }

So it would be more accurate to exclude those sub-PARAMs in the count of completed contracts.

If you're so inclined.