Data:Example

Pages in the Data: namespace are reserved for storing JSON-formatted information on game entities such as parts and celestial bodies. They are accessed and implemented in articles via Template:Data. Subpages of this page provide populated examples of various parts as well as a blank example that lists every usable data set for an entity type.

Example subpages

Parts

• Blank part
• Engine
• Command module
• Parachute
• Science experiment

Celestial Bodies

• Celestial body

Data sets

A Data: page contains a wide variety of information relevant to its subject.

All Data: pages start with the Entity element which can be "part", "body", "node", et cetera. The following lists the data sets per entity type defined.

Parts

• Name: The name of the part as it appears in-game.
• Subtitle: The subtitle of the part as it appears in-game.
• File: The file name, including the extension, of the wiki thumbnail image for the part. Should not include apostrophe, spaces, or periods.
• Category: The part’s category, e.g. fuel tank, engine, or utility.
• Family: The part’s family, or subcategory, e.g. methalox, stabilizer, or battery.
• Mass: The mass of the part, in kg.
• Size: The size of the part, using the two-character tag per Size labels e.g. SM or LG.
• Max_temp: The highest temperature the part can withstand, in K.
• Imp_tol: The highest impact velocity the part can withstand, in m/s.
• Stores_research: If the part stores the results of science experiments, either true or false.
• Resources: What resource(s) can be contained by the part. Units are in t.
• Manufacturer: The in-game manufacturer of the part, e.g. Kerbodyne.
• Modules: Each part may have zero or more of the following part modules:
  • Command module
    • Crew_required: Minimum number of Kerbals the part needs to function.
  • Reaction wheel
    • Torque: How much pitch, roll, and yaw the part can induce, in kN.
    • Resources_required: How much electric charge the part needs to use this module, in /s.