Base Installation

Start your TCVS journey with our installation guide.

Step 1: Download the Resources

Caution

1) Download The Complete Vehicle System - <Your Framework> Version from Keymaster.

2) Download Polyzone and ox_lib through Github.

3) Extract all three files inside your server’s resource folder. Make sure to name Polyzone and ox_lib correctly as needed (without -master suffix).

4) Ensure all 3 resources inside server config file.

ensure ox_lib
ensure Polyzone
ensure realisticVehicleSystem

---

Step 2: Run the SQL File

Caution

Execute the provided SQL file on your database, ensuring that you have selected the appropriate database before running the SQL file. After running it, a new table named “rvs_garages” will be created, and your player-owned vehicles table will be modified to include TCVS’ additional columns.

---

Step 3: Setup Configuration

Caution

Configure the settings based on your framework in the /configs/ directory.

For detailed configuration explanations, please click the link below.

• Configuration Settings

---

Step 4: Custom Identifiers

Danger

If you are using QBCORE / ESX / QBOX set Config.UseCustomIdentifier to true.

If you are utilizing a custom framework on your server, modify the code inside server/frameworks.lua to suit your preferences. This file contains a reference to the core you’ve downloaded.

Only set this option to false if you want to use the Rockstar License identifier. Not recommended unless you have no framework!

---

Step 5: Point your Database Resource (Optional)

Note

By default, our system is configured to use oxmysql in fxmanifest.lua. If you’re utilizing a different database system, please make the necessary updates in both fxmanifest.lua and server/database.lua to align with your chosen database setup.

'@oxmysql/lib/MySQL.lua', -- for OXMYSQL
'@mysql-async/lib/MySQL.lua', -- for MYSQLASYNC

---

Step 6: Disable Conflicting Resources (Advised)

Caution

Our system integrates multiple interconnected systems to ensure synchronization without any bugs or issues. To prevent conflicts among resources, it is recommended to disable any resource that handles vehicle keys or vehicle damage. Specifically, for QBCore users, we advise disabling qb-garages, qb-vehiclefailure, and qb-vehiclekeys.

---

Step 7: Include Import Vehicles (Advised)

Caution

Incorporate all your imported vehicles into the /configs/vehicles_config.lua file. This file contains a hardcoded section for each possible vehicle, allowing you to specify the vehicle type and its purchase price for seamless integration with our resource. We currently have added all “vanilla” vehicles of GTA.

• Vehicle Info Config

---

Step 8: Start The Server And Wait The Timer

Danger

Each time TCVS is initiated on the server, it searches for any empty fields in the database. Each vehicle entry consists of 6 fields, so for example, if you have 1000 vehicles, there would be 6000 empty fields needing updates (15 minutes). To update these fields with generated data, it takes approximately 150 milliseconds per field. Please allow the necessary time as indicated by the resource for this process to complete. Afterward, re-ensure the resource to confirm that the update process has been correctly executed.

Example with 819 vehicles.

Note

All vehicles are available at the impound with a set price of 0 and the reason listed as “NONE”. Only the vehicle owners have the ability to spawn their vehicles from the impound. Additionally, vehicles will be locked by default upon spawning. To unlock them, use the keybind designated in your locksystem_config.lua, which, by default, is set to ‘U’.

Step 9: Vehicle Shop Integration

Caution

To integrate this resource with your vehicle shop, please click on the link provided below. We’ve designed this resource with flexibility in mind, allowing you to customize and tailor it to your specific needs and requirements.

• Vehicle Shop Integration

---

Step 10: Mechanic Integration

Caution

To seamlessly integrate our comprehensive part system with your mechanic resource, we’ve made available a wide array of possibilities through our exports. For detailed documentation and step-by-step instructions, please click on the link below.

• Mechanic Integration

---

Step 11: Extras (Optional)

Note

To explore additional integration options and gain in-depth insights into our exports and explanations, please follow the links provided below. These resources will guide you through the process, ensuring that you can fully leverage our system to enhance your server’s functionalities.

• Exports