Dealership Creator (qs-dealership 3.0) replaces Vehicleshop (qs-vehicleshop 2.x). It is not an update of the old script: it is a new resource, with its own tables and its own config, and it imports nothing from v2. This page removes v2 from your server completely, so the two never run side by side.
Running both at once puts two dealerships, two sets of targets, two blips and two admin panels on the same forecourts, and players can buy the same car from either. Remove v2 before you start Dealership Creator.
What v2 Installed#
Everything v2 put on your server, and what to do with each piece:
Piece | What it is | What to do |
|---|---|---|
| The v2 resource itself. | Remove. |
| The | Remove, unless another script on your server spawns |
| The hologram and screen textures v2 drew its 3D panels with. | Remove, unless another script lists it as a dependency. Dealership Creator does not use it. |
| The showroom interior map that shipped with v2. | Optional. Dealership Creator does not need it. Keep it if you like the building — a dealership can be placed inside any interior — or remove it. |
Six | v2's dealerships, catalogue, stock, display cars, restock missions and sales. | Drop once you have a backup. |
| Added on QBCore and Qbox servers to tell cars, boats and aircraft apart. | Keep. Garage scripts read it too, and dropping it can break every garage on the server. |
Your players' cars | Every car bought from v2, in your framework's vehicle table ( | Nothing. Neither script owns that table. Every car stays with its owner. |
Job dealership money | What job-run v2 shops earned, held in the job's own company account ( | Nothing. It belongs to the job and stays there. Hand a dealership to the same job and, on frameworks with company accounts, its till is that account. |
v2 registered no inventory items and stored nothing on players' machines, so there is nothing else to clean up.
Removing It Step by Step#
Back up the database
Export the whole database with HeidiSQL, phpMyAdmin or your host's panel, or from a terminal:
bash mysqldump -u root -p your_database > backup-before-dealership-creator.sqlKeep the file until you have run Dealership Creator for a while and are sure you need nothing from v2.
Stop the old resources
Stop the server, or stop v2 and its companions from the server console:
bash stop qs-vehicleshop stop qs-flatbed stop generic_texture_renderer_gfx stop showroomsmloTake them out of server.cfg
Delete — or comment out — every line that starts v2 or its companions:
bash # ensure qs-vehicleshop # ensure qs-flatbed # ensure generic_texture_renderer_gfx # ensure showroomsmlo # optional: keep it if you want the buildingIf they lived in a bracket folder started with one line, such as
ensure [qs-vehicleshop], remove that line instead.Delete the folders
From your
resources/folder, deleteqs-vehicleshop,qs-flatbedandgeneric_texture_renderer_gfx— andshowroomsmloif you are not keeping the building. Copy out anything you want to keep first, such as vehicle photos you made yourself.Drop the v2 tables
Run this against your database. It touches only the tables v2 created:
sql DROP TABLE IF EXISTS `qs_vehicleshop_transactions`; DROP TABLE IF EXISTS `qs_vehicleshop_mission_data`; DROP TABLE IF EXISTS `qs_vehicleshop_showcase`; DROP TABLE IF EXISTS `qs_vehicleshop_stock`; DROP TABLE IF EXISTS `qs_vehicleshop_vehicles`; DROP TABLE IF EXISTS `qs_vehicleshop`;This step is optional — Dealership Creator never reads these tables and does not mind them being there — but leaving them means a database with two dealership systems in it.
Remove other dealership scripts too
While you are in
server.cfg:qb-vehicleshop,esx_vehicleshopand any other vehicle shop conflict in exactly the same way v2 does. Remove them before starting Dealership Creator.Install Dealership Creator
Follow Installation. The first start builds its own tables and opens eight starter dealerships, so the server is selling cars again before you have placed anything.
What Changes for Your Staff and Players#
In v2 | In Dealership Creator |
|---|---|
|
|
|
|
Dealerships typed into the panel and the config | Placed in game with a freecam and handles |
Settings in | Almost every setting in the in-game Settings pages, changed live |
Restock missions with a flatbed truck | Restock runs: the ordered cars wait at the port and a crew drives each one in |
v2 dealerships are not carried over — their layout was built for v2's own system. Recreate the ones you need in the creator, which takes a few minutes each, or start from the eight dealerships Dealership Creator opens with.
Checking It Is Gone#
Start the server. Nothing in the console mentions
qs-vehicleshop; a line saying it could not be found means anensureis still inserver.cfg.In game,
/vehicleshopanswers as an unknown command.Walk past an old v2 forecourt: no old blip, no old target prompt, no v2 display cars.
The Dealership Creator boot summary appears in the console, and
/qsdealershipadminopens.