Documentation

Carcols & Carvariations

How emergency lighting kits and livery slots are wired together.

These two files work together to define how your vehicle looks and lights up in-game.

carcols.meta — Kit structure

<Item type="CVehicleModelInfoVarGlobal__Lights">
  <id value="1234" />
  <Kit>
    <id value="1234" />
    <name>my_vehicle_siren</name>
    <lightSettings>
      <!-- Each entry: position, color sequence, flash pattern -->
    </lightSettings>
  </Kit>
</Item>

The kit ID must match the one referenced in vehicles.meta — or use Easy Meta to wire them automatically.

carvariations.meta — Livery entry

<Item>
  <modelName>my_vehicle</modelName>
  <variationData>
    <Item>
      <liveries0>
        <Item>my_vehicle_livery1</Item>
        <Item>my_vehicle_livery2</Item>
      </liveries0>
    </Item>
  </variationData>
</Item>

Each string in liveries0 is the name of a texture inside the vehicle's YTD. They must match exactly (case-sensitive).

Livery texture names in carvariations.meta are case-sensitive and must exactly match the texture names inside the YTD. A mismatch causes the livery slot to appear blank in-game.

Open Easy Meta and start building

Frequently asked questions

What's the difference between carcols.meta and carvariations.meta?

carcols.meta defines siren/light kits and mod kits; carvariations.meta assigns liveries and links a vehicle to a kit by ID. The kit ID must match between the two files.

Why is my livery slot blank in-game?

Livery names in carvariations.meta are case-sensitive and must exactly match the texture names inside the vehicle's YTD. A single mismatch makes that slot render blank.

How do I link a siren kit to my vehicle?

The kit ID in carcols.meta must equal the one referenced in vehicles.meta and carvariations.meta. Easy Meta wires these IDs together automatically so they can't drift out of sync.

Discussion