ships.Interface.ParsedSlot - Elite-Dangerous-Almanac/Almanac-Core GitHub Wiki
@elite-dangerous-almanac/core / ships / ParsedSlot
Defined in: src/ships/slots.ts:348
What a journal slot key says about the mount, as parseSlotName reads it.
readonlyoptionalcore?:CoreSlotType
Defined in: src/ships/slots.ts:371
For a core key, the core function it fills (MainEngines → thrusters).
readonlykind:SlotKind
Defined in: src/ships/slots.ts:350
Which kind of mount the key names.
readonlyoptionalrestriction?:SlotRestriction
Defined in: src/ships/slots.ts:369
The restriction the key implies (Military01 → military,
LargeMiningHardpoint1 → mining). Frontier gives every restricted mount its
own journal name, so a key alone is enough to tell.
readonlysize:number|null
Defined in: src/ships/slots.ts:363
Slot size (class), 1–8, or null when the key does not encode one and the mount
has one to encode (Radar, Military01, Cargo01, …) — the hull's layout
carries the size instead.
null is not the only "no size here" answer. A mount whose fit rules are not
size-based reads 0 rather than null — TinyHardpoint1 and Armour both do,
matching the size on a BuildSlot — and CargoHatch reads 1. So test
parsed.size for falsiness, or against the ParsedSlot.kind you expect;
=== null alone treats a utility mount as a sized slot.