Vehicle Meta Editor changes vehicle data in vehicles.meta. Run Scanner first.

Select a vehicle

1. Open Meta.
2. Search by model name or brand.
3. Select a vehicle in the left panel.
4. Check the active vehicles.meta path above the form before saving, especially when multiple resources use similar spawn names.

Visual Mode field groups

Group	Fields	General purpose
Identity	Model Name, TXD Name, Game Name, Brand/Make, Handling ID	Model identity, texture dictionary, display label, and handling link
Audio	Audio Name Hash	Built-in or custom engine sound name
Classification	Vehicle Class, Vehicle Type, Plate Type, Dashboard, Wheel Type, Swankness	GTA V behavior and visual presets
Wheels & Scale	Wheel Scale, Wheel Scale Rear, Steer Wheel Mult	Front/rear wheel scale and steering-wheel animation multiplier
Health & Physics	Body Health, Frequency, Max Number, Damage Map Scale, Damage Offset Scale	Durability, population settings, and damage behavior
Visual	Dirt Level Min/Max, HD Texture Dist	Dirt range and HD texture distance
Flags	FLAG_* checkboxes	Active flags joined into a space-separated string

The dropdowns expose values known to the application. Use Code Mode for elements that are not represented by the visual form.

Save and Revert

• Save updates supported fields on the <Item> identified by the target modelName.
• The application creates vehicles.meta.bak before writing.
• Revert resets the form to the last loaded/saved data. It does not restore the .bak file or undo data already written to disk.
• After saving, the application's in-memory vehicle data is updated.

Changing Model Name in Visual Mode is risky. A complete spawn-name change also requires renaming stream files and other references. Use Vehicle Renamer for that operation.

Code Mode

Code Mode opens the complete vehicles.meta file in an XML editor with line numbers, line wrapping, and two-space indentation.

1. Click Code Mode.
2. Edit the XML.
3. Click Save Code.
4. Run Scanner again and test the resource.

Save Code replaces the entire file exactly as shown and does not create an automatic backup or validate XML. Returning to Visual Mode before Save Code discards unsaved code changes.

Verification

• Compare the new file with .bak.
• Confirm that each tag remains inside the intended vehicle <Item>.
• Ensure handlingId exactly matches handlingName.
• Ensure txdName and modelName match the streamed assets.
• Restart the resource and spawn the vehicle on a development server.