SAF HUD Installation | SAF Scripts Docs

SAF HUD has no dependencies and needs no database.

Steps

Put the saf-hud folder in your resources folder.
Add it to server.cfg, after your framework:
server.cfg
```
ensure saf-hud
```
Give your staff permission to change SOE and AOP:
server.cfg
```
add_ace group.admin hud.manage allow
```
Optional: put your postal map's postals.json in the saf-hud folder to turn on the postal cell and the /p command. See Postals.

Restart the server. The HUD appears as soon as a player has a character loaded.

Permissions

hud.manage is the only permission. Anyone with it can run /soe, /soeall, the per-area shortcuts and /aop. The server console can always run them.

On ESX and QBCore, framework groups named admin, superadmin, god and mod also count. Qbox uses ACE groups, so the add_ace line above covers it.

To give one person access:

server.cfg

add_ace identifier.discord:123456789012345678 hud.manage allow

To use your own staff system instead, replace Bridge.CanManage. See Custom servers.

Postals

The postal cell and /p only turn on when saf-hud/postals.json exists and has entries. The file is a JSON list with one object per postal:

JSON

[
  { "code": "101", "x": -1263.42, "y": -1153.08 },
  { "code": "102", "x": -1204.70, "y": -1141.54 }
]

This is the format most postal map resources ship, so you can usually copy the file over as it is. With no file, the postal cell is hidden and the commands are not registered.

Updating

Replace every file except your custom/ folder. Changes made straight in config.lua are lost when you overwrite it, so keep them in custom/shared/ instead. See Custom servers.