Retro Dealership
Installation
Section titled “Installation”Add Resource
Section titled “Add Resource”Drop rs_dealerships into your resources folder and add to server.cfg:
ensure rs_dealershipsMake sure ox_lib and oxmysql start before it.
Database
Section titled “Database”All tables are created automatically on first start - no SQL import needed.
| Table | Purpose |
|---|---|
rs_dealershipss | Shop ownership, balance, settings, zone data |
rs_dealerships_stock | Per-shop vehicle inventory |
rs_dealerships_orders | Restock order history |
rs_dealerships_sales | Purchase log |
rs_dealerships_finance | Installment payment tracking |
rs_dealerships_usedcars | Second-hand vehicle listings |
rs_dealerships_showcase | Showroom display positions |
rs_dealerships_trade_requests | Pending used car trade requests |
rs_dealerships_staff | Staff roster per shop |
rs_dealerships_role_perms | Role-based permissions |
The server also runs ALTER statements automatically to add new columns as the resource updates. You don’t need to touch the database manually.
Framework
Section titled “Framework”Auto-detects QBCore, QBox (qbx_core), or ESX. Force a specific one with Config.Framework in config/config.lua.
Target System
Section titled “Target System”Auto-detection order: ox_target → qb-target → qtarget → 3D markers with E-key fallback.
Conflicts
Section titled “Conflicts”Remove or disable qb-vehicleshop or any other vehicle shop resource. Only one should be active.
Verify
Section titled “Verify”Restart the server, visit a shop location, interact with the NPC or marker, and check that the catalogue loads. Try purchasing a vehicle to confirm everything is wired up.