EliteDangerousAlmanac / Ships / BuildSlot

Defined in: dotnet/src/EliteDangerousAlmanac/Ships/BuildSlot.cs:28

One mount on a hull — its stable key, its kind and its size.

Kind decides which of the two optional fields carries a value. A core mount names its Core function and carries no restriction; a hardpoint or an optional internal may carry a Restriction and never names a core function; a utility, armour or cargo-hatch mount carries neither.

new BuildSlot(Key, Kind, Size, Core?, Restriction?)

string

The stable, journal-compatible slot key, such as PowerPlant, HugeHardpoint1, Slot01_Size6 or Military01. Every slot-key argument takes this string, matched without regard to case and otherwise exactly. Enumerate the keys rather than typing them: the numbering looks regular and on some hulls is not.

SlotKind

Which kind of mount this is.

int

The mount's class. Core, optional and hardpoint mounts are 1 to 8; a utility mount and the armour mount use 0, because their fit rules are not size-based; the cargo hatch uses 1.

CoreSlotType? = null

The core function this mount accepts, on a core mount only.

SlotRestriction? = null

The module family this mount requires, when it is restricted.

Core: CoreSlotType?

The core function this mount accepts, on a core mount only.

Key: string

The stable, journal-compatible slot key, such as PowerPlant, HugeHardpoint1, Slot01_Size6 or Military01. Every slot-key argument takes this string, matched without regard to case and otherwise exactly. Enumerate the keys rather than typing them: the numbering looks regular and on some hulls is not.

Kind: SlotKind

Which kind of mount this is.

Restriction: SlotRestriction?

The module family this mount requires, when it is restricted.

Size: int

The mount's class. Core, optional and hardpoint mounts are 1 to 8; a utility mount and the armour mount use 0, because their fit rules are not size-based; the cargo hatch uses 1.