How to name your part: Difference between revisions

From Kerbal Space Program 2 Modding Wiki
Jump to navigation Jump to search
No edit summary
m typos again
 
(One intermediate revision by one other user not shown)
Line 1: Line 1:
Stock part names somewhat follow the following pattern : <code><type>_<size>_<feature>_<resource>_<cardinal>_<name></code>
Stock part names somewhat follow the following pattern : <code><type>_<size>_<feature>_<resource>_<cardinal>_<name></code>


You should always prepend the mod name/mod ID to the part name : <code><modId>_type>_<size>_<feature>_<resource>_<cardinal>_<name></code>
You should always prepend the mod name/mod ID to the part name : <code><modId>_<type>_<size>_<feature>_<resource>_<cardinal>_<name></code>


== Type ==
== Type ==
Line 18: Line 18:


== Feature ==
== Feature ==
Optionnal.
Optional.


The feature can be anything needed to distinguish this part from a similar part. It usually has to do with the form factor.
The feature can be anything needed to distinguish this part from a similar part. It usually has to do with the form factor.
Line 25: Line 25:


== Resource ==
== Resource ==
Optionnal.
Optional.


This is meant for part that can contain a resource, like engines and fuel tanks.
This is meant for part that can contain a resource, like engines and fuel tanks.
Line 32: Line 32:


== Cardinal ==
== Cardinal ==
Optionnal.
Optional.


Useful for distinguishing same-size parts that exists in different heights, like fuel tanks.
Useful for distinguishing same-size parts that exists in different heights, like fuel tanks.
Line 39: Line 39:


== Name ==
== Name ==
Optionnal.
Optional.


You can add the part localized name at the end if it helps identifying it more easily.
You can add the part localized name at the end if it helps identifying it more easily.

Latest revision as of 12:02, 15 November 2025

Stock part names somewhat follow the following pattern : <type>_<size>_<feature>_<resource>_<cardinal>_<name>

You should always prepend the mod name/mod ID to the part name : <modId>_<type>_<size>_<feature>_<resource>_<cardinal>_<name>

Type

Mandatory.

Possible values: adapter, antenna, booster, cabin, cargobay, dockingport, engine, probe, etc.

Size

Mandatory.

From 0v (XS) to 5v (2X) but could go higher if need be.

See Sizes for a full list.

Possible values: 0v, 1v, 2v, etc.

Feature

Optional.

The feature can be anything needed to distinguish this part from a similar part. It usually has to do with the form factor.

Possible values: radial, inline, conical, dish, triangle, etc.

Resource

Optional.

This is meant for part that can contain a resource, like engines and fuel tanks.

Possible values: methalox, hydrogen, solid, crew, electricity, xenon

Cardinal

Optional.

Useful for distinguishing same-size parts that exists in different heights, like fuel tanks.

Possible values: 1x1, 1x2, 1x3, 2x3, 3x2, etc.

Name

Optional.

You can add the part localized name at the end if it helps identifying it more easily.

Example: engine_1v_methalox_terrier

Examples of stock part names

  • adapter_2v_conical_methalox_1v-2v
  • antenna_1v_dish_hg55
  • booster_1v_solid_kickback
  • cabin_2v_crew_hitchhiker
  • cargobay_3v_m3_1x2
  • collector_0v_science_radiation
  • decoupler_2v_inline
  • dockingport_1v_inline_sideport
  • engine_1v_methalox_terrier
  • fairing_1v_procedural
  • fueltank_1v_inline_methalox_1x4
  • heatshield_1v
  • panel_1v_triangle_right
  • probe_1v_hexagonal_electricity
  • solararray_1v_1x6