AWS Job Garage
Job/grade vehicle selection and configured spawning with key and fuel integrations.
Installation
Requirements
- qb-core, ox_lib and oxmysql.
- Target, menu, vehicle-key and fuel adapters depend on config.lua and client/main.lua. Native Qbox needs QB compatibility.
Startup order
This example selects one framework and target. Use the resources matching your configuration and start dependencies first.
ensure oxmysql
ensure ox_lib
ensure qb-core
ensure qb-target
ensure qb-menu
ensure qb-vehiclekeys
ensure aws-job-garage
Setup steps
- Use check-pd-vehicles.sql only after reviewing its schema changes against your existing vehicle table.
- Configure Config.konumlar, job grades, vehicle models and spawn/showroom coordinates.
- Start key/fuel integrations before the resource if enabled.
Gameplay and usage
- Interact with a configured garage NPC using a permitted job and grade, choose an available vehicle and test its delivery.
Configuration
- config.lua: Target, Notify, Progressbar, Menu, Showcase and konumlar.
- Historical riopd event identifiers remain intact for integrations; the resource folder is aws-job-garage.
Exports and integrations
No public callable export is declared with exports() in these source files. Use the documented commands or configuration; internal network events are not a trusted integration API.
Troubleshooting
-
Test unauthorized grades, showroom routing-bucket cleanup, key grants and existing vehicle persistence.
-
Include the package version, framework and exact server/F8 error when requesting support. Remove private tokens and player data.
Package reference
| Manifest | Version |
|---|---|
fxmanifest.lua |
not specified |
Database files
aws-job-garage/check-pd-vehicles.sql
Configuration reference
aws-job-garage/config.lua:Target,Notify,NotifyKonum,Progressbar,Menu,Showcase,OnxPoliceCars,OnxHighspeedCars,OnxPoliceAir,OnxEmsCars,VehicleLabels,konumlar
Frequently asked questions
Does this need Keymaster or an escrow key?
The Lua sources in this delivery package were readable in the static audit. No /assetpacks requirement is added by this package. Required framework, inventory and map resources still need to be installed separately.
Can I change the folder or database table names?
Keep the supplied folder names. Historical event, SQL and KVP identifiers are retained to protect existing integrations and saved data. Renaming a table or event requires a separate migration.
Why is an interface or item missing?
Check the startup order, selected framework/target adapter, inventory item definitions and the server/F8 console. The package does not install an entire framework or inventory for you.
Has this been tested on my server?
ZIP integrity, source readability, script syntax and manifest references were checked locally. Multiplayer gameplay, your framework version and integrations require a FiveM server acceptance test before a public release.