Installation
Install and start Nexra Handling Editor on your FiveM server.
Installation
- Ensure ox_lib is installed and started.
- Ensure oxmysql is installed, started, and connected to your database.
- Place
nexra_handling-editorin your resources folder. - Add the following to
server.cfg:
ensure ox_lib
ensure oxmysql
ensure nexra_handling-editor- Add your allowed staff licenses in
config.lua(see Permissions). - Restart the server (or start the resource).
Load order
Start ox_lib and oxmysql before nexra_handling-editor. Your framework should also be started first if you want character names and framework vehicle-name lookups.
Dependencies
Required
Auto-detected
Framework bridging is used for editor names and vehicle spawn-name lookups when available.
| Integration | Supported |
|---|---|
| Framework | qbx_core, qb-core, es_extended, custom, or none |
| Notifications | ox_lib, lation_ui, okokNotify, wasabi_notify, mythic_notify, brutal_notify, pnotify, t-notify, fl-notify, vms_notifyv2, zsx_uiv2, solaire_notify, codem-notification, custom |
For other frameworks or notify systems, edit framework/custom/ or modules/notifications/custom/.
Permissions
Handling Editor uses a license allowlist in config.lua.
Config.HandlingEditor = {
AllowedLicenses = {
'license:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX',
},
}Add each approved staff member's FiveM license identifier:
AllowedLicenses = {
'license:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX',
'license:YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY',
}If AllowedLicenses is empty, everyone can open the editor. For production servers, keep this list restricted to trusted staff.
Database
No manual SQL import is required. On startup, the resource creates these tables if they do not exist:
| Table | Purpose |
|---|---|
nexra_vehicle_presets | Saved reusable handling presets |
nexra_vehicle_uploads | Saved vehicle handling XML and optional engine sound |
Saved uploads are broadcast to clients and applied when matching vehicles are entered or scanned.
Locales
Locale files live in locales/. Set Config.Locale in config.lua.
Included: en, de, es, fr, nl, pt-br, tr, cs
Branding
The shipped UI includes editable branding assets:
| File | Purpose |
|---|---|
web/build/logo.png | UI logo |
web/build/theme.css | UI theme variables |
Replace the logo file with your own image, or edit theme.css to adjust the UI theme.
Editable files
These remain open for customization (escrow ignore):
config.lualocales/*.jsonshared/handling_config.luaserver/handling_editor.luaframework/**/*.luamodules/**/*.lua
