From a32f047b7f8dcf93526a934b822d7e9502e4ba59 Mon Sep 17 00:00:00 2001 From: Athanasius Date: Mon, 1 Nov 2021 15:58:35 +0000 Subject: [PATCH] schemas: README: outfitting-specific elisions in that file already --- schemas/README-EDDN-schemas.md | 9 --------- 1 file changed, 9 deletions(-) diff --git a/schemas/README-EDDN-schemas.md b/schemas/README-EDDN-schemas.md index a86e1b5..a986f5f 100644 --- a/schemas/README-EDDN-schemas.md +++ b/schemas/README-EDDN-schemas.md @@ -180,15 +180,6 @@ the local map. To that end, uploading applications MUST ensure that messages do not contain any Cmdr-specific data (other than "uploaderID" and the "horizons" flag). In practice as of E:D 3.3 this means: -* outfitting: Skip items whose availability depends on the Cmdr's status rather - than on the station. Namely: - - Items that aren't weapons/utilities (`Hpt_*`), standard/internal - modules (`Int_*`) or armour (`*_Armour_*`) (i.e. bobbleheads, decals, - paintjobs and shipkits). - - Items that have a non-null `"sku"` property, unless - it's `"ELITE_HORIZONS_V_PLANETARY_LANDINGS"` (i.e. PowerPlay and tech - broker items). - - The `"Int_PlanetApproachSuite"` module (for historical reasons). * shipyard: *Include* ships listed in the `"unavailable_list"` property (i.e. available at this station, but not to this Cmdr). * journal: Strip out `"..._Localised"` properties throughout the data