Installation

Installation Guide – v42-VehicleShop

Step 1: Ensure All Dependencies Are Installed

Before proceeding, confirm that all required dependencies for your framework (QBCore or ESX) are:

• Installed

• Running properly

• Using the latest stable versions

---

Step 2: Install the Resource

1. Drag and drop the v42-vehicleshop folder into your server’s resources directory.

2. Add the following line to your server.cfg after all dependencies:

ensure v42-vehicleshop

---

Step 3: Add Items & Images

Ensure all vehicle images are added correctly:

• Place them inside the following directory: img/brandname/model/

• Make sure paths are properly referenced in shared/vehicles.lua

• Remove or replace any demo images or showroom cars if needed

---

Step 4: Import SQL Files

• Import the provided vehicleshop_stocks.sql file into your server's database using your preferred SQL tool (e.g., phpMyAdmin, HeidiSQL).

---

Step 5: Configure the Script

Open config.lua and set up the core settings:

• Config.Framework – Set to 'qb' or 'esx'

• Config.CoreName – Set to your framework core folder name ('qb-core', 'es_extended', etc.)

• Config.UseTarget, Config.Debug, and other options can be customized as needed

• Review Config.Shops to modify or add vehicle shops and showroom settings

---

Step 6: Configure Vehicle Data

Open shared/vehicles.lua and:

• Add or remove vehicle entries as needed

• Ensure spawn model names do not contain spaces

• Provide complete data for each vehicle

• Assign proper image paths and details

---

Step 7: Start or Restart the Server

To apply changes:

• Run the following in your server console or F8:

  ensure v42-vehicleshop

• Alternatively, restart your server

---

Optional Commands

You can manage stock using built-in commands:

• /setstocks [shop] – Set individual vehicle stock for a shop

• /setallstocks [shop] [number] – Set a uniform stock amount for all vehicles in a shop

---

Notes

• The script is compatible with GABZ MLO by default, but locations can be customized

• Be sure no conflicting car shop scripts are running alongside this one

• Test changes on a staging server before deploying live