Changelog

1. Back up and stop

Database prerequisite for the shared configurator: when Jobs Base uses Config.UseIngameConfigurator = true (the supplied default), this upgrade's primary-group migration requires oxmysql transactions. Install oxmysql for your existing FiveM database and start it before Base. In sky_base/config/config.lua, find the existing sql = "auto" / sql = "mysql-async" entry and set sql = "oxmysql", preserving the same database connection and all data. Then follow the Base and Jobs Base update guides. This requirement applies before the first updated start; disabling automatic schema creation does not replace the transaction requirement.

These steps update sky_jobs_base from 1.54.1 to 1.55.0. If your installed version is older, complete its intervening update guides first.

1. Download and extract the new resource. Back up the installed resource, customized configuration and translations, and the FiveM database.
2. Finish active interactions and stop the server for the coordinated update. Keep the backup until the checks below pass.

2. Install the matching files

1. Delete the installed sky_jobs_base/source/ folder and insert the complete new source/ folder, including the interface files.
2. Replace fxmanifest.lua and INSTALL.md from the same download.
3. Replace the complete config/locales/ folder. Copy only your customized wording into the matching new entries, keeping every supplied key and language file.
4. Follow the remaining file and configuration actions below before restarting.

Replace the supplied import.sql and refresh the complete config/inventory/ folder, including items_ox.lua and gag.png. Keep your customized config/config.lua and apply the exact additions below instead of overwriting it with defaults. Preserve saved jobs, locations, salary/permission assignments, invoices and Dispatch records.

3. Keep settings and configure the update

Normal setup — the ingame configurator is enabled. Keep Config.UseIngameConfigurator = true and your existing saved settings. Do not run /jobconfigimport or reset the settings for this update. After the first updated start, open /jobconfig → Jobs Base. Existing Config.PrimaryJobGroups file mappings are copied into saved settings once on upgrade when no saved mapping exists. Keep the old file mappings intact until this first start finishes; afterwards edit Jobs & Storage → Primary job groups and save to apply changes immediately. A later whole-file import replaces managed settings and is not a routine update step.

Hostage and Gag are new actions and both are enabled in the supplied defaults. Before allowing players to use the updated server, either keep each action and complete its setup, or disable it in Jobs Base → Interactions → Hostage / Gag during the first maintenance start. In file mode, set Config.Hostage.enabled = false and/or Config.Gag.enabled = false for actions you do not want. Civilian access keeps its existing master switch (supplied default: off); job permissions must still allow the action.

The following other additions keep existing behavior by default: Economy → Billing → Invoice visibility by job is empty; Dispatch & Tracking → Dispatch → Phone → Preinstalled phone app is on; Interactions → Player search → Search interface remains Sky interface; Tablet & Apps → Radial menu → Allowed jobs for radial is empty. Leave them unchanged unless choosing one of the optional features below.

Only when Config.UseIngameConfigurator = false: open sky_jobs_base/config/config.lua and keep all existing settings. Add these missing fields inside the existing blocks at the positions shown; do not create a second copy of a block:

• In Config.Billing, immediately after maxAmount, add jobViewJobs = {},.
• In Config.Dispatch.phone, immediately after enabled, add defaultApp = true,.
• In Config.PlayerSearch, immediately after enabled, add inventoryMode = "sky",.
• In Config.JobRadial, immediately after enabled, add allowedJobs = {},.
• In the existing Config.JobPlayerInteractions.groups.police and .crime tables, immediately after headBag, add hostage = true, and gag = true,. Keep your existing group names, duty requirements and other permissions. Add these permissions to additional custom groups only if those groups should use them.
• In Config.CivilianUse, immediately after headBag, add hostage = true, and gag = true,. Keep its existing enabled value; the supplied default remains false.
• Immediately before the existing Config.LegRestraints block, insert both complete new blocks below. Their supplied defaults enable the feature for permitted users; set the relevant enabled = false if you do not want it. Keep Config.PrimaryJobGroups in its existing place; with the configurator disabled it remains file-owned and changes require a restart.

Config.Hostage = {
    enabled = true,
    commands = { "takehostage", "th" },
    maxDistance = 3.0,
    allowKill = true,
    releaseKey = "G",
    killKey = "H",
    allowedWeapons = {
        "WEAPON_VINTAGEPISTOL", "WEAPON_SNSPISTOL", "WEAPON_PISTOL", "WEAPON_PISTOL_MK2",
        "WEAPON_CERAMICPISTOL", "WEAPON_COMBATPISTOL", "WEAPON_HEAVYPISTOL", "WEAPON_PISTOL50", "WEAPON_REVOLVER"
    }
}

Config.Gag = {
    enabled = true,
    item = "gag", -- Required when applying through inventory AND radial.
    useItem = "both", -- "radial", "inventory", or "both"
    consumeItem = true,
    returnOnRemove = true,
    requireRestrained = true,
    allowSelfRemove = true,
    maxDistance = 2.0,
    mode = "soft", -- "soft" limits proximity; "hard" blocks outgoing voice, including radio/calls.
    softRange = 1.0, -- Metres, 1.0 to 100.0; the player cannot change this range.
    pmaMuffled = true, -- Optional muffling when pma native audio is enabled.
    propModel = "prop_rolled_sock_01",
    propOffset = { x = -0.02, y = 0.06, z = 0.0 },
    propRotation = { x = 0.0, y = 90.0, z = 0.0 }
}

Optional — hostage and gag interactions: after the updated server starts, open Jobs Base → Interactions → Hostage / Gag. Choose commands, allowed pistols, release/kill controls and gag item/voice rules. Review Civilian use and each intended job's player-interaction permissions before allowing access. Hostage defaults are /takehostage and /th, release G, execution H, with a loaded allowed pistol; players retain existing personal FiveM key bindings. The default gag requires an already restrained target, consumes one gag, and returns it to the person removing it. Self-removal requires the person to be unrestrained. Soft locks local voice range to 1 metre by default while radio/calls remain usable; Hard blocks outgoing speech, including radio/calls. PMA muffling requires pma native audio. Keep your supported voice provider; do not enable a mode its provider cannot perform.

Optional — invoice visibility: in Jobs Base → Economy → Billing → Invoice visibility by job, add the viewer job and the jobs whose issued/received invoices it may view. Sharing is directional: for mutual visibility configure both directions. It grants viewing only; payment, issue and cancellation permissions remain separate. File mode uses Config.Billing.jobViewJobs = { police = { "sheriff" }, sheriff = { "police" } } with your real job names.

Optional — inventory search interface: in Jobs Base → Interactions → Player search → Search interface, select Inventory system only when using a supported direct-search adapter (currently ox_inventory). Users require both search and confiscation access; the inventory keeps its own proximity/access and transfer rules. Other providers should keep Sky interface. File mode changes only Config.PlayerSearch.inventoryMode from "sky" to "inventory".

Optional — radial opening allowlist: select the intended jobs/groups in Tablet & Apps → Radial menu → Allowed jobs for radial. An empty list retains the previous action-based access. It controls opening Sky's own radial; direct action keybinds, target actions and external integrations retain their existing access checks. File mode uses, for example, Config.JobRadial.allowedJobs = { "police" }.

Optional — Dispatch phone installation: change Preinstalled phone app only if your phone supports the intended app-store behavior. Existing installations remain provider-controlled. Keep valid existing app identifier, route, icon and developer settings. Invalid empty values now use the supplied defaults and produce a warning, so repair the affected value in this same Phone screen rather than importing all settings.

4. Database, items and assets

The primary-group settings migration requires Base's sql = "oxmysql" whenever Config.UseIngameConfigurator = true. Complete the database prerequisite in Prepare before starting the updated libraries. If you deliberately keep Config.UseIngameConfigurator = false, that settings migration does not run; other installed features can still require oxmysql.

Keep Config.AutoExecuteQuery at its existing value in sky_jobs_base/config/config.lua. With true, startup adds primary_groups_migrated to the existing sky_jobs_configurator_settings table automatically and copies the legacy primary-group mapping once. With false, open the supplied sky_jobs_base/import.sql against the correct FiveM database before starting the resource. In its upgrade statements, find the following line and execute it only if that column does not already exist:

ALTER TABLE `sky_jobs_configurator_settings` ADD COLUMN `primary_groups_migrated` TINYINT(1) NOT NULL DEFAULT 0;

The supplied ADD COLUMN IF NOT EXISTS form is suitable for database versions that support it; on other MySQL versions check for the column first and run the statement above once. Do not delete the settings row, clear the migration flag afterwards, or replay historical seed data.

Required while Gag is enabled (the new supplied default): register the configured gag item and its icon before reopening the server. If you do not want this feature, disable Jobs Base → Interactions → Gag → Enabled during the first maintenance start before admitting players; file mode uses Config.Gag.enabled = false. Register the configured gag item in your inventory. For ox_inventory, open ox_inventory/data/items.lua, add the gag entry from the new sky_jobs_base/config/inventory/items_ox.lua inside its existing item table, and copy gag.png into ox_inventory/web/images/. Keep consume = 0; Jobs Base handles consumption and return. For other inventories use their normal item registration with the same configured item name and supplied icon. Do not register a second usable-item callback. If you explicitly disable Gag, no gag item setup is required. Keeping the new default enabled requires this item setup; it is not automatically installed in an external inventory.

No other new item, image registration or native model is required. Preserve invoices, balances, jobs, grades and existing items. Crime's Camper migration has its own separate instructions; updating Jobs Base alone does not perform that migration.

5. Start and check the result

Start the framework, database connector, inventory and configured providers first, then sky_base 1.52.0, then sky_jobs_base 1.55.0 and wait for initialization. Start the installed job resources afterwards; keep Creator after both libraries. Reconnect clients after the full restart. Complete optional menu configuration from the previous section now.

Open /jobconfig, confirm existing jobs, primary-group choices and saved locations remain present, then open a normal employee's permissions/payroll screen, including jobs with non-contiguous grades. Check that a combined job keeps its surviving registration when one resource link is removed and that off-duty access follows the intended group.

With authorized users, check invoice directions, shared viewing and any fleet Vehicle fines screen in the garage or boss menu. Fleet fines remain scoped to the actual recipient job and need the matching Police speed-camera feature. With Dispatch enabled, check an incident routed to departments using different centers, existing custom center names, the phone app after a planned phone restart, and a station announcement containing spaces/special characters. Optional RoadPad apps should be present after startup.

If you keep the new Hostage/Gag defaults enabled, or select provider-owned searches, test those with two consenting test players and the configured items, permissions and voice provider. Confirm release/removal restores normal controls and voice. These are the final operator checks after installing your packages.

1. Back up and stop the server

These steps update sky_jobs_base from 1.54.0 to 1.54.1. Complete the earlier update instructions first if your installed version is older.

1. Download and extract sky_jobs_base 1.54.1 on your computer.
2. Back up the installed resource folder, customized configuration and translations, and the game database. Keep the backup until your checks pass.
3. Finish active interactions and stop the server before replacing files.

2. Install the matching files

1. Delete the installed source/ folder and copy the complete new source/ folder into its place, including all interface files.
2. Replace fxmanifest.lua from the same download.
3. Replace the complete config/locales/ folder. Transfer only your custom wording into matching new entries; keep every supplied key and language file.

Include every job-configurator language pack inside config/locales/. Keep all other configuration files from your current installation.

3. Keep settings and apply the required configuration

No configuration value, permission ID or manual settings migration is added. Keep your existing ranks, Unit assignments, Training restrictions, garages and saved settings. Do not import or reset defaults.

With Config.UseIngameConfigurator = true, /jobconfig continues to use saved settings. With false, keep your existing Lua configuration. Unit permissions add to rank permissions; assigning a Unit does not replace a player's rank or grant unrelated Training rights.

The existing Config.JobGarage.allowPlateChange switch and its saved override keep their values. When it is already enabled (the shipped default is true), Edit plate becomes available to other authorized jobs after this update. A saved false keeps the action disabled. Existing vehicle access still applies, and only stored road vehicles are eligible; aircraft and boats remain excluded.

4. Preserve data, items and assets

No new SQL import, schema migration, item, image, streamed asset or provider setup is required. Preserve existing orders and their collection state, outfits, Unit memberships and permissions. Do not delete orders or reset the database to install this fix.

5. Start and check the result

Use Sky Base 1.51.0 or newer; the matching Base update in this set is 1.51.1. Start the database connector, framework and configured providers, then Base, then sky_jobs_base 1.54.1, followed by installed jobs and Creator. Reconnect players.

Check a player's existing rank and Unit access in the tablet, including permitted Training actions. Collect a ready supply order and confirm that its items arrive and it cannot be collected twice. Try an already-used outfit name: the editor should remain open with an explanation; enter a unique name and save. For a garage with plate editing already enabled, select an authorized stored road vehicle, choose Edit plate, enter a valid plate and use Save plate. Open an authorized job garage with several vehicles and check that the vehicle cards have clear spacing.

1. Back up and stop the server

These steps update sky_jobs_base from 1.53.0 to 1.54.0. Complete earlier update instructions first if you are using an older release.

1. Download 1.54.0 and extract it on your computer.
2. Back up the installed sky_jobs_base folder, custom configuration and translations, and the game database. Keep the backup until your checks pass.
3. Stop the server before replacing files.
4. Complete the Base 1.51.0 update first. Keep the installed jobs and Creator stopped until both Base resources finish starting.

Use the matching current Base 1.51.0 files before starting this Jobs Base package. When Creator is installed, update its 1.0.0 package in the same maintenance window. Existing-object placement needs the updated files in both libraries; do not reuse an older saved Base archive merely because its version label matches.

2. Install the matching files

Use files from the same 1.54.0 download throughout. The paths below are inside your installed sky_jobs_base folder.

1. Delete the old source/ folder and copy the complete new source/ folder into its place, including all interface files.
2. Replace fxmanifest.lua with the matching new file.
3. Copy the new config/input_dialog.lua into config/. It is required even when you want to keep the standard Sky dialog. Leave handler = false; no extra input resource is required.
4. Replace the complete config/locales/ folder, including every job-configurator language pack. Transfer only your custom wording into the matching new entries from your backup; keep all new keys and files.
5. Copy the new import.sql into the resource folder. Follow the database step before starting gameplay.

Keep your existing configured config/config.lua, provider credentials, webhooks and other public configuration. Its two new alert settings are explained in the next step. config/printers.lua changes explanatory comments only; its existing values can stay as they are.

The complete locale refresh includes both config/locales/<language>.lua and config/locales/jobconfigurator/sky_jobs_base/<language>.lua. When restoring custom wording, retain the new invitation-capacity messages and location/bell labels. Keep their nesting and the {count} and {entryLabel} placeholders exactly as supplied.

3. Keep settings and configure optional features

Keep saved settings. Do not reset the configurator, delete jobs or run /jobconfigimport for this update. Existing saved jobs, service numbers, locations, memberships and provider settings remain in use. Keep Config.UseIngameConfigurator and each resource's chosen configuration mode.

Check alert exclusions: open /jobconfig → Jobs Base Configurator → Radial & Alerts. Open Panic, then Ping, and find Excluded job groups. The new shipped value excludes crime. Keep that exclusion unless your server deliberately allows Crime organizations to use these alerts; an empty list excludes no groups. Save only if you change it. Keep existing allowed jobs, recipients, keys, cooldowns and other alert settings. A deliberately enabled per-organization Panic or Ping switch can allow that organization through the group exclusion; global alert switches, access and routing rules still apply.

If Config.UseIngameConfigurator = false, open sky_jobs_base/config/config.lua instead. Find the existing Config.Panic = { block and add this line immediately below its existing enabled entry:

disabledGroups = { "crime" },

Add the same line immediately below enabled in the existing Config.Ping = { block. If either entry already exists, keep the server's intended list rather than adding a duplicate. Use disabledGroups = {}, to exclude no groups. Keep all other fields unchanged. Restart after editing the file.

If you use Job Creator: Creator administration now has its own access permission. In sky_jobcreator/config/config.lua, find Config.CommandPermissions and its jobcreator list. Keep the existing god, superadmin and admin groups; if your administrators use a custom group, add its exact name to that same list, for example jobcreator = { "god", "superadmin", "admin", "your_group" }. Replace your_group with the existing server group name. Keep separate sky_jobs_base/config/config.lua → Config.CommandPermissions.jobconfig access for people who should also use /jobconfig. Existing explicit sky_jobscreator.jobcreator permission grants remain accepted. Employee rank permissions do not grant either administration command.

Optional — cash supply orders: open /jobconfig, select the owning job resource and the specific job, then open Online shop → Settings and enable Cash (onlineShopSettings.ownCash). Save the job. The cash button appears alongside the payment methods you already allow. Cash is off by default; no change is required to keep the old payment choices. For Mechanic's legacy parts-delivery settings, use its matching release guide and Cash setting (partsDeliveryOwnCash). Custom file-owned registrations can add ownCash = true inside their existing configuration.onlineShopSettings table only when that integration already uses the shared shop. This is optional developer integration, not a required new file setting for ordinary installations.

Optional — Crime services: use the matching Crime update guide before changing an organization's Optional job features. Enable only the services that organization needs. Global switches, job permissions and required providers still apply; employment-only features remain unavailable to gangs. Keep existing service numbers and choose General → Service badge deliberately when changing card availability. Newly created generic Creator jobs with no saved service-card choice start with that choice off.

The standard input dialogs need no further configuration. A custom input provider is an optional Lua integration in config/input_dialog.lua; keep the supplied handler = false unless you are intentionally installing one.

The recruitment and editor changes add no new configuration value or extra database step. Keep your existing MultiJob and duty policies, memberships, ranks, bell positions, locations and Dispatch settings. The full update's bonus/log schema instructions below still apply; these later changes do not require an additional import, settings reset or re-placement of existing objects.

4. Update the database and preserve data

This update adds durable bonus reservations in sky_jobs_bonus_payments and requires sky_jobs_logs to use InnoDB for transactional finance receipts. Preserve the existing tables, records and balances.

1. Open sky_jobs_base/config/config.lua and find the existing Config.AutoExecuteQuery value. This startup setting remains file-based even when /jobconfig is enabled.
2. If it is true, keep it enabled. Startup creates the new bonus table and checks/converts the bonus and log tables to InnoDB automatically. The database user needs the existing table-creation and alteration permissions. Wait for successful database initialization before using Management.
3. If it is false, keep your manual schema policy. In your database tool, select the server's game database and open the new sky_jobs_base/import.sql. Execute the ALTER TABLE sky_jobs_logs ENGINE=InnoDB statement and the complete following CREATE TABLE IF NOT EXISTS sky_jobs_bonus_payments block, including its indexes and ENGINE=InnoDB. These are the new statements between the log payment-reference indexes and sky_jobs_finance_balances. Confirm the bonus table exists and both tables report InnoDB before starting the jobs. Do not import an older SQL file or clear existing data.

No new inventory item, inventory image or streamed asset is required by Jobs Base itself. Keep existing document items and configured printers. The matching Ambulance 2.49.0 update guide includes its upright-stretcher animation and alignment steps. Follow that guide to install the animation from the Ambulance package.

Bonuses now reserve society funds once. An offline employee receives the reservation on the same character's next login; do not issue another bonus just because the employee is offline. If the menu says the payment result is uncertain, check the existing payment and society/character balances with server support before issuing a replacement. Do not delete pending reservations or replay a payment to force it through. Historical text-only finance entries remain best-effort; this update does not reconstruct old funding sources.

5. Start and check the result

Start the database, framework and configured providers, then sky_base 1.51.0, followed by sky_jobs_base 1.54.0. Wait for successful database and resource initialization before starting the installed job resources and sky_jobcreator 1.0.0 when used. Confirm the reported versions and reconnect players.

Check an existing job's members, settings, society balance and service numbers. With authorized test users, verify a small bonus to an online employee and one to an offline employee who then logs into the same character. Confirm one society expense and one recipient payment for each intent. Check a personally funded vehicle purchase or system-funded salary does not become a society expense.

Check fleet keys through the configured key provider, radial return beside an authorized empty fleet vehicle away from a garage marker, and ordinary garage parking. Open a supported Police input form, cancel it, reopen it and submit valid values. Check an active Dispatch alarm after a unit change and a moved incident's waypoint/address. Open printing from an installed job tablet and confirm unavailable items or printers produce a readable message. When using Creator, verify authorized Creator administration and separately authorized /jobconfig access. If enabling cash orders, place a small order and check the chosen payment, delivery and order history.

Open the Boss Menu's Logs page and find an existing entry with a long name or long content. Confirm the text wraps inside the table and the column headings stay aligned. Check the tablet view too if you use it. The log layout correction adds no extra setting or SQL step; it is installed with the complete new source/ folder and its interface files from this package.

If you use NPC robbery: install the matching Crime 0.14.0 update, then open /jobconfig → Crime System → Robbery → NPC pickpocketing and read Require crime job (pickpocketRequireCrimeJob) and Interaction distance (pickpocketInteractionDistance). Keep your saved choices; follow the Crime guide if you want to change them. Where public access is deliberately enabled, check on a test server with an unemployed character that the radial action can select a suitable nearby NPC in clear line of sight without exact aiming. A job-restricted setup should remain limited to its registered Crime jobs.

Optional: review recruitment and editor tools

Sky MultiJob recruitment: if Sky MultiJob is already enabled, Boss Menu invitations can now add a saved job for a nearby player who is active in another job. Acceptance keeps their current job, rank and duty selected. Existing membership in the offered job is still rejected; gang recruitment keeps its separate flow. Your configured limit remains authoritative. The unchanged shipped limit is eight non-default jobs; the default job does not consume a slot. When includeCurrentJob is enabled, an active job that is not already saved also counts.

No policy change is required. To deliberately review or change the existing policy with the configurator enabled, open /jobconfig → Jobs Base Configurator → Jobs & Storage → Multi Job, keep or change the existing enable/limit choices and save. With file-owned settings, retain Config.MultiJob in sky_jobs_base/config/config.lua; edit only an existing enabled, maxJobs or includeCurrentJob value when that change is intended, then restart. Do not add a second table or clear saved memberships.

With authorized test users and a free slot, invite a player who is active in another job. After acceptance, check the new membership in the player's existing Jobs menu, normally /jobs, and confirm their previously active job, rank and duty remain selected. Try a player at the configured limit: both sides should receive a readable full-slot message and no completed hire should appear. Keep the existing roster and use normal membership administration if a slot needs changing.

Locations and bells: open /jobconfig, select the resource and job, then Locations. Keep the existing Blip position unless you want to move it. Expand an existing location or garage group to check its saved coordinates; use Search locations when the list has more than six displayed rows. The add-entry action remains available alongside existing entries.

In Bells, choose Edit on a placed bell and review its label, sound, active state and position. Basic controls are shown directly; additional fields remain under Advanced. Use Edit position only if you want to move it. A matching visible prop is reused; an unstreamed or different model uses a temporary preview. The placement handles follow the object's own axes and centre.

On a test server, move or rotate and cancel: the saved position and original prop should remain, without a duplicate. Repeat and confirm: the new coordinates enter the draft, while the original prop returns to its old position until you choose Save. Save normally, reopen and confirm the stored result. A temporary preview should disappear when the editor closes. Existing bells and locations do not need to be placed again just to install this update.

Duty settings: keep your existing global and per-job policy. To review the job's choice, open /jobconfig, select the affected resource and job, then open General → Enable duty system. Keep the current choice unless you intend to change it; after an intended change, choose Save in the top bar. For an existing Creator job, the corresponding route is /jobcreator → Jobs → Edit the job → General → Duty → Enable duty system, followed by Save in the top bar. Check the resulting behavior against your existing global duty policy. A saved point alone does not enable a disabled global or per-job setting.

1. Back up and stop the server

These steps update sky_jobs_base from 1.52.0 to 1.53.0. Complete earlier update instructions first if you are on an older release.

1. Download 1.53.0 and extract it on your computer.
2. Back up your installed sky_jobs_base folder, custom configuration/translations and game database. Keep the backup until your checks pass.
3. Stop the server before replacing files.

Complete the Base 1.50.0 update first; its file and provider steps are separate.

2. Install the matching files

Use files from the same 1.53.0 download throughout. Paths below are inside your installed sky_jobs_base folder.

1. Delete the old source/ folder and copy the complete new source/ folder into its place, including its interface files.
2. Replace fxmanifest.lua with the matching new file.
3. Replace the complete config/locales/ folder. Transfer only your custom wording into matching new entries from your backup; retain every new key and file.

Keep existing public configuration and provider credentials. Replace the complete locale tree, including its job-configurator language packs, so every installed job receives matching new labels.

Compare the supplied config/config.lua with your backup. Keep your existing settings and provider credentials; use the settings step for the revised Dispatch defaults and optional shared channel instead of replacing the whole configured file.

3. Keep settings and configure optional features

Keep existing saved configuration. The supplied Dispatch starter defaults have changed; existing saved settings and customized file values remain authoritative. Keep Config.UseIngameConfigurator, per-resource configurator switches, provider secrets, jobs, locations, dispatch centres and permission grants. Do not run /jobconfigimport to apply ordinary fixes.

Optional — per-job service cards: open /jobconfig, select the job resource, open the specific employment job and go to General → Service badge (serviceCardEnabled). Existing and new employment jobs default to enabled; turn it off and save only for a job that should not issue a service card. In /jobcreator, the same setting is in that job’s Configuration → General. Gangs and unemployed identities do not issue service cards. The existing global document/service-card switches must also permit the feature. Turning a job’s card off preserves its saved numbers and settings and does not remove otherwise authorized inspection of another job’s card.

The new per-job switch is available through the Job Configurator. File-owned registrations retain the existing global service-card controls; adding serviceCardEnabled to their Lua job entry does not enable a per-job override. Keep the existing file-owned setup unless you deliberately migrate that resource to the configurator.

Dispatch command now follows staffed assigned units when they join, leave or disconnect. Existing self-dispatch, self-close and incident-command policies remain authoritative; no new switch or manual incident reset is required.

When linking a Creator job to a specialized resource, edit its existing profile through the ordinary job configurator. Removing that specialized link returns a Creator-managed job to its existing generic profile. Keep the job’s framework definition and data; do not delete them to perform a handover. Active Mechanic orders or deliveries must be completed before an unsafe unlink is allowed.

Check Dispatch setup: open /jobconfig, select the installed job resource, open the specific job and choose Dispatch. The setup panel now checks the saved center coverage for that job's exact internal name. If it shows Center missing, choose Open dispatch centers. Save or discard any unsaved job edits when prompted. In the existing enabled center, add that exact job name to Covered jobs, save, return to the job and reopen Dispatch to verify Center assigned. Classic map dispatch is identified separately and does not use center routing.

Covered jobs determines which departments a center may dispatch; Dispatcher jobs determines who may staff it, subject to duty, grade and permission checks. Primary jobs is an optional preference when several centers cover a call; a job can be primary in only one center and must also be covered there. A staffed center may take priority. An empty Primary jobs list leaves the center available. Every department initially receiving one incident must share an enabled center.

Optional — Shared Operations: fresh defaults now separate Police Dispatch (central_dispatch, police/sheriff) from Fire & EMS Dispatch (ems_dispatch, ambulance/fire/firefighter). Both include the channel ID DISPATCH_MAIN, shown as Shared Operations with radio memory OPS. Standard responder channels and starter response plans also include that ID. Existing working center responsibilities, custom channel lists and saved per-job overrides are kept; no reset or default import is required.

To use the common channel on an existing configured server:

1. Open /jobconfig → Jobs Base Configurator → Dispatch & Tracking → Dispatch → Centers. Open each participating center's Channels. If DISPATCH_MAIN is absent, add it with short label OPS; if it exists, keep its ID and optionally change its short label. Select that channel as the center's default and save. Preserve all other channels and access rules.
2. Open each participating job's Dispatch → Channels, including an existing Ambulance job when used. Add the same ID if missing. In the job's Dispatch settings, select it as the default channel and save. Keep existing department/tactical channels. This does not require a new Ambulance package.
3. Check any existing keyword-specific radio-channel selections: retain a deliberate department channel, or select DISPATCH_MAIN where that response should remain on shared operations after an alarm is accepted. In the Dispatch app, staff a unit and select Shared Operations; dispatchers select it in Communication. The same channel ID must be used by every participant and a working voice provider must already be configured in Base.

With Config.UseIngameConfigurator = false, preserve your existing sky_jobs_base/config/config.lua. Inside Config.Dispatch.centers, find each participating center's existing channels list. Add { id = "DISPATCH_MAIN", label = "", shortLabel = "OPS" }, only if that ID is missing; otherwise edit its existing short label. Set that center's existing defaultChannel to "DISPATCH_MAIN" only when adopting this shared default. In Config.Dispatch.groupDefaults, change the existing defaultChannel of each participating group to the same ID. Retain custom center IDs, responsibilities, dispatcher restrictions and every other field. Existing per-job channel overrides still need the matching channel; keep the server's chosen per-job configuration method. Fully restart the server after file changes. The new preset also adds sheriff to the supplied Config.Dispatch.appJobs; add your actual sheriff job name there only if it should have app access and is currently missing. This does not grant dispatcher permissions.

Do not restore Default data or run /jobconfigimport merely to obtain the new labels or shared channel: those actions replace broader saved configuration. The Dispatch guide explains the starter presets and optional shared-center arrangement.

4. Database, items and assets

No new Jobs Base SQL schema, inventory item, image or streamed asset is required. Keep saved jobs, profile IDs, society accounts/balances, role grants, memberships, service numbers, storage contents and incident history. Startup reconciles stale incident-command references through the existing tables. Do not clear those tables or recreate jobs to apply the fixes.

A template import may reuse a compatible existing account; an actual job duplicate still requires a separate account. Existing account collisions remain blocked. Independent job resources remain usable without installing Job Creator; Creator-only generic jobs and Doorlocks require Creator when used.

5. Start and check the result

Start the database, framework and configured providers, then sky_base 1.50.0 and sky_jobs_base 1.53.0. Wait for successful initialization before installed jobs and sky_jobcreator 0.2.0. Confirm Jobs Base reports 1.53.0 and reconnect players.

Switch between tablet camera/CCTV views, change a filter, return home and reopen the tablet. Check Shop/Deliveries Back and apps with the same display name. With authorized test units, confirm an incident can still be closed after its command unit leaves under your existing policy. Check an existing station/profile and its society balance. If changing service-card availability, save that job, confirm the action disappears and existing service numbers remain stored.

For Dispatch, reopen the job page and confirm its saved center coverage. Test with an on-duty responder in a virtual unit using an available FMS status, then start a new incident or mission. If adopting Shared Operations, confirm a unit and each participating dispatch desk can select the same channel through the configured voice provider.

1. Back up and stop the server

Update sky_jobs_base from 1.51.0 to 1.52.0. For an older installation, complete the intervening guides first.

1. Download 1.52.0 and extract the ZIP.
2. Back up the installed resource folder and game database outside resources/.
3. Stop the whole server in txAdmin or your hosting panel.
4. Update Base to 1.49.0 during the same maintenance. If you use Sky Mechanic, also update it to 1.38.0; the shared supply owner and the Mechanic adapter must match.

2. Install the complete runtime and support files

Inside the installed sky_jobs_base folder:

1. Delete source/ and copy the complete new source/ folder from 1.52.0 into its place.
2. Replace fxmanifest.lua and import.sql with the files from the same download.
3. Replace the complete config/locales/ folder, including the Job Configurator language packs. Transfer only your edited wording from the backup into matching new entries and keep new keys.
4. Copy config/inventory/README.md, config/inventory/chezza_restraints.lua, config/inventory/hex_restraints.lua and config/inventory/restraint_tool.png to the same paths. The hook files are optional integrations; copying them does not enable them in your inventory.
5. Keep your existing config/config.lua, jobs, item definitions and other unchanged configuration. Follow the settings step for its new options.

No streamed models need replacing for this update. The delivery props use the configured GTA models.

3. Preserve saved settings and add file-based options

Open the installed sky_jobs_base/config/config.lua and find Config.UseIngameConfigurator.

true (normal setup): keep it enabled. Existing saved settings remain, and missing new defaults are supplied automatically. No /jobconfigimport is required. Do not import the download just to obtain new settings, because that can overwrite your saved choices. The optional in-game changes below can be made after startup.

Only when Config.UseIngameConfigurator = false: open the installed sky_jobs_base/config/config.lua and make these additions. Keep every existing job, location, provider secret and other setting.

1. Find Config.Tablet = { ... }, then its apps = { ... } table. Immediately after the existing online_shop = ... entry, add online_shop_deliveries = true, if it is missing. Use false instead if you deliberately hide the new delivery app.
2. Find Config.Bells = { ... }. After that table's closing }, and before Config.Interactions = {, add this complete block if Config.OnlineShopDelivery does not already exist:

Config.OnlineShopDelivery = {
    allowsprint = true,
    openDurationMs = 5500,
    interactionDistance = 2.0,
    boxModel = "prop_cs_cardbox_01",
    carryItems = {
        enabled = true,
        storageDistance = 2.5,
        forkliftModels = { "forklift" },
        items = {},
        deliveryPallet = { enabled = true, prop = "prop_boxpile_02c" },
    },
}

3. Within the existing Config.Interactions table, find boss_menu, duty_terminal, wardrobe, storage, locker, wholesale_shop and public_forms. Add unique = false, immediately after each entry's opening { if you want more than one access point of that type. Replace an existing unique = true, instead of adding a duplicate. Keep an explicit true where a single point is intentional. Multiple storage points in the same station open the same stock.
4. The direct radio binding is optional. Find Config.JobRadial.keybinds and add this entry beside handcuff if it is absent. An empty key leaves the action unbound; change only key if you want a server default:

dispatch_radio_operate = {
    enabled = true,
    command = "sky_jobs_dispatch_radio",
    key = "",
    description = "Jobs: Operate radio"
},

5. Find the existing Config.PropPlacement = { ... } table. Immediately below its vehicleAccess = ... line, add vehicleCollectDistance = 30.0, if it is missing. Keep your existing vehicleAccess value and all other entries. This is the collection radius around the vehicle in metres; choose a value from 1 to 200 if you want a different radius. The default is 30.0.

These delivery-handling defaults apply to ordinary jobs. Mechanic keeps its own transport configuration. A job's existing onlineShopSettings now also accepts deliveryMode = "standard" for physical collection or deliveryMode = "player_inventory" for collection directly into the player's inventory. An omitted value uses physical collection. Keep the existing catalogue, collection points, delivery time and payment settings.

Existing ordinary-job online shops: an omitted delivery mode now uses physical collection. To keep collection directly into the employee's inventory, select Player inventory in the job's Online shop → Delivery mode setting after startup and save. Mechanic retains its existing mode unless you override it for the job.

Optional — configure the supply shop after startup: run /jobconfig, select the resource and job, then open Online shop. Keep existing access, catalogue and collection points. Choose Delivery mode → Physical delivery for boxes/pallets or Player inventory to put the collected order into the employee's inventory, then save. Ordinary jobs remain disabled until you enable their Online shop. The new delivery app uses the same job access. Company payment still requires the supply purchase permission.

For shared handling, open Jobs Base → Jobs & Storage → Supply delivery handling. This controls parcel opening time, pickup distance, parcel model, sprinting, storage distance, allowed forklifts, carried-item models/attachments and the delivery pallet. Save only deliberate changes. Mechanic retains its existing handling settings.

Optional — radio shortcut: open Jobs Base → Radial & Alerts → Job radial menu → Direct keybinds → Operate radio and set its key, then save. Players can set their own key in FiveM settings → Key bindings → FiveM → Jobs: Operate radio. The new default is unbound and does not replace saved player bindings.

Optional — set vehicle prop limits after startup: run /jobconfig, select the job's resource and the job, then open Vehicles. Find the existing vehicle by its spawn name. Under Prop limits, choose Add prop limit, enter a model from the job's existing Props list and set its limit. 0 disables that model for this vehicle; a model without a limit remains unlimited. Remove its limit row to make it unlimited again. Save, collect any equipment already placed from that vehicle, then park it and take it out again. New limits apply to the next vehicle spawn, not the one already outside.

Only if you maintain that job in Lua instead of /jobconfig: open the job resource's installed config/config.lua, for example sky_ambulancejob/config/config.lua. Inside Config.Jobs, find the matching job, then its vehicles list and the existing entry with the required model = .... Beside that vehicle's model line, add this complete table if propCounts is missing; if it already exists, adjust only the model keys you want to change and retain its other entries:

propCounts = {
    ["prop_roadcone02a"] = 4,
    ["prop_barrier_work05"] = 0,
},

Use model names from that job's existing prop catalogue. This example allows four cones and disables the listed barrier; omitted models stay unlimited. Existing custom per-vehicle props or trunkProps catalogues keep their explicit quantities and take precedence over propCounts. Do not remove custom catalogues during this update. Collect equipment, then park and take out the vehicle again to apply deliberate changes.

Optional — change the shared collection radius: run /jobconfig and open Jobs Base → World Interactions → Prop Placement → Collect-all radius (m). Keep the default 30 or choose 1–200, then save. This shared value measures distance from the vehicle. With Config.UseIngameConfigurator = false in Jobs Base, use the Config.PropPlacement.vehicleCollectDistance file entry described above instead.

Using Collect all: go on duty, stand beside the current job vehicle and open Radial → Vehicle interactions → Props. The selector shows remaining stock against its limit, or Unlimited; exhausted limited entries remain visible but unavailable. Collect all (count) returns that current vehicle's nearby placed equipment to its stock. Props taken from another vehicle spawn, props placed from inventory items and props outside the configured radius stay where they are. Removing one of the vehicle's props individually also returns its stock once. These vehicle-prop changes add no SQL migration or inventory item registration.

4. Update the database and check optional inventory hooks

Required database update: this version adds claim_reservations to the existing sky_mechanic_part_deliveries table so interrupted physical collection can be tracked. The historical table name is also used for ordinary jobs. Keep existing rows and order IDs.

1. In sky_jobs_base/config/config.lua, find Config.AutoExecuteQuery.
2. If it is true, do not run SQL manually. Start the updated server in the next step and wait for the database update to finish successfully.
3. If it is false, open your database tool and select the actual game database before starting the server. On MariaDB, run the new sky_jobs_base/import.sql. On MySQL, open sky_mechanic_part_deliveries in the table editor and check whether claim_reservations exists. Only if it is absent, run:

ALTER TABLE `sky_mechanic_part_deliveries`
ADD COLUMN `claim_reservations` LONGTEXT NULL;

Do not add it twice, delete orders or run clear.sql. This MySQL step applies to an already complete 1.51.0 database; older installations must complete their earlier migrations first.

Inventory: no new item registration is required for this release. Existing restraint_tool registrations remain valid. The supplied restraint_tool.png is an additional image; keep your current configured item image unless you deliberately choose to use it.

Optional — Chezza Inventory 4.3.9: after Jobs Base is installed, open that inventory's fxmanifest.lua. In its existing client_scripts list, add '@sky_jobs_base/config/inventory/chezza_restraints.lua', before client/*.lua and after its shared configuration loads. If you customized Config.isHandcuffed, transfer your additional restraint checks into the downloaded hook before enabling it. This hook also disables the original Jaksam-only trunk bridge when its owner is stopped.

Optional — Hex Inventory 1.1.7: in that inventory's fxmanifest.lua, add '@sky_jobs_base/config/inventory/hex_restraints.lua', immediately after client/os_functions.lua in client_scripts. The hook keeps the original checks and adds Sky restraint denial. Use only the hook for your inventory; no other inventory files need replacing. Neither hook requires Sky Job Creator.

5. Start and verify the installed features

1. Finish all installed resource updates. In server.cfg, start the framework, database connector and chosen providers first, then Base 1.49.0, Jobs Base 1.52.0 and the installed job resources. If used together, keep DOJ before Police and Ambulance before Crime.
2. Start the server, wait for database migration to finish and resolve the first console error before players join. Confirm Jobs Base reports 1.52.0.
3. Reconnect. Open /jobconfig and confirm your existing jobs and locations remain. Save only deliberate optional changes from the settings step.
4. Open a job's tablet and garage. If its Online shop is enabled, place a small test order, collect it using the selected delivery mode and confirm it reaches the intended inventory or authorized station storage. With Mechanic installed, check an existing order and its delivery app too.
5. Check your dispatch unit assignment and radio shortcut if used. If you enabled an inventory restraint hook, confirm a restrained player cannot open that inventory.
6. If vehicle props are enabled for the job, go on duty and take out a job vehicle. Stand beside it, open Radial → Vehicle interactions → Props, place a limited prop and check that its available count drops. Use Collect all nearby and confirm the prop disappears and the count returns. Check that another vehicle's props and any props outside the collection radius remain placed.

Keep the backup until these checks pass. Configurator saves do not install SQL, items or inventory manifest entries.

1. Back up and stop the server

Update sky_jobs_base from 1.50.0 to 1.51.0. For an older installation, follow the intervening update guides in version order first.

1. Download 1.51.0 and extract the ZIP.
2. Copy your installed sky_jobs_base folder to a backup outside the server's resources folder. Export a backup of your game database too.
3. Stop the whole server in txAdmin or your hosting panel.
4. Complete the Base update to 1.48.0 during the same maintenance. If you use Sky Mechanic, update it to 1.37.0 too.

2. Copy the new files

Open the installed sky_jobs_base folder and the new download side by side. Copy from the download into the installed folder:

1. Delete the installed source/ folder, then copy the complete new source/ folder here.
2. Delete the installed config/locales/ folder, then copy the complete new config/locales/ folder here.
3. Replace fxmanifest.lua and config/init.lua with the new files at the same paths.
4. Replace import.sql with the new copy.
5. Replace config/inventory/README.md and config/inventory/items_ox.lua with the new copies. These are reference files; copying them does not change your inventory's active item list.

Keep your other configuration files, including config/config.lua and config/printers.lua.

Only if you edited translations: copy your changed wording from the backup into the matching new language entries. Creator translations now belong in config/locales/jobconfigurator/sky_jobcreator/; the old sky_jobscreator/ locale folder must stay removed.

3. Check your settings

Open the installed sky_jobs_base/config/config.lua and find Config.UseIngameConfigurator.

• true (normal setup): keep it as it is. Saved settings are retained and new settings are supplied automatically. No configuration import is needed.
• false: find Config.Farming. If it is missing, add the following at the very end of the file, outside the other tables. If it already exists, keep your configured stations. Only if you also want the new restraint tool, copy the breakout = { ... } entry from the downloaded Config.PoliceCuffs table into that same table in your installed file; then register its item in step 4.

Config.Farming = {
    stations = {}
}

Your existing phone item setting still works. Shops, Farming points and document templates do not need to be set up to finish this update.

Only if you manually added trunkEnabled = false to a custom vehicle definition: replace that field with trunkEnabled = false, trunkPropsEnabled = false, in the same vehicle entry if vehicle props must also stay disabled. The trunk setting now controls trunk opening separately.

4. Update database and inventory

Database: in the same config/config.lua, find Config.AutoExecuteQuery and follow the matching line:

• true: no manual SQL step. Jobs Base updates the database when the server starts; wait for it to finish.
• false: before starting the server, open your database tool, select the game database and run the new sky_jobs_base/import.sql. Wait until it finishes without errors.

Keep all existing tables and orders. Do not run clear.sql.

Only if you want the new restraint tool: for ox_inventory, open the downloaded sky_jobs_base/config/inventory/items_ox.lua, copy only the complete ["restraint_tool"] entry, and insert it beside the other items inside the returned table in ox_inventory/data/items.lua. Copy sky_jobs_base/config/inventory/wire_cutter.png to ox_inventory/web/images/wire_cutter.png. For another inventory, use its item registration instructions in the supplied config/inventory/README.md.

If you do not want this tool, turn it off after startup as described in the next step. Existing printing items do not need to be registered again.

5. Start the server and check

1. Start the server. In server.cfg, keep ensure sky_base before ensure sky_jobs_base, and Jobs Base before your job resources.
2. Wait for the database update to finish. Check the server console for errors before letting players join.
3. Join the server. If you manage jobs through /jobconfig, open it and check that your existing jobs and locations are still there.
4. If Config.UseIngameConfigurator = true, open Jobs Base → Interactions → Handcuffs → Free another player. Turn Enabled off if you skipped the new tool. If you installed it, keep it enabled and test freeing another restrained player. Save any change. With the configurator disabled, leaving the new PoliceCuffs.breakout block absent keeps this feature off.
5. Check a job garage and the tablet. If you use Mechanic, open an existing supply order and confirm it is still present.

Keep the backup until these checks pass. Optional new features can be configured afterwards.

1. Prepare

These instructions cover sky_jobs_base 1.49.0 → 1.50.0. Complete applicable earlier migrations when upgrading from an older version. Back up the database, resources, custom settings/translations, document artwork, bell audio and saved jobs, grades, permissions, locations and shared /jobconfig settings. Test on staging and stop the server for replacement. Start the framework, database connector and selected inventory, keys, license, phone, banking and UI providers first, then Base 1.47.0, then Jobs Base 1.50.0 and wait for successful initialization. Start DOJ 0.5.0 before Police 1.39.0 for shared catalogue and court features, and Ambulance 2.46.0 before Crime 0.10.0 when using their medical integration. Mechanic 1.36.0 and Fire 1.18.0 follow both libraries. Treasure Hunt 1.1.0 and Pets 1.1.0 follow Base and their own listed dependencies. Install and start only resources you use.

2. Replace files

Use the complete 1.50.0 customer package. Delete the entire sky_jobs_base/source/ folder and insert the new one, then replace sky_jobs_base/fxmanifest.lua from the same download. Refresh the complete config/locales/ tree, including every jobconfigurator/ subfolder for installed consumers, while merging your translations and keeping the Base language choice.

Merge config/config.lua and server-only config/webhooks.lua, update config/init.lua, add config/player_actions.lua, and install all new config/documents/, config/postal/, config/sounds/bells/ and three stream/ files listed in Changed Files. Update import.sql and vehicle_registry.sql. Keep custom document layouts, local sounds, image URLs, provider hooks and webhook/media secrets while retaining the supplied fixes and new fields.

Document HTML, CSS, JavaScript and SVG files are editable customer files; future edits do not need a frontend build, but restart Jobs Base to reload its resource/browser cache. Tablet wallpapers and generated interfaces arrive inside the complete source replacement. Keep existing personal wallpaper choices.

Use source and manifest from the same download even with diagnostics disabled. If an older profiler package changed files outside source/, restore them from this package once and reapply intentional settings; future profiler-only updates change source Lua and the manifest.

3. Merge settings

Choose the effective settings owner. While the server is stopped, merge plaintext files and server-only secrets. Carry out the panel actions and role/unit grants in this section only after the SQL setup and the first full restart of the updated server have completed successfully. With Config.UseIngameConfigurator = true, open /jobconfig → Jobs Base and edit the saved shared sections. Their stored roots are Salary, Dispatch, Tablet, JobPlayerInteractions, LegRestraints, Nui, JobRadial, IncidentNotification, PlayerIdentityCard, Bells and Business; nested field names match the paths below. File replacement does not overwrite saved jobs or overrides. With Config.UseIngameConfigurator = false, merge these defaults in sky_jobs_base/config/config.lua instead. Use /jobconfigimport sky_jobs_base only for an intentional import of your reviewed file settings after backup; it is not a required reset and does not install SQL, sounds, models or provider secrets. Bootstrap, permissions/integration code and server-only webhook/media secrets remain file-based.

Exact config changes: “Absent” means the path was not in the previous shipped defaults. Preserve deliberate overrides rather than resetting an entire section.

Apps, images and radial settings: Merge these assignments into the existing sections for file mode; they are the new/changed values, not replacements for your complete app list:

Config.Tablet.apps.business = true
Config.Tablet.apps.training = { enabled = true, isNew = false }
Config.Tablet.apps.dispatch = { enabled = true, isNew = false }
Config.Tablet.apps.personal_notes = { enabled = true, isNew = false }
Config.Tablet.apps.crime_heist_planning = true
Config.Tablet.apps.crime_pvp_events = true
Config.Tablet.apps.crime_drug_market = true
Config.Tablet.apps.crime_drug_heat = true
Config.Tablet.apps.crime_drug_contacts = true
Config.Tablet.apps.crime_drug_business = true
Config.Tablet.apps.crime_darknet_market = true
Config.Nui.vehicleStudioImageSet = "default"
Config.JobRadial.logo = ""
Config.JobRadial.targetContext.playerToleranceRadius = 1.1
Config.JobRadial.targetContext.playerToleranceAngleDegrees = 24.0
Config.IncidentNotification.keyMappings.openMap = ""

Keep intentional app enablement choices, including enabled = false for an app you hide. The full training/dispatch/personal-notes tables above also work when your older file used a boolean app switch. Delete Config.Tablet.apps.forms_archive; Forms now contains both inbox and read-only archive. Review roles/units that previously restricted only forms_archive and apply their intended access through forms. Existing archived records are retained, and the old archive URL redirects. Crime switches require the matching installed Crime apps and their existing grants. JG Vehicle Studio is optional: when it is started, its selected stored image set is used before existing local/CDN fallbacks; no new JG installation or media secret is required to retain current images. JobRadial.logo = "" hides the logo; an HTTPS image or path relative to the shipped interface selects one, and "logo.svg" uses the supplied artwork. Target maximum distance remains 3.0. Existing personal FiveM key bindings are retained. Comment-only explanations of JobRadial.enabled and JobRadial.targetContext.enabled do not change their true defaults; supported external radial integrations retain exports, direct hotkeys and normal permissions when Sky's native UI is disabled.

Dispatch: Remove Config.Dispatch.radioKeybind; the old dispatchradio and dispatchholster commands are retired. Use the radial Radio actions to show, hide or operate the radio. Add the following values inside the existing Dispatch settings, retaining unrelated map/operation options:

Config.Dispatch.enhanced.map.nearestAvailableOnly = true
Config.Dispatch.enhanced.operations.selectCreatedIncident = false
Config.Dispatch.enhanced.operations.takeCreatedIncident = false
Config.Dispatch.enhanced.operations.suggestUnitsOnSelect = false
Config.Dispatch.enhanced.operations.recommendationStrategy = "crew"
Config.Dispatch.enhanced.operations.responsePlanMode = "full"
Config.Dispatch.postalSearch = {
    enabled = false,
    resource = "sky_jobs_base",
    file = "config/postal/oulsen_satmap_postals.json",
    entries = {}
}

Optional nearestAvailableOnly = false includes occupied units in the nearest-unit search. The three new automation switches default off; taking a new incident follows normal ownership rules and does not replace another active incident. Optional recommendationStrategy = "distance" favors nearby units. Optional responsePlanMode = "remaining" counts staffed assigned/offered units before suggesting reinforcements. Keep existing service numbers, coverage and phone provider settings.

Postal lookup defaults off. To use it, select one dataset matching your server's map in Jobs Base → Dispatch → Postal lookup; all four shipped JSON files and both license notices must be copied. Bundled maps are alternatives and are not merged. No map textures or Nearest Postal script are required, and no data is downloaded at runtime. Add custom JSON files in config/postal/, choose the resource containing that folder, save and reopen the editor to discover them. The file format is:

[
  { "code": "1000", "x": 1644.1221923828, "y": 6456.0561523438 },
  { "code": "1001", "x": 1538.3503417969, "y": 6344.6381835938 }
]

Keep codes as strings for leading zeros; optional z and label are supported. Saved manual entries override matching codes. Duplicate codes use the last row with a warning. Files are limited to 8 MiB / 20,000 rows. Restart Jobs Base after editing the selected file.

Payroll: Add the two new shared defaults:

Config.Salary.useGradeIntervals = true
Config.Salary.jobSocietyPayments = {}

Keep your existing enabled state, account, amount and interval choices. useGradeIntervals = false uses the global default interval; an explicit per-job interval still takes precedence. jobSocietyPayments maps the exact job name to true for a society-funded payout or false for server-created money. Under a non-gang job's Payroll extension, the new stored default is:

payrollSettings = {
    intervalMinutes = 0,
    fundingMode = "inherit",
}

0 inherits the global/rank interval. Optional funding modes "society" and "server" override inherited funding. This is saved job data, not another global config table to paste over existing jobs. Review each rank's actual Sky salary: a missing Sky salary now means 0 rather than silently falling back to the framework's salary. Import native amounts only through an explicit job-definition takeover after reviewing them. Payroll currency expects a configured currency key such as bank, not a currency symbol; display formatting follows Base currency settings. Native framework pay remains separate. Native funding overrides require an already installed compatible framework paycheck hook; updating Jobs Base or adding the map alone does not install that hook or change native paycheck timing.

Player actions and leg restraints: Add the new shared action defaults:

Config.JobPlayerInteractions.groups.police.identity = true
Config.JobPlayerInteractions.groups.police.licenses = true
Config.JobPlayerInteractions.groups.crime.identity = true
Config.JobPlayerInteractions.groups.crime.licenses = true

Keep existing job/rank/duty restrictions and per-job enabled/minimum-grade settings. Nonvoluntary identity/license inspection requires an authorized actor and a restrained target within the allowed distance and routing bucket. Voluntary showing and viewing your own documents remain character-bound. Saved playerInteractions.identityRequireAcceptance and .licensesRequireAcceptance are retired; delete those paths from custom job data/imports. Old license:<type> action flags no longer choose which held licenses appear: use PlayerIdentityCard.licenseTypes below. Carry's consent setting remains. Install config/player_actions.lua to retain the supplied native, jsfour, UM and Qbox document integration hooks; merge intentional custom hooks and preserve each provider's authorization/items.

Delete Config.LegRestraints.applyScenario and merge the complete replacement block, keeping your deliberate item, distance and duration values:

Config.LegRestraints = {
    enabled = true,
    requireItem = false,
    item = "legcuffs",
    useItem = "radial",
    maxDistance = 2.0,
    requireCuffed = true,
    animDict = "anim@amb@clubhouse@tutorial@bkr_tut_ig3@",
    animName = "machinic_loop_mechandplayer",
    applyDurationMs = 1600
}

Bells and Business: Add both complete new shared blocks:

Config.Business = {
    enabled = true,
    durationSeconds = 8,
    cooldownSeconds = 300,
    position = "top-center",
    maxPending = 3,
    announceExclusionZones = true,
    discord = {
        publicEnabled = false,
        adminEnabled = false,
    },
}
Config.Bells = {
    enabled = true,
    keyMappings = { accept = "Y", dismiss = "RETURN" },
    requestCooldown = 30,
    customSounds = {},
}

No bell appears until one is placed. In a non-gang job's Bells extension, the new default bells = {} permits up to 32 configured placements. Choose the desk/wall model, preset/custom sound and recipients (nearby players, employees or both). Staff requests use Y to accept a waypoint and Enter to dismiss by default; personal bindings, request cooldowns and death/cuff/busy checks still apply. Copy custom OGG/WAV/MP3 files under config/sounds/bells/custom/, add a unique ID, label, local path and actual duration between 0.1 and 15 seconds in Jobs Base → Bells → Custom sounds, then restart Jobs Base. Example optional catalogue:

Config.Bells.customSounds = {
    { id = "reception", label = "Reception", file = "config/sounds/bells/custom/reception.ogg", duration = 2.0 },
}

Config export/import transfers the catalogue, so copy the audio files separately. Personal bell/business notification placement is available in tablet settings and /notifications.

In a non-gang job's Business extension, add/review this new stored default:

businessSettings = {
    statusEnabled = false,
    announcementsEnabled = false,
    requireOnDuty = true,
    imageUrl = "",
    openColor = 2,
    closedColor = 1,
    openSprite = 0,
    closedSprite = 0,
    closedAlpha = 180,
}

Both staff actions default disabled. Enable only the desired job actions and grant existing roles/units Business status (permission 34) or Business announcements (permission 35); keep existing grants. Opening state persists without an additional Business table. Optional announcements respect exclusion zones and retain their history.

In server-only sky_jobs_base/config/webhooks.lua, the previously absent Webhooks.businessAnnouncements now defaults to:

Webhooks.businessAnnouncements = {
    public = "",
    admin = "",
}

Add it without replacing existing media/provider secrets. Discord outputs default off in Config.Business.discord; enable the desired public/admin output in the effective Jobs Base settings and privately set its matching URL in this file, then restart. Use different webhook IDs for the public and private admin channels. Public messages omit staff admin data and suppress mentions. Failed Discord delivery does not undo an in-game announcement; empty URLs do not establish working delivery.

Document cards: Add the complete new shared card defaults:

Config.PlayerIdentityCard = {
    enabled = true,
    serviceEnabled = true,
    position = "right",
    x = 75,
    y = 50,
    scale = 85,
    issuer = "",
    logo = "",
    licenseTypes = { "dmv", "drive", "drive_bike", "drive_truck", "driver", "weapon", "business" },
    serviceCards = {
        { job = "police", template = "official", background = "matte", color = "#3177b7", logo = "", title = "", prefix = "PD", format = "{prefix}-{number}", digits = 3 },
        { job = "ambulance", template = "medical", background = "matte", color = "#bf465b", logo = "", title = "", prefix = "EMS", format = "{prefix}-{number}", digits = 3 },
        { job = "mechanic", template = "compact", background = "matte", color = "#a36a24", logo = "", title = "", prefix = "MECH", format = "{prefix}-{number}", digits = 3 },
        { job = "fire", template = "official", background = "matte", color = "#b84732", logo = "", title = "", prefix = "FD", format = "{prefix}-{number}", digits = 3 },
        { job = "doj", template = "official", background = "matte", color = "#775487", logo = "", title = "", prefix = "DOJ", format = "{prefix}-{number}", digits = 3 },
        { job = "*", template = "official", background = "matte", color = "#3e6770", logo = "", title = "", prefix = "", format = "{prefix}-{number}", digits = 3 }
    }
}

Exact job names take priority over "*"; review the shipped "fire" name against your actual job. Set your issuer, artwork, card position and department format in the effective shared settings. The listed license types show only held licenses; optional licenseTypes = { "*" } includes all held types. Managers assign/change persistent service numbers through employee management using the existing member-management permission; no new service-number permission is required. Keep document renderer/artwork files together, and preserve custom edits.

Interaction object rotation: For each existing Config.Interactions.<type>.object, add pitch = 0.0 and roll = 0.0. The sixteen exact types are job_garage, garage_vehicle_spawn, garage_vehicle_park, garage_helicopter_menu, garage_helicopter_spawn, garage_helicopter_park, garage_boat_menu, garage_boat_spawn, garage_boat_park, boss_menu, duty_terminal, wardrobe, storage, locker, wholesale_shop and public_forms. The full default object subtable is:

object = {
    enabled = false,
    model = "",
    pitch = 0.0,
    roll = 0.0,
    heading = 0.0,
    offset = vector3(0.0, 0.0, 0.0)
}

Keep each location's enabled/model/heading/offset, marker, blip and NPC choices. Old heading-only objects remain upright. Install Base 1.47.0 together with Jobs Base 1.50.0 for full placed-object rotation. config/init.lua also reloads the existing restaurant locale packs; there is no new language setting.

Optional profiling remains disabled by default. To enable it for a support investigation, put setr sky_profiler 1 in server.cfg before the Sky ensure lines and perform a full server restart. Start a recording manually with profiler record 1000, wait until profiler status reports completion, then run profiler saveJSON sky-release-20261014.json; choose a new filename for every capture. Disable it with setr sky_profiler 0 followed by another full server restart. This is not a /jobconfig value, and neither recording nor upload starts automatically.

4. Database, items and assets

SQL: Back up first. The existing automatic Jobs Base migration creates four additional tables: sky_jobs_service_card_settings, sky_jobs_service_numbers, sky_jobs_vehicle_temporary_registrations and sky_jobs_vehicle_registration_payments. Keep your current migration policy and confirm successful migration/readiness before using the features. If automatic migration is intentionally unavailable, open your database manager, select the database used by this FiveM server, open its SQL/query editor, and execute these four additive statements from the matching new import.sql before starting the updated resource:

CREATE TABLE IF NOT EXISTS `sky_jobs_service_card_settings` (
    `job` VARCHAR(64) NOT NULL,
    `settings_json` TEXT NULL,
    `revision` INT UNSIGNED NOT NULL DEFAULT 0,
    `next_number` BIGINT UNSIGNED NOT NULL DEFAULT 0,
    PRIMARY KEY (`job`)
) ENGINE=InnoDB;
CREATE TABLE IF NOT EXISTS `sky_jobs_service_numbers` (
    `id` BIGINT UNSIGNED NOT NULL AUTO_INCREMENT,
    `job` VARCHAR(64) NOT NULL,
    `identifier` VARCHAR(128) NOT NULL,
    `service_number` BIGINT UNSIGNED NOT NULL,
    PRIMARY KEY (`id`),
    UNIQUE KEY `uq_service_character` (`job`, `identifier`),
    UNIQUE KEY `uq_service_number` (`job`, `service_number`)
) ENGINE=InnoDB;
CREATE TABLE IF NOT EXISTS `sky_jobs_vehicle_temporary_registrations` (
    `vehicle_id` CHAR(36) NOT NULL,
    `holder_identifier` VARCHAR(128) NOT NULL,
    `remaining_seconds` INT UNSIGNED NOT NULL,
    `playtime_seconds` BIGINT UNSIGNED NOT NULL,
    `document_id` CHAR(36) NOT NULL,
    `document_version` INT UNSIGNED NOT NULL DEFAULT 1,
    `issued_at` BIGINT UNSIGNED NOT NULL,
    PRIMARY KEY (`vehicle_id`),
    UNIQUE KEY `uniq_temporary_document` (`document_id`)
) ENGINE=InnoDB;
CREATE TABLE IF NOT EXISTS `sky_jobs_vehicle_registration_payments` (
    `operation_id` CHAR(36) NOT NULL,
    `holder_identifier` VARCHAR(128) NOT NULL,
    `amount` INT UNSIGNED NOT NULL,
    `state` VARCHAR(24) NOT NULL,
    `updated_at` BIGINT UNSIGNED NOT NULL,
    PRIMARY KEY (`operation_id`)
) ENGINE=InnoDB;

The matching vehicle_registry.sql contains the two registration tables but does not install the service-card tables. Do not drop/reset existing jobs, registry records, forms, grants or documents. No charset/collation override or data-clearing migration is required; the new tables inherit your active database settings. The existing oxmysql/InnoDB transaction path is required for service-number allocation and registration payment claims. /jobconfig does not create the tables.

Items and document images: Jobs Base introduces no mandatory inventory item or inventory image. Existing tablet, cuffs, leg-restraint and printing items keep their existing definitions. Optional native/third-party document providers need their own existing item/template setup. Install the complete editable document files and SVG artwork listed in Changed Files, retaining custom layouts and configured logo URLs.

Bell assets and postal data: Install all seven bundled OGG presets, their provenance.json, custom/README.md, and the three stream/sky_job_bells.ytyp, stream/sky_job_deskbell.ydr, stream/sky_job_doorbell.ydr files with the matching manifest. Bell placements are world locations, not new inventory items. Copy custom audio files separately from saved config exports. Install all four complete postal JSON datasets, their README and both license notices; select the dataset matching your map. No external map texture pack or postal script is bundled.

Optional citizen-office registration: This release supplies integration support, not a bundled citizen-office app or physical paper item. Use it only when a trusted server integration explicitly registers its authority and the existing Mechanic vehicle-inspection and registration features are enabled. No new config flag automatically enables that authority, and classic workshop registration remains when none is registered. In authority mode, a valid KUV inspection is required even if the optional workshop check is disabled. The integration owns document items, inventory capacity, presentation and xnPlates setup. Temporary permits default to 259,200 online seconds of the holder character, including parked vehicles; offline time pauses. Replacement papers do not extend the budget, ownership transfer preserves remaining time, and expired permits remain expired. Previously permanent registrations require transfer rather than a fresh temporary permit. Preserve the vehicle identity and inspection/history records. Reconcile unconfirmed payments/refunds against the actual bank ledger before retrying; never delete pending payment claims to force a repeat.

5. Restart and check

Perform a full server restart to load new file lists, sounds and streamed assets, then reconnect clients. Start the framework, database connector and selected inventory, keys, license, phone, banking and UI providers first, then Base 1.47.0, then Jobs Base 1.50.0 and wait for successful initialization. Start DOJ 0.5.0 before Police 1.39.0 for shared catalogue and court features, and Ambulance 2.46.0 before Crime 0.10.0 when using their medical integration. Mechanic 1.36.0 and Fire 1.18.0 follow both libraries. Treasure Hunt 1.1.0 and Pets 1.1.0 follow Base and their own listed dependencies. Install and start only resources you use. Confirm the installed versions, all four additional tables, successful Jobs Base initialization and the first database/provider error before gameplay checks. Library restarts can stop dependent resources; restore previously used dependents in the same order.

After SQL setup and this first successful restart, open /jobconfig and verify preserved jobs, grades, locations, grants and effective shared overrides. Test one opt-in bell for nearby/employees recipients, Y waypoint acceptance, Enter dismissal, cooldowns, custom audio and removal. Enable Business only for a test job and authorized roles; verify duty restrictions, opening/closed blips, announcement history and exclusion zones. If you enabled Discord output, test the actual public/private channels separately; check secrets remain server-only.

Test identity/license inspection on both an allowed restrained target and a denied unrestrained target, voluntary showing, current character ownership and a service card with a persistent number after reconnect. Check customized card layouts at your actual FiveM resolution; browser previews do not prove CEF behavior. Verify an authorized manager can assign a unique department number. Check nested radial actions, cuff hotkeys, target changes while holding the menu, full prop rotation and placement confirm/cancel cleanup.

For Dispatch, verify radio show/hide/operate through the radial menu, incident creation/selection/ownership, preserved vehicle selection during background updates, nearest/response recommendations and actual phone call closure. Test a known/unknown postal code only if lookup was enabled, using the chosen map. Change shift or save settings and confirm existing incidents are not announced again. Check Forms inbox/archive access and drug-test changes while retaining a draft/selection; verify matching Crime apps and their permissions when installed.

Check every rank's actual Sky salary and one intended interval/funding choice without duplicating native framework pay. Test nearby invoice recipients with your chosen billing provider; a submitted invoice is not proof of payment. Known rejections should remain visible, while uncertain provider outcomes require ledger reconciliation before retrying. Test retrieval/storage for a real saved vehicle with an eight-character/spaced plate; keep its original record and correct any reported collision instead of rewriting all plates.

If a trusted registration integration is installed, test inspection, a parked vehicle's registration, paper replacement, sale/transfer, remaining online budget and confirmed fee handling. Check expiry and permanent transfer without resetting vehicle history. Standard resource/source checks do not establish third-party document, bank, billing, xnPlates, QB/Qbox or multiplayer acceptance; verify the providers actually used by your server.

1. Prepare

These instructions cover sky_jobs_base 1.48.1 → 1.49.0. Complete applicable earlier migrations when upgrading from an older version. Back up the database, resources, framework files, custom configuration/translations and saved /jobconfig/Creator data. Test on staging and stop the server for replacement. Install the coordinated versions for your installed resources. Start the framework, database connector and selected inventory, phone, banking and UI providers first, then Base 1.46.0 and Jobs Base 1.49.0. Start DOJ 0.4.0 before Police 1.38.0 for their shared catalogue and court workflows. Start Ambulance 2.45.0 before Crime 0.9.0 when using their medical integration. Mechanic 1.35.0 and Fire 1.17.0 follow both libraries. Include only installed resources.

2. Replace files

Use the complete 1.49.0 customer package. Delete the entire sky_jobs_base/source/ folder and insert the new one, then replace sky_jobs_base/fxmanifest.lua from the same package. Refresh the complete sky_jobs_base/config/locales/ tree and merge custom translations. Preserve your selected language. Do not restore an older bootstrap or merge generated interface files.

Merge config/config.lua, add config/images/duty/employee_card.svg and update its accompanying README.md. Refresh the complete config/locales/ tree, including jobconfigurator/ subfolders for every installed consumer; their configurator text is supplied by Jobs Base. Keep custom duty images and configured image URLs.

Deploy Ambulance 2.45.0 together with Jobs Base 1.49.0: hospital-bed Respawn labels now belong to Jobs Base's config/locales/jobconfigurator/sky_ambulancejob/ packs.

3. Merge settings

When Config.UseIngameConfigurator = true, saved /jobconfig settings take precedence over the plaintext defaults. Change the effective values in /jobconfig; copying config files does not replace saved jobs, grades, locations or overrides. Keep the saved data and do not reset the configurator. Use /jobconfigimport sky_jobs_base only if you intentionally want to import your edited plaintext configuration, after backing up and reviewing its replacement scope. With Config.UseIngameConfigurator = false, merge the settings into the supplied config files instead.

Existing job behaviour is retained unless you enable a new action. Open /jobconfig, select the linked job and its Player interactions extension (playerInteractions). All new actions default off; requireOnDuty defaults true for jobs, each enabled action's <action>MinGrade defaults 0, and carryRequireAcceptance, identityRequireAcceptance and licensesRequireAcceptance default true. Select each permitted license:<type> explicitly; these default false. Gangs do not gain job duty or billing settings. Search and confiscation are separate switches. Retain existing Police/Crime permissions; this editor adds explicit access for the selected linked group.

Per-job Duty system (dutySystemEnabled) defaults enabled under the resource's existing global duty policy. Disabling it keeps the capable group's members on duty and hides its duty terminals; saved off-duty aliases and locations remain. It cannot override a disabled global duty system. In location appearance, retain inherited defaults or set explicit Marker, Blip, NPC and Object values. Appearance changes do not grant access or change public/duty rules.

Global appearance is under /jobconfig → Jobs Base → Interactions. Config.Interactions.<type>.object is new for job_garage, garage_vehicle_spawn, garage_vehicle_park, garage_helicopter_menu, garage_helicopter_spawn, garage_helicopter_park, garage_boat_menu, garage_boat_spawn, garage_boat_park, boss_menu, duty, wardrobe, storage, locker, wholesale_shop and public_forms. Each defaults to:

object = {
    enabled = false,
    model = "",
    heading = 0.0,
    offset = vector3(0.0, 0.0, 0.0)
}

For plaintext mode, add the block to the corresponding existing Config.Interactions entry, preserving its marker, blip and NPC settings. No props are enabled by this update. Existing custom renderers retain their own behaviour. Keep dispatch service numbers, centre coverage, selected phone provider and saved access settings.

Optional profiling remains off by default. If support requests it, put setr sky_profiler 1 before the Sky ensure lines in server.cfg, perform a full server restart, run profiler record 1000, wait for profiler status to show completion, then run profiler saveJSON sky-release-20261008.json with a new filename for each capture. Disable it with setr sky_profiler 0 and another full server restart. This is not a /jobconfig setting; no recording or upload starts automatically.

4. Database, items and assets

SQL: No new Jobs Base table, column or manual migration in this release. Preserve job settings, assignments, duty state, documents, locations and stored grants. Items: No new items. Assets: Add the supplied config/images/duty/employee_card.svg; configured custom cards keep their priority. Optional props require their configured models. No map or streamed-model replacement is required.

5. Restart and check

Perform a full server restart to reload changed manifests and file lists, then reconnect clients. Start the framework, database connector and selected inventory, phone, banking and UI providers first, then Base 1.46.0 and Jobs Base 1.49.0. Start DOJ 0.4.0 before Police 1.38.0 for their shared catalogue and court workflows. Start Ambulance 2.45.0 before Crime 0.9.0 when using their medical integration. Mechanic 1.35.0 and Fire 1.17.0 follow both libraries. Include only installed resources. Check actual installed versions and the first startup/database error before testing.

Reopen /jobconfig and confirm saved jobs, grades and locations. On staging, enable one linked-job action and test allowed and denied grades, duty, consent refusal and disconnect/character change. Both carry participants can use /cancelcarry or ESC to set down; also check pause-menu behaviour on your client. Check identity and only the enabled licence types, inspection-only search and the selected invoice recipient. Confirm per-job duty control and an inherited/overridden location appearance, including removal cleanup. Place and accept a real dispatch call using your selected provider; reopen the incident from its notification. Check normal folders while shared documents load and preserve a draft through a deadline update.

Open a job or creator entry, choose a tab, close /jobconfig and reopen it. Confirm the remembered available view loads current data. Navigation is kept for the current NUI session; it does not save an unsaved draft or survive a resource restart.

1. Prepare

These instructions cover sky_jobs_base 1.48.0 → the refreshed 1.48.1 package. If you installed an earlier 1.48.1 download today, download the current 1.48.1 package again and apply these steps. The manifest version stays the same, so the version number alone does not identify the refreshed package. Back up resources, the database, custom configuration, translations and saved Job Configurator/Creator data. Validate on staging and stop the server for replacement. Install the refreshed Base 1.45.1, then Jobs Base 1.48.1, then the matching updates for your installed jobs and Crime. Complete earlier migrations first when upgrading from an older version.

2. Replace files

Use the complete 1.48.1 package. Delete the entire sky_jobs_base/source/ folder and insert its new version, then replace sky_jobs_base/fxmanifest.lua from the same package. Do not merge old generated interface files. Refresh the complete sky_jobs_base/config/locales/ tree and merge custom translations. Keep your existing selected language in sky_base/config/config.lua.

The dependency bootstrap ships as an editable file. Use the supplied file; do not restore an older custom bootstrap. Base also keeps its callback files editable for support. Install the source and manifest together.

3. Merge settings

No new Jobs Base plaintext configuration keys or defaults are introduced. Keep existing jobs, grades, locations and saved overrides; no reset or configuration re-import is required. /jobconfig does not replace runtime files, install schema or reload changed manifests.

The refreshed Mechanic 1.34.1 supplies the global vehicle price settings vehiclePriceSource = "auto", vehiclePriceTable = "vehicles", vehiclePriceModelColumn = "model", vehiclePricePriceColumn = "price" and vehiclePriceHashColumn = "", at Mechanic Jobs → General → Database. Its new feature tuningFreeCamera defaults to true, at Mechanic Jobs → Features → Free camera in tuning menu. Jobs Base supplies these controls' translations; the matching Mechanic runtime and configuration must also be updated. Use the complete Mechanic 1.34.1 update instructions for the plaintext blocks, price hook and existing saved overrides.

The refreshed Crime 0.8.1 adds resource-wide laboratory limits, at Crime System → Drug System → General: drugMaxLaboratoriesPerCharacter = 0 and drugMaxLaboratoriesPerFaction = 0; 0 means unlimited. Jobs Base supplies the translated labels. Install the matching Crime runtime and follow the complete Crime 0.8.1 update instructions for its plaintext block and saved overrides. New controls alone do not install either resource's behaviour.

The existing Mechanic Jobs → Parts Delivery Shop → Delivery handling selector is restored. Its setting remains partsDeliveryMode; without /jobconfig, retain Config.PartsDelivery.deliveryMode in sky_mechanicjob/config/config.lua ("standard" or "player_inventory"). The shipped default remains "standard". Saved overrides remain authoritative when enabled.

Optional diagnostics are disabled by default. If support requests a recording, put setr sky_profiler 1 before the Sky ensure lines in server.cfg, restart the server, run profiler record 1000, wait for profiler status to show completion, then run profiler saveJSON sky-startup-hotfix.json. Disable with setr sky_profiler 0 and another full server restart. This is not a /jobconfig setting; no recording or upload starts automatically.

4. Database, items and assets

SQL: No new table, column or manual SQL update is introduced by this patch. Existing failed migrations still need their original database error repaired; continuing startup does not create a missing schema. Keep the existing automatic/manual migration policy. Do not replay a full import, clear tables, force success markers or reset saved job/Creator data. Items: No new definitions or inventory registrations. Assets: No new item images, models or stream assets; keep existing assets. Earlier release requirements still apply for older installations.

5. Restart and check

Perform a full server restart after replacement so the changed manifests and file lists are reloaded. Start the framework, database connector and selected providers first, then Base 1.45.1, Jobs Base 1.48.1 and the installed consumers. Unrelated clothing, vehicle and map packs can remain after Sky in server.cfg. Reconnect clients. Open /jobconfig, check saved settings and an installed job. For Mechanic, open Parts Delivery Shop and confirm the Delivery handling selector shows your saved mode. A long dependency wait now continues until initialization completes; it no longer aborts at 60 seconds. Database migration warnings remain actionable, and failure to read saved settings remains a visible initialization error. Collect the first error, preceding lines and actual installed versions if a feature remains unavailable. On staging, create and duplicate a temporary job and confirm it can be saved with its own locations and access settings. Check deletion of a temporary standalone creator entry without deleting an existing production location. Open the phone emergency form, check service selection, required-message validation and unavailable-service feedback. For a permitted staging report, confirm success feedback and that text entered while submission is pending is retained. Check the matching Mechanic and Crime configurator controls in your selected language and confirm saved choices remain after reopening.

1. Prepare

These instructions cover sky_jobs_base 1.47.1 → 1.48.0. Before replacing files, confirm that your customer download platform provides the versions below and check each downloaded resource's fxmanifest.lua; published documentation or a source tag alone does not establish that its customer download has been uploaded. Complete earlier migrations first if upgrading from an older version. Back up the database, resources, custom config, translations and saved Job Configurator/Creator data. Validate the update on staging before applying it to your production server. Stop the server during replacement. Install Sky Base 1.45.0, then Sky Jobs Base 1.48.0, then the matching releases for your installed jobs and Crime. Keep provider dependencies and optional integrations compatible; preserve saved overrides and existing records.

2. Replace files

Use the complete 1.48.0 release package. Delete the entire sky_jobs_base/source/ folder and insert its new version; do not merge old generated interface files. Replace sky_jobs_base/fxmanifest.lua from the same package. Refresh the complete sky_jobs_base/config/locales/ tree and merge your custom translations into the new files. Keep your selected shared language in sky_base/config/config.lua. Install the following shipped paths from that package, merging custom configuration into the updated public files rather than restoring old complete files:

• sky_jobs_base/config/config.lua
• sky_jobs_base/config/init.lua
• sky_jobs_base/config/inventory/README.md
• sky_jobs_base/config/item_containers.lua
• sky_jobs_base/config/locales/*
• sky_jobs_base/fxmanifest.lua
• sky_jobs_base/import.sql
• sky_jobs_base/source/* — delete and reinsert

3. Merge configuration

Jobs Base uses saved /jobconfig settings and shipped defaults while Config.UseIngameConfigurator = true. Saved overrides are retained. Manage the shared changes in Jobs Base inside /jobconfig; changing managed values only in config.lua does not replace saved values in this mode. If you intentionally work from files, set Config.UseIngameConfigurator = false in sky_jobs_base/config/config.lua and restart; saved settings are retained for later use. To deliberately import your plaintext shared settings into the saved configuration, review those values and use /jobconfigimport sky_jobs_base; this is an explicit replacement/import action, not a required automatic step for every update.

In sky_jobs_base/config/config.lua, Config.Billing did not exist in 1.47.1. Add this complete new table when maintaining an existing plaintext config:

Config.Billing = {
    enabled = true,
    command = "billing",
    openKey = "",
    defaultCurrency = "bank",
    depositToSociety = true,
    requireOnDuty = true,
    maxAmount = 1000000,
    range = 6.0,
    paymentTermDays = 7,
    autoPayOverdue = true,
    onsiteTimeoutSeconds = 120,
    installmentPlans = {},
    employeeShares = {},
}

With /jobconfig enabled, the key is Billing at Jobs Base → Administration → Billing. The new fields are enabled=true, command="billing", openKey="", defaultCurrency="bank", depositToSociety=true, requireOnDuty=true, maxAmount=1000000, range=6.0, paymentTermDays=7, autoPayOverdue=true, onsiteTimeoutSeconds=120, installmentPlans={} and employeeShares={}. Missing saved Billing fields receive these defaults. Plans and employee shares enable no jobs by default; add approved jobs deliberately. New invoice deadlines and percentages do not change the terms already stored on existing invoices. Command/key changes require a resource restart, and existing personal FiveM key bindings remain saved.

In the same file:

• Config.HeadBag.useItem changes from "inventory" to "both". In /jobconfig, edit key HeadBag.useItem under Jobs Base → Interactions → Head bag if you want that new default. Existing saved "inventory" overrides stay as they are.
• Config.StationBlip.useBlipPrefix is new; add useBlipPrefix = true, inside the existing StationBlip table. The /jobconfig key is StationBlip.useBlipPrefix, labelled Show blip prefix. false hides the prefix while keeping the configured label saved.
• Config.Dispatch.centers[1].restrictToDispatcherJob (center central_dispatch) and Config.Dispatch.centers[2].restrictToDispatcherJob (center ems_dispatch) are new. Add restrictToDispatcherJob = true, beside each center's enabled field. The /jobconfig key is Dispatch.centers.<entry>.restrictToDispatcherJob, labelled Restrict to own job. Saved centers that omit the field inherit true from the new defaults. Set it explicitly to false for each center intended to coordinate multiple departments, and review its dispatcher/covered job lists. In plaintext mode a custom center that omits the field is not restricted; the bundled centers now explicitly set it to true.
• Config.AutoExecuteQuery remains true; only its ownership/comment changed. It is now exclusively a startup value in this file, in both configurator modes. The old AutoExecuteQuery / Database Setup setting is removed from /jobconfig and import/runtime application. Existing saved overrides are ignored and disappear on the next settings write. Keep the plaintext value you require and restart after changing it.
• The new comments describing gang:<internal_name> in activity and prop access lists change accepted selector guidance, not the shipped list values. Existing job/group selectors remain valid.

In sky_jobs_base/config/item_containers.lua, the first item sky_briefcase gains the file-based value Config.ItemContainers.items[1].hiddenByDefault = true; it was absent before. Add hiddenByDefault = true, beside autoShowWhenOwned = true,. Keep autoShowWhenOwned as true: after an explicit Show it still follows inventory ownership. Visibility resets to hidden for the next character session. This container configuration is not a /jobconfig setting.

Replace sky_jobs_base/config/init.lua from the same release download. It reuses already loaded language packs and loads the optional Jobs Creator configuration locale pack; it introduces no user option. Update the complete sky_jobs_base/config/locales/* folder, including all Job Configurator packs. Hungarian was already included before this release.

Bootstrap, permissions, Lua callbacks/metadata and provider secrets remain file-based. sky_jobs_base/config/webhooks.lua and config/printers.lua have no net changes in this release; retain your existing secrets and settings. Update config/inventory/README.md for the new briefcase visibility instructions. No current item definition needs a rename or reset.

The save protection, shutdown and update-routing changes introduce no additional plaintext settings, Job Configurator keys, default values or saved-override migrations. Replace config/init.lua to install the matching server and client locale loader, and replace the Job Configurator locale packs to install the save-in-progress and save-rate messages. The existing configured language is retained. Existing Job Configurator values remain with their current resource and saved revision. Saved Job Configurator values must still be reviewed separately from file defaults. Install the complete generated frontend and source package together; copying Lua alone does not install the Save controls. The optional Creator consumes the same stores but remains a separately unreleased product.

Optional diagnostics are disabled by default. If support requests a recording, put setr sky_profiler 1 before the Sky ensure lines in server.cfg, then restart the server. Run profiler record 1000, wait for profiler status to show that recording has completed, then run profiler saveJSON sky-release-profile.json. Disable diagnostics with setr sky_profiler 0 and another server restart. This is not a /jobconfig setting; no recording or upload starts automatically.

For an older explicit profiler package, replace any previously modified public config/provider/compatibility files with the supplied versions and merge your intentional customizations. In this release package, profiler preparation preserves all files outside source/ byte for byte except fxmanifest.lua; the functional config changes listed in this guide still require their own merge.

4. Data, items and dependencies

SQL: Back up the active database and select the same database used by the server. Choose exactly one route: automatic setup with Config.AutoExecuteQuery = true, or the manual block for your database engine with Config.AutoExecuteQuery = false. Do not run both manual dialects or repeat the manual update after successful automatic setup. This plaintext switch in sky_jobs_base/config/config.lua applies independently of /jobconfig mode.

Automatic route. Allow the startup migration to finish. It creates sky_jobs_invoices, adds department ownership to Dispatch audit/map/call/chat records and ensures InnoDB for the Dispatch map table. No manual SQL is needed for this route.

Manual route - MariaDB. With automatic setup disabled and job resources stopped, apply this complete targeted block to the selected server database. The new invoice table did not exist in release 1.47.1. The block creates it without seeding invoices and adds the new Dispatch columns; existing data and the database's charset/collation remain. Do not run unrelated historic import/seed operations. The ADD COLUMN IF NOT EXISTS syntax in this retained block is specific to MariaDB.

CREATE TABLE IF NOT EXISTS `sky_jobs_invoices` (
    `id` BIGINT UNSIGNED NOT NULL AUTO_INCREMENT,
    `reference` VARCHAR(128) NOT NULL,
    `issuer_type` VARCHAR(16) NOT NULL,
    `job_name` VARCHAR(64) NOT NULL DEFAULT '',
    `job_label` VARCHAR(120) NOT NULL,
    `account` VARCHAR(128) NOT NULL DEFAULT '',
    `issuer_identifier` VARCHAR(128) NOT NULL DEFAULT '',
    `issuer_name` VARCHAR(120) NOT NULL,
    `actor_name` VARCHAR(120) NOT NULL,
    `actor_identifier` VARCHAR(128) NOT NULL DEFAULT '',
    `employee_share_percent` TINYINT UNSIGNED NOT NULL DEFAULT 0,
    `employee_share_paid` INT UNSIGNED NOT NULL DEFAULT 0,
    `employee_share_phase` VARCHAR(24) NULL,
    `employee_share_pending` INT UNSIGNED NULL,
    `employee_share_next_attempt_at_ts` BIGINT NOT NULL DEFAULT 0,
    `payment_mode` VARCHAR(16) NOT NULL DEFAULT 'later',
    `due_at_ts` BIGINT NOT NULL DEFAULT 0,
    `installment_count` TINYINT UNSIGNED NOT NULL DEFAULT 1,
    `installment_interval_days` SMALLINT UNSIGNED NOT NULL DEFAULT 0,
    `installment_start_at_ts` BIGINT NOT NULL DEFAULT 0,
    `next_attempt_at_ts` BIGINT NOT NULL DEFAULT 0,
    `collection_failure_code` VARCHAR(32) NOT NULL DEFAULT '',
    `collection_failed_at_ts` BIGINT NOT NULL DEFAULT 0,
    `reminder_at_ts` BIGINT NOT NULL DEFAULT 0,
    `recipient_type` VARCHAR(16) NOT NULL,
    `recipient_job` VARCHAR(64) NOT NULL DEFAULT '',
    `recipient_identifier` VARCHAR(128) NOT NULL DEFAULT '',
    `recipient_name` VARCHAR(120) NOT NULL,
    `reason` TEXT NOT NULL,
    `amount` INT UNSIGNED NOT NULL,
    `amount_paid` INT UNSIGNED NOT NULL DEFAULT 0,
    `currency` VARCHAR(64) NOT NULL,
    `deposit_to_society` TINYINT NOT NULL DEFAULT 1,
    `source_type` VARCHAR(64) NOT NULL,
    `status` VARCHAR(24) NOT NULL DEFAULT 'open',
    `payment_phase` VARCHAR(24) NULL,
    `pending_amount` INT UNSIGNED NULL,
    `pending_currency` VARCHAR(64) NULL,
    `payer_identifier` VARCHAR(128) NULL,
    `payer_job` VARCHAR(64) NULL,
    `created_at` DATETIME NOT NULL DEFAULT CURRENT_TIMESTAMP,
    `updated_at` DATETIME NOT NULL DEFAULT CURRENT_TIMESTAMP,
    `paid_at` DATETIME NULL,
    PRIMARY KEY (`id`),
    UNIQUE KEY `uq_sky_invoice_reference` (`reference`),
    KEY `idx_sky_invoice_recipient` (`recipient_identifier`, `id`),
    KEY `idx_sky_invoice_sender` (`job_name`, `id`),
    KEY `idx_sky_invoice_society` (`recipient_job`, `id`),
    KEY `idx_sky_invoice_due` (`payment_mode`, `status`, `next_attempt_at_ts`, `due_at_ts`),
    KEY `idx_sky_invoice_employee` (`employee_share_phase`, `employee_share_next_attempt_at_ts`, `actor_identifier`)
) ENGINE=InnoDB;

ALTER TABLE `sky_jobs_dispatch_audit` ADD COLUMN IF NOT EXISTS `job` VARCHAR(80) NULL AFTER `center_id`;
ALTER TABLE `sky_jobs_dispatch_map_features` ADD COLUMN IF NOT EXISTS `job` VARCHAR(80) NULL AFTER `center_id`;
ALTER TABLE `sky_jobs_dispatch_calls` ADD COLUMN IF NOT EXISTS `job` VARCHAR(80) NULL AFTER `center_id`;
ALTER TABLE `sky_jobs_dispatch_center_chat` ADD COLUMN IF NOT EXISTS `job` VARCHAR(80) NULL AFTER `center_id`;

SET @dispatch_engine_upgrade = IF(
    (SELECT UPPER(ENGINE) FROM INFORMATION_SCHEMA.TABLES
        WHERE TABLE_SCHEMA = DATABASE() AND TABLE_NAME = 'sky_jobs_dispatch_map_features') = 'INNODB',
    'SELECT 1',
    'ALTER TABLE `sky_jobs_dispatch_map_features` ENGINE=InnoDB'
);
PREPARE dispatch_engine_upgrade FROM @dispatch_engine_upgrade;
EXECUTE dispatch_engine_upgrade;
DEALLOCATE PREPARE dispatch_engine_upgrade;

Manual route - MySQL 8. Run this complete alternative instead of the MariaDB block, with Config.AutoExecuteQuery = false and job resources stopped. Select the server's active database first and run all statements in the same SQL session. Each column is checked through INFORMATION_SCHEMA.COLUMNS in DATABASE() before it is added; existing columns are retained. The invoice table and conditional Dispatch engine upgrade are included here as well.

CREATE TABLE IF NOT EXISTS `sky_jobs_invoices` (
    `id` BIGINT UNSIGNED NOT NULL AUTO_INCREMENT,
    `reference` VARCHAR(128) NOT NULL,
    `issuer_type` VARCHAR(16) NOT NULL,
    `job_name` VARCHAR(64) NOT NULL DEFAULT '',
    `job_label` VARCHAR(120) NOT NULL,
    `account` VARCHAR(128) NOT NULL DEFAULT '',
    `issuer_identifier` VARCHAR(128) NOT NULL DEFAULT '',
    `issuer_name` VARCHAR(120) NOT NULL,
    `actor_name` VARCHAR(120) NOT NULL,
    `actor_identifier` VARCHAR(128) NOT NULL DEFAULT '',
    `employee_share_percent` TINYINT UNSIGNED NOT NULL DEFAULT 0,
    `employee_share_paid` INT UNSIGNED NOT NULL DEFAULT 0,
    `employee_share_phase` VARCHAR(24) NULL,
    `employee_share_pending` INT UNSIGNED NULL,
    `employee_share_next_attempt_at_ts` BIGINT NOT NULL DEFAULT 0,
    `payment_mode` VARCHAR(16) NOT NULL DEFAULT 'later',
    `due_at_ts` BIGINT NOT NULL DEFAULT 0,
    `installment_count` TINYINT UNSIGNED NOT NULL DEFAULT 1,
    `installment_interval_days` SMALLINT UNSIGNED NOT NULL DEFAULT 0,
    `installment_start_at_ts` BIGINT NOT NULL DEFAULT 0,
    `next_attempt_at_ts` BIGINT NOT NULL DEFAULT 0,
    `collection_failure_code` VARCHAR(32) NOT NULL DEFAULT '',
    `collection_failed_at_ts` BIGINT NOT NULL DEFAULT 0,
    `reminder_at_ts` BIGINT NOT NULL DEFAULT 0,
    `recipient_type` VARCHAR(16) NOT NULL,
    `recipient_job` VARCHAR(64) NOT NULL DEFAULT '',
    `recipient_identifier` VARCHAR(128) NOT NULL DEFAULT '',
    `recipient_name` VARCHAR(120) NOT NULL,
    `reason` TEXT NOT NULL,
    `amount` INT UNSIGNED NOT NULL,
    `amount_paid` INT UNSIGNED NOT NULL DEFAULT 0,
    `currency` VARCHAR(64) NOT NULL,
    `deposit_to_society` TINYINT NOT NULL DEFAULT 1,
    `source_type` VARCHAR(64) NOT NULL,
    `status` VARCHAR(24) NOT NULL DEFAULT 'open',
    `payment_phase` VARCHAR(24) NULL,
    `pending_amount` INT UNSIGNED NULL,
    `pending_currency` VARCHAR(64) NULL,
    `payer_identifier` VARCHAR(128) NULL,
    `payer_job` VARCHAR(64) NULL,
    `created_at` DATETIME NOT NULL DEFAULT CURRENT_TIMESTAMP,
    `updated_at` DATETIME NOT NULL DEFAULT CURRENT_TIMESTAMP,
    `paid_at` DATETIME NULL,
    PRIMARY KEY (`id`),
    UNIQUE KEY `uq_sky_invoice_reference` (`reference`),
    KEY `idx_sky_invoice_recipient` (`recipient_identifier`, `id`),
    KEY `idx_sky_invoice_sender` (`job_name`, `id`),
    KEY `idx_sky_invoice_society` (`recipient_job`, `id`),
    KEY `idx_sky_invoice_due` (`payment_mode`, `status`, `next_attempt_at_ts`, `due_at_ts`),
    KEY `idx_sky_invoice_employee` (`employee_share_phase`, `employee_share_next_attempt_at_ts`, `actor_identifier`)
) ENGINE=InnoDB;

SET @sky_release_add_column = IF(
    EXISTS (SELECT 1 FROM INFORMATION_SCHEMA.COLUMNS
        WHERE TABLE_SCHEMA = DATABASE()
            AND TABLE_NAME = 'sky_jobs_dispatch_audit' AND COLUMN_NAME = 'job'),
    'SELECT 1',
    'ALTER TABLE `sky_jobs_dispatch_audit` ADD COLUMN `job` VARCHAR(80) NULL AFTER `center_id`'
);
PREPARE sky_release_add_column FROM @sky_release_add_column;
EXECUTE sky_release_add_column;
DEALLOCATE PREPARE sky_release_add_column;
SET @sky_release_add_column = IF(
    EXISTS (SELECT 1 FROM INFORMATION_SCHEMA.COLUMNS
        WHERE TABLE_SCHEMA = DATABASE()
            AND TABLE_NAME = 'sky_jobs_dispatch_map_features' AND COLUMN_NAME = 'job'),
    'SELECT 1',
    'ALTER TABLE `sky_jobs_dispatch_map_features` ADD COLUMN `job` VARCHAR(80) NULL AFTER `center_id`'
);
PREPARE sky_release_add_column FROM @sky_release_add_column;
EXECUTE sky_release_add_column;
DEALLOCATE PREPARE sky_release_add_column;
SET @sky_release_add_column = IF(
    EXISTS (SELECT 1 FROM INFORMATION_SCHEMA.COLUMNS
        WHERE TABLE_SCHEMA = DATABASE()
            AND TABLE_NAME = 'sky_jobs_dispatch_calls' AND COLUMN_NAME = 'job'),
    'SELECT 1',
    'ALTER TABLE `sky_jobs_dispatch_calls` ADD COLUMN `job` VARCHAR(80) NULL AFTER `center_id`'
);
PREPARE sky_release_add_column FROM @sky_release_add_column;
EXECUTE sky_release_add_column;
DEALLOCATE PREPARE sky_release_add_column;
SET @sky_release_add_column = IF(
    EXISTS (SELECT 1 FROM INFORMATION_SCHEMA.COLUMNS
        WHERE TABLE_SCHEMA = DATABASE()
            AND TABLE_NAME = 'sky_jobs_dispatch_center_chat' AND COLUMN_NAME = 'job'),
    'SELECT 1',
    'ALTER TABLE `sky_jobs_dispatch_center_chat` ADD COLUMN `job` VARCHAR(80) NULL AFTER `center_id`'
);
PREPARE sky_release_add_column FROM @sky_release_add_column;
EXECUTE sky_release_add_column;
DEALLOCATE PREPARE sky_release_add_column;

SET @dispatch_engine_upgrade = IF(
    (SELECT UPPER(ENGINE) FROM INFORMATION_SCHEMA.TABLES
        WHERE TABLE_SCHEMA = DATABASE() AND TABLE_NAME = 'sky_jobs_dispatch_map_features') = 'INNODB',
    'SELECT 1',
    'ALTER TABLE `sky_jobs_dispatch_map_features` ENGINE=InnoDB'
);
PREPARE dispatch_engine_upgrade FROM @dispatch_engine_upgrade;
EXECUTE dispatch_engine_upgrade;
DEALLOCATE PREPARE dispatch_engine_upgrade;

Items: No Jobs Base item definition, container slot limit or item name changes in this release. The briefcase only gains its hidden-by-default attachment policy in config/item_containers.lua; existing Show/Hide item buttons remain usable. No inventory reimport is needed for that policy change.

Assets: Install source/* from the same completed release package so its rebuilt tablet/configurator files and police files icon are included. Existing external image URLs and inventory images remain your own settings. No new Jobs Base streamed model or separate image installation is required.

Providers and invoice scope: Select Sky Billing through Base Config.billing="sky" and use matching updated job resources for their supported billing workflows. Police/Ambulance/Fire keep their own saved billing-mode overrides; modes must reach the selected provider for new Sky invoices. Explicit external provider invoices are not automatically copied into /billing. Mechanic Advanced Billing keeps its own service invoices, payments and order completion; central installments and employee shares do not apply to those invoices. Plans and shares are opt-in by job; only confirmed qualifying payments earn a share, and offline employee payouts wait until login. A payment awaiting verification is not proof of a failed debit; check the invoice and provider account history before attempting manual recovery.

Permissions and dependencies: Existing invoice/management permissions still control staff actions; this release does not require reassigning new global permission IDs. Stop the server for the coordinated update, install matching Base 1.45.0 first, Jobs Base 1.48.0 second and updated affected job resources after them, then restart and reconnect clients. The optional Jobs Creator must be updated to a compatible build if its embedded editor/native administration is used. It remains a separate resource; these library notes do not publish its full product or promise a complete Hex/Jaksam replacement.

No additional SQL, inventory item definitions, item icons or streamed assets are required for these Jobs Base changes. The invoice and Dispatch schema instructions in this guide still apply. Shutdown records accrued work time and leaves unpaid salary intervals for the next normal payroll run; it does not issue a salary payment from an unloading resource. Jobs Creator remains a separate unreleased resource; its existing Archive/Restore behavior is unchanged.

5. Restart and check

Start your framework, database connector and configured providers first, then Base, Jobs Base and the updated job resources in dependency order. Reconnect clients. After restarting, confirm that startup migrations finish and both Base/Jobs Base show the expected release versions. Open /jobconfig → Jobs Base → Administration → Billing and confirm default empty plans/shares, intended command, duty policy and invoice limits. Check each Dispatch center's Restrict to own job setting, then compare two departments' visibility and a direct unit assignment. Verify /dispatchholster, radio/bodycam after reopening, map GPS/sharing rules and an interrupted hands-up pose. Own a briefcase, open its container, select Show/Hide, then switch characters to confirm the hidden start. Issue one Sky invoice, pay it through the selected bank/cash option and confirm a single income entry; separately retain the existing external/Mechanic path where used. Reopen saved settings/locations without manually refreshing. No new many-player, live CEF or provider acceptance is claimed by this publication.

Open Job Configurator, confirm an unchanged section has a disabled Save button, change one existing value, save once and reopen the same section to verify persistence. During a pending save, confirm a second click cannot submit another write and that a rejected save retains the draft. With a representative test character, clock in, stop the final resource owning that job, then restart it and verify the accrued duty time remains and the next normal payroll run pays only outstanding intervals. Confirm the configured language and English fallback still render the Job Configurator. The disposable database and source fixtures do not prove a live payroll or multi-player performance result.

If a check fails, keep the update on staging and collect the installed resource versions, selected provider, effective saved setting and the first relevant startup or action error. A successful source test, build or copy does not establish live FiveM, provider or customer acceptance.

1. Prepare

These instructions cover sky_jobs_base 1.47.0 → 1.47.1. Complete earlier migrations first if upgrading from an older version. Back up the database, resources, custom configuration and saved job/Creator data. Stop the server for the coordinated update. Install Base 1.44.1, then Jobs Base 1.47.1, then the matching hotfixes for your installed Sky jobs and Crime.

2. Replace files

Use the 1.47.1 download. Delete the entire sky_jobs_base/source/ folder and insert the new folder. Replace sky_jobs_base/fxmanifest.lua from that same package. Refresh the complete sky_jobs_base/config/locales/ tree and reapply custom translations. Keep the new source and manifest together; do not merge old generated interface files into them.

Replace sky_jobs_base/config/inventory/ox_briefcase_buttons.lua. Existing ox_inventory item definitions continue to load that file; no item-definition rewrite is required.

3. Keep settings

No configuration values or Job Configurator setting keys are added, removed or reset by this hotfix. Keep your current settings and saved overrides. Hungarian uses the existing Config.locale = "hu" setting in sky_base/config/config.lua; leave your selected language unchanged if you do not want to switch. Update the matching Base, Jobs Base and installed resource locale folders together. For Hungarian ox_inventory briefcase buttons, use the existing setr ox:locale "hu" in server.cfg before ox_inventory starts; this inventory language is separate from Config.locale.

Optional diagnostics stay disabled by default. If support requests a recording, put setr sky_profiler 1 before the Sky ensure lines in server.cfg, restart, run profiler record 1000, wait for profiler status to show completion, then run profiler saveJSON sky-hotfix-profile.json. Disable with setr sky_profiler 0 and another restart. This is not a /jobconfig option; nothing is recorded or uploaded automatically.

4. Data and assets

No new SQL import, item definition, inventory image or stream asset is required for this hotfix. Keep saved job/Creator data; do not reset or reimport it. Required earlier migrations still apply when upgrading from an older release.

5. Restart and check

Start your framework, database connector and configured providers first, then Base 1.44.1, Jobs Base 1.47.1 and the updated jobs/Crime. Reconnect clients. Open /jobconfig, check an installed job, and test helicopter spotlight direction with another player if you use it. If startup still fails, collect the first error and its preceding log lines together with the installed versions.

1. Prepare the update

Back up your database and your existing sky_jobs_base folder. Also back up the inventory item definitions and images you will edit. Keep your existing settings, provider choices, webhooks and API keys.

Install Sky Base 1.44.0, Jobs Base 1.47.0, and the matching releases of your installed Sky job resources together. Install the matching Crime System update if you use raids or Crime organizations. Jobs Base now uses the updated Base migration and startup contracts; an older Base package is not compatible with this update. Keep optional resources installed only when you use them.

Before stopping the server, record the effective Jobs Base → General → Database setup (AutoExecuteQuery) value in /jobconfig; a saved override takes precedence over the file default. Stop the server during file replacement and database changes. Plan one full server restart after completing all steps below. Restarting only Jobs Base is insufficient for the command ownership changes in this release.

2. Replace the package files

Delete the old sky_jobs_base/source/ folder and insert the complete new source/ folder. Copy the new fxmanifest.lua from the same package; its version must be 1.47.0 without a v. Update config/locales/ and merge your own translations. Copy import.sql and the changed config/inventory/ files listed above. Add config/item_containers.lua and stream/sky_briefcase_grip.ycd.

The complete source/ replacement includes the compiled tablet interface, the certificate name-stamp font and its license. Do not copy only individual Lua files or keep an older compiled interface. Merge the settings below into config/config.lua; do not replace your customized configuration with defaults. Keep your existing config/init.lua, config/webhooks.lua, provider secrets and printer customizations. No outside-source file must be removed or renamed for this update.

3. Merge configuration and saved overrides

Hungarian language

Refresh the complete resource locale folder from this download, including hu.lua, and carry over your custom translations. To use Hungarian, set the existing Config.locale value to "hu" in sky_base/config/config.lua; its supplied default remains "en". Keep your current value if you are not changing language. This is the shared Sky language setting, so update the matching Base, Jobs Base and installed job locale folders together. Jobs Base supplies the Hungarian /jobconfig translations too. No new /jobconfig language setting, saved-job reset or database migration is required for this language addition. Apply the normal restart and reconnect steps at the end of this update.

For the Show briefcase and Hide briefcase actions in ox_inventory, also update sky_jobs_base/config/inventory/ox_briefcase_buttons.lua. Its labels follow the inventory's ox:locale setting separately from Config.locale. To select Hungarian for those inventory actions, prepare setr ox:locale hu in server.cfg before the inventory starts; keep a different intentional inventory language if desired. Copy the helper and the Jobs Base hu.lua before the inventory loads its item catalog, then use the normal restart sequence. Existing item keys, callbacks and metadata stay the same.

Settings saved in /jobconfig are authoritative over file defaults. Updating config/config.lua alone does not replace a saved value. Missing settings inherit their new defaults; explicitly saved values and lists remain effective. After the server restarts, open /jobconfig, select Jobs Base, and check the sections below. Preserve your jobs, locations, ranks and saved overrides; do not reset or reimport them to install this update.

Admin command permissions — file only. Inside the existing Config.CommandPermissions table in config/config.lua, add the two new Crime command entries and rename the two old MultiJob entries. Preserve the administrator groups you already use. The shipped values for these four entries are:

setcrimeboss = { "god", "superadmin", "admin" },
removecrimeboss = { "god", "superadmin", "admin" },
skygivejob = { "god", "superadmin", "admin" },
skyremovejob = { "god", "superadmin", "admin" },

setcrimeboss and removecrimeboss were absent previously. givejob becomes skygivejob; removejob becomes skyremovejob. Remove the obsolete Sky entries after moving their groups. Leave other entries, including setboss, unchanged. These bootstrap permission entries are not managed through /jobconfig.

MultiJob command names — Jobs Base → Jobs → MultiJob. Change Config.MultiJob.giveJobCommand from "givejob" to "skygivejob" and Config.MultiJob.removeJobCommand from "removejob" to "skyremovejob". Update the corresponding saved settings if they contain the old default names. The runtime normalizes those legacy default names, while other custom command names remain unchanged. /jobs and /multijobadmin retain their names. Choose unused names if you use custom commands; a conflicting registration is skipped with a console warning.

If you maintain external ACE rules or admin menu shortcuts for Sky's old commands, change their command names and Sky ACE references: sky_jobs_base.givejob → sky_jobs_base.skygivejob, command.givejob → command.skygivejob, and the corresponding removejob → skyremovejob references. Preserve any separate framework/Qbox rules that intentionally refer to the framework's own commands.

/setboss <job> <grade> grants rank permissions for a regular job and no longer accepts a player assignment argument. Use /setcrimeboss <organization> <playerId> to assign the highest existing Crime rank. Use /removecrimeboss <organization> <playerId> to remove that player's membership in the named Crime organization; this removes membership rather than merely lowering the rank. Independent and native-gang providers retain the normal employer job. With a framework-job provider, assigning a Crime organization cannot replace an unrelated normal job, and removing that Crime membership returns the character to unemployed, rank 0. Existing admission requirements still apply. Existing organization definitions, ranks and permission grants do not need migration.

External hands-up detection — Jobs Base → Interactions → Handcuffs & hands up → Animation check. Config.PoliceCuffs.animationCheck is new. Insert this complete block inside your existing Config.PoliceCuffs table, alongside handsUp:

animationCheck = {
    enabled = true,
    animations = {
        { dict = "random@mugging3", name = "handsup_standing_base" },
        { dict = "missminuteman_1ig_2", name = "handsup_base" },
        { dict = "anim@mp_player_intuppersurrender", name = "idle_a_fp" },
        { dict = "anim@mp_rollarcoaster", name = "hands_up_idle_a_player_one" },
        { dict = "anim@scripted@bty2@ig2_beat_target@male@", name = "leaning_idle_bounty" },
        { dict = "anim@scripted@bty2@ig2_beat_target@male@", name = "standing_idle_bounty" }
    }
},

The exact managed settings are PoliceCuffs.animationCheck.enabled and PoliceCuffs.animationCheck.animations. Detection defaults to enabled and recognizes the listed RPEmotes hands-up animations for searches and zipties. It works even when PoliceCuffs.handsUp.enabled is disabled. The existing Sky hands-up defaults remain enabled, key H, hold time 3 seconds. For another emote, add its animation dictionary and clip name rather than its chat command or display label. Keep an intentional saved false or custom animation list.

Alert keys — Jobs Base → Radial & Alerts. Add keyMapping = "K", inside Config.Panic and keyMapping = "L", inside Config.Ping; these fields were absent before. Keep the remaining values, including Panic.useKeybind, unchanged. Add the complete new keyMappings table to Config.IncidentNotification; the full shipped notification block is:

Config.IncidentNotification = {
    durationMs = 30000,
    keyMappings = {
        acceptDispatch = "J",
        setWaypoint = "G",
        openMap = "M",
        dismiss = "BACK"
    }
}

Preserve your custom durationMs. The managed paths are Panic.keyMapping, Ping.keyMapping and IncidentNotification.keyMappings.acceptDispatch, .setWaypoint, .openMap, .dismiss. These values define defaults for new bindings. Existing personal bindings remain in Settings → Key Bindings → FiveM and can be changed there. J accepts the displayed dispatch, or the unit's pending radio assignment when no dispatch notification is shown; G only sets the waypoint. Saving a registered key or command change displays a restart notice. Restart the affected resource after later binding changes; this release itself requires the full server restart described below.

Garage spawn points — Jobs Base → World → Interactions. In Config.Interactions.garage_helicopter_spawn and Config.Interactions.garage_boat_spawn, add interaction = false,. The field was absent on both entries; the vehicle-spawn entry already used false. These are spawn positions, while menu and parking positions remain separate. Preserve your marker, blip and NPC choices. Review the corresponding saved interaction settings and any resource-specific location overrides so an intentional override is not mistaken for the new default. No location needs deletion or recreation.

Other repaired interaction settings retain their saved values: explicit empty labels/scenarios, marker offsets/scales, blip display/scale, NPC models and disabled parking markers are now applied consistently. Close and reopen existing configurator pages after the update before saving. With the matching Fire Job update, Automatic Missions lists now save correctly even when the saved list was empty or arranged differently; existing missions do not need to be recreated.

4. Apply SQL, inventory and asset updates

config/item_containers.lua is a new plaintext, file-only configuration. It is not exposed through /jobconfig, and changes require a Jobs Base restart. Add the complete file. Its shipped configuration is:

Config.ItemContainers = {
    enabled = true,
    nativeOxProperties = true,
    items = {
        {
            name = "sky_briefcase",
            label = "Briefcase",
            description = "A lockable case for documents and work materials.",
            weight = 1500,
            slots = 24,
            maxWeight = 25000,
            allowlistEnabled = true,
            allowlist = { "sky_case_folder", "job_document", "doj_document", "doj_law_book" },
            blacklist = { "sky_briefcase" },
            autoShowWhenOwned = true,
            attachment = {
                model = "prop_ld_case_01",
                bone = 57005,
                offset = { x = 0.15, y = 0.0, z = -0.01 },
                rotation = { x = -90.0, y = -90.0, z = 0.0 },
                rotationOrder = 3, -- Native XZY matches the grip's Blender YZX transform.
                collision = false,
                animation = {
                    dict = "sky_briefcase_grip",
                    name = "grip",
                    flag = 305, -- Loop + upper body + secondary + additive; preserve normal body movement.
                },
            },
        },
        {
            name = "sky_case_folder",
            label = "Case Folder",
            description = "A folder for case files and loose documents.",
            weight = 450,
            slots = 12,
            maxWeight = 8000,
            blacklist = { "sky_briefcase", "sky_case_folder" },
            autoShowWhenOwned = false,
        },
    },
}

The briefcase accepts sky_case_folder, job_document, doj_document and doj_law_book by default. Set its allowlistEnabled to false only if you want other items to be allowed; its self-blacklist remains. The folder blocks both container item names. DOJ is not a dependency merely because its document names are listed. Register items you actually use through their owning product's instructions.

For ox_inventory or Qbox using ox_inventory, merge these two complete entries into the existing returned item table in ox_inventory/data/items.lua. Do not replace the whole inventory catalog, and do not duplicate existing entries:

["sky_briefcase"] = {
        label = "Briefcase",
        weight = 1500,
        stack = false,
        close = false,
        consume = 0,
        description = "A lockable case for documents and work materials.",
        client = { image = "sky_briefcase.png" },
        buttons = require "@sky_jobs_base.config.inventory.ox_briefcase_buttons",
    },
    ["sky_case_folder"] = {
        label = "Case Folder",
        weight = 450,
        stack = false,
        close = false,
        consume = 0,
        description = "A folder for case files and loose documents.",
        client = { image = "sky_case_folder.png" },
    },

Copy sky_jobs_base/config/inventory/sky_briefcase.png to ox_inventory/web/images/sky_briefcase.png and sky_jobs_base/config/inventory/sky_case_folder.png to ox_inventory/web/images/sky_case_folder.png. Keep the buttons = require "@sky_jobs_base.config.inventory.ox_briefcase_buttons" line on the briefcase and copy that helper file before the inventory loads its item catalog. It provides the localized Show briefcase and Hide briefcase actions. No ox core edit or second usable-item callback is required. Reloading the inventory definitions is included in the full server restart.

For other inventories, register the same two names in that provider's item catalog using its equivalent unique/non-stackable, reusable settings and copy the two PNGs into its image folder. Keep per-item metadata intact during storage and transfers. Each physical item owns a separate container identifier; do not clone that identifier or strip its metadata.

ox_inventory uses its native container metadata; Jobs Base also supports older ox versions without the runtime container-properties export through the native metadata path and a swap filter. CodeM V2, Core, One, Origen, PS, QB Inventory, QS and Tgiann use their metadata and stash APIs; filter enforcement depends on provider support. Jaksam and AK47 use their native item filters. Native ESX/VRP, JPR, CodeM V1 and custom adapters without both item metadata and stash support cannot open unique item containers. If your adapter lacks those capabilities, set Config.ItemContainers.enabled = false and omit these optional items until it supports them.

The default capacities are 24 slots / 25,000 weight units for a briefcase and 12 slots / 8,000 for a folder. The owned briefcase appears on the local player's hand after inventory loading. Hiding it persists until Show is selected or the character logs out; opening or closing its contents does not change visibility. Losing the last briefcase removes the prop. The folder has no prop by default. Add the items to your own shop or distribution system if you want players to obtain them; this update does not populate an existing shop automatically.

Apply the database change

This Jobs Base release adds one table, sky_jobs_tablet_notices, to remember per-character acknowledgements of the temporary File Explorer move notice. It adds no columns to existing tables, renames no existing table and requires no data reset.

When the effective Jobs Base AutoExecuteQuery setting is true, startup creates the table automatically. Use the effective Jobs Base → General → Database setup value recorded before shutdown; a saved override takes precedence over the file default. If you deliberately use AutoExecuteQuery = false, apply the following statement to the database used by your server before starting the updated resources:

CREATE TABLE IF NOT EXISTS `sky_jobs_tablet_notices` (
    `id` BIGINT UNSIGNED NOT NULL AUTO_INCREMENT,
    `character_identifier` VARCHAR(128) NOT NULL,
    `notice_key` VARCHAR(64) NOT NULL,
    `acknowledged_at` DATETIME NOT NULL DEFAULT CURRENT_TIMESTAMP,
    PRIMARY KEY (`id`),
    UNIQUE KEY `uniq_character_notice` (`character_identifier`, `notice_key`)
) ENGINE=InnoDB;

The table inherits your database's character set and collation. Keep existing notice acknowledgements, tablet data and container metadata. Do not delete job tables or rerun an old destructive setup script. Follow the separate Crime System instructions for its raid data changes if that product is installed; those are not additional Jobs Base tables.

5. Restart and verify

Complete the coordinated update, then fully restart the server. Start the framework, database/inventory and other required providers first, followed by sky_base, sky_jobs_base, and your installed Sky job resources. Keep their existing provider-specific start order requirements. A full restart releases the old shared command registrations; restarting Jobs Base alone does not do that for this update.

Check that Jobs Base reports 1.47.0, Base reports 1.44.0, and startup finishes without missing exports or migration errors. Open /jobconfig and confirm saved settings, locations and employer duty terminals remain present. If automatic SQL is disabled, check that sky_jobs_tablet_notices exists. Test your customized MultiJob commands and Crime administration with authorized accounts, then check the FiveM key bindings and one dispatch acceptance. If you enabled containers, give two separate test items, put different documents in each, transfer one to another player, and check that contents and Show/Hide controls work with your actual inventory provider.

If raids are used, update the matching Crime System package and test an authorized raid: the tablet starts the raid, while participants breach and access authorized storage or garages at the world locations. Raid storage permits withdrawals, and raid garage access does not grant the normal purchase, sale, transfer, plate-change or trunk-management actions. Preserve existing raid data and follow Crime's own migration instructions.

If /jobconfig still reports a save error, enable the optional diagnostic for one reproduction with set sky_jobconfig_trace 1 in the server console, reproduce the failing save, keep the complete Jobs Base error/traceback, then disable it with set sky_jobconfig_trace 0. It is disabled by default, is not a /jobconfig setting, and does not upload logs automatically.

Optional profiler capture

Profiler support is disabled by default. To collect a profile, place setr sky_profiler 1 in server.cfg before the Sky resource ensure lines, then restart the affected resources or the server. In the console for the side you are measuring, run profiler record 1000, reproduce the action, and use profiler status until recording has finished. Save the result manually with profiler saveJSON sky-release-profile.json and retain it for your support report. Recording and uploading do not start automatically.

After recording, change the setting to setr sky_profiler 0 and restart the affected resources or the server. This switch is not managed through /jobconfig. Keep source/ and fxmanifest.lua from the same release package. If you previously installed an older instrumented package that changed files outside source/, restore those shipped files once while merging back your custom settings; current profiler packages should not change plaintext configuration, locales, images or SQL.

1. Prepare the update

Back up the server KVP database (db/<sv_kvsName>) as well as SQL. Printer supplies now use that storage. Keep stable printer IDs, owning resource names and KVP data when moving servers.

If Fire Job is installed, take all breathing bottles out of vehicle bottle storage before stopping the old server. The Fire update cannot migrate its old live vehicle-state contents. Complete this pre-shutdown step before updating Base or Jobs Base.

These instructions cover sky_jobs_base 1.45.0 → 1.46.0. Complete earlier required migrations first if upgrading from an older release. Stop the server for the coordinated update and back up the resource, database, customized configuration and saved job/creator settings. Install Base 1.43.0 first, then Jobs Base 1.46.0, then the matching installed job releases.

2. Replace the package files

Use the matching 1.46.0 package. Delete the old sky_jobs_base/source/ directory completely and insert the new directory. Replace sky_jobs_base/fxmanifest.lua from the same package. Refresh the entire sky_jobs_base/config/locales/ tree and merge your custom translations back. Include all nested job-configurator locale folders. Copy stream/sky_printer_01.ydr and stream/sky_printers.ytyp, import.sql, config/inventory/README.md, config/inventory/items_ox.lua and config/inventory/printer_ink.png. Merge config/config.lua and config/printers.lua as described here; preserve webhooks and other provider secrets. A full server restart loads the new streams, schema and consumers together.

Do not merge old generated interface files into the new source/ directory.

3. Merge configuration and saved overrides

Prepare file changes while the server is stopped. Perform the /jobconfig, Creator and other in-game actions described in this section after starting the updated resources in step 5, during maintenance and before admitting players.

The complete executable Config.Cctv block before the update, with comments omitted only for readability:

Config.Cctv = {
    allowedJobs = { "police", "ambulance", "fire" },
    requireBodycamItem = false,
    bodycamItem = "bodycam",
    bodycamRecorderEnabled = true,
    recordBitrateKbps = 1500,
    bodycamViewJobs = nil
}

The new shipped block:

Config.Cctv = {
    allowedJobs = { "police", "ambulance", "fire", "doj" },
    requireBodycamItem = false,
    bodycamItem = "bodycam",
    bodycamRecorderEnabled = true,
    recordBitrateKbps = 1500,
    recordMaxSizeMb = 32,
    bodycamViewJobs = nil
}

Exact changes: Cctv.allowedJobs adds "doj" to the supplied array, and Cctv.recordMaxSizeMb is new with default 32 decimal MB. Preserve actual custom job/group names and custom visibility rules; add DOJ only when wanted. A nil allowlist still uses the existing police/ambulance fallback, so leaving it nil does not automatically add Fire or DOJ.

Cctv.recordBitrateKbps remains 1500, but is now the requested bitrate: the recorder lowers it when required to keep the rolling window within the upload budget. Match recordMaxSizeMb to the real media-provider maximum. Keep any custom recordBufferMinutes; this release does not add that key to the shipped public block, and the runtime's default rolling window remains five minutes. Existing recording enable/item/visibility choices remain valid.

Managed path when Config.UseIngameConfigurator = true: /jobconfig → Jobs Base → Tablet & Apps, with Allowed jobs, Video bitrate (kbit/s) and Maximum video upload (MB). Exact managed keys are Cctv.allowedJobs, Cctv.recordBitrateKbps, Cctv.recordMaxSizeMb.

If a custom configuration contains the obsolete bodycamSaveKey, remove it. The player action is Save bodycam in the radial menu.

Managed configuration, imports and file-only values

• With Config.UseIngameConfigurator = true, stored /jobconfig overrides remain authoritative. Defaults can change only where there is no saved override; editing a public file alone does not replace a saved override. Review the new upload limit and camera allowlist in Jobs Base's configurator.
• Shared policy managed since 1.44.0, including civilian use, carry, restraints/search and NUI image choices, remains managed there. This release does not change their defaults; preserve them rather than re-entering them unnecessarily.
• Use /jobconfigimport sky_jobs_base only when you intentionally want to import the edited file configuration into the stored configurator state. Back up saved settings first. This command explicitly imports the file configuration; it is not required to reset existing overrides.
• To continue managing shared settings in files, set Config.UseIngameConfigurator = false and maintain the file changes above. Bootstrap settings, configurator access/permission configuration and provider credentials remain file-based.
• config/webhooks.lua and provider secrets have no diff in this range. Preserve their working values; do not replace secrets with defaults. Bodycam uploads still need the existing configured media provider. No new secret or webhook key is introduced.
• Config.Printers below is file-based shared printer configuration. Per-job printerSettings and printers are separate job-configurator data and can override those shared defaults.

config/printers.lua — shared printer defaults and models

Old exact changed values:

inkCapacity = 100,
inkRefillAmount = 100,
models = {
    { model = "prop_printer_01", class = "office" },
    { model = "prop_printer_02", class = "office" },
    { model = "v_res_printer", class = "standard" },
    { model = "v_ret_gc_print", class = "standard" },
    { model = "prop_copier_01", class = "professional" },
    { model = "v_med_cor_photocopy", class = "professional" },
},

Complete new shared block, preserving shipped defaults:

Config.Printers = {
    enabled = true,
    resources = {
        sky_ambulancejob = true,
        sky_policejob = true,
        sky_mechanicjob = true,
        sky_dojjob = true,
        sky_firejob = true,
    },
    secondsPerDocument = 6.0,
    documentAppearance = { leftImage = "", rightImage = "", watermark = "" },
    queueEnabled = true,
    inkEnabled = false,
    inkCapacity = 1200,
    inkPerDocument = 1,
    inkRefillItem = "printer_ink",
    inkRefillAmount = 1200,
    queueTimeoutSeconds = 60,
    jamChance = 0.08,
    maintenanceTimeoutSeconds = 45,
    models = {
        { model = "sky_printer_01", class = "office" },
        { model = "prop_printer_01", class = "office" },
        { model = "prop_printer_02", class = "office" },
        { model = "v_res_printer", class = "standard" },
        { model = "v_ret_gc_print", class = "standard" },
        { model = "prop_copier_01", class = "professional" },
        { model = "v_med_cor_photocopy", class = "professional" },
    },
}

Merge into custom blocks instead of overwriting their resource allowlists, stationery or models. inkEnabled remains false by default. queueTimeoutSeconds remains 60; it now measures extra active printing time and pauses during FIFO waiting, missing supplies and jams. It is not a grace period that deletes a blocked job while a player obtains paper.

Per-job printer configuration and existing saved overrides

Use /jobconfig → owning job resource → Jobs → relevant job → Printers. Printer settings are grouped into paper and ink; per-printer sections cover printing/access and model/placement. Persisted explicit values are not silently reset by new shared defaults.

The new field belongs inside the existing printer entry; no replacement table or coordinate is required:

deleteCopiesAfterRestart = false,

false preserves uncollected ready copies. true clears ready output only, not already collected documents or unrelated rows. The startup cleanup is applied when Jobs Base or the registered output owner starts. Saving normal configuration and merely disabling/re-enabling the printer do not repeatedly purge ready copies. The current matching DOJ consumer supports the same policy; older DOJ consumers do not (see compatibility).

For a new native printer, select Sky printer from the job location catalog. Its origin is at the bottom of the prop: place that origin on the table/surface. To reuse an MLO/existing object, choose Select existing printer, aim at the printer, confirm with Enter or cancel with Escape, then save the job settings. Selection captures model, position and heading and sets spawnProp = false; it does not move or duplicate the existing world object. Existing custom models/no-spawn locations remain valid. The new world paper/ink indicators apply to sky_printer_01 only.

Custom integrations and DOJ compatibility

Custom integrations using the removed GetAvailableRemotePrinters, CreateTemporaryPrinter or RemoveTemporaryPrinter APIs must use persistent configured nearby printers. Current DOJ packages that register their printer output storage require Jobs Base 1.46.0. Older DOJ packages can keep their existing printer workflow but do not implement the new ready-copy restart cleanup. Install a matching DOJ consumer only when using its new feature set; this release set does not introduce a new DOJ version.

Optional performance diagnostics

Extra profiler information is disabled by default. If support requests a recording, add setr sky_profiler 1 to server.cfg before the Sky ensure lines and restart. In the server console, run profiler record 1000, wait until profiler status reports completion, then run profiler saveJSON sky-release-profile.json. To disable the extra information, use setr sky_profiler 0 and restart. This is not a /jobconfig setting. Enabling it does not start recording or upload anything automatically.

Keep source/ and fxmanifest.lua from the same download even when diagnostics are disabled. Profiler processing changes only source Lua and the manifest; public configuration and provider files remain unchanged by that processing. If an older profiler package altered files outside source/, restore those once from the current download and reapply your own customizations.

4. Apply SQL, inventory and asset updates

Printer supplies and restarts

Paper and ink now persist by the owning config resource and stable printer ID in FiveM resource KVP storage. New printers, or printers without a saved stock entry on the first upgraded run, start at zero for enabled supplies and must be filled. Old volatile stock cannot be recovered retroactively. Existing KVP entries survive normal resource/server restarts; copying only SQL to another server is insufficient. Keep the server's KVP data and stable names/IDs. FIFO jobs, maintenance sessions and jams are still runtime state rather than a promise that in-flight work resumes after a server restart.

SQL and inventory

Apply these two additive schema changes while retaining existing data. They inherit the active database character set and collation.

• With Config.AutoExecuteQuery = true, the normal automatic migration creates sky_jobs_organization_roles and adds sky_jobs_gallery.is_deleted; let migration complete before testing features.
• With Config.AutoExecuteQuery = false, the automatic schema path is skipped. Back up the database and apply these changes manually before starting the new code.

New complete table:

CREATE TABLE IF NOT EXISTS `sky_jobs_organization_roles` (
    `organization` VARCHAR(64) NOT NULL,
    `grades` LONGTEXT NOT NULL,
    PRIMARY KEY (`organization`)
) ENGINE=InnoDB;

Check the existing gallery before adding the column:

SHOW COLUMNS FROM `sky_jobs_gallery` LIKE 'is_deleted';

If that returns no column, run:

ALTER TABLE `sky_jobs_gallery`
    ADD COLUMN `is_deleted` TINYINT(1) NOT NULL DEFAULT 0;

The updated import.sql contains the new column in its fresh table definition. Running CREATE TABLE IF NOT EXISTS against an existing gallery does not add the column, so that alone is not a manual upgrade. No SQL item insertion, data wipe, membership reset or permission-ID migration is required by these changes.

Independent organization grades are initialized from their configured grades/current framework catalog where available, otherwise member/boss defaults, and stored independently in the new table. This does not require changing a player's primary job. These organization ranks do not create framework salary payments. Review rank permissions after intentional edits; keep existing membership grants.

Inventory item and image

Servers using ink consumption must register the configured item. The new supplied entry in sky_jobs_base/config/inventory/items_ox.lua is:

["printer_ink"] = {
    label = "Druckerpatrone", weight = 200, stack = true, close = true, consume = 0,
    description = "Ersatzpatrone zum Nachfüllen eines Druckers.",
    client = { image = "printer_ink.png" },
},

For ox_inventory, merge this entry into ox_inventory/data/items.lua, copy sky_jobs_base/config/inventory/printer_ink.png to ox_inventory/web/images/printer_ink.png, then restart the inventory/server through the normal deployment process. Labels/descriptions may be translated for the server. If printerSettings.inkRefillItem/Config.Printers.inkRefillItem is customized, register that actual name and use its intended image instead.

For another supported inventory, add the equivalent stackable cartridge item without automatic use consumption. Jobs Base removes the cartridge after successful maintenance, so the inventory must not also consume it on use. Existing job_document and printer_paper definitions/images are unchanged in this range. A fresh install should merge all supplied entries and copy all three matching images; an update from 1.45.0 only introduces the ink entry/image. job_document must remain nonstackable with document metadata and consume = 0.

Bodycam retention and provider requirements

Bodycam Save requires the enabled recorder, an available buffered recording and the permitted active job/duty; the optional bodycam item requirement remains enforced. Use the existing configured media upload provider and keep its credentials. recordMaxSizeMb is a decimal limit, not an uploaded file guarantee; oversized output or provider rejection is shown as an error.

Sharing accepts bodycam recordings and supported legacy cctv video URLs, not arbitrary gallery photos or camera-folder videos. Gallery removal hides the recording from that owner's normal list while retaining accepted sharing/evidence references and media. Removing from the gallery is therefore not revocation. Revoke shares separately first if recipients must lose access; the UI confirmation explains this behavior. Removing a recording from the gallery does not free media storage or delete evidence that has already been accepted.

5. Restart and verify

Start Base 1.43.0, Jobs Base 1.46.0 and the matching consumers after their dependencies. Check manifest versions, startup errors and migration completion. Refill enabled supplies for printers with no saved stock, then verify stock after a restart. Check a Sky printer and an existing world printer, queue waiting, a jam and collection of ready output. Verify an independent organization’s facilities and saved ranks if used.

Save a buffered bodycam recording through the radial menu, open it from the bodycam gallery and test authorized sharing. Removing a shared recording from the owner’s gallery does not revoke recipients’ access; revoke its shares separately if access must end. Confirm the configured upload limit matches the real media provider.