One resource. Every car you add.
A vehicle resource whose fxmanifest is written once and never touched again. Adding a car is making a numbered folder and dropping your files in. It ships with a working car already installed, so the first thing you do is watch it spawn, not debug your own model against a folder you can't be sure about.
- New car is a new numbered folder, no manifest edits
- Ships with a complete working vehicle in slot 1
- Works on Enhanced and Legacy, any framework
Free, one step
Connect Discord and the download unlocks. This also adds you to the Trase.Dev server, which is where the support and updates live.
I only ever see your username and avatar. No email, no password, and you can leave the server whenever you want. Already in from another download? This unlocks straight away.
Everything that's in the folder
No mystery zip. Eleven files, listed in full, and it's the same template I use when I record.
The folder, already shaped right
- ›vehicle_template/
- ›fxmanifest.lua
- ›data/1/ › the meta files for car 1
- ›stream/1/ › the model files for car 1
- ›Car 2 is a folder called 2. That's the whole system.
fxmanifest.lua, written once and never again
- ›Every data_file globbed as data/**/
- ›stream/ picked up recursively
- ›Ten data_file types already declared
- ›Adding a car needs zero edits in here
Seven meta files, filled in and working
- ›vehicles.meta
- ›carvariations.meta
- ›carcols.meta
- ›handling.meta
- ›vehiclelayouts.meta
- ›shop_vehicle.meta
- ›dlctext.meta
A car that already works
- ›A complete vehicle installed in slot 1
- ›yft, _hi.yft and ytd, all three present
- ›Spawns on first boot, before you change anything
- ›Copy its folders as the shape for your own
Adding your own car
Step one gets the resource running with the car it came with. Two to four are what you repeat for every car after that.
- 01
Drop it in and ensure it
Put vehicle_template in your resources folder, add the one line to server.cfg, restart. The car in slot 1 spawns straight away, so you know the resource works before you touch anything.
- 02
Make a numbered folder
For your second car, create data/2 and stream/2. The number is only a name. Nothing else in the resource needs to know it exists.
- 03
Fill the two folders
Your model files go in stream/2, your meta files go in data/2. Copy the ones from slot 1 if your model didn't come with a full set.
- 04
Restart
That's it. fxmanifest globs data/** and streams everything under stream/, so it finds the new car on its own. You never open fxmanifest.lua again.
Before you ask in the Discord
Do I have to edit fxmanifest.lua for every car?
No, and that's the entire point of this. The data_file lines are globbed as data/**, so a new numbered folder is found without the manifest ever mentioning it. Most vehicle packs make you add seven lines per car, which is where the typos come from.
What are the numbered folders for?
One number per car, in both data/ and stream/. Nothing reads the number, it just keeps each car's files apart so a broken one is obvious and deleting it is dragging a folder to the bin.
Can I delete the car that comes with it?
Yes. Delete data/1 and stream/1 once you've seen it spawn and you have an empty template. It ships installed so the first thing you do is watch it work, rather than debug your own model against a folder you can't be sure about.
Why is vehiclelayouts.meta so big?
It's the full set of game layouts, which is what lets custom seat and animation setups resolve instead of falling back. It's data, it costs you nothing at runtime, and you can leave it alone.
Does this work on Enhanced and Legacy?
Yes. Streaming a vehicle didn't change between them, so the same folder works on both. I test against Enhanced, so that's the one I'll support.
My car spawns invisible or as a default model. Why?
Almost always the spawn name not matching across vehicles.meta, carvariations.meta and handling.meta, or a missing .ytd. Slot 1 is a working reference, so diff yours against it before asking.
Does it matter what framework I run?
No. This is a streaming resource, so ESX, QB and standalone all treat it the same. Adding the car to a dealership or a job is your framework's job, not this folder's.
Can I use this on a server I charge for?
The template is mine and it's free to use however you want. The car that comes with it is an example, so check you're allowed to run any model you ship, including that one.