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 Police Job 1.43.1 to 1.44.0. Install Sky Base 1.52.0 and Sky Jobs Base 1.55.0 together with Police and complete both Base update guides.

Back up the FiveM database and the complete installed resource, including your customized configuration and translations. Keep a copy of the old files until your checks pass. Stop the server before replacing files so saved jobs and active work cannot change during the update. Keep the resource folder names unchanged.

Preserve existing citizens, cases, reports, warrants, evidence, jails, sentences and speed-camera reviews. The two new speed-camera columns must be present before Police is reopened to players; use the automatic or manual route below.

2. Install the matching files

In your installed sky_policejob folder:

1. Delete the old source/ folder completely, then copy the complete source/ folder from the new download, including its interface.
2. Copy the matching fxmanifest.lua, INSTALL.md and import.sql from that same download. Copying import.sql does not execute it; use the database decision below.
3. Replace the complete config/locales/ folder with the one from this download. If you customized translations, copy only your changed wording into the matching entries of the new files and retain every new key. If you customized dispatch alerts, put your wording into the matching DispatchAlerts entries at the root of the new locale table; those entries are no longer nested under Nui.
4. Keep your existing config/config.lua, saved jobs, jails, offences, provider selections and permissions. This Police delta adds no required configuration key.

No item image or streamed asset replacement is introduced by this Police update. There are no outside-source removals or renames.

3. Keep settings and configure the update

With Config.UseJobConfigurator = true: retain all saved /jobconfig settings. Do not import or reset them for this update. With false, keep your existing sky_policejob/config/config.lua; no new block is required.

If using shared-fleet speed-camera fines: after startup, open /jobconfig, select Police Jobs, and review your existing Billing and Speed Camera settings. Keep Billing and speed-camera billing enabled as intended and select review processing for captures that officers approve. With file-based configuration, keep Config.Billing.enabled = true, Config.SpeedCam.billingEnabled = true and Config.SpeedCam.processingMode = "review" when using this workflow. Preserve other billing and offence values.

Faction settlement uses Sky Billing. In sky_base/config/config.lua, the existing Config.billing provider must be "sky" for these faction invoices. Keep another provider if that is your server's choice, but it cannot settle these faction fines; approval reports billing unavailable instead. No provider switch is required for servers that do not use this feature. Keep the existing Billing duty policy, View Billing (VIEW_BILLING) permission for viewing invoices and Manage Money (MANAGE_MONEY) permission for payment from the faction account.

Optional — repair an invalid Speed Cams phone-app setup: after startup, open /jobconfig, select Police Jobs, then Speed Camera > Speed Camera App. Valid customized settings remain unchanged. Blank or invalid required fields fall back to the shipped values below; review and save a corrected value if the app previously failed to register or renew:

App size and Interval days must be positive integers; Route must be a nonempty route beginning with /. Keep your valid custom values rather than replacing them all. With the configurator disabled, edit only the invalid existing fields in sky_policejob/config/config.lua, save and restart. No phone provider, subscription reset or new app block is required.

4. Database, items and assets

Back up the FiveM database before applying this schema update. Choose one route:

• Automatic, when Config.AutoExecuteQuery = true: keep that existing option enabled in sky_policejob/config/config.lua. The first updated startup creates the two missing columns. Wait for successful migration before players use speed-camera reviews; do not also import the full SQL file.
• Manual, when Config.AutoExecuteQuery = false: before starting Police, open your database tool, select the FiveM database and inspect the Structure of sky_job_speedcam_reviews. Open the included sky_policejob/import.sql and locate its ALTER TABLE sky_job_speedcam_reviews additions. Add only the missing new columns: registered_owner_job as VARCHAR(80) NULL after registered_owner_name, and fleet_lookup_completed as TINYINT(1) NOT NULL DEFAULT 0 after owner_lookup_completed. The existing owner_lookup_completed column belongs to the previous version and must remain.

On a database engine without ADD COLUMN IF NOT EXISTS, the following ordinary statements can add the two columns. Run each statement only if that specific column is absent; skip the statement for any column already present:

ALTER TABLE `sky_job_speedcam_reviews`
  ADD COLUMN `registered_owner_job` VARCHAR(80) NULL
  AFTER `registered_owner_name`;

ALTER TABLE `sky_job_speedcam_reviews`
  ADD COLUMN `fleet_lookup_completed` TINYINT(1) NOT NULL DEFAULT 0
  AFTER `owner_lookup_completed`;

Confirm that both columns now appear with those types and defaults. Preserve all existing reviews and evidence; do not run clear.sql or delete the table.

No new inventory item, item image, model or permission is introduced by this Police update. Keep existing registrations and assets. Pending ownerless legacy captures receive one guarded fleet lookup after migration; already reviewed captures and known private-owner recipients retain their existing assignments.

5. Start and check the result

Start your framework, database connector and configured inventory, garage, target, phone and other providers first. Start sky_base 1.52.0, then sky_jobs_base 1.55.0, and wait for successful initialization before starting this job. Install only the providers and optional resources your server uses.

If you use the DOJ integration, start its matching updated package after Jobs Base and before Police. Otherwise do not add DOJ just for this update. Start sky_policejob 1.44.0, complete any automatic migration and reconnect to load the new interface. Resolve the first migration/startup error before reopening the server.

1. In your database tool, confirm that sky_job_speedcam_reviews contains registered_owner_job and fleet_lookup_completed. Open an existing police record and jail to confirm retained data.
2. If using shared-fleet review billing, photograph an active shared Sky job-garage vehicle and approve that capture as an authorized officer. Confirm that exactly one received faction invoice with the correct plate appears in Vehicle fines in the garage and Boss Menu. Pay it through one view and check that the other reflects the same payment. Personal vehicles keep private-owner billing; faction self-invoicing and gang-account settlement are not introduced.
3. Open citizen, case, report and warrant selectors. Check readable citizen numbers and retained links. Add a long linked report in a BOLO or warrant and confirm its Add control remains reachable.
4. Try the active jail cleaning job and confirm props stay around its configured job NPC. Test your configured social-work pickup and drop-off targets. If using the Speed Cams phone app, open it and verify its registration and saved positive subscription interval.
5. Issue and close a small test bill, checking its direction label and printer-prop cleanup.

Optional developer integration: external MDT resources can use the documented server jail integration to list jails, sentence/release online players and read remaining time. No MDT hook is installed automatically. The integrating server resource must authorize its actors; ordinary server owners need no code change. Follow the server jail reference for exact calls and units.

1. Back up and stop the server

These steps update sky_policejob from 1.43.0 to 1.43.1. Complete the earlier update instructions first if your installed version is older.

1. Download and extract sky_policejob 1.43.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.

Keep your existing configuration, inventory definitions, streamed assets and SQL files.

3. Keep settings and apply the required configuration

No Police configuration change or new /jobconfig setting is required. Keep your existing Jail settings, confiscation policy and return locations. Both saved configurator settings and file-based settings remain valid.

For Unit-based tablet access, also install Jobs Base 1.54.1. That fix belongs to the shared library and preserves existing rank permissions and Unit assignments.

4. Preserve data, items and assets

No SQL import, schema change, new item, image, streamed asset or provider migration is required. Preserve existing Jail records and stored confiscated belongings; do not run clear.sql or replace the database tables.

This fix preserves belongings that are still stored. Items already overwritten by an older version cannot be recreated by the update; recovery of those older items requires an existing backup or other verified record.

5. Start and check the result

For this coordinated update, install Sky Base 1.51.1 and Jobs Base 1.54.1 before Police. Start the database connector, framework and configured providers, then Base, Jobs Base, an installed DOJ integration if used, and sky_policejob 1.43.1. Reconnect players.

Check the existing Confiscated items return point after release: current inventory items must remain, and stored belongings must be returned with their metadata. If the inventory fills, make room and use the same return point again to collect only what remains. Check that an existing Jail sentence and its stored belongings still load.

Confirm that the configured jail boundary remains active after connecting or restarting Police, including the normal outside-zone report when tested with an authorized test character.

1. Back up and stop the server

These steps update sky_policejob from 1.42.0 to 1.43.0. Complete earlier update instructions first if you use an older version.

1. Download 1.43.0 and extract it on your computer.
2. Back up the installed sky_policejob folder, your custom configuration/translations and the game database. Keep the backups until your checks pass.
3. Stop the server before replacing files.
4. Complete the Base 1.51.0 update and Jobs Base 1.54.0 update, including their separate database and inventory steps. The new citizen phone lookup and input forms need these matching Base packages.

If DOJ is installed, update it to the matching release before reopening the shared offence catalogue. Police also works without DOJ.

2. Install the matching files

Use files from the same 1.43.0 download throughout. The following paths are inside your installed sky_policejob 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 and stream/sky_speedradar.ydr with the matching new files.
3. Replace the complete config/locales/ folder. Copy only your custom wording into the matching new entries; keep every new key and language file.
4. Replace import.sql as your installation/schema reference. Follow the database step below instead of running the complete installation file over an existing server.
5. Open the installed config/functions.lua and the new download's copy side by side. Find Config.Functions.OpenImpoundForm = function(payload). If you use the shipped function, replace that entire function with the new download's function so the standard impound reason and fee appear in one form. Keep all other functions and your own changes. If you replaced this hook with your own garage integration, keep your custom hook and check its impound workflow after the update.

Keep config/config.lua and apply only the jail outfit changes in the next step. Do not copy an old configuration or old source folder over the new package.

3. Review settings and optional features

Keep your existing jobs, jail sentences, dispatch recipients, GPS access rules, saved Creator entries and all unrelated settings.

When /jobconfig is enabled: open /jobconfig, select the Police profile, then open Settings → Jail → Male Outfit and Female Outfit. The new accessory settings use the following defaults. Review them for your uniform and save any intended changes. Existing saved overrides take priority over config.lua.

These fields were absent in the previous shipped configuration. 0 clears the corresponding mask, bag or vest component; -1 removes an ear accessory, watch or bracelet prop. The second value selects the texture.

Two existing female defaults also changed: Shoes 1 (jailOutfitFemaleShoes1, Config.Jail.outfit.female.shoes_1) changes from 12 to 3; Glasses 1 (jailOutfitFemaleGlasses1, Config.Jail.outfit.female.glasses_1) changes from 0 to -1, which removes glasses. Saved choices are retained; change those two fields yourself if you want the corrected shipped uniform.

Only when Config.UseJobConfigurator = false: open sky_policejob/config/config.lua, find Config.Jail, then outfit. Add the following fields inside each existing male and female table, just before that table's closing brace. Add a comma to the preceding entry if needed and keep all existing outfit choices:

mask_1 = 0,
mask_2 = 0,
bags_1 = 0,
bags_2 = 0,
bproof_1 = 0,
bproof_2 = 0,
ears_1 = -1,
ears_2 = 0,
watches_1 = -1,
watches_2 = 0,
bracelets_1 = -1,
bracelets_2 = 0,

In the female table, change shoes_1 = 12 to shoes_1 = 3 and glasses_1 = 0 to glasses_1 = -1 if you use the shipped uniform. Keep your values if you deliberately use a custom uniform. No existing block needs removing.

The existing dispatch-recipient setting jailDispatchJobs (Config.Jail.dispatch.jobs) now offers a job dropdown. The carry offset jailJobsCarryPickupOffset (Config.JailJobs.carry.pickupOffset) now offers X, Y and Z fields; its default remains { x = 1.0, y = 0.0, z = 0.0 }. Keep your saved recipients and offsets; no data conversion is required.

Optional after the required update: in the tablet's offence catalogue, edit an offence to add Law and section, Sort order, or a Legal penalty range. Enter both minimum and maximum of a range, or leave both empty. Keep Execution defaults set to the fixed jail/service/fine values you want to apply. Displaying a range does not change those fixed penalties or the configured length of a jail month. Existing fixed-only catalogues can stay as they are.

Citizen phone numbers appear automatically for supported configured phone providers when the citizen list is filled from framework data. In manual citizen mode, authorized record editors can enter a number while creating a citizen or use the pencil beside Phone number in the profile; an empty value clears it. Automatic records are read-only for this field. No phone provider needs changing for this update.

4. Update the database

Database changes are required. In sky_policejob/config/config.lua, find Config.AutoExecuteQuery and use the matching route:

• With true, keep automatic migration enabled. Starting the new Police package checks the existing columns and adds the missing ones. The database account needs permission to alter tables; resolve any migration error before players open records.
• With false, use the manual steps below while the server remains stopped. They work with both MariaDB and MySQL.

Manual route: open the existing game database in your SQL client after taking the backup. First run these three read-only checks:

SHOW COLUMNS FROM `sky_job_citizen_profiles`;
SHOW COLUMNS FROM `sky_job_offence_categories`;
SHOW COLUMNS FROM `sky_job_offences`;

Compare the results' Field column with the column names in the statements below. Execute each ALTER TABLE statement separately, only if its named column is missing from that table. Skip statements for columns already present; do not paste and run the entire list blindly. For example, if manual_phone is already listed for sky_job_citizen_profiles, skip its statement.

ALTER TABLE `sky_job_citizen_profiles` ADD COLUMN `manual_phone` VARCHAR(40) NOT NULL DEFAULT '';
ALTER TABLE `sky_job_offence_categories` ADD COLUMN `sort_order` INT NULL;
ALTER TABLE `sky_job_offences` ADD COLUMN `law_reference` VARCHAR(120) NULL;
ALTER TABLE `sky_job_offences` ADD COLUMN `sort_order` INT NULL;
ALTER TABLE `sky_job_offences` ADD COLUMN `legal_fine_min` INT NULL;
ALTER TABLE `sky_job_offences` ADD COLUMN `legal_fine_max` INT NULL;
ALTER TABLE `sky_job_offences` ADD COLUMN `legal_he_min` INT NULL;
ALTER TABLE `sky_job_offences` ADD COLUMN `legal_he_max` INT NULL;
ALTER TABLE `sky_job_offences` ADD COLUMN `legal_currency_symbol` VARCHAR(8) NULL;

Run the three SHOW COLUMNS checks again and confirm all nine listed table/column combinations exist with the types shown above. manual_phone must be VARCHAR(40), disallow NULL and default to empty text. Every new offence/category field permits NULL and defaults to NULL. If an SQL statement fails, stop and resolve that error before continuing; on a later attempt, check the columns again and run only the statements still needed.

Existing citizens, offences and fixed penalties stay in place. /jobconfig does not install database columns. Do not run clear.sql, replay the complete import.sql, or import a server-specific replacement catalogue as a normal update.

No new item, inventory image or model registration is required. The existing radar asset must be replaced as described in the file step; all other Police assets stay in place.

5. Start and check the result

Start the framework, database connector and selected providers, then sky_base 1.51.0 and sky_jobs_base 1.54.0, followed by your updated job resources. If you use DOJ, install its matching update before testing shared catalogues.

1. Confirm Police reports 1.43.0 and that startup contains no migration error.
2. Reconnect players, open citizen records and check phone display. In manual citizen mode, create or edit an authorized record, save a number and then clear it; confirm the saved result remains visible.
3. Open the offence catalogue and confirm existing offences and fixed penalties remain. If you use optional legal ranges, save a complete minimum/maximum pair and check its displayed reference and order.
4. Test jail uniforms on the relevant male/female characters and switch away from a jailed character, then return. Confirm the sentence remains and the switch is not counted as an escape.
5. Open the standard impound or camera setup form. Check GPS placement appears only with the configured job/duty access and required tracker item.

1. Back up and stop the server

These steps update sky_policejob from 1.41.0 to 1.42.0. Complete earlier update instructions first if you are on an older release.

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

Also complete the Base 1.50.0 update and Jobs Base 1.53.0 update; their database and inventory steps are separate.

2. Install the matching files

Use files from the same 1.42.0 download throughout. Paths below are inside your installed sky_policejob 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.

Replace meta/weapons.meta with the file from this same download.

3. Keep settings and configure optional features

No configuration change is required. Keep your jobs, radar settings, shots-fired exclusions/chances/cooldown, saved creator entries and /jobconfig overrides. This also applies with Config.UseJobConfigurator = false.

The radar gun now requires the player to be on foot. Entering a vehicle clears its active measurement, display and editor focus. Equip it again on foot to start a fresh measurement. Existing shots-fired cooldown settings still apply after the first alert is sent.

4. Database, items and assets

No new Police schema, item, image or model is required. Replace meta/weapons.meta as instructed in the file step: it contains the updated radar equipment flags. Do not replay import.sql or run the destructive clear.sql reset for this update.

5. Start and check the result

Start the framework, database connector and selected providers, then sky_base 1.50.0 and sky_jobs_base 1.53.0. If DOJ is installed, update it to 0.8.0 and start it before sky_policejob 1.42.0.

Confirm Police reports 1.42.0. Reconnect players, test an on-foot radar measurement, enter a vehicle and confirm its display closes. Check an eligible first shots-fired alert after startup and a second alert against the configured cooldown. Open the offence and prison permissions in your selected language.

1. Back up and stop the server

These steps update sky_policejob from 1.40.0 to 1.41.0. If you are on an older version, complete its earlier update instructions first.

1. Download 1.41.0 and extract the ZIP on your computer.
2. Back up your server files and game database, including the installed sky_policejob folder and your custom translations.
3. Stop the server before replacing files. Keep the backup until your checks are complete.

Also complete the Base 1.49.0 update and Jobs Base 1.52.0 update. Keep their required database and inventory steps separate from this resource's steps.

2. Copy the new files

Use the files from the same 1.41.0 download for every replacement. The following paths are inside your installed sky_policejob folder.

1. Delete the old source/ folder, then copy the complete new source/ folder into its place, including the interface files.
2. Replace fxmanifest.lua with the file from that download.
3. Replace the complete config/locales/ folder. If you changed translations, copy only your edited wording from the backup into the matching new entries; keep all new keys and files.

Keep your existing config/config.lua and other configuration files. The settings section below lists any separate file replacement required by this update.

3. Keep settings and update required hooks

No settings changes are required. Keep your existing config/config.lua, jobs, cameras, fines, billing provider, processing mode, saved creator entries and /jobconfig overrides. This applies both with /jobconfig and with Config.UseJobConfigurator = false.

Automatic immediate camera fines keep their normal payment notifications without opening a receipt. Manually issued immediate fines still show their acknowledgement receipt. No new switch needs to be enabled.

4. Database, items and models

No new Police schema migration, inventory item, image or model is required. Do not replay import.sql for this update and do not run the destructive clear.sql reset.

When DOJ is available, Police automatically repairs pending automatic speed-camera documents whose author is missing, then retries delivery. Keep the existing document queue and history. Already delivered documents and manually issued fines retain their existing authors; do not delete or recreate fines to trigger recovery.

5. Start the server and check

1. Start the framework, database connector and your configured providers first. Start sky_base 1.49.0, then sky_jobs_base 1.52.0, and wait for successful initialization before starting installed jobs.
2. Check the server console for the first startup or database error. Confirm that sky_policejob reports version 1.41.0.
3. Reconnect players so they load the new interface, then check the workflows below before reopening the server to everyone.

If DOJ is installed, update it to 0.7.0 and start it before sky_policejob 1.41.0. Police remains usable without the Job Creator product; its jail and community-service editors load their own stored data.

Check saved jail and community-service locations, an existing ankle monitor and a GPS tracker. With DOJ enabled, open a pending automatic speed-camera document after delivery. Test an automatic immediate camera fine on a test server: the payment notification should appear without a receipt taking driving controls. A manual immediate fine should still show its receipt.

1. Back up and stop the server

Update sky_policejob from 1.39.0 to 1.40.0. For an older installation, follow the intervening update guides in version order first.

1. Download 1.40.0 and extract the ZIP.
2. Copy your installed sky_policejob 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. This release adds weapon files, so use a full server restart for the update.
4. Complete the Base 1.48.0 and Jobs Base 1.51.0 updates during the same maintenance.

2. Copy the new files

Open the installed sky_policejob 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 with the new file.
4. Copy the complete new meta/ folder here and replace matching files.
5. Copy stream/sky_speedradar.ydr to the same path.
6. Copy licenses/fivem_radargun-MIT.txt to the same path.
7. Copy config/inventory/README.md and config/inventory/weapon_sky_speedradar.png to the same paths.

Keep config/config.lua and your other configuration files. If you edited translations, copy your changed wording from the backup into the matching new language entries.

3. Check your settings

For your existing Police features, keep the current settings and department shops. No default import or permission reset is needed.

Only if you want the new radar gun: open sky_policejob/config/config.lua and find Config.UseJobConfigurator.

• true (normal setup): no Lua additions are needed. After startup, open /jobconfig → Police Jobs → Radar Gun. Keep Enabled and Require duty on, check Allowed jobs, and choose Use MPH: off means KM/H and metres; on means MPH and feet. Save your settings.
• false: copy the complete Config.RadarGun = { ... } block from the downloaded config/config.lua to the end of your installed file. In the installed Config.Keybinds table, add radarGunToggleUiKey = "F7", and radarGunClearKey = "R", beside the other key entries. Keep your existing departments and keybinds. To sell the radar in a department shop, add { name = "weapon_sky_speedradar", label = "SKY SR-2 Radar Gun", price = 1200 }, beside the existing items in that department's Config.Jobs → shop table before startup.

The inventory registration in the next step is also required before anyone can use the radar gun. Skip both radar setup sections if you do not want to introduce it yet.

4. Update database and inventory

No Police database update is required.

Only if you want the new radar gun — choose your inventory, not your framework:

• ox_inventory, including servers on QBCore/Qbox: open ox_inventory/data/weapons.lua. Add the following entry inside the existing Weapons table. Then copy sky_policejob/config/inventory/weapon_sky_speedradar.png to ox_inventory/web/images/weapon_sky_speedradar.png.

['WEAPON_SKY_SPEEDRADAR'] = {
    label = 'SKY SR-2 Radar Gun',
    weight = 795,
    durability = 0.1,
    ammoname = nil,
},

• qb-inventory: open qb-core/shared/items.lua. Add the following entry beside the other weapon items inside its existing item table. Then copy the same image to qb-inventory/html/images/weapon_sky_speedradar.png.

weapon_sky_speedradar = {
    name = 'weapon_sky_speedradar',
    label = 'SKY SR-2 Radar Gun',
    weight = 795,
    type = 'weapon',
    ammotype = nil,
    image = 'weapon_sky_speedradar.png',
    unique = true,
    useable = false,
    description = 'Handheld police radar for vehicle speed measurements',
},

For another inventory, follow its custom-weapon registration instructions using weapon name WEAPON_SKY_SPEEDRADAR. Adding an ordinary item or an ESX items SQL row alone will not register this weapon. The supplied config/inventory/README.md contains the weapon details.

5. Start the server and check

1. Start the whole server. Keep this order in server.cfg: ensure sky_base, ensure sky_jobs_base, then ensure sky_policejob. If you use Sky DOJ, start sky_doj before Police.
2. Check the server console for startup errors, then reconnect to load the new files.
3. Open the Police tablet and an existing record. Check that your departments and participant names are present.
4. If you installed the radar gun: complete the Radar Gun settings from step 3. With /jobconfig enabled, to make it available in the Police shop, open /jobconfig → Police Jobs → Jobs → your department → Shop, add item weapon_sky_speedradar with a label and price, and save.
5. If you installed the radar gun: as an allowed on-duty officer, equip it and aim at a moving vehicle. Check the speed reading; F7 toggles the HUD and R clears the reading unless you have rebound those keys.

Skip the last two checks if you did not set up the radar gun. Keep the backup until the checks for your setup pass.

1. Prepare

These instructions cover sky_policejob 1.38.0 → 1.39.0. Complete applicable earlier migrations first if you are upgrading from an older version. Back up the database, resources, custom configuration/translations and saved jobs, roles, locations and /jobconfig data. Test on staging and stop the server before replacing files. Start the framework, database connector and selected inventory, phone, banking and UI providers first, then sky_base 1.47.0 and sky_jobs_base 1.50.0, followed by the installed job resources. If you use DOJ with Police, start DOJ 0.5.0 before Police 1.39.0. If you use the Crime medical integration, start Ambulance 2.46.0 before Crime 0.10.0. Mechanic 1.36.0 and Fire 1.18.0 follow both libraries. Include only resources you have installed.

2. Replace files

Use the complete 1.39.0 customer package. Delete the entire sky_policejob/source/ folder and insert the new one. Replace sky_policejob/fxmanifest.lua from the same download; do not merge old generated interface or bootstrap files. Refresh the complete sky_policejob/config/locales/ tree and merge custom translations without restoring an older dictionary. Preserve the selected locale value in sky_base/config/config.lua.

Merge sky_policejob/config/config.lua and sky_policejob/config/functions.lua using the exact changes below, preserving your other custom values and Lua hooks. Keep the supplied sky_policejob/import.sql as the matching schema reference; apply only the required existing-database migration described below. Install the matching Jobs Base 1.50.0 locale packs as part of the Jobs Base update.

3. Merge settings

Retired speed-camera placement settings. In sky_policejob/config/config.lua, remove Config.SpeedCam.moveStep (old shipped value 0.08) and Config.SpeedCam.rotateStep (old 3.0) from the existing Config.SpeedCam table. Movement and rotation now use the shared placement tools. Keep your camera models, item, speed limits, detection, billing and notification policy. The shipped Config.SpeedCam.enabled = true and Config.SpeedCam.policeNotification.requireDuty = true are unchanged; preserve intentional differences. Placement still checks job, duty and item access.

With Config.UseJobConfigurator = true, /jobconfig remains the owner of managed values. Make any desired configurator changes after the updated server has started and before the gameplay checks. The retired keys speedCamMoveStep and speedCamRotateStep are no longer offered or read; existing values for those keys are ignored. Do not reset saved camera locations or other overrides. With the configurator disabled, remove the two obsolete plaintext fields. Jobs Base 1.50.0 is required for the new placement tools.

New automatic-alert hook. In sky_policejob/config/functions.lua, add this complete block after the existing Config.Functions initialization, retaining all your other functions:

Config.Functions.beforeDispatchAlert = function(context)
    return true
end

This hook was previously absent. The shipped true return preserves normal automatic alerts. It runs on the affected player's client; context.alertType is "officerDown" or "shotsFired", context.playerPed is that local ped, and shots fired also supplies context.weaponHash. Return false to suppress the selected alert in your installed activity. Keep the hook synchronous and call only resources installed on your server. The supplied comments show FFA/paintball examples; leave them commented unless you intentionally configure that integration.

The hook is executable plaintext Lua and remains in this file when /jobconfig is enabled. It has no saved setting key and is not replaced by a configurator import. Existing alert enable/chance/cooldown settings and your other saved overrides remain. No configuration reset or routine /jobconfigimport is required.

Optional profiling is disabled by default. If support requests a recording, put setr sky_profiler 1 in server.cfg before the Sky ensure lines and perform a full server restart. In the server console, run profiler record 1000, wait for profiler status to show completion, then run profiler saveJSON sky-release-20261014.json; choose a new filename for each recording. 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

Database: Add sky_job_jail_records.hidden, type TINYINT(1) NOT NULL DEFAULT 0. With Config.AutoExecuteQuery = true, the supplied startup migration adds it to an existing table. Check the first migration error if it fails. With Config.AutoExecuteQuery = false, select your FiveM database in your database administration tool and apply this before starting Police:

SHOW COLUMNS FROM `sky_job_jail_records` LIKE 'hidden';

Only if that query returns no row, run:

ALTER TABLE `sky_job_jail_records`
    ADD COLUMN `hidden` TINYINT(1) NOT NULL DEFAULT 0;

If the column already exists, keep it and its stored values. The updated sky_policejob/import.sql contains the matching schema and a MariaDB ADD COLUMN IF NOT EXISTS mirror; the guarded statement above also works without relying on that syntax in MySQL. Preserve all prison and other Police records. Do not run clear.sql: it is a destructive reset, not an update. /jobconfig does not install SQL.

Permission: Once the updated server has started, open the role or unit permission editor in Jobs Base. Grant Hide prison records (2402) only to the intended Police roles or units and save those permission assignments. Normal prison-editing access is also required. Existing all-permissions access remains. Hiding removes an entry from the tablet list; history is retained and an active sentence continues. There is no new tablet unhide action.

Items and assets: No new inventory definition, image, map or streamed model is introduced. Keep the existing camera and repair item registrations. There are no additional non-source files to remove or rename.

5. Restart and check

Perform a full server restart after all replacements and migrations so manifests and file lists reload, then reconnect clients. Start the framework, database connector and selected inventory, phone, banking and UI providers first, then sky_base 1.47.0 and sky_jobs_base 1.50.0, followed by the installed job resources. If you use DOJ with Police, start DOJ 0.5.0 before Police 1.39.0. If you use the Crime medical integration, start Ambulance 2.46.0 before Crime 0.10.0. Mechanic 1.36.0 and Fire 1.18.0 follow both libraries. Include only resources you have installed. Check the actual installed versions and the first startup/database error before testing.

Check the hidden column and permission 2402, then open a prison record, edit its notes/duration and hide a staging entry. Verify the history remains and any active sentence continues. Check a user without the permission cannot hide records. Create a confiscation and confirm the current search survives the automatic update. Place and cancel a speed camera, check its selected height after streaming, and repair a camera with exactly one repair item. With an intentionally configured activity filter, test officer-down and shots-fired alerts inside and outside that activity. Check person radial grouping, community-service editing and nearby-player invoice selection.

1. Prepare

These instructions cover sky_policejob 1.37.1 → 1.38.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.38.0 customer package. Delete the entire sky_policejob/source/ folder and insert the new one, then replace sky_policejob/fxmanifest.lua from the same package. Refresh the complete sky_policejob/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 if you want the updated speed-camera configuration comments; no executable key or default changes there. Refresh all locales and install the full source with the matching manifest.

3. Merge settings

When Config.UseJobConfigurator = 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_policejob only if you intentionally want to import your edited plaintext configuration, after backing up and reviewing its replacement scope. With Config.UseJobConfigurator = false, merge the settings into the supplied config files instead.

No new Police configuration key or shipped default. Keep speed-camera recipients, billing provider and existing permissions. Automatic fines follow the configured faction and can be issued without an on-duty officer; manual self-billing restrictions remain. DOJ's new handovers and bodycamRequests feature settings control their shared request availability; do not use an unrelated bail setting. When using DOJ offence/court integration, install DOJ 0.4.0 and start it before Police 1.38.0. Police retains its standalone catalogue when DOJ is unavailable. Existing saved offence snapshots and completed documents are retained.

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 Police table, column or manual migration. Follow the separate DOJ 0.4.0 database instructions if DOJ is installed. Items: No new definitions. Assets: No new item images, map or streamed assets.

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.

Check report offence selection with the installed DOJ state, an existing saved report, and court execution deadlines while preserving a draft. Test a speed-camera fine with no on-duty officer using your actual billing provider. Check a denied and an accepted ankle-monitor placement. With DOJ, request a bodycam recording, fulfil it from the archive or a permitted HTTPS video, and check an unavailable response/extension and exact notification target. Confirm serial-number clipboard copying and normal File Explorer/invoice workflows.

1. Prepare

These instructions cover sky_policejob 1.37.0 → the refreshed 1.37.1 package. If you installed an earlier 1.37.1 download today, download the current 1.37.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.37.1 package. Delete the entire sky_policejob/source/ folder and insert its new version, then replace sky_policejob/fxmanifest.lua from the same package. Do not merge old generated interface files. Refresh the complete sky_policejob/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 plaintext configuration options, Job Configurator keys or defaults are added, removed or reset by this hotfix. Keep your existing configuration, jobs, grades, locations and saved overrides. /jobconfig does not replace runtime files, install schema or reload changed manifests. No configuration import or reset is required.

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 the Police tablet, check your normal duty workflow and existing creator locations. 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, open a weapon examination result with a serial number, use its copy button and paste into a text field to compare the copied value with the displayed serial. Check placement and removal through the normal ankle-monitor actions. For those normal placement/removal actions, the configured animation should start only after server approval. When your existing configuration requires the placement item, use a permitted target without a monitor, test placement with that item missing, then restore it and check an otherwise permitted placement. Normal removal does not require that placement item; check the permitted removal separately.

1. Prepare

These instructions cover sky_policejob 1.36.1 → 1.37.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.37.0 release package. Delete the entire sky_policejob/source/ folder and insert its new version; do not merge old generated interface files. Replace sky_policejob/fxmanifest.lua from the same package. Refresh the complete sky_policejob/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_policejob/config/config.lua
• sky_policejob/config/functions.lua
• sky_policejob/config/init.lua
• sky_policejob/config/locales/*
• sky_policejob/config/sv_functions.lua
• sky_policejob/fxmanifest.lua
• sky_policejob/source/* — delete and reinsert
• sky_policejob/stream/sky_crime_scene_tape.ydr
• sky_policejob/stream/sky_crime_scene_tape.ytd
• sky_policejob/stream/sky_crime_scene_tape_post.ydr
• sky_policejob/stream/sky_crime_scene_tape_section_025.ydr
• sky_policejob/stream/sky_crime_scene_tape_section_050.ydr
• sky_policejob/stream/sky_crime_scene_tape_section_100.ydr
• sky_policejob/stream/sky_crime_scene_tape_section_200.ydr
• sky_policejob/stream/sky_germ_speedcam.ydr
• sky_policejob/stream/sky_germ_speedcam1.ydr
• sky_policejob/stream/sky_germ_speedcam2.ydr
• sky_policejob/stream/sky_germ_speedcam_textures.ytd
• sky_policejob/stream/sky_props.ytyp

Remove these obsolete files outside source/:

• sky_policejob/stream/sky_crime_scene_tape.ytyp

3. Merge configuration

In sky_policejob/config/config.lua, replace the old Config.SpeedCam.advanced.enabled switch with:

Config.SpeedCam.processingMode = "later"

"instant" attempts immediate collection; "later" creates a payable invoice; "review" records a case for officer review before invoice creation. Keep the existing advanced table's evidence, recognition and offence options; remove only its retired enabled entry. If your old switch was true, choose "review"; if it was false, choose "later" to retain the previous workflow. Sky Billing supports offline registered owners; external providers still require a supported online recipient/issuer. Issuing an invoice is not proof of payment.

In /jobconfig → Policejob → Speed Camera, speedCamProcessingMode replaces speedCamAdvancedEnabled. Saved legacy values are migrated automatically (true → review, false → later) when no new mode is already saved. Review the migrated selection; preserve your other overrides.

Add the new evidence cleaning block:

Config.EvidenceField.cleaner = {
    allowEveryone = true,
    jobs = {},
    gangs = {}
}

Configure /jobconfig → Policejob → Evidence with evidenceCleanerAllowEveryone, evidenceCleanerJobs and evidenceCleanerGangs. With allowEveryone = false, a matching job OR gang grants cleaning access; both lists empty deny cleaning. Evidence collection keeps its existing police access rules.

Add the new VIN gang lists without replacing your job or grade lists:

Config.FakePlateRecognition.vinCheck.allowedGangs = {}
Config.FakePlateRecognition.vinCheck.allowedGangGrades = {
    -- { gang = "mafia", grade = 2 }
}

Configure /jobconfig → Policejob → Fake Plates → VIN using fakePlateVinAllowedGangs and fakePlateVinAllowedGangGrades. Use exact internal names. An empty gang-rank list allows all ranks of explicitly allowed gangs; populated rows set minimum ranks. Gang grants do not require job duty; job grants keep their configured duty requirement.

Merge stationBlip = true and blip.useBlipPrefix = true into the existing Config.CreatorInteractions.jailcreator.jail_public_blip profile, keeping its name, color, sprite and enabled state. Review the effective jail blip in the Jail Creator/Configurator and use the prefix option deliberately. Empty custom names are retained.

Keep the current standard Config.SpeedCam.propModel, damagedPropModel and destroyedPropModel values unless changing the camera family. Standard models remain sky_speedcam, sky_speedcam2 and sky_speedcam1; the German family uses sky_germ_speedcam, sky_germ_speedcam2 and sky_germ_speedcam1. The /jobconfig model picker is speedCamPropModel; its matching model choices update the damaged/destroyed selections. Review saved custom models instead of renaming every existing camera.

Config.Billing.mode = "framework" keeps its value. Set Sky Base Config.billing = "sky" for central invoices and configure Jobs Base billing/payment permissions and plans. External invoices remain with their selected provider. Do not treat receipt previews as issued invoices or credited society income.

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: The Police import.sql has no release change. Keep existing records and do not replay a fresh-install import. Apply the Base and Jobs Base migrations for central invoices. If using linked incarceration documents or bail settlement, install the matching DOJ 0.3.0 release and apply its documented additive migration without resetting document, role, template or case tables.

Assets: Replace the updated sky_policejob/stream/sky_props.ytyp, all Changed Files for crime scene tape, and all three new German speed camera .ydr models plus sky_germ_speedcam_textures.ytd. Delete the obsolete sky_policejob/stream/sky_crime_scene_tape.ytyp; its archetypes are supplied by sky_props.ytyp. Update fxmanifest.lua from the same package so the shared archetype is mounted once. Existing tape and speed camera item registrations remain in use; no new inventory item ID is required for selecting the German model family.

Dependencies: Install Sky Base 1.45.0 and Jobs Base 1.48.0 releases before Policejob 1.37.0. If used, update DOJ 0.3.0 in the same maintenance window. Install both Police and DOJ before starting either. Start framework/database/providers, Base, Jobs Base, Police and then DOJ; finish startup of both before testing their linked document or bail workflows. Keep DOJ finance/tablet enabled and the existing finance permission grants for bail; installing Police does not grant those permissions.

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. Verify startup, then test all configured speed camera modes with a registered plate, billing failure and an offline owner when using Sky Billing. Confirm review mode requires approval and unrelated blip edits do not reload camera data. Print a receipt using the installed printer and distinguish a preview from an issued invoice. Test custody persistence failure on staging before job/item side effects, then confirm a successful booking has one linked document and source report. Test evidence cleaning for an allowed and denied job/gang, VIN minimum ranks, jail name/prefix controls and both camera model families. If DOJ is enabled, check the authorized bail workflow and rejected insufficient funds.

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_policejob 1.36.0 → 1.36.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.36.1 download. Delete the entire sky_policejob/source/ folder and insert the new folder. Replace sky_policejob/fxmanifest.lua from that same package. Refresh the complete sky_policejob/config/locales/ tree and reapply custom translations. Keep the new source and manifest together; do not merge old generated interface files into them.

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.

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 and check the Police tablet and your normal duty workflow. If startup still fails, collect the first error and its preceding log lines together with the installed versions.

1. Prepare the update

These instructions cover sky_policejob 1.35.0 → 1.36.0. Complete earlier required migrations first if upgrading from an older version. Stop the server for the coordinated update and back up the database, resource files, customized configuration and saved job/Creator data. Install Base 1.44.0 first, then Jobs Base 1.47.0, then sky_policejob 1.36.0 and the matching updates for your other installed Sky jobs. The updated manifest requires the matching Base and Jobs Base imports; do not combine it with older dependency folders.

2. Replace the package files

Use the matching 1.36.0 package. Delete the complete old sky_policejob/source/ folder and insert the new folder. Replace sky_policejob/fxmanifest.lua from the same download. Refresh the entire sky_policejob/config/locales/ tree and merge your custom translations back. Do not merge old generated interface files into the new source/ folder.

No public configuration file, SQL file, inventory definition or stream asset changes in this release. No files outside source/ are removed or renamed.

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.

No values are added, removed or changed in sky_policejob/config/config.lua; there are no new /jobconfig setting keys or permission IDs. Preserve saved configuration and role grants. After starting the updated resources, review these existing settings during maintenance:

• Evidence markers keep Config.EvidenceField.marker and collectDistance, including your existing color, dimensions, alpha and draw/collection ranges. The matching Evidence Field settings now apply live, including enabling a feature that was off at startup.
• Keep Config.CreatorInteractions.stationcreator.evidence_storage / .evidence_laboratory, the existing jailcreator profiles and socialworkcreator.social_work_jobs, .social_work_dumpster and .social_work_box_dropoff. Names, placed headings and appearance now follow the saved profiles. The persisted social-work interaction key remains socialworkcreator::social_work_jobs; do not rename saved keys or recreate sites.
• Keep the jail's existing perimeter and each fence cut/exit position. An exit inside that perimeter now retains the prison sentence; a destination outside it records the escape. Correct an incorrectly placed perimeter or exit in the existing jail editor rather than clearing prisoners.
• Custom department job names remain supported. No rename to police or role reassignment is needed for civilian jail actions.

The optional DOJ person lookup requires the matching DOJ registry integration. Existing Police records work without installing DOJ, and this release does not grant broader record access.

Optional performance diagnostics

Extra profiler information remains disabled by default. If support requests a 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 until profiler status reports completion, then run profiler saveJSON sky-release-profile.json. Share the file only when requested. To disable the extra information, change the line to setr sky_profiler 0 and restart again. This is not a /jobconfig setting; enabling it does not record 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. If an older profiler package changed public files outside source/, restore those files once from the clean current download and reapply your own customizations.

4. Apply SQL, inventory and asset updates

No Police SQL migration, table/column type/default change, new item, inventory image or streamed asset installation is required for 1.35.0 → 1.36.0. Keep all existing records and profile shares. clear.sql is a destructive reset tool and is not part of this update. If upgrading from an older version, complete that version's separate migrations first.

5. Restart and verify

Start providers/framework, Base 1.44.0, Jobs Base 1.47.0 and Police 1.36.0, then reconnect. Confirm the installed versions and check startup errors. At a test jail, cut an inner fence and then the outer fence: the first must retain custody and the last must record the escape. Test prisoner tasks and confiscated-item return on a server using your actual custom department names, including switching from cleaning to carrying.

Check evidence marker appearance in your configured targeting mode, change a marker/range while connected, and disable/re-enable field evidence. Check evidence storage/laboratory names, headings and duty access. Verify the three social-work point profiles and their cleanup when the sentence ends. Select a vehicle in the radial menu and confirm extraction uses its occupant rather than a different nearby vehicle. Open a custom register and vehicle document, check loading/error feedback, keyboard selection and 24-hour times. If DOJ is installed with the matching caller, test an authorized person search and a denied user.

1. Prepare the update

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.

2. Replace the package files

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.

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.

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.

4. Apply SQL, inventory and asset updates

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.

5. Restart and verify

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.

1. Prepare the update

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.

2. Replace the package files

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.

3. Merge configuration

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.

4. Apply data and inventory updates

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.

5. Restart and verify

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.

1. Prepare the update

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.

2. Replace the package files

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.

3. Merge configuration

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.

4. Apply data and inventory updates

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.

5. Restart and verify

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.

1. Prepare the update

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.

2. Replace the package files

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.

3. Merge configuration

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.

4. Apply data and inventory updates

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.

5. Restart and verify

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.

1. Prepare the update.

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.

2. Replace the package files.

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.

3. Merge and review configuration.

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.

4. Apply database and item changes.

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.

5. Start and verify the 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.

1. 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.
2. 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.
3. Review the configuration steps.

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.

4. Apply the data, inventory and asset steps.

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.

5. 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.

1. 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.
2. 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.
3. Apply the following configuration changes before starting the resource.

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.

4. Complete the following database, inventory, and asset steps.

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.

5. 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.

1. Install sky_base 1.37.0 and sky_jobs_base 1.40.0, stop the server, and back up the complete Police resource, Job Configurator data, and all Police/Jobs Base record tables.
2. Delete the old folder and install the complete 1.29.0 package. Do not mix 1.28.0 manifest, config, locales, UI, schema, or source files with this release.
3. Review the new sharing defaults: cases, reports, warrants, BOLOs, and vehicle records are enabled for the doj job and police group. Existing saved /jobconfig Share settings override Lua; change them intentionally if DOJ must not receive one of these record classes.
4. With automatic migrations enabled, start Police once and let it extend map zones, vehicle registry, jail, and social-work data. Otherwise run the complete new import.sql before startup.
5. Restart Base, Jobs Base, and Police in order. Verify fingerprint evidence, citizen custody state, plate changes, DOJ sharing, social-work synchronization/escalation, ankle monitors, delayed speed-camera captures, clamps, and long offence lists.

1. Install sky_base 1.36.0 and sky_jobs_base 1.39.0, including the Jobs Base fleet-impound SQL migration. Stop the server and back up the complete Police resource, Job Configurator tables, and Police/Jobs Base vehicle data.
2. Delete the old folder and install the complete 1.28.0 package. Do not mix the old config/functions.lua, manifest, built UI, locales, or source files with this release.
3. Add the new ankle-monitor setting to the existing table. The path was absent in 1.27.1 and ships enabled:
   config/config.lua

   Config.AnkleMonitor.persistOnDisconnect = true
   

   
   In the table definition, insert persistOnDisconnect = true after the unchanged returnOnRemove = true field and before the unchanged placeDistance = 2.0 field. /jobconfig stores this setting as ankleMonitorPersistOnDisconnect, and a saved value overrides Lua. true keeps active monitors in the database across disconnects/restarts; false removes the active monitor when the target leaves.
4. Start from the new config/functions.lua. In 1.27.1, Config.Functions.OpenImpoundForm handled supported external garage providers only and did not support OP Garages or persistent Jobs Base fleet vehicles. In 1.28.0, it checks a Jobs Base fleet vehicle first, asks for a reason and fee from 0 through 1000000, submits that action for server validation, and otherwise supports OP Garages by running its impoundmenu command. Config.Functions.StoreVehicle also adds the same OP Garages command path. Keep deliberate custom provider code only after merging those complete new branches.
5. Police adds no resource-owned SQL statement in this release. The required impounded state and fleet columns belong to sky_jobs_base 1.39.0; run that complete migration before starting Police. No new Police inventory item, image, stream asset, or provider secret is required.
6. Restart Base, Jobs Base, and Police in order. Test a normal owned-vehicle impound, a persistent job-fleet impound and release, OP Garages storage/impound, ankle-monitor reconnect/restart behavior, explicit removal/cutting, registry lookup, and both jail-breakout steps.

1. Update Base to 1.35.1 and Jobs Base to 1.38.1, stop the server, and back up Police.
2. Delete the old resource and install the complete 1.27.1 package, especially its manifest, built UI, and locale defaults.
3. No public config value, /jobconfig key, SQL statement, item, image, stream asset, or provider setting changed.
4. Restart dependencies and Police, then verify the tablet and every translated Police view shows usable text.

1. Update sky_base to 1.35.0 and sky_jobs_base to 1.38.0. Stop the server and back up the complete Police resource, Job Configurator data, and every sky_job_* Police table.
2. Delete the old folder and install the complete 1.27.0 package. Keep the new manifest, source, built UI, locales, inventory image, and all tape stream files together.
3. Add the new police_sharing_defaults block before Config.Jobs, then set sharing = police_sharing_defaults on each intended Police/Sheriff job:
   config/config.lua

   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 jobs = {} exposes nothing outside the listed Jobs Base group. Configure actual target jobs in /jobconfig on the Share tab.
4. Add { name = "crime_scene_tape", label = "Crime Scene Tape", price = 150 } to each intended Config.Jobs[*].shop, then add this complete block:
   config/config.lua

   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 }
           }
       }
   }
   

5. Apply the remaining exact config changes:

   Config path	1.26.0	1.27.0
   Config.CreatorInteractions.jailcreator.jail_electric_box.interaction	false	true
   Config.CreatorInteractions.jailcreator.jail_electric_box.blip.enabled	true	false
   Config.CreatorInteractions.jailcreator.jail_fence_cut.blip.enabled	true	false
   Config.DispatchAlerts.shotsFired.chance	Missing	1.0
   Config.DispatchAlerts.shotsFired.suppressedChance	Missing	0.25

6. Add the complete Config.Cctv.motionDetection block: enabled/default-camera enabled true, radius 25.0, FOV 90.0, minimum speed 0.35, check interval 750, client cooldown 5000, alert cooldown 60, and jobs { "police" }. The client scans its current ped or vehicle for speed, radius, FOV, line of sight, and client cooldown; the server confirms reporter distance and the per-camera alert cooldown before creating the dispatch. These values and the entire Crime Scene Tape block are /jobconfig settings; saved overrides take precedence.
   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.
7. With automatic migration disabled, execute the complete new import.sql. It adds motion_alerts TINYINT(1) NOT NULL DEFAULT 1 to sky_job_cctvcams and creates sky_job_warrant_subjects plus sky_job_bolo_vehicles with their unique keys, indexes, and foreign keys. With Config.AutoExecuteQuery = true, restart performs the equivalent migration. All shipped schema definitions now inherit the active database character set and collation.
8. Register the stackable crime_scene_tape item (suggested weight 750) and copy crime_scene_tape.png into the inventory image folder. Do not run clear.sql during an update; it permanently deletes Police data. Restart dependencies and Police in order, then test sharing, linked subjects/plates, tape placement/removal, motion alerts, shots fired, jail interactions, and evidence discovery.

1. Update sky_base to 1.34.0 and sky_jobs_base to 1.37.0. Stop the server, back up the complete sky_policejob folder, and export all Police database tables.
2. Delete the old resource folder and install the complete 1.26.0 package. Replace fxmanifest.lua, source, the built UI, and every file in config/locales; start from the new config/config.lua and config/functions.lua.
3. Without /jobconfig, add the three scalars that did not exist in 1.25.0: Config.Billing.showRecipientName = false, Config.PoliceTablet.apps.speedcam_reviews = true, and Config.PoliceTackle.needsSprint = true. The neighboring tackle values remain Config.PoliceTackle.enabled = true and Config.PoliceTackle.requireOnDuty = true. Billing previews, recipient receipts, and Citizens billing history now display a linked offenceId; confirm all three surfaces after the database migration. Billing requests now validate configured Police job and duty on the server, while ankle-monitor client detection now uses Police-specific rather than generic configured-job state.
4. Config.SpeedCam.advanced also changes from absent to this complete block:

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

Keep enabled = false until the database, image upload, permission 18, and complete runtime are verified. recognizedSides accepts only "front" and/or "rear"; pageSize accepts 5..100. 5. With /jobconfig, save these exact keys: billingShowRecipientName (false), tabletSpeedcamReviews (true), tackleNeedsSprint (true), speedCamAdvancedEnabled (false), speedCamAdvancedRecognizedSides ({ "rear" }), speedCamAdvancedReviewPermission (18), speedCamAdvancedRequireEvidence (true), speedCamAdvancedStoreUnregistered (true), speedCamAdvancedAllowFakePlateApproval (false), and speedCamAdvancedPageSize (25). Saved values replace the corresponding Lua defaults; the recognized-sides list is stored as a complete list. 6. In sky_policejob/config/functions.lua, make both CodeM calls exact:

-- Impound: old -> new
TriggerServerEvent("codem-garage:stored", plate, 0, "Impound Garage")
TriggerServerEvent("codem-garage:stored", plate, 1, "impound")

-- Normal storage: old -> new
TriggerServerEvent("codem-garage:stored", plate, 0, "Impound Garage")
TriggerServerEvent("codem-garage:stored", plate, 1, "Garage")

7. When Config.AutoExecuteQuery = false, run the complete sky_policejob/import.sql. For an existing sky_job_billing_history, also ensure the new nullable column exists because CREATE TABLE IF NOT EXISTS does not alter an existing table:

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. 8. Never run sky_policejob/clear.sql for an update, a failed review, or routine cleanup. It now deletes review rows too, but remains an optional destructive reset of the complete Police dataset. 9. Server resources can resolve a framework-registered vehicle through the guaranteed external API exports["sky_policejob"]:ResolveRegisteredVehicle(plate). It trims surrounding whitespace, uppercases the plate, limits it to 16 characters, and returns plate, owner_name, owner_identifier, model, and color for a match. The current framework-table query returns image_url and image_id as nil and tags, notes, and cases as empty tables; it does not return linked Police-profile data. Invalid or unknown plates return nil. 10. When Config.UseJobConfigurator = true, saved interaction settings own the jail electric-box and fence-cut blips and manual blipOverrides are ignored. When it is false, file-config interaction blips and manual overrides remain active. Both modes now refresh those blips after creator/configuration updates without a resource restart. 11. Restart Base, Jobs Base, and Police in that order. No new Police inventory item is required. Verify the external vehicle resolver's normalization, returned plate/owner/model/color fields, expected empty profile fields, and nil result, then check visible offence IDs, billing authorization, ankle-monitor Police-job detection, the full SQL schema/charset/collation, and the advanced review flow.

1. Update sky_base to 1.33.0 and sky_jobs_base to 1.36.0.
2. Back up Police plus the database, delete the old resource folder, and install the complete 1.25.0 package.
3. Without /jobconfig, add Config.PoliceCarry.allowCarrierInVehicle = false. With /jobconfig, review and save the managed carryAllowCarrierInVehicle value; the saved value overrides the generated Lua default.
4. Run the updated import.sql when automatic migration is disabled. It adds sky_job_offence_categories.color VARCHAR(7) NOT NULL DEFAULT '#2563EB' plus court_required TINYINT(1) NOT NULL DEFAULT 0, criminal_record TINYINT(1) NOT NULL DEFAULT 0, and nullable bail_amount INT to sky_job_offences.
5. Do not run clear.sql during a normal update; it deletes Police-owned data and is only for an intentional reset after a verified database backup.
6. No item, image, or stream asset is required. Restart Base, Jobs Base, and Police in that order.

1. Update sky_base to 1.32.0 and sky_jobs_base to 1.35.0.
2. Back up sky_policejob and both the Police and Jobs Base config files.
3. Delete the old Police resource folder and install the complete new 1.24.0 folder. A clean replacement is required because the old restraint scripts were removed.
4. Reapply custom function hooks inside the new files and keep the new CodeM, Hex Garage V3, and JG Advanced Garages integrations.
5. Move shared restraint permissions, keybinds, cuffs, zipties, leg restraints, head bags, escorting, vehicle placement, and search settings from Police into the new sky_jobs_base config. Do not restore Config.CivilianUse.
6. Copy the restraint item images from sky_jobs_base/config/inventory into your inventory image folder when required.
7. Restart sky_base, sky_jobs_base, and sky_policejob in that order and test all restraint and garage actions.