Changelog

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_policejob 1.34.0 → 1.35.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.

Use the matching 1.35.0 package. Delete the old sky_policejob/source/ directory completely and insert the new directory. Replace sky_policejob/fxmanifest.lua from the same package. Refresh the entire sky_policejob/config/locales/ tree and merge your custom translations back. Replace sky_policejob/import.sql from the same download. Copying this file does not execute SQL.

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

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.

No Police setting, /jobconfig key or permission ID changes in this release. Keep existing configuration and saved overrides. The existing file setting Config.AutoExecuteQuery in sky_policejob/config/config.lua controls the database update route.

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.

With Config.AutoExecuteQuery = true, startup fills missing profile-share-state rows automatically; no manual SQL is needed. With false, run the following complete block in one connection to the active server database while Police is stopped:

CREATE TABLE IF NOT EXISTS `sky_police_profile_share_state` (
    `id` BIGINT UNSIGNED NOT NULL AUTO_INCREMENT,
    `job_id` INT NOT NULL,
    `kind` VARCHAR(16) NOT NULL,
    `profile_id` INT NOT NULL,
    `owner_job` VARCHAR(64) NOT NULL,
    `recipients` TEXT NOT NULL,
    `title` VARCHAR(160) NOT NULL,
    `revision` INT NOT NULL DEFAULT 1,
    `updated_at` DATETIME NOT NULL DEFAULT CURRENT_TIMESTAMP,
    PRIMARY KEY (`id`),
    UNIQUE KEY `uq_profile_share_state` (`job_id`, `kind`, `profile_id`, `owner_job`)
) ENGINE=InnoDB;

SET @sky_police_previous_group_concat_max_len = @@SESSION.group_concat_max_len;
SET SESSION group_concat_max_len = GREATEST(@@SESSION.group_concat_max_len, 65535);
INSERT IGNORE INTO `sky_police_profile_share_state`
    (`job_id`, `kind`, `profile_id`, `owner_job`, `recipients`, `title`, `revision`, `updated_at`)
SELECT `job_id`, `kind`, `profile_id`, `owner_job`,
    CONCAT('[', GROUP_CONCAT(JSON_QUOTE(`recipient_job`) ORDER BY `recipient_job` SEPARATOR ','), ']'),
    MAX(`title`), 1, MAX(`updated_at`)
FROM `sky_police_profile_shares`
GROUP BY `job_id`, `kind`, `profile_id`, `owner_job`;
SET SESSION group_concat_max_len = @sky_police_previous_group_concat_max_len;

This targeted block is for an existing 1.34.0 installation, where the source sharing table and other Police schema already exist. It preserves existing destination rows, including revoked shares. No existing column type/default changes; no new item or asset installation is needed. Do not run the entire import as an upgrade on MySQL 5.7: unrelated existing statements use syntax unavailable there. Do not run clear.sql; it is a destructive reset tool.

Start dependencies, Base 1.43.0, Jobs Base 1.46.0 and Police 1.35.0, then reconnect. Check startup for SQL errors. Verify existing citizen/vehicle profile shares, including a previously revoked share. Open documents and test tablet dialogs at the screen resolutions your server supports.

Update sky_base to 1.42.0, then sky_jobs_base to 1.45.0, then sky_policejob to 1.34.0. Install the matching updates for your other Sky jobs. These instructions cover 1.33.0 → 1.34.0; complete earlier migrations first. Stop the server and back up the resource, customized files, database and saved configurator/Creator data.

Install the matching 1.34.0 package. Replace every Changed Files path, delete and reinsert sky_policejob/source/*, and replace sky_policejob/config/locales/* completely. Merge the public configuration described in this view and retain saved database records.

Replace source/* and fxmanifest.lua from the same download even if optional diagnostics remain off. The profiler may change Lua inside source/ and the generated manifest; public configuration and integration files must match the clean source. If an older profiler package changed public files, restore those files once from the clean new package and merge your own changes. Keep customized configuration, writable data and private provider credentials backed up.

In sky_policejob/config/config.lua, merge these changes. With Config.UseJobConfigurator = true, the corresponding /jobconfig values use shipped defaults plus stored overrides; editing only the file does not replace those overrides. With false, maintain the Lua values directly.

Place the following app assignments after your existing Config.PoliceTablet table when copying directly:

Config.PoliceTablet.apps.files = true
Config.PoliceTablet.apps.registry = false

Add this complete field inside each department's entry in Config.Jobs, including customized departments:

caseNumbering = {
    prefix = "CASE"
},

Use /jobconfig → Police → department → Case numbers → Prefix (caseNumbering.prefix) when managed in-game. The prefix is trimmed, converted to uppercase and limited to 16 characters; blank uses CASE. Only newly generated case numbers change. Existing and manually entered case numbers stay unchanged; retain any saved department-specific prefix.

For a complete manual file merge, these are the changed entries inside the existing local police_sharing_defaults.records table:

citizenRecords = { enabled = true, jobs = {}, groups = { "police", "ambulance", "mechanic" } },
vehicleRecords = { enabled = true, jobs = { "doj" }, groups = { "police", "ambulance", "mechanic" } },

The old sharing.records and sharing.links sections, including those entries, are no longer effective and can be removed from customized job definitions. Keep the sharing.training rules for courses and qualifications. Record sharing now uses explicit recipients from Share on saved citizen/vehicle profiles, reports, cases, BOLOs and warrants. Existing explicit recipients are retained. Registered jobs are possible recipients, not automatic readers. Sharing requires an on-duty member with source-app access and ownership/clearance where applicable; recipients receive read access and must still satisfy their app, duty and clearance checks. A normal record save does not replace its separately edited sharing list.

File Explorer on existing servers: tabletFiles groups the permitted Citizens, Vehicles, Reports, Cases, BOLOs and Warrants directories under File Explorer. Their individual app switches and rank restrictions remain authoritative. When Explorer is disabled, the permitted standalone apps remain available. Native records, previews, sharing and printing no longer need DOJ; compatible DOJ content appears only when its resource/provider is running. The old personal folder and pinned-shortcut workspace is replaced by these record directories. Its stored sky_police_workspace rows are retained but no longer shown; no manual conversion exists or is needed for the source records. Do not reset that table.

Custom RP registers require tabletRegistry = true, tabletFiles = true and an applicable definition under Jobs Base setting Registries; the new default leaves them off. Citizen and vehicle files do not require that setting. Turning the optional registers off does not delete saved register data.

Required permission correction: after installing the matching packages, perform a full server restart. In the Boss Menu, reselect Manage offences for the Police ranks and organization units that should edit the offence catalog. Its ID changes from 2101 to 2401; old Police grants do not authorize this action. Ambulance continues to use 2101 for medical evaluations, so never replace 2101 globally in the database. A full-access rank keeps its existing full-access behavior.

No new Police provider credentials, callback settings or Creator definitions need merging. Existing prisons, social-work locations, trackers, cameras and records do not need recreating. There is no manual action for the transport, dropdown or mugshot fixes beyond installing the complete package. Newly captured booking photos use the shared gallery; this release does not bulk-import older gallery rows.

Optional performance diagnostics: extra profiler information stays disabled by default. To make a support recording, place setr sky_profiler 1 in server.cfg before the Sky ensure lines and restart the server. Run profiler record 1000 in the server console, wait until profiler status reports completion, then run profiler saveJSON sky-release-profile.json. Share the file only when requested by support. To turn the extra information off, set setr sky_profiler 0 and restart again. This is not a /jobconfig setting; enabling it neither starts a recording nor uploads data automatically.

Police SQL: with Config.AutoExecuteQuery enabled, startup applies the new schema and preserves existing profile-sharing recipients. With automatic migrations disabled, run the complete SQL below against the backed-up existing database before starting Police. It adds sky_job_reports.revision, sky_job_bolos.revision and sky_job_warrants.revision, each INT NOT NULL DEFAULT 1, plus the three InnoDB tables sky_police_document_outbox, sky_police_profile_shares and sky_police_profile_share_state. The final copy into the state table preserves any existing profile grants and is safe to repeat. Existing cases already have their revision column from 1.33.0.

CREATE TABLE IF NOT EXISTS `sky_police_document_outbox` (
    `sequence_id` BIGINT UNSIGNED NOT NULL AUTO_INCREMENT,
    `id` CHAR(36) NOT NULL,
    `payload_json` LONGTEXT NOT NULL,
    `created_at` DATETIME NOT NULL DEFAULT CURRENT_TIMESTAMP,
    `delivered_at` DATETIME NULL,
    PRIMARY KEY (`sequence_id`),
    UNIQUE KEY `uq_police_document_event` (`id`),
    KEY `idx_police_document_pending` (`delivered_at`, `sequence_id`)
) ENGINE=InnoDB;
CREATE TABLE IF NOT EXISTS `sky_police_profile_shares` (
    `id` BIGINT UNSIGNED NOT NULL AUTO_INCREMENT,
    `job_id` INT NOT NULL,
    `kind` VARCHAR(16) NOT NULL,
    `profile_id` INT NOT NULL,
    `owner_job` VARCHAR(64) NOT NULL,
    `recipient_job` VARCHAR(64) NOT NULL,
    `title` VARCHAR(160) NOT NULL,
    `updated_at` DATETIME NOT NULL DEFAULT CURRENT_TIMESTAMP,
    PRIMARY KEY (`id`),
    UNIQUE KEY `uq_profile_share` (`job_id`, `kind`, `profile_id`, `owner_job`, `recipient_job`),
    KEY `idx_profile_share_recipient` (`job_id`, `kind`, `recipient_job`, `owner_job`, `updated_at`)
) ENGINE=InnoDB;

SET @sky_update_sql = IF(
    EXISTS(SELECT 1 FROM information_schema.COLUMNS WHERE TABLE_SCHEMA = DATABASE() AND TABLE_NAME = 'sky_job_reports' AND COLUMN_NAME = 'revision'),
    'SELECT 1', 'ALTER TABLE `sky_job_reports` ADD COLUMN `revision` INT NOT NULL DEFAULT 1'
);
PREPARE sky_update_statement FROM @sky_update_sql;
EXECUTE sky_update_statement;
DEALLOCATE PREPARE sky_update_statement;

CREATE TABLE IF NOT EXISTS `sky_police_profile_share_state` (
    `id` BIGINT UNSIGNED NOT NULL AUTO_INCREMENT,
    `job_id` INT NOT NULL,
    `kind` VARCHAR(16) NOT NULL,
    `profile_id` INT NOT NULL,
    `owner_job` VARCHAR(64) NOT NULL,
    `recipients` TEXT NOT NULL,
    `title` VARCHAR(160) NOT NULL,
    `revision` INT NOT NULL DEFAULT 1,
    `updated_at` DATETIME NOT NULL DEFAULT CURRENT_TIMESTAMP,
    PRIMARY KEY (`id`),
    UNIQUE KEY `uq_profile_share_state` (`job_id`, `kind`, `profile_id`, `owner_job`)
) ENGINE=InnoDB;

INSERT IGNORE INTO `sky_police_profile_share_state`
    (`job_id`, `kind`, `profile_id`, `owner_job`, `recipients`, `title`, `revision`, `updated_at`)
SELECT `job_id`, `kind`, `profile_id`, `owner_job`, JSON_ARRAYAGG(`recipient_job`), MAX(`title`), 1, MAX(`updated_at`)
FROM `sky_police_profile_shares` GROUP BY `job_id`, `kind`, `profile_id`, `owner_job`;

SET @sky_update_sql = IF(
    EXISTS(SELECT 1 FROM information_schema.COLUMNS WHERE TABLE_SCHEMA = DATABASE() AND TABLE_NAME = 'sky_job_bolos' AND COLUMN_NAME = 'revision'),
    'SELECT 1', 'ALTER TABLE `sky_job_bolos` ADD COLUMN `revision` INT NOT NULL DEFAULT 1'
);
PREPARE sky_update_statement FROM @sky_update_sql;
EXECUTE sky_update_statement;
DEALLOCATE PREPARE sky_update_statement;
SET @sky_update_sql = IF(
    EXISTS(SELECT 1 FROM information_schema.COLUMNS WHERE TABLE_SCHEMA = DATABASE() AND TABLE_NAME = 'sky_job_warrants' AND COLUMN_NAME = 'revision'),
    'SELECT 1', 'ALTER TABLE `sky_job_warrants` ADD COLUMN `revision` INT NOT NULL DEFAULT 1'
);
PREPARE sky_update_statement FROM @sky_update_sql;
EXECUTE sky_update_statement;
DEALLOCATE PREPARE sky_update_statement;

Keep existing Police records and sky_police_workspace. clear.sql is a destructive reset tool and is never a normal update step. These migrations do not require a record reset or reimport.

Shared printing SQL: complete the Jobs Base 1.45.0 migration before Police starts. The required shared tables are sky_jobs_record_shares, sky_jobs_record_share_state and sky_jobs_printed_documents; use that release's supplied sky_jobs_base/import.sql additions or its enabled automatic migration. Police's SQL does not replace the Jobs Base migration.

Inventory and printer setup: there is no new Police-owned inventory item or stream model. The new Print action uses Jobs Base's job_document item from sky_jobs_base/config/inventory/items_ox.lua and image sky_jobs_base/config/inventory/job_document.png. Printing requires a metadata-capable inventory; for ox_inventory, merge the entry below into ox_inventory/data/items.lua and copy the image to ox_inventory/web/images/job_document.png. Use the equivalent unique, usable and non-stackable item in another supported inventory.

["job_document"] = {
    label = "Document",
    weight = 10,
    stack = false,
    close = true,
    consume = 0,
    description = "Printed copy of a job record.",
    client = { image = "job_document.png" },
},

Keep existing station printers. If none exists, add one in /jobconfig → Police → department → Locations and review printerSettings; printer_paper and printer_ink are only needed when the respective consumption is enabled. The new per-job documentAppearance extension optionally sets leftImage, rightImage and watermark HTTP(S) URLs. Jobs Base's global Config.Printers.documentAppearance defaults to three empty strings. No logos or extra images are required to use the plain document layout.

Printed copies capture the saved record when produced. Only the requesting officer can collect their queued output; after collection, possession of the metadata-bearing item allows reading that unchanged paper copy even after the source is edited or digital sharing is revoked. /jobconfig installs neither the item, image, SQL, runtime nor manifest.

Perform a full server restart: database, framework and edited inventory first, then Base 1.42.0, Jobs Base 1.45.0 and Police 1.34.0 with the matching installed jobs. Reassign Police Manage offences (2401) to the intended ranks and organization units after startup. Confirm the new versions and resolve startup or migration errors before admitting players.

Test offence editing with an allowed rank and read-only access with a rank lacking that right. Check File Explorer without DOJ, including its individual app restrictions and the optional Registry switch. Create an automatically numbered case using your department prefix; verify an existing number stays unchanged. Share a saved profile or record with another job, read it as that recipient, then revoke access. Print it, collect the item and reopen its paper copy. Edit the same report or sharing list in two sessions and verify the older save cannot overwrite the newer one. Capture a booking mugshot and check the correct department gallery. If compatible DOJ is installed, verify queued document changes arrive after it returns. These are live-server checks; a successful build alone does not establish them.

Update Base to 1.41.0 and Jobs Base to 1.44.0 before installing sky_policejob 1.33.0. These instructions cover 1.32.0 → 1.33.0; complete earlier migrations first when upgrading from an older version. Stop the server and back up the resource, database, customized files and saved configurator/creator data.

Install the matching 1.33.0 download. Update every path in Changed Files, delete and reinsert sky_policejob/source/*, and replace sky_policejob/config/locales/* completely. Remove the exact paths under Removed Files and apply any listed renames. Preserve unrelated files, writable data and custom assets; merge the configuration changes in this tab into your customized public files.

Replace source/* and fxmanifest.lua from the same download even when optional diagnostics remain off. Profiler instrumentation is confined to Lua in source/ and the generated manifest. Public configuration, integration and compatibility files match the uninstrumented source; their functional changes are listed separately for this release. If an older profiler package modified public files, restore those once from the clean new package and reapply your own edits.

In sky_policejob/config/config.lua, add Config.PoliceTablet.apps.files = false. The setting was absent in 1.32.0. With /jobconfig, the setting is Police → Settings → Tablet → File Explorer (tabletFiles). It is an optional preview and requires a running, compatible sky_dojjob; this release does not enable it automatically. If an administrator already saved tabletFiles = true on a development build, that override remains and must be switched off explicitly if the preview is unwanted. Standalone Police apps continue to work without DOJ.

The Config.CreatorInteractions.jailcreator.jail_public_blip definition previously contained only label = "Jail". Merge the full new definition below. This is a creator definition, not a new ordinary saved settings switch; check each prison's saved public-blip override in the Jail Creator as well. It remains a map marker, not an interaction point.

Config.CreatorInteractions.jailcreator.jail_public_blip = {
            label = "Jail",
            interaction = false,
            blip = {
                enabled = true,
                name = "Jail",
                sprite = 188,
                color = 1
            }
        }

In the Boss Menu, grant Manage offences (MANAGE_OFFENCES) only to ranks that should create, change or delete offences. Other Police ranks retain read access; job membership alone no longer authorizes catalog changes. Existing full-access policy and DOJ-owned catalogs retain their separate authority. Review shared record-clearance levels in Jobs Base 1.44.0 before using restricted records.

For linked local Police warrants, automatic completion requires every subject to have served their latest linked sentence. Early release and escape do not complete the warrant. DOJ warrants remain governed by DOJ. The new investigation fields do not require resetting existing cases. No other executable config.lua values change.

Optional performance diagnostics

Extra profiler information remains disabled by default. For a support recording, add setr sky_profiler 1 to server.cfg before the Sky ensure lines and restart the server. In the server console, run profiler record 1000, wait for profiler status to report completion, then run profiler saveJSON sky-release-profile.json. Share that file when requested by support. Set setr sky_profiler 0 and restart again to disable the extra information. This is not a /jobconfig setting; enabling it does not start a recording or upload data automatically.

With Config.AutoExecuteQuery enabled, startup applies the new schema. If automatic migrations are disabled, run this upgrade against your existing backed-up database before starting Police. It adds sky_job_cases.investigation (LONGTEXT NULL), sky_job_cases.revision (INT NOT NULL DEFAULT 1), sky_job_jail_records.sentence_completed_at (DATETIME NULL), the warrant and owner indexes, and sky_police_workspace. Existing cases start at revision 1. The owner index expects the existing manual_owner_identifier column from earlier releases; complete those migrations first.

SET @sky_update_sql = IF(
    EXISTS(SELECT 1 FROM information_schema.COLUMNS WHERE TABLE_SCHEMA = DATABASE() AND TABLE_NAME = 'sky_job_cases' AND COLUMN_NAME = 'investigation'),
    'SELECT 1', 'ALTER TABLE `sky_job_cases` ADD COLUMN `investigation` LONGTEXT NULL'
);
PREPARE sky_update_statement FROM @sky_update_sql;
EXECUTE sky_update_statement;
DEALLOCATE PREPARE sky_update_statement;

SET @sky_update_sql = IF(
    EXISTS(SELECT 1 FROM information_schema.COLUMNS WHERE TABLE_SCHEMA = DATABASE() AND TABLE_NAME = 'sky_job_cases' AND COLUMN_NAME = 'revision'),
    'SELECT 1', 'ALTER TABLE `sky_job_cases` ADD COLUMN `revision` INT NOT NULL DEFAULT 1'
);
PREPARE sky_update_statement FROM @sky_update_sql;
EXECUTE sky_update_statement;
DEALLOCATE PREPARE sky_update_statement;

SET @sky_update_sql = IF(
    EXISTS(SELECT 1 FROM information_schema.COLUMNS WHERE TABLE_SCHEMA = DATABASE() AND TABLE_NAME = 'sky_job_jail_records' AND COLUMN_NAME = 'sentence_completed_at'),
    'SELECT 1', 'ALTER TABLE `sky_job_jail_records` ADD COLUMN `sentence_completed_at` DATETIME NULL'
);
PREPARE sky_update_statement FROM @sky_update_sql;
EXECUTE sky_update_statement;
DEALLOCATE PREPARE sky_update_statement;

SET @sky_update_sql = IF(
    EXISTS(SELECT 1 FROM information_schema.STATISTICS WHERE TABLE_SCHEMA = DATABASE() AND TABLE_NAME = 'sky_job_jail_records' AND INDEX_NAME = 'idx_job_jail_warrant'),
    'SELECT 1', 'CREATE INDEX `idx_job_jail_warrant` ON `sky_job_jail_records` (`job_id`, `warrant_id`, `citizen_identifier`, `id`)'
);
PREPARE sky_update_statement FROM @sky_update_sql;
EXECUTE sky_update_statement;
DEALLOCATE PREPARE sky_update_statement;

SET @sky_update_sql = IF(
    EXISTS(SELECT 1 FROM information_schema.STATISTICS WHERE TABLE_SCHEMA = DATABASE() AND TABLE_NAME = 'sky_job_vehicle_profiles' AND INDEX_NAME = 'idx_vehicle_profile_owner'),
    'SELECT 1', 'CREATE INDEX `idx_vehicle_profile_owner` ON `sky_job_vehicle_profiles` (`job_id`, `manual_owner_identifier`)'
);
PREPARE sky_update_statement FROM @sky_update_sql;
EXECUTE sky_update_statement;
DEALLOCATE PREPARE sky_update_statement;

CREATE TABLE IF NOT EXISTS `sky_police_workspace` (
    `id` BIGINT UNSIGNED NOT NULL AUTO_INCREMENT,
    `owner_identifier` VARCHAR(128) NOT NULL,
    `job` VARCHAR(64) NOT NULL,
    `parent_id` BIGINT UNSIGNED NULL,
    `kind` VARCHAR(16) NOT NULL,
    `name` VARCHAR(160) NOT NULL,
    `target_type` VARCHAR(24) NULL,
    `target_id` VARCHAR(32) NULL,
    `created_at` DATETIME NOT NULL DEFAULT CURRENT_TIMESTAMP,
    PRIMARY KEY (`id`),
    INDEX `idx_police_workspace_owner` (`owner_identifier`, `job`, `parent_id`),
    INDEX `idx_police_workspace_parent` (`parent_id`)
) ENGINE=InnoDB;

No new inventory item is required. Keep all Police records. clear.sql is a destructive reset tool and must not be run as an update step.

Restart the database, framework and any edited inventory first, then Base, Jobs Base and the installed job resources. Confirm 1.33.0 and resolve startup errors before admitting players. Test offence-catalog editing with a permitted rank and read-only access with an unpermitted rank. Save an investigation from two open sessions and verify stale edits are rejected. Complete a sentence and inspect its linked warrant; an escape or early release must not complete it. Check a disabled jail marker and a prison exit after intake grace. Test citizen-to-vehicle links. If enabling the Explorer preview, test its folders and shared documents with the matching DOJ installation; with the preview off, use the standalone Police apps.

Update Base to 1.40.0 and Jobs Base to 1.43.0 before installing sky_policejob 1.32.0. Vehicle documents also require Mechanic 1.29.0 and Police 1.32.0 together. These instructions cover 1.31.0 → 1.32.0; complete earlier migrations first when upgrading from an older version. Stop the server and back up the resource, database, customized files and saved configurator/creator data.

Install the matching 1.32.0 package. Update every path in Changed Files, delete and reinsert sky_policejob/source/*, and replace sky_policejob/config/locales/* completely. Remove every exact path listed under Removed Files and apply any listed renames. Preserve unrelated files, writable data and your own custom assets; merge the configuration changes in this tab into customized public files.

Replace source/* and fxmanifest.lua from the same download even when optional diagnostics remain off. The profiler only instruments Lua inside source/ and adds its manifest entries; public configuration, integration and compatibility files must match the uninstrumented package. Apply the separate functional public-file changes listed for this release. If an older profiler package modified public files, restore those once from the clean new package and reapply your edits.

In sky_policejob/config/config.lua, add this assignment after the existing Config.PoliceTablet table declaration: Config.PoliceTablet.apps.confiscations was absent and now defaults to true.

Config.PoliceTablet.apps.confiscations = true

With /jobconfig enabled, use /jobconfig > sky_policejob > Settings and search for Confiscations (tabletConfiscations) to enable or hide the app. The app provides department-scoped read access to on-duty police. It does not allow editing confiscation history. Existing saved settings remain in effect; a missing new key uses the shipped default. With the configurator disabled, the Lua value is authoritative.

Vehicle inspections and registrations are enabled and configured in Mechanic 1.29.0; Police only reads their status and signed history. Complete the Base/Jobs Base/Mechanic database and service-point setup before testing these records. Other Police settings, fine amounts, jail rules and stored creator positions are unchanged. The jail blip's derived position remains read-only; its teleport button does not enable the map blip.

Optional performance diagnostics

Extra profiler information remains disabled by default. Normal use needs no diagnostic setting. For a support recording, add setr sky_profiler 1 to server.cfg before the Sky ensure lines and restart the server. In the server console, run profiler record 1000, wait for profiler status to report completion, then run profiler saveJSON sky-release-profile.json. Share that file only when requested by support. Set setr sky_profiler 0 and restart again to disable the extra information. This is not a /jobconfig option; enabling it does not start a recording or upload data automatically.

Back up the database. The new sky_job_billing_history.offences LONGTEXT NULL column stores the selected offence snapshot for new fines. With Police Config.AutoExecuteQuery = true, its startup migration adds the column. With it disabled, execute this idempotent upgrade in the active game database (the same new column is included in sky_policejob/import.sql):

SET @sky_release_sql = IF(
    EXISTS(SELECT 1 FROM information_schema.COLUMNS WHERE TABLE_SCHEMA = DATABASE() AND TABLE_NAME = 'sky_job_billing_history' AND COLUMN_NAME = 'offences'),
    'SELECT 1', 'ALTER TABLE `sky_job_billing_history` ADD COLUMN `offences` LONGTEXT NULL'
);
PREPARE sky_release_migration FROM @sky_release_sql;
EXECUTE sky_release_migration;
DEALLOCATE PREPARE sky_release_migration;

Also complete the Jobs Base 1.43.0 schema update, including sky_job_confiscations and the payment-reference column/index. Vehicle documents require the Base owned-vehicle ID, Jobs Base registry tables and Mechanic invoice migration. Historical fines without offence snapshots remain readable; do not invent old offence lists or confiscations. No new items are required. Do not run clear.sql for a normal update.

Confirm version 1.32.0. Issue a test fine with multiple selected offences and check the receipt, amount and citizen history; test the actual multicharacter framework. Confiscate one item successfully and check the correct department, officer and citizen; a failed transfer must not create a successful seizure record. Read a Mechanic-issued signed document without editing it. Remove a speed camera and verify its object/CCTV entry disappear. Test the selected vehicle occupant and the derived jail-position teleport.

Update sky_base to 1.39.0 and sky_jobs_base to 1.42.0 before installing sky_policejob 1.31.0. These steps cover 1.30.1 → 1.31.0. Follow earlier update instructions first when upgrading from an older version. Stop the server and back up the resource, database, custom settings, and saved configurator data.

Install the matching 1.31.0 package. Update every path listed in Changed Files, delete and reinsert sky_policejob/source/*, and replace sky_policejob/config/locales/* completely. Merge the configuration changes in this tab into your customized files. Preserve writable data and generated user content.

Required profiler files

For the profiler update, replace the complete sky_policejob/source/* tree and sky_policejob/fxmanifest.lua from the same download, even if diagnostics stay disabled. Delete the old source/ folder before copying the new one.

The profiler builder leaves configuration, integration and compatibility files unchanged. Apply any separate configuration or integration changes listed for this release as usual.

If you previously installed an older profiler package that also modified files outside source/, restore those affected files once from the unmodified versions in the new download and reapply your custom edits. Later profiler-only updates do not require this step.

In sky_policejob/config/config.lua, Config.Jail.requireJailTerminal changes from true to false:

Config.Jail.requireJailTerminal = false

This makes a jail terminal optional when assigning a sentence. Keep true if your server requires officers to use the terminal. Config.Jail.assignRange = 8.0 and Config.Jail.terminalRange = 5.0 remain unchanged. The target must still be nearby and the selected jail still needs valid arrival and release points.

With Config.UseJobConfigurator = true, review Police → Jail and the setting jailRequireJailTerminal. A saved true override continues to require a terminal after updating. Change it there if you want the new default. With the configurator disabled, merge the file value above and restart.

Speed-camera billing needs an officer who belongs to the camera's department, is on duty, and is allowed to issue invoices through the selected billing provider. If the owner is ineligible, another eligible officer is selected. For Apex, check that officer's billing permission; creating a fine does not automatically pay it.

Optional performance diagnostics

Sky's extra profiler information is disabled by default. This update does not start recordings or send data automatically. No configuration change is required for normal use. If support needs a performance recording, add the following line to server.cfg before the Sky ensure lines, then restart the server:

setr sky_profiler 1

This global setting is configured in server.cfg; it is not managed by /jobconfig. The previous state with no setting remains disabled. Set the value to 1 only when you want the additional diagnostics.

Run profiler record 1000 in the server console for a server delay, or in the player's F8 console for a client problem. Reproduce the issue during the recording. Wait until profiler status reports that recording has stopped, then run profiler saveJSON sky-profile.json in the same console to save the capture. These are the standard FiveM profiler commands.

After diagnostics, change the line to setr sky_profiler 0 and restart again. Keep the new package files installed; disabling diagnostics does not require editing Lua or removing manifest entries.

No SQL schema, inventory item, or streamed-asset migration is introduced. Replace all Police locales and preserve existing jails, sentences, speed cameras, and records. clear.sql is a destructive reset tool and is not part of this update.

Assign a sentence with the intended terminal requirement and verify missing-location messages. Confirm the submit button cannot send the same request twice. Test a speed-camera fine with an eligible officer, then with its owner off duty or in another job. Check tackle, cuff, and release actions without the removed notifications.

Update sky_jobs_base to 1.41.1 and use sky_base 1.38.0 before updating sky_policejob. These steps cover 1.30.0 → 1.30.1; complete earlier release instructions first if you are upgrading from an older version. Stop the server and back up the resource, database, saved Job Configurator settings and custom configuration. Preserve generated reports and other writable data.

Install 1.30.1 as a matching package. Update every path in Changed Files, delete and reinsert sky_policejob/source/*, and replace sky_policejob/config/locales/* completely. Merge the configuration instructions in this tab into customized files; retain intentional settings and persistent data.

No public configuration value or /jobconfig setting changes between the tagged 1.30.0 and 1.30.1 releases. Keep your existing jail configuration, alert recipients and saved overrides. Jail alerts now use the configured Police language; update the full locale folder with the runtime.

Replace all sky_policejob/config/locales/* so the new jail alert translations are present in every bundled language. No SQL schema, inventory item, image, stream asset or provider secret changes are required. Preserve existing jail records. Do not run clear.sql; it is a reset tool, not an update step.

Start providers, Base, Jobs Base and Police in that order. Escape the assigned jail by helicopter, reopen the prisoner list and confirm that the escaped status and remaining sentence are retained after the original sentence deadline. Separately verify that completing a sentence still produces a normal release. Check escape, wrong-PIN and helicopter jail alerts in your configured language, including an unnamed jail.

Update sky_base to 1.38.0 and sky_jobs_base to 1.41.0 before updating sky_policejob. Stop the server and back up the complete sky_policejob resource, its database and inventory data, saved Job Configurator settings where applicable, and intentional public configuration edits. Preserve writable reports and other generated data outside the replaceable source files.

Install 1.30.0 as a consistent package. Replace every file listed in Changed Files, delete and reinsert sky_policejob/source/*, and replace sky_policejob/config/locales/* completely. Merge the public configuration changes listed in this tab into your customized files; do not copy old configuration files over the new package wholesale. Keep the manifest, built UI, runtime and dependencies from the matching release set.

In sky_policejob/config/config.lua, add the complete Config.Keybinds block. This table and its paths were absent in 1.29.0; 1.30.0 uses the following string defaults instead of scattered settings or fixed controls. Preserve your chosen keys when transferring old settings.

Config.Keybinds = {
    policeBillingControl200 = "ESCAPE",
    policeBillingControl322 = "ESCAPE",
    policeEditorControl73 = "X",
    policeEditorControl322 = "ESCAPE",
    policeEditorControl21 = "LSHIFT",
    policeEditorControl36 = "LCONTROL",
    policeEditorControl172 = "UP",
    policeEditorControl32 = "W",
    policeEditorControl173 = "DOWN",
    policeEditorControl33 = "S",
    policeEditorControl174 = "LEFT",
    policeEditorControl34 = "A",
    policeEditorControl175 = "RIGHT",
    policeEditorControl35 = "D",
    policeEditorControl10 = "PAGEUP",
    policeEditorControl11 = "PAGEDOWN",
    policeEditorControl44 = "Q",
    policeEditorControl38 = "E",
    policeEditorControl191 = "RETURN",
    policeEditorControl177 = "BACK",
    policeEditorControl201 = "RETURN",
    policeEditorControl202 = "ESCAPE",
    policeEditorControl37 = "TAB",
    tackleKey = "N",
    tackleCuffKey = "E",
    tackleReleaseKey = "X",
    gpsTrackerRemoveKey = "E",
    jailJobsCleaningPickupKey = "E",
    jailJobsCleaningDumpsterKey = "E",
    jailJobsCarryPickupKey = "E",
    jailJobsCarryDropoffKey = "E",
    jailJobsCarryInspectKey = "G",
    vehicleRadarToggleKey = "Y",
    vehicleRadarIncreaseLimitKey = "ADD",
    vehicleRadarDecreaseLimitKey = "SUBTRACT",
    vehicleRadarModeFrontKey = "NUMPAD7",
    vehicleRadarModeRearKey = "NUMPAD4",
    vehicleRadarXmitFrontKey = "NUMPAD8",
    vehicleRadarXmitRearKey = "NUMPAD5",
    vehicleRadarLockFrontKey = "NUMPAD9",
    vehicleRadarLockRearKey = "NUMPAD6",
}

With Config.UseJobConfigurator = true, open /jobconfig → this resource → General → Keybinds. Every key inside the block is also its exact saved setting ID; for example Config.Keybinds.policeBillingControl200 is saved under the same final name. Saved overrides take precedence over the generated defaults. Numeric overrides migrate to their corresponding QWERTY key, and -1 migrates to an empty string. An empty string means no initial binding. Players retain their own assignments in Settings → Key Bindings → FiveM; changing a server default does not overwrite those assignments.

With Config.UseJobConfigurator = false, edit these paths in the file and restart the resource. Keep mouse/controller prefixes exactly as shown. Command permissions and Config.AutoExecuteQuery remain file settings; their reordering does not change their values.

Remove the following old paths after transferring your overrides. The new paths all live in config/config.lua; the saved setting ID is the final segment of each new path.

Delete the now-empty old Config.VehicleRadar.controls block after moving all nine values. Keep existing radar/tackle command names, duty requirements, job lists, and camera configuration. Config.PrimaryColor, command permissions and sharing defaults were only moved within the file; their shipped values are unchanged. No new CCTV or vehicle-registry config option is required.

No Police SQL schema, new inventory item, image, production stream file, or provider secret is introduced. Existing camera, GPS, monitoring and vehicle registry data is reused. Install the matching Jobs Base synchronization/key-mapping runtime. Do not run clear.sql: it is a destructive reset tool, not an update step.

Restart Base, Jobs Base and Police, then rebind tackle, radar, GPS removal, jail work and editor actions. Confirm current key labels and existing input suppression. Check camera/monitor removal and late joining, Crime CCTV control when installed, a camera-relevant versus unrelated configuration edit, and BOLO links for lowercase, padded, empty and whitespace-only plates.

Install Base 1.37.0 and Jobs Base 1.40.0, stop the server, and back up the resource, Job Configurator settings, Police record tables, sky_jobs, jail/social-work data, map zones, and vehicle registry data. Record every intentional Share setting before updating.

Install 1.29.0 as one clean package. Its manifest, frontend, locales, migration runtime, and source files must match.

Delete and reinsert the complete resource. At minimum replace fxmanifest.lua, import.sql, config/config.lua, the complete config/locales and source directories, and the built frontend.

The resource-owned sharing defaults change from Police-only group access to Police group plus DOJ job access:

records = {
    cases = { enabled = true, jobs = { "doj" }, groups = { "police" } },
    reports = { enabled = true, jobs = { "doj" }, groups = { "police" } },
    warrants = { enabled = true, jobs = { "doj" }, groups = { "police" } },
    bolos = { enabled = true, jobs = { "doj" }, groups = { "police" } },
    vehicleRecords = { enabled = true, jobs = { "doj" }, groups = { "police" } }
}

In 1.28.0, the first four jobs arrays were empty and vehicleRecords was absent. Existing /jobconfig settings override these defaults. Open every Police job's Share section after migration and confirm which DOJ jobs/groups may read each record type; do not delete existing intentional partners when adding doj.

With Config.AutoExecuteQuery = true, start Police once and wait for migration completion. Otherwise run the complete 1.29.0 import.sql. The coordinated schema update:

• Expands the map-zone label column from VARCHAR(64) to VARCHAR(80).
• Creates sky_job_vehicle_registry_identities with a stable UUID identity, job/provider keys, current plate, timestamps, retirement state, a unique provider-key index, a plate index, and the Jobs Base relationship.
• Adds remaining_ms INT NOT NULL DEFAULT 0 to sky_job_jail_records.
• Adds nullable external_reference VARCHAR(128) to sky_job_social_work_records plus a unique (job_id, external_reference) index.

Back up before running the migration. No new Police inventory item, image, or stream asset is required.

Start Base, Jobs Base, and Police in order and confirm migration success. Capture and open fingerprint evidence, inspect a jailed and non-jailed citizen, change a registered vehicle's plate and verify the stable record identity, and test each DOJ sharing permission with both allowed and denied users. Complete, reconnect during, and exceed the configured inactivity limit for social work; verify synchronized remaining work and the intended jail result. Test ankle-monitor restore/removal, a delayed speed-camera capture after state changes, all four wheel clamps, a long offence catalogue, and number inputs in FiveM CEF.

Before updating, install Base 1.36.0 and Jobs Base 1.39.0, stop the server, and back up the resource, intentional config/functions.lua edits, Job Configurator tables, and Police/Jobs Base vehicle data.

Install 1.28.0 as one clean package. The manifest, UI, locales, config functions, and source runtime must match.

Delete and reinsert the complete resource. At minimum replace fxmanifest.lua, config/config.lua, config/functions.lua, and the complete config/locales and source directories plus the built UI.

Add persistOnDisconnect after the unchanged placement/removal policy values in Config.AnkleMonitor:

Config.AnkleMonitor.persistOnDisconnect = true

This path was absent in 1.27.1. Its shipped 1.28.0 value is true; inside the table it belongs between unchanged returnOnRemove = true and placeDistance = 2.0. /jobconfig uses the exact key ankleMonitorPersistOnDisconnect; saved settings override the file. Explicit officer removal or player cutting still deletes the monitor regardless of this persistence setting.

config/functions.lua is plaintext/custom integration code, not Job Configurator data. Its exact behavior changes are:

Keep the full new implementations because the fleet branch also preserves the ten-second action, confirms that the vehicle is still present, and relies on server-side group, duty, bucket, distance, state, reason, and fee validation. Reapply custom provider edits only after those paths remain intact.

Police has no new or changed import.sql statement in this release. Persistent job-fleet impounds require the complete Jobs Base 1.39.0 migration, including state = 'impounded', impound metadata columns, key-holder data, and idx_job_state. Run that migration before Police starts. Existing ankle-monitor storage is reused; no manual Police schema change is required.

No new Police inventory item, image, stream asset, or provider credential is required. OP support requires a started op-garages resource and its working impoundmenu command.

• The console reports Base 1.36.0, Jobs Base 1.39.0, and Police 1.28.0 in that order.
• The Jobs Base fleet table contains the new impound state, columns, and index before Police starts.
• A parked Jobs Base fleet vehicle can be impounded with a reason and fee, disappears from normal parking, and can be released through the fleet flow.
• Invalid job, duty, bucket, distance, state, reason, or fee data is rejected by the server.
• OP Garages opens its native impound menu for both configured Police storage and impound actions.
• An ankle monitor restores after reconnect/restart when ankleMonitorPersistOnDisconnect is true and disappears on disconnect when false.
• Explicit ankle-monitor removal and cutting still remove persisted state and return or consume items according to the existing settings.
• Vehicle-registry searches work with the active framework database collation.
• Jail electrical and fence breakout completion only succeeds with valid location, item, and power state.

Update Base to 1.35.1 and Jobs Base to 1.38.1, stop the server, and back up Police.

Install 1.27.1 as one clean package; a .1 manifest beside the .0 built UI is a mixed update.

Delete and reinsert the resource. Replace fxmanifest.lua, the built UI, and config/locales completely.

No public config value or /jobconfig key changed in 1.27.1.

No SQL, item, image, stream asset, or provider credential changed.

• Base 1.35.1, Jobs Base 1.38.1, and Police 1.27.1 start in order.
• Police tablet, record, evidence, dispatch, and jail labels fall back to readable English when a translation key is absent.

Update sky_base to 1.35.0 and sky_jobs_base to 1.38.0. Stop the server; back up the Police resource, Job Configurator tables, record tables, CCTV data, and inventory definitions.

Install 1.27.0 as one complete package. Do not mix its record schema, UI, source runtime, generated defaults, or streamed tape models with 1.26.0.

Delete and reinsert the complete resource. Replace fxmanifest.lua, import.sql, config/config.lua, config/locales, source, the built UI, config/inventory/README.md, crime_scene_tape.png, and all seven tape stream assets. Preserve clear.sql only as the new destructive reset utility; never execute it as an update step.

Add the complete police_sharing_defaults before Config.Jobs, then assign sharing = police_sharing_defaults to every intended Police/Sheriff job:

local police_sharing_defaults = {
    enabled = true,
    records = {
        cases = { enabled = true, jobs = {}, groups = { "police" } },
        reports = { enabled = true, jobs = {}, groups = { "police" } },
        warrants = { enabled = true, jobs = {}, groups = { "police" } },
        bolos = { enabled = true, jobs = {}, groups = { "police" } }
    },
    training = {
        courses = { enabled = true, jobs = {}, groups = { "police" } },
        qualifications = { enabled = true, jobs = {}, groups = { "police" } }
    },
    links = { warrantSubjects = true, boloVehicles = true }
}

Empty target-job lists share nothing outside the police group until configured in the Share tab.

Add this item row to each intended job shop:

{ name = "crime_scene_tape", label = "Crime Scene Tape", price = 150 },

Add the complete tape configuration:

Config.CrimeSceneTape = {
    enabled = true,
    item = "crime_scene_tape",
    model = "sky_crime_scene_tape",
    label = "Crime Scene Tape",
    jobs = { "police", "sheriff" },
    requireOnDuty = true,
    consumeItem = true,
    returnItemOnRemove = true,
    enforceRemovalAccess = true,
    streamDistance = 150.0,
    removeDistance = 2.5,
    zOffset = 0.0,
    dynamic = false,
    variableLength = {
        enabled = true, minLength = 1.0, maxLength = 12.0, lengthStep = 0.25,
        maxPlacementDistance = 15.0, tapeHeight = 1.035, sag = 0.115,
        showPosts = false, collisionEnabled = true,
        postModel = "sky_crime_scene_tape_post",
        sections = {
            { model = "sky_crime_scene_tape_section_200", length = 2.0 },
            { model = "sky_crime_scene_tape_section_100", length = 1.0 },
            { model = "sky_crime_scene_tape_section_050", length = 0.5 },
            { model = "sky_crime_scene_tape_section_025", length = 0.25 }
        }
    }
}

Add this complete motion block:

Config.Cctv.motionDetection = {
    enabled = true,
    defaultCameraEnabled = true,
    detectionRadius = 25.0,
    fieldOfView = 90.0,
    minimumSpeed = 0.35,
    checkIntervalMs = 750,
    clientCooldownMs = 5000,
    alertCooldownSeconds = 60,
    jobs = { "police" }
}

Motion detection runs from the reporting client's current ped or vehicle. The client applies minimumSpeed, radius/FOV, line of sight, and clientCooldownMs; the server confirms reporter distance and alertCooldownSeconds for the camera before creating the dispatch. Install the current client and server source together.

Apply every remaining exact config change:

/jobconfig manages Crime Scene Tape, CCTV motion detection, shot probabilities, and per-job Share data; saved overrides win over Lua values.

Exact /jobconfig keys

• Crime Scene Tape: crimeSceneTapeEnabled, crimeSceneTapeItem, crimeSceneTapeModel, crimeSceneTapeLabel, crimeSceneTapeJobs, crimeSceneTapeRequireOnDuty, crimeSceneTapeConsumeItem, crimeSceneTapeReturnItemOnRemove, crimeSceneTapeEnforceRemovalAccess, crimeSceneTapeStreamDistance, crimeSceneTapeRemoveDistance, crimeSceneTapeZOffset, crimeSceneTapeDynamic, crimeSceneTapeVariableLength, crimeSceneTapeMinLength, crimeSceneTapeMaxLength, crimeSceneTapeLengthStep, crimeSceneTapeMaxPlacementDistance, crimeSceneTapeTapeHeight, crimeSceneTapeSag, crimeSceneTapeShowPosts, crimeSceneTapeCollisionEnabled, crimeSceneTapePostModel, and crimeSceneTapeSections.
• CCTV motion detection: cctvMotionDetectionEnabled, cctvMotionDefaultCameraEnabled, cctvMotionDetectionRadius, cctvMotionFieldOfView, cctvMotionMinimumSpeed, cctvMotionCheckIntervalMs, cctvMotionClientCooldownMs, cctvMotionAlertCooldownSeconds, and cctvMotionJobs.
• Shots fired: dispatchShotsFiredChance and dispatchShotsFiredSuppressedChance.
• Share-tab recipients and direct-link toggles are saved per-job sharing data, not ordinary global setting keys.

Automatic migration and the complete manual import.sql mirror apply:

ALTER TABLE `sky_job_cctvcams`
    ADD COLUMN IF NOT EXISTS `motion_alerts` TINYINT(1) NOT NULL DEFAULT 1;

CREATE TABLE IF NOT EXISTS `sky_job_warrant_subjects` (
    `id` BIGINT NOT NULL AUTO_INCREMENT,
    `warrant_row_id` INT NOT NULL,
    `citizen_identifier` VARCHAR(80) NOT NULL,
    `citizen_name` VARCHAR(120) NULL,
    `created_at` DATETIME NOT NULL DEFAULT CURRENT_TIMESTAMP,
    PRIMARY KEY (`id`),
    UNIQUE KEY `uniq_warrant_subject` (`warrant_row_id`, `citizen_identifier`),
    INDEX `idx_warrant_subject_citizen` (`citizen_identifier`, `warrant_row_id`),
    FOREIGN KEY (`warrant_row_id`) REFERENCES `sky_job_warrants` (`id`)
);

CREATE TABLE IF NOT EXISTS `sky_job_bolo_vehicles` (
    `id` BIGINT NOT NULL AUTO_INCREMENT,
    `bolo_row_id` INT NOT NULL,
    `plate` VARCHAR(16) NOT NULL,
    `created_at` DATETIME NOT NULL DEFAULT CURRENT_TIMESTAMP,
    PRIMARY KEY (`id`),
    UNIQUE KEY `uniq_bolo_vehicle` (`bolo_row_id`, `plate`),
    INDEX `idx_bolo_vehicle_plate` (`plate`, `bolo_row_id`),
    FOREIGN KEY (`bolo_row_id`) REFERENCES `sky_job_bolos` (`id`)
);

The updated manual and automatic schema definitions inherit the active database character set and collation.

Register crime_scene_tape and install its image. The resource registers its usable behavior; no custom item event is needed. All seven tape stream files are required.

• Base 1.35.0, Jobs Base 1.38.0, and Police 1.27.0 start in that order.
• Both link tables exist and CCTV has motion_alerts = 1 by default.
• Shared records remain read-only outside the owning job and source-job context is visible.
• Warrants link citizens and BOLOs link plates without duplicate rows.
• Tape consumes/returns the item, respects job/duty/removal access, and renders each configured length.
• The client reports moving player/vehicle entities only when speed, cone, line-of-sight, and client-cooldown filters pass; the server rejects distant reporters and camera-cooldown repeats. Normal/suppressed shots create alerts at their configured limits.
• Jail electrical interactions work without duplicate electrical/fence blips.
• clear.sql was not used for the update.

Stop the server after both dependencies are current. Back up the complete sky_policejob folder and export the Police database tables. Preserve intentional changes to config/config.lua and config/functions.lua separately.

Install the complete package. An old UI cannot display the review queue, and an old server module cannot safely claim or process the new database rows.

Replace fxmanifest.lua, source, the complete built UI, and config/locales. Merge public config and function values into the new files. Keep import.sql for migration comparison. Keep clear.sql available only for an explicitly requested full reset.

Apply these exact public changes when /jobconfig is not used:

The rebuilt UI also carries the linked offenceId through billing: it is visible in the billing preview, recipient receipt, and Citizens billing-history row. This display change has no additional config key.

Copy the complete new advanced block:

Config.SpeedCam.advanced = {
    enabled = false,
    recognizedSides = { "rear" },
    reviewPermission = 18,
    requireEvidence = true,
    storeUnregisteredVehicles = true,
    allowSuspectedFakePlateApproval = false,
    pageSize = 25
}

recognizedSides accepts only "front" and/or "rear"; pageSize accepts 5..100. Keep advanced mode disabled until SQL, image uploads, permission 18, and the complete new runtime are verified.

With /jobconfig, save every exact managed key after updating Jobs Base. Stored values replace their Lua defaults, and the recognized-sides setting replaces the complete list.

In sky_policejob/config/functions.lua, replace both exact CodeM calls:

-- Impound: 1.25.0
TriggerServerEvent("codem-garage:stored", plate, 0, "Impound Garage")
-- Impound: 1.26.0
TriggerServerEvent("codem-garage:stored", plate, 1, "impound")

-- Normal storage: 1.25.0
TriggerServerEvent("codem-garage:stored", plate, 0, "Impound Garage")
-- Normal storage: 1.26.0
TriggerServerEvent("codem-garage:stored", plate, 1, "Garage")

The guaranteed external registered-vehicle API is this server export:

local record = exports["sky_policejob"]:ResolveRegisteredVehicle(plate)

It trims surrounding whitespace, uppercases the plate, truncates it to 16 characters, and queries the active framework vehicle table. A match provides plate, owner_name, owner_identifier, model, and color. In the current query, image_url and image_id are nil, while tags, notes, and cases are empty tables; these fields do not contain linked Police-profile data. An invalid or unknown plate returns nil.

Billing requests now receive the new server-side configured Police-job and duty validation. The ankle-monitor change is client-side job detection only: it now checks Police-specific state instead of generic configured-job state.

Jail blips have two exclusive sources. With Config.UseJobConfigurator = true, saved interaction settings own jail_electric_box and jail_fence_cut; manual blipOverrides from file data are ignored to avoid conflicting owners. With Config.UseJobConfigurator = false, the file-config interaction blip and manual override remain effective. Creator and configuration updates now invalidate the cached blip data and refresh both interaction types immediately.

Run the complete sky_policejob/import.sql when Config.AutoExecuteQuery = false. sky_job_billing_history.offence_id changes from absent to VARCHAR(32) NULL. For an existing table, run this idempotent statement because its CREATE TABLE IF NOT EXISTS definition cannot add the column:

ALTER TABLE `sky_job_billing_history`
    ADD COLUMN IF NOT EXISTS `offence_id` VARCHAR(32) NULL AFTER `offence_category_id`;

The new sky_job_speedcam_reviews schema is:

The table uses ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci. It also creates idx_speedcam_review_queue (owner_job, status, created_at), idx_speedcam_review_plate (plate), and idx_speedcam_review_owner (registered_owner_identifier). The shipped follow-up ALTER TABLE ensures owner_lookup_completed TINYINT(1) NOT NULL DEFAULT 0 exists on an earlier copy of this table.

sky_policejob/clear.sql now also deletes sky_job_speedcam_reviews rows, but it deletes the rest of the Police dataset as well. Never execute it for this migration, a failed review, or routine cleanup; it remains an explicitly requested destructive full reset only.

• Base 1.34.0, Jobs Base 1.37.0, and Police 1.26.0 start in order.
• With advanced review disabled, existing speed-camera billing still works.
• With it enabled, valid captures enter the review queue once and require evidence when configured.
• Approve creates one bill; discard closes one row; simultaneous reviewers cannot process the same row twice.
• Unregistered vehicles, incomplete owner lookup, suspected plates, missing offences, and unavailable billing return clear results.
• Tackle requires sprinting, ticket names follow the privacy value, and billing rejects unauthorized or off-duty requests.
• The billing preview, recipient receipt, and Citizens billing history show the linked offence ID.
• exports["sky_policejob"]:ResolveRegisteredVehicle(plate) normalizes surrounding whitespace and case, returns plate/owner/model/color data for a known plate with image_url/image_id still nil and tags/notes/cases empty, and returns nil for an invalid or unknown plate.
• Ankle-monitor client availability follows Police-specific job state.
• Jail electric and fence blips refresh after creator changes.
• Impounded and normally stored CodeM vehicles appear in the correct destination.
• External tablet navigation, authorization, return, and close work without duplicate focus.

Back up the complete resource and database. Install the full manifest, runtime, UI, locales, SQL, and generated defaults from one package.

Keep the new clear.sql as an administrator-only maintenance tool. Replace fxmanifest.lua, source, built UI, locales, import.sql, and generated defaults. Police carry must remain connected to Jobs Base 1.36.0.

The only executable config/config.lua addition is:

/jobconfig manages this value as carryAllowCarrierInVehicle after the current Police and Jobs Base packages are installed; the saved value overrides the generated Lua default. No other executable public Police config.lua value changed.

Existing databases gain:

• sky_job_offence_categories.color VARCHAR(7) NOT NULL DEFAULT '#2563EB'
• sky_job_offences.court_required TINYINT(1) NOT NULL DEFAULT 0
• sky_job_offences.criminal_record TINYINT(1) NOT NULL DEFAULT 0
• sky_job_offences.bail_amount INT NULL

Run current import.sql if Config.AutoExecuteQuery is disabled. Missing columns can cause offence categories or DOJ-supplied legal fields to fail when loading or saving.

clear.sql deletes Police-owned records and selected shared Police tables inside a transaction. It is not a migration, must not be run for a normal update, and should only be used after stopping Police and confirming a verified database backup.

• Base 1.33.0, Jobs Base 1.36.0, and Police 1.25.0 are running.
• The four new offence/category columns exist.
• Jail zones, prisoner blips, terminals, fences, and electric-box blips match the saved configuration.
• Offence colors and available DOJ catalogue fields persist after restart.
• Evidence serials, shared restraints, offline licenses, social-work deletion, carry, and image fallbacks work correctly.
• clear.sql was not executed unless a full Police reset was explicitly intended.

Update sky_base to 1.32.0 and sky_jobs_base to 1.35.0 first, then stop the server. Police 1.24.0 cannot use the old Jobs Base restraint runtime.

A clean replacement is mandatory. Several old Police restraint scripts were deleted; copying 1.24.0 over 1.23.0 would leave them active through the manifest globs.

Remove the old runtime instead of overlaying it:

The new function files include CodeM Garage, Hex Garage V3, and safer JG Advanced Garages handling. Preserve those integrations while reapplying your own hooks.

If you update manually instead of replacing the complete folder, these old Police-owned files must be deleted:

Do not delete the complete PoliceRadial, PoliceTackle, or PoliceCarry sections; only the shared parts listed in the next phase moved.

Start with the new Police config and the new Jobs Base config side by side. Do not paste an old complete block into Jobs Base; transfer only intentional values using this full migration:

Config.CommandPermissions = {
    admincuff = { "god", "superadmin", "admin" },
    adminuncuff = { "god", "superadmin", "admin" }
}

chancePercent = 3.0,
delayMinSeconds = 30,
delayMaxSeconds = 120,
cooldownSeconds = 900,
minimumInputMs = 125,
latencyGraceMs = 175,
decoyCount = 5,
allowZipties = false

/jobconfig does not manage any of these shared Jobs Base settings.

There is no Police SQL migration from 1.23.0 to 1.24.0. Complete the sky_jobs_base 1.35.0 database migration before starting Police.

Restraint items and images now belong to Jobs Base:

Copy handcuffs.png, zipties.png, wire_cutter.png, legcuffs.png, and headbag.png into your inventory image folder when required. Do not register duplicate items that already exist.

Use this order:

ensure sky_base
ensure sky_jobs_base
ensure sky_policejob

Test with two players before production:

• The console reports Police 1.24.0 and no duplicate restraint events or missing dependencies.
• Cuffs, zipties, escape, leg restraints, head bags, escort, vehicle placement, and search work once—not twice.
• Tackle-to-cuff uses the rear-cuff pose.
• Person/vehicle radial submenus and optional direct keybinds work.
• CodeM, Hex Garage V3, or JG storage/impound works when selected.
• A speed camera can be damaged, repaired, synchronized, and issue an invoice with the expected source.