How to name your part

Overview

Stock part names follow this pattern (where some sections only make sense in some contexts): <type>_<size>_<feature>_<resource>_<cardinal>_<name>.

You should always prepend the name of your mod to the name of your part: <modId>_<type>_<size>_<feature>_<resource>_<cardinal>_<name>.

As an example: mybigenginemod_engine_4v_methalox_bigboom would be a good name for an XL methalox engine called “Big Boom” in a mod called “My Big Engine Mod”.

Name sections

Section

Mandatory

Description

Possible values

Mod ID

✅

The ID of your mod in order to prevent conflicts with other mods’ similarly named parts

ModID from your swinfo.json

Type

✅

The category/type of your part

adapter, dockingport, engine, probe, etc.

Size

✅

See Sizes for a full list.

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.

radial, inline, conical, dish, triangle, etc.

Resource

Optional

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

methalox, hydrogen, solid, crew, etc.

Cardinal

Optional

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

1x1, 1x2, 1x3, 2x3, 3x2, etc.

Name

Optional

You can add the part localized name at the end to help identify it more easily.

terrier, swivel, etc.

Examples of stock 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