Vehicle Entry Generator
Prepare a shared vehicle definition for your installed core.
Vehicle fields → qb-core/shared/vehicles.luaInputs
Results
qb-core shared/vehicles.lua entry
{
['model'] = 'sultan',
['name'] = 'Sultan',
['brand'] = 'Karin',
['price'] = 15000,
['category'] = 'sports',
['type'] = 'automobile',
['shop'] = 'pdm',
},Paste inside the local Vehicles array in qb-core/shared/vehicles.lua. Match the vehicle type and shop to your server, then perform a coordinated staging restart. Follow the vehicle integration guide.
Generate an entry for the local Vehicles array in the referenced qb-core/shared/vehicles.lua. This format includes the explicit model, vehicle type and shop fields consumed by the current source. It is not the older model-keyed configuration format.
Tuning guidance
This tool edits shared vehicle configuration only. It does not modify handling, install model files, create a dealership, grant keys or persist ownership. Choose a category, type and shop supported by your installed resources. Sample defaults are editable examples, not a recommended economy configuration.
For the complete process, follow Add custom vehicles to QBCore: asset validation → shared entry → dealership or job garage → keys and persistence.
Export & rollout
Paste the entry inside the existing local Vehicles = { ... } list, preserving its surrounding entries and the lookup-building loop. Do not paste it after the list or replace the whole file. Compare older forks before using this format.
Review the diff and perform a coordinated staging restart after changing shared core configuration. refresh rescans resources; it does not reload an already-running core's Lua table. Test selection, purchase, keys, storage and reconnect through your actual integrations before production deployment.
Source
QBCore vehicle definitions and numeric array loop at 9b3cddcc. Generated configuration is not executed by this website.