Elite Dangerous Journal Schemas

Cargo

When written: at startup, note this is now written slightly later in startup, after we have initialised missions, so we can detect if any cargo came from an abandoned delivery mission. The first Cargo event in the file will contain the full inventory, others just indicate a separate file has been written. The full data is now written to a separate file Cargo.json. A simple event (with no parameters) is written to the main journal file when the cargo file is updated.

Properties

Name Type Optional Description Examples
timestamp string No Timestamp in UTC, ISO 8601
  • 2022-09-11T22:00:45Z
  • 2022-09-12T08:54:21Z
  • 2022-09-12T08:54:24Z
event string No
  • Cargo
Vessel string No
  • Ship
  • SRV
Count integer No
  • 16
  • 0
  • 1
Inventory array Yes -
Name Type Optional Description Examples
Name string No
  • drones
  • metaalloys
  • bertrandite
Name_Localised string Yes
  • Limpet
  • Meta-Alloys
  • Guardian Relic
Count integer No
  • 16
  • 1
  • 5
Stolen integer No
  • 0
  • 1
  • 7
MissionID integer Yes
  • 811118045
  • 811114594
  • 893617620