Installation

Requirements

Component	Required?
ox_lib	Yes — shared utilities and notifications
oxmysql and a working MySQL connection	Yes — saved jobs and earnings statistics
es_extended, qb-core, or qbx_core	One supported framework
lb-phone	Yes for the included Employment interface
Society account provider	Optional for balances and society transfers

The framework bridge is included. A separate inventory or target system is not required by this resource.

Resource files

Install the folder as:

resources/[nuiro]/nurio-multijob/

Keep config.lua, bridge/, client/, server/, sql/ and web/build/. The phone loads the compiled app from web/build/index.html; Node.js is not needed to run an already-built release on the game server.

The resource's ui_page is web/blank.html, not the visible app. This lets the phone host Employment while the resource's own NUI page stays empty. Check that this file exists in the release package. If it is missing, its contents can be:

<!doctype html>
<html lang="en">
  <head><meta charset="UTF-8"><title>Employment NUI</title></head>
  <body style="margin:0;background:transparent"></body>
</html>

Keep ui_page 'web/blank.html' and the phone UI path separate. Pointing the resource UI page at the visible app can draw it over gameplay.

Start order

Example for ESX and its society account provider:

ensure oxmysql
ensure ox_lib
ensure es_extended
# Optional society account integration:
ensure esx_addonaccount
ensure lb-phone
ensure nurio-multijob

Use qb-core or qbx_core instead of es_extended for your framework. Start your chosen society provider before MultiJob if you use one. Keep each dependency's own requirements in its normal start order.

The resource detects integrations when it starts. Check the startup message, for example:

[nurio-multijob] framework esx | notify ox_lib | society esx
[nurio-multijob] ready, paycheck mode track

Set explicit bridge IDs if auto-detection does not select the provider you intend. A test-server manifest may contain extra server-specific imports, such as Reaper imports; those are separate from the product's built-in bridge dependencies and must match the environment where that manifest is used.

Database and existing jobs

On MySQL readiness, the resource creates nurio_multijob and nurio_multijob_stats if needed. The schema is also included in sql/install.sql.

On ESX, startup also imports valid saved jobs from wasabi_multijob when that table exists, then imports the current jobs from users joined to job_grades. Existing saved rows are retained, and the current ESX job grade takes precedence for its row. Blacklisted jobs and the configured off-duty job are excluded. This automatic import is ESX-specific.

Back up existing employment data before a migration. Use one job-management flow at a time; leave an older menu disabled once players are using Employment. Do not drop the old tables just to make this resource start.

Phone registration

The app registers itself with LB Phone using Config.App.id, defaulting to nurio_multijob. Do not add a second custom app with the same ID. Registration retries during startup and is attempted again if LB Phone starts later.

Config.App.defaultApp = true marks Employment as a default app. Setting it to false changes that installation flag; it does not disable the resource.

First-run check

1. Join with a fully loaded character and open Employment in LB Phone.
2. Confirm the character's current job and valid saved jobs appear.
3. Switch to a held job, clock out and clock back in. Allow the default eight-second cooldown between successful changes.
4. Check that Config.OffDutyJob exists in your framework. It defaults to unemployed, grade 0.
5. Review the configured paycheck mode before waiting for a cycle. track does not pay money.
6. With a boss-grade character, open that job's detail and verify the roster. If using society accounts, test a small deposit and withdrawal through your normal server testing process.

Continue with Employment App and Configuration.