EliteDangerousAlmanac / Ships / ModuleEngineering

Defined in: dotnet/src/EliteDangerousAlmanac/Ships/SlefRecords.cs:39

The durable modification applied to one module.

A journal capture may also name the engineer, the engineer's identifier and the numeric blueprint identifier. They are deliberately outside this shape: the engineer fields record who applied a modification, and the numeric identifier repeats BlueprintName. None of them changes the fitted module.

new ModuleEngineering(BlueprintName, Level, Quality)

string

The blueprint's journal name, such as FSD_LongRange. It names a craftable recipe or a fixed pre-engineered identity such as a grade-five festive launcher.

int

The blueprint grade, 1 through 5.

double

The roll quality, 0 through 1.

BlueprintName: string

The blueprint's journal name, such as FSD_LongRange. It names a craftable recipe or a fixed pre-engineered identity such as a grade-five festive launcher.

ExperimentalEffect: string?

Defined in: dotnet/src/EliteDangerousAlmanac/Ships/SlefRecords.cs:46

The experimental effect's journal name, when one is applied.

ExperimentalEffectLocalised: string?

Defined in: dotnet/src/EliteDangerousAlmanac/Ships/SlefRecords.cs:50

The experimental effect's display name, when the source states one.

Level: int

The blueprint grade, 1 through 5.

Modifiers: IReadOnlyList<EngineeringModifier>?

Defined in: dotnet/src/EliteDangerousAlmanac/Ships/SlefRecords.cs:60

Every stat this engineering changed, or null when none are stated.

A journal Loadout event always writes the list, but SLEF requires only the blueprint name, the grade and the quality, and the specification's own example omits it. A parser that demands the list cannot read the format it implements. Absent means "not stated" rather than "changed nothing", so an export never invents an empty list.

Quality: double

The roll quality, 0 through 1.