Guest User

Missile Launch Mission

a guest
Nov 1st, 2017
80
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 6.84 KB | None | 0 0
  1. CONTRACT_TYPE
  2. {
  3. // Unique name of the contract type (required)
  4. name = Missile Test
  5.  
  6. // The title of the contract, which is displayed in Mission Control
  7. // Required: Yes
  8. //
  9. title = Missile Test
  10.  
  11. // Generic version of the contract title
  12. // Required: Yes (unless can be defauled from title).
  13. //
  14. genericTitle = Missile Test
  15.  
  16. // Reference to a CONTRACT_GROUP node which supplies additional rules
  17. // for limiting the number of contracts within a given group.
  18. group = Twitchi Tech Group
  19.  
  20. // Two options for specifying the description:
  21. // 1) Supply the full text here in the description field
  22. //description = A more detailed description of the contract.
  23.  
  24. // 2) Supply the following fields, which will be fed into the text
  25. // generator. Use of the CoherentContracts mod is highly
  26. // recommended, as it generates far more meaningful text.
  27. topic = Missile // Topic of the contract. Should be a
  28. // singular noun.
  29. subject = Kerbal // Subject of the contract. See
  30. // CoherentContracts for some possible
  31. // values. Includes stuff like Kerbal,
  32. // Experiment, Parts, Mun, MunSrf, etc.
  33. motivation = test // Motivation for why we are doing the
  34. // contract. See CoherentContracts for
  35. // some possible values. Some values
  36. // used are: flags, test, rescue.
  37.  
  38. // Generic version of the contract description that is displayed in
  39. // Mission Control when no contract is currently generated. This
  40. // defaults to the description, but only if it is deterministic (ie.
  41. // the value can be determined at parse time).
  42. //
  43. // Type: <a href="String-Type">string</a>
  44. // Required: Yes (unless can be defauled from description).
  45. //
  46. genericDescription = Hey Buddy.. Wanna launch a missile Test?
  47.  
  48.  
  49. // The contract synopsis appears in bold. Give a quick summary of the
  50. // contract objective.
  51. synopsis = We want you to launch a missile.
  52.  
  53. // The completedMessage is the message that is displayed when the
  54. // contract completes.
  55. completedMessage = Missile Flown, Data Stored
  56.  
  57. // Agent (agency). If not populated, the agent from the contract group
  58. // will be used. If there is no group or no agent on the group, a
  59. // random agent will be selected.
  60. agent = Twitchi Technologies
  61.  
  62. // Contract min/max expiry in days. If both are set to 0.0, it will
  63. // result in a contract that never expires.
  64. // Default = 5.0 and 100.0 days, respectively
  65. minExpiry = 5.0
  66. maxExpiry = 100.0
  67.  
  68. // Contract deadline in days. Default is no deadline.
  69. deadline = 0
  70.  
  71. // Controls for whether a contract can be declined or cancelled, default
  72. // is true for both
  73. cancellable = true
  74. declinable = true
  75.  
  76. // When set to true, this contract is automatically accepted when
  77. // offered. Use it to make a contract like the stock World-Firsts
  78. // Record contracts.
  79. // Default = false
  80. autoAccept = false
  81.  
  82. // Prestige. If not specified, this contract type will be available at
  83. // any prestige level. Otherwise, locked to the level specified. Can
  84. // be specified multiple times.
  85. // Values from Contract.ContractPrestige:
  86. // Trivial
  87. // Significant
  88. // Exceptional
  89. prestige = Significant
  90.  
  91. // Target Celestial body - controls where the contract must be
  92. // completed, has some automated effects on numeric values (increasing
  93. // science, etc.). Also gets used in some of the parameter classes.
  94. //
  95. // Default = null (no celestial body)
  96. targetBody = Kerbin
  97.  
  98. // The maximum number of times this contract type can be completed (0
  99. // being unlimited).
  100. // Default = 0
  101. maxCompletions = 1
  102.  
  103. // The maximum instances of this contract that can be active at one
  104. // time.
  105. // Default = 4 (unless maxCompletions is set).
  106. maxSimultaneous = 1
  107.  
  108. // Contract rewards. Note that advanceFunds are automatically added to the
  109. // failureFunds.
  110. rewardScience = 20.0
  111. rewardReputation = 20.0
  112. rewardFunds = 100000.0
  113. failureReputation = 10.0
  114. failureFunds = 10000.0
  115. advanceFunds = 1000.0
  116.  
  117. // The weight is used in the contract generation process. Each contract
  118. // type that is available to be offered is added to a weighted list.
  119. // Contract types with a higher value are more likely to be chosen.
  120. // Note that the weight is applied per contract group.
  121. //
  122. // Default = 1.0
  123. weight = 10.0
  124.  
  125. // The DATA node is a special node that is not used by contracts
  126. // or parameters directly, but provide storage for generic values
  127. // that can be used as part of expressions.
  128. DATA
  129. {
  130.  
  131. }
  132.  
  133. // The PARAMETER node defines a contract parameter. The following
  134. // shows an example parameter. See the Parameters page for examples of
  135. // all supported parameters.
  136. PARAMETER
  137. {
  138. name = ReachState1
  139.  
  140. // The type defines the type of Parameter. See the Parameters page
  141. // for a list of all supported Contract Configurator parameters.
  142. type = ReachState
  143.  
  144. // This is a parameter specific to the ReachState parameter type.
  145. // Each parameter type can have include its own custom fields.
  146. minAltitude = 45000
  147. }
  148.  
  149. // The REQUIREMENT node defines a contract requirement - a prerequisite
  150.  
  151. REQUIREMENT
  152. {
  153. name = ReachSpace1
  154. type = ReachSpace
  155. invertRequirement = true
  156. }
  157.  
  158. // The BEHAVIOUR node adds additional special contract level behaviour.
  159. // See the Behaviours page for examples of all supported behaviours.
  160. BEHAVIOUR
  161. {
  162. name = ExperimentalPart
  163. type = ExperimentalPart
  164.  
  165. // The name of the part to add/remove.
  166. //
  167. // Type: AvailablePart
  168. // Required: Yes (multiples allowed)
  169. //
  170. part = largeSolarPanel
  171.  
  172.  
  173. // When (or if) the part should be added as an experimental part.
  174. //
  175. // Type: ExperimentalPart.UnlockCriteria
  176. // Required: No (defaulted)
  177. // Values:
  178. // DO_NOT_UNLOCK
  179. // CONTRACT_ACCEPTANCE (default)
  180. // CONTRACT_COMPLETION
  181. // PARAMETER_COMPLETION
  182. //
  183. unlockCriteria = CONTRACT_ACCEPTANCE
  184.  
  185.  
  186. // When (or if) the part should be removed as an experimental part.
  187. //
  188. // Type: ExperimentalPart.LockCriteria
  189. // Required: No (defaulted)
  190. // Values:
  191. // DO_NOT_LOCK
  192. // CONTRACT_ACCEPTANCE
  193. // CONTRACT_COMPLETION (default)
  194. // PARAMETER_COMPLETION
  195. //
  196. lockCriteria = CONTRACT_COMPLETION
  197.  
  198.  
  199. }
  200. }
Add Comment
Please, Sign In to add comment