This defines which tags are required for this livery to show up for a given Preset. This parameter lets you disable a livery if it is not compatible when a tag is missing. Multiple tags can be specified by separating them using a comma. Tags are defined in the attachment.cfg so, for example, if you have two attachments and want to use the livery on both, you would set the Tag.N in the attachment.cfg files, then list both the tags in this parameter:

required_tags = node_default, nose_cargo

Each editable_colour.N entry in the section is used to define a base colour and an optional material and fallback colour for the editable colour. Colours are indexed from 0 and should be incremented by 1 for each new colour that is added.

The colour hash map is comprised of the following multiple key:value pairs, separated by the # symbol:

editable_color.N = color:<R, G, B> #materials:<material_name>, <material_name>, ... #fallback:<fallback_index>

The colour value is defined using three values for the RGB components, and will be the default colour for the livery adaptive colour "slot" corresponding to the index. This key is the only required key in the hash map.

The material name given is a flightsim material to target with this colour, as defined in one of the livery glTF files. When giving the material name, it can be formatted in any one of the following ways depending on the requirements of the SimObject:

1. "<material_name>" - this simply looks for material_name in the exterior model (excluding attachments)
2. "<tag>:<material_name>" - this looks for material_name on all attachments with the given tag
3. "<material_name>@<alias>" - this looks for material_name on the attachment with the given alias
4. "no_material" - this can be used if there is no material assigned to the editable colour.

The fallback index that you give is the index of the editable_colour.N entry to use if there are not enough custom colors for the number of adaptative colors defined in the livery. If not included, the initial colour value will be used.

A full example of a single colour definition would be like this:

editable_color.0 = color: 158, 158, 158 #materials: "airframe:CustomColor_01_Base", "airframe:CustomColor_01_DoorTail"

Hash Map

label_key.0     = "Activity"
label_value.0     = "AAD"
label_key.1     = "Country"

This parameter can be used to create a list of dynamic parameters which will override any value created using the vcockpit_parameter.N or vpainting_parameter.N attachment parameters. The value for the parameter is a string, and within the string you give two pieces of data, separated by a comma:

1. "the parameter name,the parameter value"

Parameters indexed from 0 and should be incremented by 1 for each new parameter that is added. A full example of a single parameter definition would be like this:

param.0 = "exterior_registration_number_color,0x080808"

This parameter specifies for which career specialisations the livery is applicable. If the livery is applicable to multiple different specialisations, these can be added as a comma separated list, for example:

dressing_codes = "CAR-PSO, CAR-PLC, CAR-PCC, CAR-PVO"

The default value is an empty string "" which means the livery can be used in all careers.

List of strings

A single tag string to be associated with the livery. Tags are indexed from 0 and should be incremented by 1 for each new tag that is added, for example:

tag.0 = "fire_fighting"
tag.1 = "fire_fighting_livery_01"