SAF Garage Installation | SAF Scripts Docs

SAF Garage needs nothing else to run. oxmysql is optional: without it, vehicles are saved to a JSON file. ox_lib is not needed either; if it is running, notifications use it.

Steps

Put the saf-garage folder in your resources folder.
Add it to server.cfg, after your framework and oxmysql:
server.cfg
```
ensure oxmysql
ensure saf-garage
```
Optional: give your staff the higher vehicle limit:
server.cfg
```
add_ace group.admin garage.staff allow
```
Start the server. The console prints the framework it found and where vehicles are saved.

Storage

With oxmysql running, the tables saf_garage_vehicles and saf_garage_shares are created on the first start. There is no SQL file to run.

Without oxmysql, vehicles go to garage.json in the resource folder. Pick one by hand with Config.Storage.

Fuel and keys

These are picked up on their own when they are running:

Kind	Scripts
Fuel	LegacyFuel, ox_fuel, cdn-fuel, ps-fuel, lj-fuel, okokGasStation
Keys	qbx_vehiclekeys, qb-vehiclekeys, wasabi_carlock, MrNewbVehicleKeys, qs-vehiclekeys, Renewed-Vehiclekeys

For anything else, replace Bridge.SetFuel or Bridge.GiveKeys. See Custom servers.

Permissions

garage.staff raises a player's limit from Config.MaxVehicles to Config.StaffMax. Framework groups named admin, god and superadmin (Config.StaffGroups) also count.

Updating

Replace every file except your custom/ folder and garage.json if you use it. Keep config changes in custom/shared/ so a new config.lua doesn't undo them.