@elite-dangerous-almanac/core / ships / BuildSlotBase

Defined in: src/ships/slots.ts:167

The stable identity and size shared by every hull mount.

Use BuildSlot when the mount kind and its narrowed core or restriction field matter. This base is useful for consumers that only display or persist a slot key and size.

• CoreBuildSlot
• HardpointBuildSlot
• OptionalBuildSlot
• SimpleBuildSlot

readonly key: string

Defined in: src/ships/slots.ts:191

Stable, journal-compatible slot key, e.g. "PowerPlant", "HugeHardpoint1", "TinyHardpoint2", "Slot01_Size6", "Military01", "PlanetaryApproachSuite", and on a restricted mount "LargeMiningHardpoint1", "Cargo01", "LimpetController01", "FighterBay01", "Passenger01".

This is the string every slotKey argument takes. It is matched case-insensitively and otherwise exactly — no surrounding whitespace, no abbreviation — because a SLEF producer may lower-case the game's own identifier, as the specification's own example does. Enumerate keys with ShipLoadout.slots() rather than typing them. Note a core BuildSlot's core function name is a different string (thrusters vs the key MainEngines); see CoreSlotType.

Do not compute one. The numbering looks regular and on some hulls is not: the Anaconda's smallest optionals are Slot13_Size2 and Slot14_Size1 with no slots 11 or 12, the Type-9 Heavy starts at Slot00_Size8, the Type-7 Transporter uses the number 09 twice, and the Keelback's Slot03_Size3 sits on a size-4 mount. Such a mount carries its own name; see enumerateSlots.

---

readonly size: number

Defined in: src/ships/slots.ts:197

Slot size (class). Core/optional/hardpoint slots are 1–8; utility and armour use 0 placeholders because their fit rules are not size-based, while the fixed cargo hatch uses 1.