Documentation

Spawn Code Finder

List every vehicle spawn code in a resources folder, with exports.

The Spawn Code Finder reads a pile of vehicle packs and gives you one searchable index of their spawn codes. It needs a free Workshop account (no paid plan) and runs in your browser.

How to use it

1Click Pick a folder for a resource or your whole resources/ folder, or Pick zips for archives. You can also drag them onto the drop zone. No files handy: load a sample pack.
2Check the totals: resources, spawn codes, codes from vehicles.meta, guessed, duplicated across packs, and packs with no codes.
3Use the search box to find a code or a resource, and read each pack's caveats under its heading.
4Export what you need from the buttons above the results.

Inputs and output

In: a folder, or zip archives. Text files are opened up to 4 MB each; binary assets are only counted by name and size.
Out: spawn-codes.txt, spawn-codes.csv, vehicles.lua, and a QBCore qb-shared-vehicles.lua.

Look at the Duplicated across packs figure first. Two packs that claim the same code is the finding you would otherwise only discover in game.

The full reference is on the tool page.

Open Spawn Code Finder and start building

Frequently asked questions

What does 'Guessed' mean in the totals?

The code came from a file name rather than from a vehicles.meta entry. Treat guessed codes as leads to check, and the From vehicles.meta count as the reliable one.

Which export do I want?

Copy list (.txt) downloads a plain-text list, Spreadsheet gives CSV, and the two Lua buttons produce a vehicles.lua and a QBCore shared/vehicles.lua you can paste into a framework.

A pack shows zero codes. Is that a bug?

Every pack dropped gets its own heading, including empty ones, with the reason printed under it. Names the tool set aside are listed in the Seen and not listed section, each with an Add to the list button. Rows you add move to the Restored by hand section, where Undo puts them back.

Discussion