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 explicitly because it doesn't affect the vehicle visually or physically.
Attributes
| Name | 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 /material/ui/accessory/ to the icon for the accessory, omitting the file extension. For example, icon: "truck_name/fancy_doodad" would point to /material/ui/accessory/truck_name/fancy_doodad.mat.
| |
| info | string_array | Additional information about the accessory. Few accessory types still use this for UI display (e.g. engine). | |
| price | s64 | The price of the accessory in the store in the base currency (ETS2 → EUR, ATS → 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. |
| suitable_for | string_array | Each array member specifies a unit name — or a pattern using wildcards (*) — which must be present on the vehicle for this accessory to become visible in the store and applicable to the vehicle. | |
| conflict_with | string_array | Each array member specifies a unit name — or a pattern using wildcards (*) — with which this accessory is incompatible. The conflicting accessories will be removed from the vehicle if this accessory is applied. | |
| defaults | string_array | 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. | |
| require | token_array | 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 require[]: mudflaps 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 foo.bar.mudflaps.
Note: Every required accessory type should always have a corresponding accessory of that type in defaults! |
Subclasses
- accessory_addon_data
- accessory_cabin_data
- accessory_cargo_data
- accessory_chassis_data
- accessory_engine_data
- accessory_head_lights_data
- accessory_hookup_data
- accessory_interior_data
- accessory_paint_job_data
- accessory_sound_data
- accessory_transmission_data
- accessory_truck_data
- accessory_rim_data
- accessory_wheel_data
Raw Unit Definition
"accessory_data":{
"superclass":"unit",
"attrs":{
"name":{
"type": "string"
},
"short_name":{
"type": "string"
},
"icon":{
"type": "string"
},
"info":{
"type": "string_array"
},
"price":{
"type": "s64"
},
"unlock":{
"type": "uint"
},
"suitable_for":{
"type": "string_array"
},
"conflict_with":{
"type": "string_array"
},
"defaults":{
"type": "string_array"
},
"require":{
"type": "token_array"
}
}
},