Caerfinon

But as @linuxgurugamer says "there's a lot to do" and there is a lot to see in airplanes. It's not the destination its the journey

Airstrips Current Status: v1.0.0 released on Spacedock - https://spacedock.info/mod/2685/Kerbin Side Remastered Gap Extras KSR GAP status: v2.0.5 released on Spacedock - https://spacedock.info/mod/2573/Kerbin Side Remastered GAP

if you enable Advanced Tweakables in settings then you get an option on parts to remove them from staging.

Have you enabled "Allow other Launchsites" in the Difficulty Settings for the career game?

Looks like the start of a GSP mod... Give Seas Purpose! Hmmmmmm.

I like the winch and cable tether for Bill.

Airstrips Current Status: Have play tested all 20 Airstrips and verified that the navigation tool data is working for all of them Should have the package released tomorrow or Friday. KSR GAP status: Took another crack at writing a flight plan for Baikerbanur ILS 20. This one is a little different in that it starts from the east, flies in low over the mountains and turns sharply to the left. Best have a small maneuverable craft for this one. Not recommenced for the large commercial aircraft. Val and Bill died a few times in testing

Data from a group config is accessed by @[groupname]:[variable] in an expression. In your example if your group name was "MyGroup" your variable in a contract would be @MyGroup:fundModifier. Group data is good for static values that do not change that can be shared with all contracts offered by the group. The $fundModifier is a variable in the persistent data store that you are referencing in your contract. If not previously set, the default value of 0 is set for numbers and whatever the default value is for other data types like strings etc. Your initial contract should set values in the data store to what you want. In the example below I set the value I want in my first contract in a series when the contract is offered. Subsequent contracts can then read this value and then update it on success of failure. It is a good idea to prepend some kind of mod identifier on your persistent data store variables (I use "ksrgap") because it is accessible by all contracts from any pack. If some other mod uses "fundModifier" it will interfere with yours. // Persistent Storage routines BEHAVIOUR { name = Expression type = Expression CONTRACT_OFFERED { type = int ksrgapFlightProgress = -2 } // On success set the progress counter CONTRACT_COMPLETED_SUCCESS { type = int ksrgapFlightProgress = $ksrgapFlightProgress + 1 } } You can see the contents of the persistent data store in your games save persistent.sfs file. Open it with a text editor and search for Persistent Data Store and you can see all the values that are set there.

The best kind!

Might just be AWESOME! Good hunting. Fly safe.

Well yours is certainly a much needed role in this game. Those pesky Kraken get into everything! Welcome to the forums. Fly safe.

Airstrips Current Status: The navigation patches are completed and I'm now play-testing approaches and landings at each new site. KSR GAP status: Always bugged me that there wasn't a runway 27 flight plan for the Island Airport, So I've added it for the next release.

I'd have to see the contract code. Generally I find that Vessel parameter groups can break if they are satisfied by more than one vessel at a time (this is also the cause of several contracts failing at the same time.) Yes, you can use "Expression-Behaviour" to set variables in the persistent datastore in your game save file. Once set the variables can be called from any other contract. See data-store-identifiers Also, you can use Expression-Requirement to use the stored variables as requirements for a contract to start. The general order is; Requirements define when a contract will be offered. Behaviours determine things that will occur and placement of spawned items for an offered contract Parameters need to be met and completed to progress the mission, trigger some behaviours etc. The best way to learn how contract configurator works is by deconstructing contracts written by others that do something similar to what you want to do. I learned a great deal from Contract Pack: Field Research by nightengale and Career Evolution by pap1723 .

This is the way.

Glad it got sorted out. Fly Safe.

Not necessary, Just select the probe cores individually with the rotate tool and turn them until the logos on the side all face the same way.

Have you tried orienting all of the probe cores in the same direction? Currently they face outward from each direction of the craft. I experienced similar issues until I oriented them all the same way.

Ah, yes. Those ones are mine, not in the original GAP packs. I'll see what I can do.

@Coyote21 have you tried JNSQ GAP? It already has flights to some of the JNSQ bases.

the new v2 code is fairly adaptable to making the port. I will give some thought to installing a JNSQ sandbox and see how feasible it would be.

the bases need to be "opened" to launch vessels from there or store vessels inside hangers located there. If not using this feature or the business/research features of other bases, there isn't really a point to opening them. The contract pack does not require the bases to be opened to use. I don't really use the built in feature. The contract pack has support for the NavUtil mod which I find to be a more useful navigation tool.

Hiya. Welcome. Fly safe

I like the early game airplane focus.

Generally requirements must be met for a contract to be offered at all. Typically it it the success or failure of parameters that govern if the contract fails or not, and parameters can be classified as optional so that their success of failure doesn't effect the contract success of failure but can offer additional rewards. I'm not sure. I would experiment by coding one up and seeing what happens,

You can set a "VesselNotDestroyed Parameter" that checks to see if a vessel defined by a "vessel parameter" has been destroyed. If it has been the contract will fail. As with all parameters you can set penalties using "failureFunds"