Integrations
The resource includes editable bridge files under bridge/. They are listed in escrow_ignore alongside config.lua; a separate Nuiro/Lumix bridge is not required.
Framework selection
| ID | Resource |
|---|---|
esx | es_extended |
qb | qb-core |
qbx | qbx_core |
Auto-detection checks Qbox, QBCore, then ESX among started resources. Use qbx, not qbox, as the explicit config ID. Start the framework before MultiJob, or force the intended provider when more than one core is present.
ESX characters use their identifier; QB/QBX use citizenid. Saved grades must exist in the framework's job definitions. A phone tile does not create a framework job.
Society accounts
| Config ID | Provider | Account lookup |
|---|---|---|
esx | esx_addonaccount | Shared account society_<job> |
qb | qb-banking | Job account |
management | qb-management | Job account |
renewed | Renewed-Banking | Job account |
okok | okokBanking | Job account |
custom | Editable adapter | Bridge.CustomSociety(jobName) |
off | No provider | Society transfers unavailable |
Auto-detection prefers ESX's addon account when running ESX, then qb-banking, qb-management, Renewed-Banking and okokBanking. The account must already exist in that provider.
For a custom provider, set Config.bridge.society = 'custom' and implement the placeholder in bridge/custom.lua. Return nil when no account exists; otherwise return a table with money, addMoney(amount) and removeMoney(amount). The supplied placeholder returns nil until adapted.
Notifications
Supported IDs are auto, ox_lib, esx, qb, okok, mythic and custom. Auto selects ox_lib when available, then the framework notification path.
For custom, handle the configured client event, defaulting to nurio-multijob:customNotify. Its arguments are (message, kind, title), where kind is success, error or inform.
LB Phone
The app is registered through LB Phone's custom-app exports with:
App ID: nurio_multijob
UI: nurio-multijob/web/build/index.html
Icon: https://cfx-nui-nurio-multijob/web/build/icon.svgThe folder name is used dynamically for the UI path. The app ID comes from Config.App.id. Keep the compiled app and icon in the resource's files entries.
Older job menus and developer hooks
The ESX startup import from wasabi_multijob is described in Installation. It is a data import, not a requirement to keep the old menu running.
The supplied resource has no public server export for granting arbitrary jobs or skipping boss checks. Internal NUI callbacks and request/response events are the app's transport, not an admin API. Integrate job assignment through your framework and keep the saved employment data consistent with its job-change lifecycle.
