AWS Dealership

A vehicle showroom and dealership-management resource with stock, test drives and staff controls.

Installation

Requirements

• oxmysql
• QBCore or ESX; Qbox uses the QB compatibility path in the supplied framework config
• A compatible vehicle ownership/garage schema and the selected target/fuel/key integrations

Startup order

This example selects one framework and target. Use the resources matching your configuration and start dependencies first.

ensure oxmysql
ensure qb-core
ensure aws-dealership

Setup steps

1. Back up existing dealership data and review dealership.sql. It includes vehicle catalog seed rows as well as table creation; use it on a new installation or merge deliberately.
2. Configure dealerships, catalog/stock and staff jobs in shared/config_dealers.lua.
3. Review vehicle ownership persistence in server/functions/sv_editable.lua and the framework adapter before testing purchases.

Gameplay and usage

1. Visit a configured dealership, inspect a vehicle and test-drive it.
2. Use /dealeradmin with a permitted account to check management. Complete a controlled purchase and verify the garage ownership record.

Configuration

• shared/config_dealers.lua: Config.JobName, AuthorizedJobs, MinGradeForManagement and BossGrade define staff access.
• Config.AdminCommand defaults to dealeradmin; the source includes an additional /dealership command.
• shared/config.lua controls targets, plates, test drives, showroom music and selling options.
• shared/config_cameras.lua, client/config/cl_targets.lua and cl_config.lua contain camera and integration hooks.

Exports and integrations

• aws-dealership.IsInDealer — see aws-dealership/client/config/cl_baseevents.lua for its arguments and client/server context.

Troubleshooting

• Stock does not load: check dealership.sql table names and dealer keys.

• Purchased vehicle missing from garage: inspect the ownership schema and editable server integration.

• Do not grant a dealer job grade until its management permissions have been reviewed.

• Include the package version, framework and exact server/F8 error when requesting support. Remove private tokens and player data.

Package reference

Database files

• aws-dealership/dealership.sql

Configuration reference

• aws-dealership/client/config/cl_baseevents.lua (edit the table returned/defined by this file).
• aws-dealership/client/config/cl_blips.lua (edit the table returned/defined by this file).
• aws-dealership/client/config/cl_config.lua (edit the table returned/defined by this file).
• aws-dealership/client/config/cl_hud_control.lua (edit the table returned/defined by this file).
• aws-dealership/client/config/cl_targets.lua (edit the table returned/defined by this file).
• aws-dealership/shared/config.lua: Debug, TestDrive, Settings, Plates, DefaultBucketId, ShowroomMusic, SellVehicle, HudResources
• aws-dealership/shared/config_cameras.lua: Camera
• aws-dealership/shared/config_dealers.lua: JobName, AuthorizedJobs, AdminCommand, MinGradeForManagement, BossGrade
• aws-dealership/shared/config_framework.lua (edit the table returned/defined by this file).

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.