Skip to main content
Set Config.Debug = true in shared/config.lua and restart to print the detected framework, target system, textui system, notify system, and keys system on boot. That alone solves most of the reports we get. Check the F8 console (client) and your server console, filtered for [nex_dealerships]. Most issues print a clear error there.

Common issues

ProblemFix
Dealership browser is emptyThe catalog has no vehicles in the lot’s categories. Open /dealershipadminImport and import from your framework, or add models manually.
Lots don’t show up after editing shared/locations.luaYou restarted the wrong resource. Use restart nex_dealerships (or refresh ; ensure nex_dealerships). Make sure each entry’s key (['pdm']) is unique.
Vehicle is bought but doesn’t show in the player’s garageWrong garage script wiring. The resource writes to owned_vehicles (ESX) or player_vehicles (QB/Qbox) — your garage script must read from that. If you use a non-standard schema, set Config.GiveVehicleFn. See Integrations → Garage.
Keys don’t work after purchaseConfig.Keys.System doesn’t match the keys script you actually have running. Set Config.Debug = true and re-check on boot. For unsupported scripts, set Config.KeyFn.
Money is charged but the vehicle never spawnsThe framework’s vehicle insert failed. Check the server console for the SQL error. Common cause: missing columns in owned_vehicles / player_vehicles — the resource only writes the standard columns; if your garage script added required columns, add a Config.GiveVehicleFn to fill them.
/dealershipadmin does nothing when typedYou don’t have permission. Add it with add_ace identifier.steam:<HEX> nex_dealerships.admin allow, or grant group.admin via add_principal.
/dealershipmgmt does nothingYou don’t own a dealership and aren’t an admin. Set yourself as the owner of a lot via /dealershipadminSet Owner, or add the management ace.
Catalog edits don’t propagate to other playersThe sync event didn’t fire. Check the F8 console on the other player for receive errors. Make sure all clients are on the same resource version.
Test drive HUD timer is mis-positionedTweak Config.TestDrive.TimerPosition (normalized 0.0–1.0 screen coords).
Test drive ends instantlyThe vehicle spawn failed at TestCoordinates — pick coords that are above ground level and clear of obstructions.
Showroom preview is on top of the pedPreviewCoords is too close to PedCoordinates. Move it somewhere private — most operators use a rooftop or an interior.
Player has the vehicle but can’t see it on the mapGarage script issue — they likely have to retrieve it from DefaultGarage. Or set Config.Garage.State = 0 to spawn it parked.
Stock never goes down for a public lotConfig.Stock.EnforceOnPublic = false by default — public lots are unlimited. Flip it to true to enforce stock everywhere.
Restock orders never fulfilThe CreateThread worker that ticks orders runs once per minute. Wait a minute. If it never fires, the script crashed on boot — check the server console.
Financing payments don’t auto-debitPlayers need to be online (or recently online) for installments to fire. If Config.Financing.Enabled = true and a real framework is detected, the worker runs every minute. Check the console for [nex_dealerships] errors.
Repossession deletes a vehicle the player just paid offA race between manual pay-off and the auto-debit. Set a slightly longer Config.Financing.GraceMinutes.
Owner cut doesn’t pay outOwner identifier in nex_dealership_settings.owner_identifier is wrong or unset. Re-run /dealershipadminSet Owner with the player’s steam identifier visible while they’re online.
Discord webhook isn’t firingConfig.Logs.Enabled = true and Config.Logs.Webhook set? Some networks block outbound from FiveM — test with curl from the server box.
[ESX] players can’t be detectedIf you’re on legacy ESX (pre-1.2), set Config.OldESX = true.
Display vehicles spawn but won’t accept paintVanilla colour indexes are integers 0–159. RGB takes { r, g, b }. If you pass both, RGB wins.

Before opening a support ticket

Please include:
  1. Your framework ('esx', 'qb', 'qbox') and FiveM artifact build number.
  2. Whether it’s a fresh install or after a config change.
  3. Boot log with Config.Debug = true, filtered for [nex_dealerships].
  4. Server console output when the issue happens, filtered for [nex_dealerships].
  5. F8 console output on the affected player.
  6. Which dealership key the issue happens at, and whether it’s owned or public.
See Support & contact for how to reach us.