Getting Started

Nord Garages v2.0.0
Nord Garages v2.0.0
Nord Garages is a complete vehicle storage and lifecycle system for FiveM. Version 2.0.0 combines public/job/fleet/house garages, dedicated impounds, native showrooms, vehicle transfers, real/persistent parking, framework ownership synchronization and the Vehicle OS layer.
Main capabilities
Public, job, fleet and house garage workflows.
Dedicated impound yards separated from normal garages.
Land, boat, helicopter and plane type safety.
In-game Admin Creator and Garage Manager.
Native GTA showroom interiors without a shell dependency.
Vehicle transfer system with configurable fees and delivery times.
Job impound workflow and field impound action.
VIP Persistent Parking backed by OneSync.
Permanent VIN identity and plate alias/history support.
Vehicle snapshots, service, insurance, stolen state and EV metadata.
Collections, favourites, reservations and physical parking slot backend.
Recovery Center, analytics and provider registry.
Live synchronization hooks for Nord Staff and Nord Phone.
AutoSQL with versioned migrations.
Supported frameworks
Config.Framework = 'auto' detects Qbox/QBX, QBCore, ESX, Nord Core, then falls back to standalone operation.
Important design rule
Framework vehicle tables remain the ownership source where applicable, while Nord Garages is authoritative for its runtime garage/impound/Vehicle OS state. Avoid editing 
nord_garage_vehicles manually while the server is live unless you fully understand the state model.

Requirements
Requirements
Required
FiveM server using 
cerulean fx_version.
Lua 5.4 support.
oxmysql started before 
nord_garages.
OneSync is strongly recommended and required for the full persistent-world behaviour.
Frameworks
The resource can run with:
ESX
QBCore
QBX / Qbox
Nord Core
Standalone
Optional integrations
nord_vehiclekeys
qb-vehiclekeys
nord_inventory
ox_inventory
qb-inventory
qs-inventory
ps-inventory
codem-inventory
lj-inventory
tgiann-inventory
ox_fuel
lc_fuel
LegacyFuel
ox_lib for notifications/TextUI when configured
Recommended start order
ensure oxmysql
# framework/core resources
# inventory/fuel/keys resources
ensure nord_vehiclekeys   # when used
ensure nord_garages
# integrations such as nord_staff / nord_phone
Starting the key/inventory/fuel providers before Nord Garages allows auto-detection to resolve them immediately.

Installation
Installation
Copy the 
nord_garages folder into your server resources directory.
Ensure 
oxmysql is installed and connected to the same database used by your framework.
Review 
shared/config.lua before first start.
Add 
ensure nord_garages to 
server.cfg after its dependencies.
Restart the server or start the resource.
Database installation
Nord Garages includes AutoSQL. On normal installations you do not need to manually import the SQL file. The resource creates and migrates its own tables on startup.
The included 
sql/nord_garages.sql is a manual fallback for environments where you explicitly prefer manual SQL setup.
First validation
After first start:
Confirm there are no oxmysql errors.
Run 
/garageadmin with an account that has the configured ACE permission.
Create or inspect a garage.
Publish the garage.
Store and retrieve one owned test vehicle.
Verify fuel, keys and vehicle properties are restored.
Test an impound separately from a normal garage.
Existing installations
Do not drop old Nord Garages tables when upgrading. AutoSQL migrations are designed to upgrade the current schema in place while preserving data.

Quick Start
Quick Start
1. Give yourself admin access
Default permission:
add_ace group.admin nord.garages.admin allow
The permission node can be changed using 
Config.AdminAce.
2. Open the creator
Default command:
/garageadmin
3. Create a garage
Use New Garage and choose the correct vehicle categories. Configure at minimum:
Name and identifier
Garage type
Vehicle categories
Access policy
Garage point
Store point(s)
Spawn point(s)
Blip visibility
Published state
4. Test the player flow
Enter the garage interaction area, open the garage, spawn an owned vehicle, then return it through a compatible store point.
5. Create impounds separately
Impound yards have their own management flow. Keep land, boat and air impounds separated unless the configuration deliberately supports the matching vehicle classes.