Back
    GuidesGTA Knowledge · Fixing Modkit ID Conflicts
    Workshop Docs

    Contents

    GTA Knowledge
    GTA5 File FormatsVehicle Meta FilesFiveM Resource StructureEUP Clothing SystemLivery & Texture BasicsCarcols & Carvariations32 Siren ScriptFixing Modkit ID Conflicts

    Documentation

    Fixing Modkit ID Conflicts

    Why two cars share liveries in the mod shop, and how to fix it.

    A modkit defines the visual customisation options for a vehicle — bumpers, spoilers, wheels, livery slots, and so on. Every vehicle that uses mods must declare a kit in carcols.meta and reference the same kit number in carvariations.meta. When two vehicles on the same server share an identical modkit ID, one vehicle's parts will visually bleed onto the other in the mod shop.

    Symptoms of a modkit ID conflict

    • Another vehicle's spoilers or bumpers appear in your vehicle's mod shop.
    • Selecting a livery slot changes a completely different vehicle's appearance.
    • Extras toggle on the wrong car.
    • Tuning parts disappear or show 0 options in Los Santos Customs.

    How to fix it

    1. 1Open your vehicle's carcols.meta and find the <id value="..." /> inside the <Kit> block.
    2. 2Open your carvariations.meta and find the matching <kitNumber value="..." />.
    3. 3Pick a new unique number. Values above 500 are rarely used by vanilla vehicles and are a safe range. Avoid 0, 255, and 65535 (reserved by the engine).
    4. 4Update both files to the new ID — they must match exactly.
    5. 5If you're running multiple custom vehicles on the same server, make sure every vehicle uses a different kit ID. Keep a server-wide ID list to prevent future conflicts.
    6. 6Restart the resource and test in Los Santos Customs.

    Where to change the ID

    <!-- carcols.meta -->
    <Item type="CVehicleModelInfoVarGlobal">
      <id value="530" />          <!-- ← change this -->
      <Kit>
        <id value="530" />        <!-- ← and this (must match) -->
        <name>my_vehicle_mods</name>
        ...
      </Kit>
    </Item>
    <!-- carvariations.meta -->
    <Item>
      <modelName>my_vehicle</modelName>
      <variationData>
        <Item>
          <kitNumber value="530" />   <!-- ← must match carcols id -->
          ...
        </Item>
      </variationData>
    </Item>
    A common convention is to derive the kit ID from the vehicle's spawn name hash, or to simply assign incrementing IDs starting at 600 for all custom vehicles on the server and document them in a shared spreadsheet.
    Easy Meta handles kit ID assignment automatically when you generate meta files — just make sure you enter a unique kit ID in the form before exporting.
    Open Easy Meta and start building

    Frequently asked questions

    Why do two of my FiveM cars share liveries or parts?

    They've been given the same modkit ID. When two vehicles declare an identical kit ID, one car's bumpers, spoilers, or livery slots bleed onto the other in Los Santos Customs.

    How do I fix a modkit ID conflict?

    Change the <id> inside the <Kit> block in carcols.meta and the matching kitNumber in carvariations.meta to a new unique value (above 500 is safe), update both files identically, then restart the resource and test in LSC.

    What kit ID values are safe to use?

    Numbers above 500 are rarely used by vanilla vehicles. Avoid 0, 255, and 65535, which are reserved by the engine, and keep a server-wide list so every custom vehicle uses a different ID.

    How do I avoid modkit conflicts entirely?

    Assign a unique kit ID to every custom vehicle on the server — Easy Meta does this automatically when you generate meta files, so IDs stay unique across your fleet.

    Discussion

    Fixing Modkit ID Conflicts

    Previous32 Siren Script
    The Workshop logoThe Workshop

    The browser workspace for serious FiveM creators.

    Tools

    Paint BoothUV StudioBlinklabEasyMetaPackBenchCode SmithScript DocsEUP Viewer

    Legal

    Refund policyPrivacy policyTerms of serviceCancellation policy
    Built for creators who ship assets, resources, and servers.