View source for Documentation/Engine/Units/accessory data

The '''accessory_data''' unit class is the superclass for all ''accessory_*_data'' classes and defines basic UI attributes and compatibility/interactions between accessories. It is generally not used ''directly'' because it doesn't affect the vehicle visually or physically. Instead, more specialized subclasses have been derived from it to define specific accessory types. Basically, think of '''accessory_data''' as a template from which all ''accessory_*_data'' classes have been derived.

== Attributes ==
{|class="wikitable"
!Name
![[Documentation/Engine/Units#Attribute_types|Type]]
!Default Value
!Description
|-
|name
|string
|
|Full name of the accessory for UI display.
|-
|short_name
|string
|
|Condensed name of the accessory for UI display in contexts with limited space or where full names are otherwise ill-suited.
|-
|icon
|string
|
|Path relative to <code>/material/ui/accessory/</code> to the icon for the accessory, omitting the file extension. For example, <code>icon: "truck_name/fancy_doodad"</code> would point to <code>/material/ui/accessory/truck_name/fancy_doodad.mat</code>.
|-
|info
|array&lt;string&gt;
|
|Additional information about the accessory. Few accessory types still use this for UI display (e.g. engine).
|-
|price
|s64
|0
|The price of the accessory in the store in the base currency (ETS2 &rarr; EUR, ATS &rarr; USD). If zero, the accessory will not be visible to the player.
|-
|unlock
|uint
|0
|The minimum level the player must achieve before the accessory becomes available in the store.
|-
|part_type
|token
|<code>unknown</code>
|It defines icon and tooltip shown on accessory. Available values are <code>factory</code>, <code>aftermarket</code>, <code>licensed</code> or <code>unknown</code>. ''Added in 1.44.''
|-
|suitable_for
|array&lt;string&gt;
|
|Each array member specifies a unit name &mdash; or a pattern using wildcards (*) &mdash; which must be present on the vehicle for this accessory to become visible in the store and applicable to the vehicle.
|-
|conflict_with
|array&lt;string&gt;
|
|Each array member specifies a unit name &mdash; or a pattern using wildcards (*) &mdash; with which this accessory is incompatible. The conflicting accessories will be removed from the vehicle if this accessory is applied.
|-
|defaults
|array&lt;string&gt;
|
|Each array member specifies a path to an accessory definition file which is applied to the vehicle if no other suitable accessory of the same type exists on the vehicle.
|-
|overrides
|array&lt;string&gt;
|
|Each array member specifies a path to an accessory definition file which is applied to the vehicle, overriding other accessories of the same type if one already exists on the vehicle. This eliminates the need for suitable_for/defaults relationships in most cases (e.g. engine badges and sounds). ''Added in ETS 1.27/ATS 1.6.''
|-
|require
|array&lt;token&gt;
|
|Each array member specifies an accessory type that must exist on the vehicle while this accessory is installed. For example, if a truck has separate accessories for mudflaps and mudflap hangers, each hanger accessory might declare <code>require[]: mudflaps</code> to disallow a state where the truck has mudflap hangers but no mudflaps. The token is the final segment of each unit name, so matching accessories would have unit names like <code>foo.bar.mudflaps</code>.
{{Note|Every ''require''d accessory type should '''always''' have a corresponding accessory of that type in ''defaults''!}}
|}