Flawless.Customs

Flawless Developer Hub · Docs

Vehicle Resource Validator

How to run it, what it checks, and what it cannot tell you.

How to use it

  1. Open the validator.
  2. Pick a tab: Vehicle check for cars (free), or Resource check for any resource such as scripts, maps and MLOs (Premium, coming soon).
  3. Choose a resource folder (the one containing fxmanifest.lua), or a whole [category] folder to check every resource inside it.
  4. Read the report. Fix errors first, then decide which warnings apply to you.
  5. Optional: download or copy the report to share it when asking for help.

Your files stay on your computer. The page is blocked from sending data anywhere, and it never changes, renames or deletes files.

What it does not do

All 53 checks

Every finding in a report comes from this list. Each one states its limit, so you know what it proves and what it does not.

Errors (22)

Something is definitely missing or broken.

  • Too many files FILE_LIMIT

    Limit: The limit protects your browser; split large packs into smaller folders.

  • Unsafe file path skipped UNSAFE_INPUT_PATH

    Limit: Files whose paths leave the selected folder are ignored, never read.

  • No fxmanifest.lua MANIFEST_MISSING

    Limit: Only fxmanifest.lua and the legacy __resource.lua are recognised as manifests.

  • Manifest file name has capital letters MANIFEST_NAME_CASE

    Limit: Windows servers accept any letter case; Linux servers need the exact lowercase name.

  • Manifest syntax error MANIFEST_SYNTAX

    Limit: The manifest is read as text, never run. Some valid but unusual Lua may be reported here.

  • fx_version missing FX_VERSION_MISSING

    Limit: Checks presence only, not whether the version name is current.

  • Manifest path leaves the resource UNSAFE_MANIFEST_PATH

    Limit: Paths with ".." or drive letters are never followed.

  • Referenced file is missing FILE_NOT_FOUND

    Limit: Checks that the file exists, not that its contents are correct.

  • File is loaded but never sent to players DATA_FILE_NOT_IN_FILES

    Limit: Checks the manifest only; it cannot see what clients actually downloaded.

  • Broken .meta file META_XML_INVALID

    Limit: This reader is strict. The game is sometimes more forgiving, but fixing the XML is always safe.

  • .meta file contains a DOCTYPE META_DOCTYPE

    Limit: Refused for safety; GTA .meta files never need one.

  • File is loaded as the wrong type META_TYPE_MISMATCH

    Limit: Known for vehicle-related data_file types only.

  • Car entry has no name VEHICLE_NO_MODELNAME

    Limit: Checks vehicles.meta entries only.

  • Car defined twice DUPLICATE_MODEL

    Limit: Checks within this resource only, not across your whole server.

  • Car model file missing STREAM_MODEL_MISSING

    Limit: Checks that the model file exists. Damaged model files are reported separately; badly built ones are not detected.

  • Car weight is zero or negative HANDLING_MASS_INVALID

    Limit: Checks fMass only.

  • Tuning kit has no valid number KIT_NO_ID

    Limit: Checks carcols.meta kits in this resource.

  • Two tuning kits share a number DUPLICATE_KIT_ID

    Limit: Checks within this resource only. Clashes with kits in other resources are not detected.

  • Game file is empty ASSET_EMPTY

    Limit: Checks the file size only.

  • Not a GTA V game file ASSET_NOT_RSC7

    Limit: Checks the first 4 bytes. Files for other games or game editions are reported here too.

  • Game file is damaged or cut off ASSET_CORRUPT

    Limit: Proves the file unpacks fully. It cannot tell whether the model or textures inside look right.

  • Different cars share a tuning kit number CROSS_KIT_ID_CLASH

    Limit: Compares carcols.meta kits in the resources you selected together. Clashes with the game's own kits are not checked.

Warnings (27)

Often a problem, but sometimes intentional. The limit explains when it is safe to ignore.

  • File too large to read TEXT_TOO_LARGE

    Limit: Text files above the size limit are skipped, so checks that need them are incomplete.

  • Manifest may be one folder too deep MANIFEST_NESTED

    Limit: Based on folder layout only. Ignore it if you deliberately selected a parent folder.

  • Resource inside another resource RESOURCE_INSIDE_RESOURCE

    Limit: FiveM only looks for resources inside [category] folders, not inside other resources.

  • Legacy __resource.lua LEGACY_MANIFEST

    Limit: Legacy manifests still load today but are deprecated by Cfx.re.

  • Manifest has code this tool can't run MANIFEST_UNPARSED

    Limit: Variables, loops and functions are never executed, so files they add are not checked.

  • game / games missing GAMES_MISSING

    Limit: Checks presence only.

  • Manifest line finds no files PATTERN_NO_MATCH

    Limit: Harmless if you never had this file; a problem if you expected it to load.

  • Capital letters don't match (breaks on Linux) PATH_CASE_MISMATCH

    Limit: Works on Windows servers, fails on Linux servers.

  • .meta file is never loaded META_NOT_LOADED

    Limit: Only vehicle-related .meta types are flagged as problems.

  • Driving settings defined twice DUPLICATE_HANDLING

    Limit: Checks within this resource only, not across your whole server.

  • Car texture file missing STREAM_TXD_MISSING

    Limit: Checks the file name only. Shared texture dictionaries in other resources are not checked.

  • Game file in the wrong folder STREAM_OUTSIDE_FOLDER

    Limit: FiveM only auto-streams files inside a folder named "stream".

  • Driving settings come from elsewhere HANDLING_NOT_IN_RESOURCE

    Limit: Fine if it is a base-game handling name or comes from another resource; those are not checked.

  • Colour settings for a car that isn't here VARIATION_UNKNOWN_MODEL

    Limit: Fine if it intentionally changes a base-game vehicle.

  • Changes the game's own vehicles BASE_GAME_OVERRIDE

    Limit: Recognises the vehicles in the original game file only, not DLC vehicles. Fine if you meant to change them.

  • Typo in a car setting VEHICLE_FIELD_INVALID

    Limit: type, vehicleClass and plateType are checked against the full list; dashboardType and wheelType only for near-miss typos.

  • Driving setting is not a number HANDLING_VALUE_INVALID

    Limit: Checks that values are readable numbers, not whether they make the vehicle drive well.

  • Tuning kit type not recognised KIT_TYPE_INVALID

    Limit: Checks the MKT_ naming pattern only.

  • Tuning kit not found KIT_NOT_FOUND

    Limit: Fine if the kit is defined in another resource or is one of the game's own kits; only 0_default_modkit is recognised as built in.

  • Game file has an unexpected format version ASSET_VERSION_MISMATCH

    Limit: Checked for .yft, .ytd, .ydr and .ycd files only.

  • Oversized game file ASSET_OVERSIZED

    Limit: The 48 MiB level is community guidance for FiveM, not an official limit.

  • Heavy game file ASSET_HEAVY

    Limit: FiveM servers print their oversized-asset warning from about 16 MiB (seen in real server logs; not officially documented).

  • Same car in two resources CROSS_DUPLICATE_MODEL

    Limit: Compares the resources you selected together, not your whole server unless you select it all.

  • Same streamed file in two resources CROSS_DUPLICATE_STREAM

    Limit: Compares file names only. Identical files in two resources are reported too, as one is redundant.

  • Two resources share driving settings CROSS_DUPLICATE_HANDLING

    Limit: Compares handlingName values in the resources you selected together.

  • Needed resource not found CROSS_MISSING_DEPENDENCY

    Limit: Resource check only. Fine if the resource is elsewhere on your server; choose your whole resources folder to be sure.

  • Server secrets inside the resource SECRET_FILE

    Limit: Detects common setting names only. Values are never shown in the report.

Notes (4)

Worth knowing; does no harm.

  • Extra file that isn't used META_UNUSED

    Limit: Informational; unused files do no harm.

  • No high-detail model STREAM_HI_MISSING

    Limit: Optional: the vehicle still loads, but looks lower quality up close.

  • Escrow-protected files skipped ASSET_ESCROW

    Limit: These files are encrypted by FiveM's asset escrow. They are never decoded, so nothing inside them is checked.

  • Damage check skipped for a large selection ASSET_DEEP_SKIPPED

    Limit: Above 400 game files only headers are read. Check resources one at a time for the full damage check.