Scanner is the foundation of the application. Its resource and vehicle results are held in memory for the current application session and are used by the other editors.

Add workspace folders

1. Open Scanner.
2. Click Add Folder and choose a parent folder containing one or more resources.
3. Repeat to add multiple root folders. The same path cannot be added twice.
4. Remove an active folder with the cross button when it is not needed.
5. Click an item under Recent Folders to add it again. The application stores up to five recent folders locally.
6. Click Scan Workspace.

Selecting a folder does not read its files immediately. Scanning starts only after Scan Workspace is clicked.

How a resource is detected

• A folder is treated as a resource when it contains fxmanifest.lua or __resource.lua.
• Root discovery is limited to six levels (depth 0 through 5).
• Hidden folders whose names begin with a dot are skipped.
• After a manifest is found, that folder is processed as one resource. Nested resource folders below it are not independently discovered.
• A resource appears in results only when it has parsed vehicles or supported stream files.
• All .meta files inside a resource are searched recursively.
• Recorded stream extensions are .yft, .ytd, .ydr, .ycd, .ybn, and .ymap.
• The presence of audioconfig or sfx marks the resource as containing audio.

Vehicle data read by Scanner

Scanner reads each direct <Item> inside <InitDatas> in vehicles.meta. Extracted fields include model/spawn name, TXD, handling ID, game name, brand, audio hash, class/type, plate/dashboard/wheel type, flags, scale, health, damage, visual settings, camera settings, and LOD distances.

If one resource contains the same model name more than once, only the first item is added for that resource. Duplicate names across separate resources remain visible and will later be rejected by Merger.

Results and navigation

• The status bar shows the resource and vehicle totals.
• Search matches model name, brand, game name, and audio hash.
• The class filter uses vehicleClass from vehicles.meta.
• Click a vehicle card to open it directly in Meta Editor.
• Manage Workspace returns to the folder list. Existing results remain in memory until a new scan replaces them.

When to rescan

Rescan after adding or deleting files/resources, changing a spawn name, creating split/merge output, or modifying metadata outside the application. A Visual Meta save updates in-memory vehicle data, but structural and Code Mode changes should always be confirmed with a fresh scan.

Empty scan results

Check that the manifest is at each resource root, the filename is exactly vehicles.meta, the XML contains <InitDatas>, and the resource is not beyond the discovery depth. A stream-only resource can be detected without producing a vehicle card because it has no vehicles.meta entry.