thedmbarlow

Please try and remember I'm not a programmer. A big part of why I'm doing this entire project is to expand my skillset, so I don't have knowledge that may to you simply be basic stuff. Most of my specific in-context knowledge actually comes from your excellent CC wiki (which I originally didn't like much, fill disclosure), Nightingale. So now that I'm getting a useful output (I don't know how what I changed fixed that!) in the debug window, I've found and fixed the root issue. Many thanks, nightingale. When you initially gave the suggestion, I assumed that the name of the CFG file would work, and that's part of why it seemed to continue. Now that I've fixed that and the contract is loading, however, I have another question. How can I make sure that a contract appears when it's prerequisites are satisfied?

Sure. https://www.dropbox.com/s/vz1wer80hm9s8zx/KSP.log?dl=0

I've fixed the part references. I appreciate that detail, I suspected that it wouldn't be right but I had no idea where I'd find the proper names. I tested it and it didn't fix the contract not loading bit.

I didn't mean to imply that was useful by itself, just confirm that it's a possible cause. However, I've cut nothing out of the line itself. Here's it and all following lines until the next heading. UnityEngine.Debug:LogException(Exception) ContractConfigurator.LoggingUtil:LogException(Exception) ContractConfigurator.ConfigNodeUtil:ParseValue(ConfigNode, String, Action`1, IContractConfiguratorFactory, List`1, Func`2) ContractConfigurator.ConfigNodeUtil:ParseValue(ConfigNode, String, Action`1, IContractConfiguratorFactory, List`1) ContractConfigurator.PartValidationFactory:Load(ConfigNode) ContractConfigurator.ParameterFactory:GenerateParameterFactory(ConfigNode, ContractType, ParameterFactory&, ParameterFactory) ContractConfigurator.ParameterFactory:GenerateParameterFactory(ConfigNode, ContractType, ParameterFactory&, ParameterFactory) ContractConfigurator.ContractType:Load(ConfigNode) ContractConfigurator.<LoadContractConfig>d__1e:MoveNext() ContractConfigurator.ContractConfigurator:Update()

Would something like this cause it? UnityEngine.Debug:LogException(Exception)

Indeed. That sort of thing is on my list, you're quite right. I just wanted to deal with the missions actually working before I worried too much about things like grammar, accuracy & balancing. Edit: Might make more sense if I said the orbit was supposed to be MUCH higher in concept, in my head. 300K-500K

OK, see that I could've figured out. Here's the problem.

More info! Whee! (It's payday today, sorry for the long wait) Edit: Context: This is the mission in question. It's #2 on a "story" tree I'm trying to build out. It's supposed to be unlocked immediately on completing the prior mission. AGENT { name = Kerbal Space Agency (KSA) description = We are the organization you're running. We built KSC. You run us. logoURL = logoScaledURL = } CONTRACT_TYPE { name = ExodusFirstStation title = Exodus Plan -- Your First Space Station group = ExodusStory description = [KSA Tracking Station Dept.] Administrator - We have a plan. We're calling it "The Exodus Plan." Unfortunately that space rock we had you confirm for us is too large and too dense for us to redirect or destroy. So we had to start thinking out of the box. All of us are going to live in space. First, we need a space station & colony in orbit of Kerbin. This station will act as both a proof of concept and a mission setup point, so that we can send up the individual assemblies for later missions individually. We'll start with a basic station but we'll be sending you missions over time both to resupply it and to improve it's self-sufficicency. synopsis = Put a space station into high orbit (100,000km) of Kerbin. It needs to be sef-sustaining and to have at least 3 unused docking ports, and a permanent crew of 1 pilot, 1 scientist, and 1 engineer. It also needs a sufficient electrical system for it's chosen orbit, and a Nom-O-Matic, with at least 100 days worth of supplies. completedMessage = Thank you, Administrator. The people's hope lies in you from this point on. agent = Kerbal Space Agency (KSA) cancellable = false declinable = false deadline = 0 autoAccept = false targetBody = Kerbin maxCompletions = 1 maxSimultaneous = 1 rewardScience = 50.0 rewardReputation = 50.0 rewardFunds = 100000.0 failureReputation = 30.0 failureFunds = 50000.0 advanceFunds = 50000.0 PARAMETER { name = All type = A11 PARAMETER { name = Param1 type = Orbit targetBody = Kerbin situation = ORBITING minAltitude = 100000 } PARAMETER { name = Nom-O-Matic type = PartValidation part = Nom-O-Matic 5000 Greenhouse part = Nom-O-Matic 25000 Greenhouse minCount = 1 } PARAMETER { name = DockingPorts type = PartValidation part = Clamp-O-Tron Jr. part = Clamp-O-Tron Docking Port part = Clamp-O-Tron Shielded Docking Port part = Clamp-O-Tron Sr. Docking Port part = Inline Clamp-O-Tron part = Mk2 Clamp-O-Tron minCount = 3 } PARAMETER { name = ElectricalGen type = PartValidation part = Gigantor XL Solar Array part = OX-4W 2x3 Photovoltaic Panels part = OX-4L 1x6 Photovoltaic Panels part = SP-W 2x3 Photovoltaic Panels part = SP-L 1x6 Photovoltaic Panels part = OX-STAT Photovoltaic Panels part = PB-NUK Radioisotope Thermoelectric Generator part = Fuel Cell part = Fuel Cell Array minCount = 2 } PARAMETER { name = InitialStationResource type = HasResource RESOURCE { resource = Supplies minQuantity = 2000 maxQuantity = 6000 } RESOURCE { resource = Mulch minQuantity = 2000 maxQuantity = 6000 } RESOURCE { resource = ElectricCharge minQuantity = 400 maxQuantity = 600 } } PARAMETER { name = PilotParam type = HasCrew trait = Pilot } PARAMETER { name = EngiParam type = HasCrew trait = Engineer } PARAMETER { name = ScienParam type = HasCrew trait = Scientist } PARAMETER { name = FullCrew type = HasCrew minCrew = 3 } REQUIREMENT { name = InitialOrbitComplete type = CompleteContract contractType = ExodusOrbitalContract minCount = 1 maxCount = 1 } } }

A bit of an oddity. So I'm trying to build out the Exodus Contract Pack (github), This is very early days yet, but I'm hoping for a playable release by the 1st of the month. However, I've run into a wall with Contract Configurator. My second "story mission" contract fails to load and I can find nothing whatsoever in eithr of the debug windows. The only place I find a reference to this otherwise silent failure is in the CC debug window, where up in the top left corner it says: "Successfully loaded one out of two contracts." What could cause this?

+1 in agreement here. It would certainly be useful to players of Exodus once Exodus is playable.

Hey, I'm in the US and Google Play won't show me the app, wtf's with that?

Alright! So I've made some little progress on the Exodus Contract Pack: 0.0.1 has been pushed to Github. So has 0.0.1.5 because I forget an important progression clause in the Kerbin Station mission. It's entirely untested, but I've rewritten the initial Kerbin Station mission to be a more reasonable open-loop system at first. I believe that both the original mission and the initial mission should be completeable at this time. I will be attempting to test this for the next little while. We'll see what happens.

Fair enough! I say "modpack" because that's how I intend it to be played. The contract pack and/or any mods I write for this will make little sense without the modlist, assuming that it won't just crash KSP by referencing stuff that isn't there. You can't think of any way of doing this?

I'd prefer if you read the whole thing before guessing that I'm going to do something, that I did talk about. And I plan to ( assuming it doesn't go belly up in the meantime ) suggest that the player uses CKAN. It's simplest for everyone involved in such a project.