Resource Integration
A guide to help customers understand how to make cd_garage compatible with other resources.
Compatible Resources
Compatibility Type
There is multiple ways another resource can be considered compatible with cd_garage. Some are easier for the customer than others.
Built-in (recommended) - This means the resource's creator has already made the changes to their resource to make it compatible with cd_garage, so you don’t have to.
Creator Docs - This means the creator provides documentation for the required changes you need to make to make their resource compatible with cd_garage.
ESX Resources
Keys
To use our built-in vehicle keys feature with official ESX resources, these are the only modifications required because most ESX resources usually call these functions to spawn in vehicles.
Still don't recieve keys? If you don't receive keys to a vehicle, most likely, one of your resources does not use any of the ESX spawn vehicle functions, so you will need to refer to #VehicleKeys and add the event to that resource.
Click this link to view the code on GitHub: ex_extended/server/onesync.lua
Job Garages
To use our built-in job garage feature with official ESX resources, these are the only modifications required.
Click this link to view the code on GitHub: esx_policejob/server/main.lua
Boat & Air Garages
To use our built-in boat & air garages feature with official ESX resources, these are the only modifications required.
Click this link to view the code on GitHub: esx_boat/client/main.lua
Persistent Vehicle
To use our built-in persistent vehicle feature with official ESX resources, these are the only modifications required.
Vehicles still respawn when deleting them? If vehicles still respawn when deleting them, most likely, one of your resources does not use the ESX delete vehicle function, so you will need to refer to #PersistentVehicles and add the event to that resource.
Click this link to view the code on GitHub: es_extended/client/functions.lua
QBCore Resources
Keys
To use our built-in vehicle keys feature with official QBCore resources, these are the only modifications required.
This process is much simpler on QBCore compared to ESX because we have added event handlers for the default QBCore qb-vehiclekeys resource into cd_garage, meaning its mostly pre-configured.
Click this link to view the code on GitHub: qb-core/client/events.lua
Boat & Air Garages
To use our built-in boat & air garages feature with official QBCore resources, these are the only modifications required.
Click this link to view the code on GitHub: qb-vehicleshop/client/main.lua
Persistent Vehicle
To use our built-in persistent vehicle feature with official QBCore resources, these are the only modifications required.
Vehicles still respawn when deleting them? If vehicles still respawn when deleting them, most likely, one of your resources does not use the QBCore delete vehicle function, so you will need to refer to #PersistentVehicles and add the event to that resource.
Click this link to view the code on GitHub: qb-core/client/functions.lua
Garage Phone Apps
To make your phones garage app compatible with cd_garage, these are the only modifications required. If you use a phone thats not listed below, these changes may not work for you.
Click this link to view the code on GitHub: qb-phone/server/main.lua
Paid Resources
Keys
You can find this event in [okok-vehicleshop/sv_utils.lua]
(approx; line 72).
Boat & Air Garages
You can find this event in [okok-vehicleshop/sv_utils.lua]
(approx; line 68).
Garage Phone Apps
To make your phones garage app compatible with cd_garage, these are the only modifications required.
lb-phone comes pre-configured to work with cd_garage, so no modifications are required.
Last updated