Whitecat106 / Historic-Missions

Historic Missions Contract Pack for KSP 2.2.0
2 stars 0 forks source link

Prepare HM for CC-1.15.1 #15

Closed Whitecat106 closed 8 years ago

Whitecat106 commented 8 years ago

Need to:

jrossignol commented 8 years ago

My plan was to add a sortKey field for CONTRACT_TYPE to allow spring within a group. I can do the same for v CONTRACT_GROUP, with the caveat that it would only work for child groups. The reasoning is I don't want one contract pack to do stuff that can affect others (such as using the sort order to force itself to the top of the list).

So for you I'd suggest something like: Historic Missions |- Gemini |- Apollo Etc.

The other thing that I forgot about was the intermediate groups that you use for setting maxSimultaneous for a subset of contracts. Do you still need this functionality? If so I'll need to introduce functionality to hide these nodes in the hierarchy.

I'll try to get these changes done tonight.

Whitecat106 commented 8 years ago

I see your reasoning! However within child groups would work too, since my pack is defined from the HistoricMissions group with a max simultaneous of 100 and then by say 'apollo group', 'gemini group'.

This would allow a chronological order for subgroups along with alphabetical order for the actual contract pack with other packs in the mission control preventing packs from bumping themselves to the top! :)

I do not actually use max simultaneous too much, it's only really necessary for afew contracts (since I have added the newVessel requirement) such as the buran shuttle mission and the space shuttle, both have similar requirements that would fulfil eachother so they needed to be separated, the same with some early apollo and Soyuz missions.

I love the new changes, really makes the mission control more friendly and organised!