Changelog

1. Back up and prepare

These steps update sky_crimesystem from 0.11.0 to 0.12.0. Complete earlier update guides first if you use an older version.

1. Download and extract 0.12.0.
2. Back up your database, installed Crime folder, customised configuration and exported Drug, Weapon and Heist Creator content.
3. Stop the server before replacing files. Complete the Base 1.49.0 update and Jobs Base 1.52.0 update in the same maintenance window.

2. Copy the package files

Inside the installed sky_crimesystem folder:

1. Delete the old source/ folder and insert the complete new source/ folder, including the built interface and its images.
2. Replace fxmanifest.lua with the one from the same 0.12.0 package.
3. Replace the complete config/locales/ folder. Copy any custom wording from your backup into matching new entries, keeping every new key and removing obsolete keys with the old files.
4. Keep your existing config/config.lua and make the exact changes in the settings step. Keep all other configuration files, heist files, stream assets and inventory images.

3. Keep or configure settings

Required file change: open sky_crimesystem/config/config.lua, find Config.ShopRobbery and remove its codeAttempts = 3, line, or the same line with your customised number. Safe codes no longer have an attempt limit. Keep reservationTimeoutSeconds and the other timeouts: they still apply to their remaining actions.

Using /jobconfig (the default): keep your saved jobs and settings. The obsolete saved shopCodeAttempts option is discarded automatically; do not reset the resource or reimport its defaults. No other setting change is required.

Optional — report every valid robbery start: after startup, open /jobconfig → Crime → Robberies → Shop robberies → Dispatch and enable Always send dispatch (shopDispatchAlways). Configure pickpocketing separately under Robberies → NPC pickpocketing → Dispatch with the same label (pickpocketDispatchAlways), then save. Both default to off, preserving the existing alert policy. Each enabled setting sends one alert at the accepted start; later results do not send a second one.

Only for file-based settings (Config.UseJobConfigurator = false): in the existing Config.ShopRobbery.dispatch table, add always = false, before radius; in the existing Config.Pickpocket.dispatch table, add the same line before radius. Use true for either feature only if you want every accepted start reported. Keep your current radius, duration, priority and jobs in both tables. Do not paste a second dispatch table over customised values.

Existing Drug, Weapon and Heist Creator entries remain saved. No default import or content recreation is required. Money Wash and the Online Heist Hub remain unavailable; this update does not enable them.

4. Database, items and assets

No Crime SQL migration, new inventory item, inventory image or stream-model installation is required for 0.11.0 → 0.12.0. Keep all existing organisations, plants, campers, laboratory stock, treasury history and heist plans. Complete the library database steps from the Jobs Base 1.52.0 guide if they apply to your installation.

Treasury transfers use the existing ledger and require the supported oxmysql transaction provider. If a transfer fails, check the displayed result and server log before trying again. An unresolved transfer deliberately blocks further treasury transfers for that facility; keep its history and ask support to check the exact transaction. Do not delete the ledger, replay the payment or issue a guessed refund.

5. Start and check

1. Start your database connector, framework and selected providers, then sky_base 1.49.0, sky_jobs_base 1.52.0 and sky_crimesystem 0.12.0. If using the Ambulance integration, start the matching Ambulance resource before Crime.
2. Resolve the first startup/database error, then reconnect for the updated interface.
3. Open a saved laboratory and camper. Check their stock and balance, complete one small production order through Produce, and check current orders and management access.
4. Test one small treasury deposit and withdrawal with the configured currency, confirming both the wallet and facility history.
5. Open a saved heist, test placement followed by Back, and review its planning/keycard guidance. Test a shop safe with an issued code, including a wrong entry before the correct one. If enabling either new dispatch option, verify one alert per accepted start with a receiving officer.
6. Receive or remove an enabled finished drug product and confirm its street-sale availability updates. Check the interrogation workflow you use before reopening the server.

1. Back up and stop the server

Update sky_crimesystem from 0.10.0 to 0.11.0. For an older installation, follow the intervening update guides in version order first.

1. Download 0.11.0 and extract the ZIP.
2. Copy your installed sky_crimesystem folder to a backup outside the server's resources folder. Export a backup of your game database too.
3. Stop the whole server in txAdmin or your hosting panel.
4. Complete the Base 1.48.0 and Jobs Base 1.51.0 updates during the same maintenance.

2. Copy the new files

Open the installed sky_crimesystem 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. Replace config/heist_exports/heist_4_v1.json with the new copy. This updates the supplied preset file only; do not import it over an existing saved heist.

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

3. Check your settings

Open your installed sky_crimesystem/config/functions.lua and choose the matching case:

• You never edited this file: replace it with the new config/functions.lua from the download.
• You edited it and use Jobs Base dispatch: open the old and downloaded files side by side. Find function Config.Functions.SendPickpocketPoliceDispatch(payload) in both. In the installed file, replace that entire function, through its closing end, with the new version. Keep your other functions.
• You deliberately use another dispatch system for pickpocket alerts: keep your custom dispatch function so the same alert is not sent twice.

This file change fixes pickpocket alerts and is needed even when you use /jobconfig. Your existing config/config.lua, saved factions and heists can stay as they are.

4. Update database and inventory

Crime 0.11.0 needs no manual SQL, new inventory items or extra models. The Base and Jobs Base updates have their own database steps.

Do not run clear.sql, import default factions, or reimport your heists for this update. Existing stock, balances and heist progress are retained. Optional new preparation recipes can be configured later.

5. Start the server and check

1. Start the server. In server.cfg, keep ensure sky_base before ensure sky_jobs_base, and both before ensure sky_crimesystem. If you use Sky Ambulance with Crime, start sky_ambulancejob before Crime.
2. Check the server console for startup errors, then reconnect. Open an existing faction, its stock and a saved heist to check that your data is still present.
3. Only if members should buy campers with faction money: join as the faction boss, open the tablet → Management → Roles, select the member's role, switch on Purchase campers under Permissions, and save. Repeat only for the roles that should be allowed. Boss/co-boss roles with full access already have it. Check one allowed role and one role that should be refused. This setting is in the tablet's Boss Menu.
4. If you use pickpocketing: test a failed attempt and check that your selected dispatch system receives the alert.

Keep the backup until the checks for your setup pass.

1. Prepare

These instructions cover sky_crimesystem 0.9.0 → 0.10.0. Complete earlier migrations first when upgrading from an older version. Back up the database, resource configuration, translations, inventory definitions and saved /jobconfig/Creator data. Test on staging and stop the server before replacing files. Start the framework, database connector and selected inventory, phone, banking, vehicle-key, weather and UI providers first, then sky_base 1.47.0 and sky_jobs_base 1.50.0. Start DOJ 0.5.0 before Police 1.39.0 for their shared court and catalogue workflows, and Ambulance 2.46.0 before Crime 0.10.0 when using the medical integration. Mechanic 1.36.0, Fire 1.18.0, Treasure Hunt 1.1.0 and Pets 1.1.0 follow the libraries. Include only installed resources.

2. Replace files

Use the complete 0.10.0 customer package. Delete the entire sky_crimesystem/source/ folder and insert the new one, then replace sky_crimesystem/fxmanifest.lua from the same package. Refresh the entire sky_crimesystem/config/locales/ folder and merge custom translations. Merge the listed config files using the exact changes in this guide, refresh the listed built-in heist JSON files and inventory examples, and retain import.sql for manual migrations. Preserve custom locations and saved Creator data. Keep sky_crimesystem/config/moneywash.lua with Config.Moneywash.enabled = false; its delta is a comment change and no activation is required.

3. Merge settings

In sky_crimesystem/config/config.lua, Config.UseJobConfigurator = true uses saved /jobconfig settings for sky_crimesystem over managed file defaults. Preserve those overrides, including deliberate deactivation. With Config.UseJobConfigurator = false, merge the plaintext values instead. Drug Creator and Heist Creator keep their own saved definitions; copying files does not replace them. Configure settings, install SQL/items/assets and import Creator content as separate actions.

sky_crimesystem/config/config.lua

1. Config.CommandPermissions.crimeminigame did not exist; add { "god", "superadmin", "admin" }. This is an administrative no-reward preview command, not a new global player entitlement.
2. Config.HeistDefinitionFiles gains Pacific Standard. Preserve any existing custom entries; shipped list:

Config.HeistDefinitionFiles = {
    "config/heists/fleeca_legion_square_v1.json",
    "config/heists/pacific_standard_v1.json",
}

3. New Config.HeistPlanning.blockadeExplosionDamageScale = 0.75 and blockadeExplosionCameraShake = 0.15. Both options were previously absent; merge them into the existing HeistPlanning table. These are plaintext, not new Job Configurator keys.
4. New Config.HeistPlanning.glassCaseTestCommand = "glasscasetest" and full new table:

Config.HeistPlanning.glassCaseTest = {
    cutDuration = 12000,
    completedDisplayDuration = 15000,
    lootHeight = 1.0,
}

5. Add the previously absent Config.HeistPlanning.jewelCase.animation.impactPhase = 0.15 to the existing animation block. It sets the first glass impact within the animation from 0 to 1. Jewellery cases are now available in the Creator.

Crime continues to use sky_base/config/config.lua → Config.locale. Refresh the supplied Crime locale folder and preserve your selected language.

sky_crimesystem/config/drugs_growing.lua

Add these two new tables to Config.Drugs.Growing, preserving its existing settings. Environment survey settings are plaintext and are not managed by /jobconfig.

Config.Drugs.Growing.environmentSurvey = {
    enabled = true,
    scannerAce = "sky_crimesystem.environment.scan",
    mapRevision = "1",
    intervalSeconds = 15,
    refreshSeconds = 300,
    scanRadius = 15,
    batchSize = 4,
    timeoutSeconds = 10,
    rayLength = 80,
    originHeight = 0.3,
    indoorAirflow = 20,
    indoorTemperature = 21,
    gameHourProvider = function() return nil end,
}

Config.Drugs.Growing.wildPlantHighlight = {
    enabled = false,
    distance = 25.0,
}

Add dedicated ACE only for a trusted maintenance administrator, e.g. add_ace group.admin sky_crimesystem.environment.scan allow in server.cfg. The administrator's connected client in routing bucket 0 automatically scans registered world plant placements within 15 m, up to 4 every 15 s. Existing unknown/unscanned world plants pause growth and environmental water/stress changes. Survey the existing placements before treating the new default as ready, or deliberately set environmentSurvey.enabled = false to preserve the prior outdoor simulation. Samples persist in existing plant metadata, survive restart and remain usable without connected players. Increasing mapRevision after map/MLO/IPL/collision changes or moving plants invalidates prior samples. gameHourProvider returns authoritative game hour in [0,24) if integrated; default nil preserves host-clock seasonal simulation. It does not automatically integrate an arbitrary weather clock.

Managed new keys under Growing are drugWildPlantHighlightEnabled (false) and drugWildPlantHighlightDistance (25.0; supported 1–200 m); saved values override file defaults. Outline radius does not extend harvest reach.

Add RAIN_HALLOWEEN to Config.Drugs.Growing.outdoor.liveWeather.rainTypes: { "RAIN", "THUNDER", "CLEARING", "RAIN_HALLOWEEN" }; add SNOW_HALLOWEEN to Config.Drugs.Growing.outdoor.liveWeather.snowTypes: { "SNOW", "BLIZZARD", "SNOWLIGHT", "XMAS", "SNOW_HALLOWEEN" }. Preserve custom existing members.

sky_crimesystem/config/drugs_market_threat_processing.lua

Add these entries to existing Config.Drugs.Processing.minigames, preserving the existing entries:

batch_cooling = { baseQuality = 68, variance = 22, failBelow = 36 },
bottle_blending = { baseQuality = 66, variance = 24, failBelow = 36 },
seal_pouch = { baseQuality = 70, variance = 20, failBelow = 35 },
seal_jar = { baseQuality = 70, variance = 20, failBelow = 35 },
seal_vacuum = { baseQuality = 70, variance = 20, failBelow = 35 },
seal_brick = { baseQuality = 70, variance = 20, failBelow = 35 },
seal_bottle = { baseQuality = 70, variance = 20, failBelow = 35 },
seal_foil = { baseQuality = 70, variance = 20, failBelow = 35 },
seal_cup = { baseQuality = 70, variance = 20, failBelow = 35 },
seal_sleeve = { baseQuality = 70, variance = 20, failBelow = 35 },

In Config.Drugs.Processing.routes.meth_basic.steps, change the key = "cool" step's minigame from "timing" to "batch_cooling". In Config.Drugs.Processing.routes.lean_bottle.steps, change the key = "blend" step's minigame from "timing" to "bottle_blending". Other shipped step values remain the same. Saved Drug Creator recipe entries retain their existing choices: choose the new minigame in that recipe or explicitly import only the intended replacement default. File changes/restart do not rewrite saved recipes. This is Creator content, not a new global /jobconfig setting.

sky_crimesystem/config/weapons.lua

Config.Weapons.enabled: false → true in the supplied file defaults. Creator.enabled and Runtime.enabled stay true. Saved weaponSystemEnabled, weaponRuntimeEnabled and entry/default overrides remain authoritative after startup. Do not overwrite deliberate deactivation when making the section visible. Review the existing Weapon Routes General, Access, Collection, Production, Market, Contract and Street Sale settings.

Add the previously absent complete plaintext runtime blocks/values:

Config.Weapons.Runtime.collectorVisualModel = "prop_rub_scrap_06"
Config.Weapons.Runtime.collectorVisualVariants = {
    { model = "prop_rub_scrap_06" },
    { model = "prop_rub_carpart_02", pitch = 90 },
    { model = "prop_rub_carpart_04" },
    { model = "w_pi_pistol_mag1", pitch = 90 },
    { model = "w_ar_assaultrifle_mag1", pitch = 90 },
    { model = "w_at_scope_small" },
    { model = "w_at_pi_supp" },
    { model = "prop_ld_ammo_pack_01" },
}
Config.Weapons.Runtime.collectorHighlight = {
    color = { 80, 210, 255, 210 },
    activeColor = { 255, 205, 70, 255 },
    markerSize = 0.10,
    activeMarkerSize = 0.15,
}
Config.Weapons.Runtime.collectorGroundOffsets = { prop_rub_pile_01 = -0.45 }
Config.Weapons.Runtime.collectorPickupDistance = 0.55
Config.Weapons.Runtime.collectorWalkTimeout = 6000
Config.Weapons.Runtime.collectorPickupAnimation = {
    dict = "anim@mp_snowball", clip = "pickup_snowball", duration = 2400,
}

Collection default definition key = "minigame", settingKey = "weaponDefaultCollectionMinigame": default "timing" → "scrap_search"; allowed options add "scrap_search" to timing/precision/pressure. Existing weaponDefaultCollectionUseMinigame = false remains so direct collection is the default. Saved overrides and per-entry choices remain. The visual runtime blocks above are not new configurator keys.

The shipped Config.Weapons.Defaults now contains 26 definitions. Refresh the full default catalog from the new file when desired; it is importable content, never a startup overwrite of existing routes. Four production processor defaults use prop_table_03; three staged weapon defaults end at assembly, without the old final calibration stage. Import affected existing defaults with replacement enabled only after reviewing custom settings; alternatively change their prop/steps in the Creator. Foundation dependencies must be imported with the dependent routes or already exist.

The following new per-entry values are managed by Weapon Creator and saved in its existing data: collector propModel, propCount (default 1, max 12), propRadius (default 0), partsPerHeap (default old minigameRounds or 5, range 1–10); processor propModel (except trade), tradeRewardMode (all/parts/weapons/mixed, default all), tradeAggressionEnabled (true), tradeBlockSeconds (300), tradeNegotiationEnabled (true), tradeNegotiationChance (50), tradeDiscountPercent (20), tradeNegotiationCooldownSeconds (300). Existing entries receive compatible absent-field defaults; original data is retained.

Other saved content changes

• Shop shopRegisters is no longer a separate settings table; migration attaches the first matching legacy register to shopLocations as registerId, registerX, registerY, registerZ, retains existing embedded values, assigns missing shop IDs and removes shopRegisters from the transformed payload. Only one register per shop is supported. Plaintext Config.ShopRobbery.locations[].registers likewise takes its first register and requires one. Review affected saved shops and use separate shop entries for additional independent registers. Clerk/register/safe placement uses the existing world placement controls. No changed public ShopRobbery default file/table needs replacing beyond source/configurator data.
• New laboratory/camper Creator fields: purchaseEquipment = false, purchaseUpgradeLevel = 0 (0–5), ownedBlipEnabled = false. Existing tier remains independent. Set per definition; no global Job Configurator setting or SQL schema change. Existing owned assets do not receive grants. Campers use the fixed Drug Wars interior and no longer need a selected interior template. Preserve old saved templates/data; do not delete them as an update step.
• Heist Creator authoring: gas duration = 0 means persistent until plan closes; crew-mask scaling is explicit per preparation, laser hack settings are per group, crew/police values are integers. Existing custom definitions remain; choose the new controls to adopt the behavior.
• Storage weapons visibility is a registration capability fixed in both file-based and configurator-based Crime group paths. No grant reset/permission-ID migration is needed.

New weapon contracts remain active until delivery or explicit cancellation at the buyer. Only one contract may be active. Expiry prevents delivery but does not discard the contract. The server calculates a dirty-money cancellation fee of 15% of the agreed value including contract bonus, minimum 1; existing contracts without a recorded fee retain zero. There is no new cancellation-percentage setting.

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-20261014.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; recording and upload do not start automatically.

4. Database, items and assets

Database

Config.AutoExecuteQuery = true performs the normal Crime schema migration on start and now adds the three lab indexes. Config.HeistPersistence.enabled = true plus .autoMigrate = true controls the separate heist migration and now creates sky_crime_heist_loot_templates. Manual installations need both changes; /jobconfig does not install either.

For manual migrations, open your database management tool, select the active FiveM database, and use its SQL query editor. Create the following new table:

CREATE TABLE IF NOT EXISTS `sky_crime_heist_loot_templates` (
    `id` VARCHAR(64) NOT NULL,
    `label` VARCHAR(80) NOT NULL,
    `loot_type` VARCHAR(8) NOT NULL,
    `full_value` BIGINT UNSIGNED NOT NULL,
    PRIMARY KEY (`id`)
) ENGINE=InnoDB;

Inspect the indexes on sky_crime_drug_equipment:

SHOW INDEX FROM `sky_crime_drug_equipment`;

If no returned row has Key_name = idx_drug_equipment_lab, add that missing index:

ALTER TABLE `sky_crime_drug_equipment` ADD INDEX `idx_drug_equipment_lab` (`lab_id`);

Inspect the indexes on sky_crime_drug_workers:

SHOW INDEX FROM `sky_crime_drug_workers`;

If no returned row has Key_name = idx_drug_workers_lab, add that missing index:

ALTER TABLE `sky_crime_drug_workers` ADD INDEX `idx_drug_workers_lab` (`lab_id`);

Inspect the indexes on sky_crime_drug_plants:

SHOW INDEX FROM `sky_crime_drug_plants`;

If no returned row has Key_name = idx_drug_plants_lab, add that missing index:

ALTER TABLE `sky_crime_drug_plants` ADD INDEX `idx_drug_plants_lab` (`lab_id`);

The shipped import uses MariaDB ADD INDEX IF NOT EXISTS; MySQL installations should inspect information_schema.statistics/SHOW INDEX and run only absent plain ALTERs. Retain all existing rows. There is no new element-image table in the final delta and no new weapon/camper/ownership/environment schema. Retain the existing 0.9.0 batch-retired/index migrations; older installations must complete earlier update instructions.

Items and images

• Optional QBCore stackable dirty money: the newly supplied black_money item in sky_crimesystem/config/inventory/items_qb.lua; only install if sky_base/config/qb_money.lua uses Config.QBBlackMoney.mode = "item" and item "black_money". One item is one dollar, weight 0, unique false, useable false. Account/marked-bills setups retain their selected mode and should not adopt the optional item needlessly.
• Image sky_crimesystem/config/inventoryimages/png/black_money.png already exists; use that image if installing the optional QB item. It is not a new image in the tag delta.
• Weapon/material catalog registration runs on save/import/startup and preserves existing inventory definitions. If the inventory does not support runtime registration (e.g. ox_inventory), define missing items manually from actual selected catalogs/server warning; do not claim all inventories auto-register them. Existing ESX loadout vs item mode and ammo/metadata/provider behavior need the current Base. No forced item conversion or existing-item rewrite.
• Updated route defaults still require their selected tools, materials and item-based weapon outputs to be available. New/default recipe imports and item installation are separate actions.

If installing the optional QBCore item, copy only this missing entry into the existing QBShared.Items table, then copy sky_crimesystem/config/inventoryimages/png/black_money.png into your inventory image directory:

["black_money"] = {
        name = "black_money",
        label = "Black Money",
        weight = 0,
        type = "item",
        image = "black_money.png",
        unique = false,
        useable = false,
        shouldClose = false,
        description = "Black Money",
},

Assets

The new workbench, gallery, countdown and handbook assets plus optimized weapon models ship through the complete sky_crimesystem/source/ replacement. It removes obsolete source textures. No new Crime stream model, map or inventory-image file outside source is required. Use source and manifest from the same package.

5. Restart and check

Perform a full server restart and reconnect clients. Start the framework, database connector and selected inventory, phone, banking, vehicle-key, weather and UI providers first, then sky_base 1.47.0 and sky_jobs_base 1.50.0. Start DOJ 0.5.0 before Police 1.39.0 for their shared court and catalogue workflows, and Ambulance 2.46.0 before Crime 0.10.0 when using the medical integration. Mechanic 1.36.0, Fire 1.18.0, Treasure Hunt 1.1.0 and Pets 1.1.0 follow the libraries. Include only installed resources.

Confirm Crime 0.10.0, library readiness, the global loot-template table and all three named laboratory indexes. Check the first startup/database error. Verify saved shops and Creator definitions, visible storage weapons and disabled tablet-app restrictions. On staging, check surveyed world plants and unknown-plant pause, optional outlines and ownership icons for eligible/ineligible players, purchase presets without modifying existing assets, private lockpicking, camper plates/keys/resale and manual drug production/sales. Resume an Easy heist draft, undo/redo an edit and test crew/police conditions, jewellery cases and the Pacific Standard prerequisites. If adopting Weapon Routes, test configured items, scrap refill, one production route, NPC exchange and contract delivery/cancellation with your selected providers.

1. Prepare

These instructions cover sky_crimesystem 0.8.1 → 0.9.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 0.9.0 customer package. Delete the entire sky_crimesystem/source/ folder and insert the new one, then replace sky_crimesystem/fxmanifest.lua from the same package. Refresh the complete sky_crimesystem/config/locales/ tree and merge custom translations. Preserve your selected language. Do not restore an older bootstrap or merge generated interface files.

Merge config/drugs_labs_power_workers.lua and review the updated supplier comments in config/drugs_laboratories.lua. Keep your custom locations and drug settings. Retain the supplied main import.sql for manual updates. Use the complete release package and its matching manifest rather than selected generated interface files.

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

New Config.Drugs.Labs.maxLaboratoriesPerCharacter = 0 and maxLaboratoriesPerFaction = 0 in config/drugs_labs_power_workers.lua retain unlimited ownership. In /jobconfig → Crime → Drug System, use Laboratories per Character (drugMaxLaboratoriesPerCharacter) and Laboratories per Faction (drugMaxLaboratoriesPerFaction), each 0–100. Owned and rented fixed laboratories count; campers and shared access do not. Existing owners keep their data; limits apply when acquiring another laboratory.

Removing installed equipment returns its configured item to laboratory storage and preserves condition, fuel and oil. Active production/busy equipment cannot be removed; starting storage stays, and removing a shelf requires enough remaining storage capacity. No new item definition is required if using the supplied existing equipment catalogue. Custom equipment needs its configured return item.

Supplier entries in Config.Drugs.Laboratories are import templates. After import, move the saved supplier with Set position in Drug Creator; editing the template does not relocate the saved entry. Do not reimport/reset saved locations to move one supplier. Camper manual locking is available only when no enabled key provider owns that workflow; a configured working provider keeps control. Plant grounding retains saved coordinates and supports the bundled growth models. Keep existing heist/drug activation and permissions.

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: New generated sky_crime_drug_batches.retired is a virtual TINYINT derived from boolean metadata.consumed or metadata.sold; it is not a manually written status or a deletion. Ten indexes cover active batches, sales history, processing/distribution orders, routes, threats, work orders and laboratory ledger reads:

• sky_crime_drug_batches: idx_drug_batch_retired_lab(retired, lab_id).
• sky_crime_drug_sales: idx_drug_sale_time(sold_at), idx_drug_sale_market_time(drug_type, sale_channel, sold_at), idx_drug_sale_seller_time(seller, sold_at).
• sky_crime_drug_processing: idx_drug_processing_status_lab(status, lab_id).
• sky_crime_drug_distribution: idx_drug_distribution_status_dealer(status, dealer_id).
• sky_crime_drug_route_runs: idx_drug_route_status_expiry(status, expires_at).
• sky_crime_drug_threats: idx_drug_threat_type_time(threat_type, created_at).
• sky_crime_drug_work_orders: idx_drug_work_order_lab_status(lab_id, status).
• sky_crime_drug_lab_ledger: idx_drug_lab_ledger_time(lab_id, created_at).

With Config.AutoExecuteQuery = true, let the automatic migration finish. In manual mode, execute the matching Existing MariaDB installations; automatic resource migrations apply the same schema. ALTER statements from the current main import.sql before starting Crime. They add the generated column and these indexes to existing tables; confirm them in the database. Use your database's supported syntax. Retain retired batches, sales history, plants, laboratories, production and all creator data. No new heist import is needed for this release. Items: No new published item definitions; existing equipment return/harvest items still need their configured inventory definitions. Assets: No new published stream model, map or inventory-image requirement.

The supplied ADD COLUMN/INDEX IF NOT EXISTS manual syntax is for MariaDB. On MySQL 8, first inspect SHOW COLUMNS and SHOW INDEX for each named table, then add only missing columns/indexes using MySQL-supported ADD COLUMN/ADD INDEX without IF NOT EXISTS. Keep the supplied definitions and generated expression unchanged. Do not execute an unsupported clause or delete an existing column/index to rerun it.

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.

Confirm migration success, the generated retired column and all ten indexes. Check a saved lab's active production and storage, acquire a disposable lab under character/faction limits, and verify shared access/campers do not count. Remove inactive equipment and confirm the returned item's condition/fuel/oil; test busy and insufficient-capacity rejection. Check a saved supplier position after restart, camper lock ownership and plant ground contact through growth. Confirm configured harvest output and an existing robbery/Heist Creator preview. Preserve historical sales and batches.

1. Prepare

These instructions cover sky_crimesystem 0.8.0 → the refreshed 0.8.1 package. If you installed an earlier 0.8.1 download today, download the current 0.8.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

Replace sky_crimesystem/fxmanifest.lua, the listed config files and the complete sky_crimesystem/config/locales/ folder from the matching download. Delete the installed sky_crimesystem/source/ folder and reinsert the complete new sky_crimesystem/source/ folder; merge your own configuration separately using the exact changes below. Preserve existing database rows and saved creator entries. The file list is based on the committed shipped resource tree; frontend source, tests, internal docs and output reports are not customer replacement paths.

3. Merge settings

In sky_crimesystem/config/drugs_labs_power_workers.lua, add Config.Drugs.Labs.maxLaboratoriesPerCharacter and Config.Drugs.Labs.maxLaboratoriesPerFaction. Both fields were absent before this update; both new shipped values are 0, meaning unlimited. Valid values are whole numbers from 0 to 100. Preserve your existing laboratory settings and merge these two fields into the existing table; the complete new shipped table below is a reference, not a request to reset your custom values.

Config.Drugs.Labs = {
    enabled = true,
    maxLaboratoriesPerCharacter = 0, -- Fixed laboratories, owned or rented; 0 = unlimited.
    maxLaboratoriesPerFaction = 0, -- Campers and shared access do not count.
    camperHotVehicleMinutes = 240,
    defaultRentDays = 7,
    rentWarningHours = 24,
    rentExpiredHeatGain = 8,
    camperMoveCooldownMinutes = 30,
    camperMoveHeatGain = 4,
    upgradeCostMultiplier = 1.0,
    ownershipRequired = true,
    storageUnitsPerAmount = 1.0,
    storageOverloadHeatGain = 1.4,
    storageOverloadDecayMultiplier = 1.45,
    cleanlinessDecayPerLifecycle = 1.2,
    odorGainPerLifecycle = 0.9,
    noiseDecayPerLifecycle = 0.8,
    maintenanceDecayPerLifecycle = 0.7,
    dirtyContaminationMultiplier = 1.35,
    dirtyQualityPenalty = 4,
    maintainPaymentAccount = "money",
    rentPaymentAccount = "bank",
    rentDepositMultiplier = 2,
    maximumRentDays = 28,
    seizureHeatThreshold = 96,
    seizureChancePerLifecycle = 4,
    seizureDurationMinutes = 90,
    unusableMaintenanceThreshold = 8,
    recoveryBaseCost = 12000,
    maintainActions = {
        clean = { cost = 180, cleanliness = 30, odor = -8, maintenance = 2, heat = -1 },
        ventilate = { cost = 120, odor = -28, noise = 4, heat = -0.5 },
        repair = { cost = 350, maintenance = 26, cleanliness = 4, heat = -1 },
        sanitize = { cost = 260, cleanliness = 20, odor = -16, maintenance = 4, heat = -1.5 },
    },
    accessRoles = { "owner", "manager", "producer", "storage", "security", "guest" },
    accessCapabilities = { "enter", "storage", "equipment", "workers", "keys", "upgrades" },
    roleCapabilities = {
        owner = { enter = true, storage = true, equipment = true, workers = true, keys = true, upgrades = true },
        manager = { enter = true, storage = true, equipment = true, workers = true, keys = true, upgrades = true },
        producer = { enter = true, storage = true, equipment = true, workers = false, keys = false, upgrades = false },
        storage = { enter = true, storage = true, equipment = false, workers = false, keys = false, upgrades = false },
        security = { enter = true, storage = false, equipment = false, workers = false, keys = false, upgrades = false },
        guest = { enter = true, storage = false, equipment = false, workers = false, keys = false, upgrades = false },
    },
    actionCapabilities = {
        enter = "enter",
        batchStorage = "storage",
        market = "storage",
        route = "storage",
        consume = "storage",
        processing = "equipment",
        placeEquipment = "equipment",
        serviceEquipment = "equipment",
        plantSeed = "equipment",
        maintainPlant = "equipment",
        harvestPlant = "equipment",
        hireWorker = "workers",
        manageKeys = "keys",
        manageUpgrades = "upgrades",
    },
    labTypes = {
        camper = { label = "Camper", slots = 3, storage = 120, power = 500, heatMultiplier = 1.35, mobile = true },
        basement = { label = "Basement", slots = 8, storage = 450, power = 1500, heatMultiplier = 1.0 },
        garage = { label = "Garage", slots = 10, storage = 650, power = 2200, heatMultiplier = 1.08 },
        apartment = { label = "Apartment", slots = 7, storage = 360, power = 1250, heatMultiplier = 0.92 },
        warehouse = { label = "Warehouse", slots = 18, storage = 1400, power = 5500, heatMultiplier = 1.25 },
        industrial = { label = "Industrial Hall", slots = 21, storage = 1750, power = 7200, heatMultiplier = 1.34 },
        bunker = { label = "Bunker", slots = 24, storage = 2200, power = 9000, heatMultiplier = 0.78 },
    },
    tiers = {
        { tier = 1, label = "Starter", cost = 0, slotBonus = 0, storageMultiplier = 1.0, security = 10, qualityBonus = 0, powerBonus = 0 },
        { tier = 2, label = "Improved", cost = 25000, slotBonus = 2, storageMultiplier = 1.25, security = 25, qualityBonus = 2, powerBonus = 250 },
        { tier = 3, label = "Professional", cost = 65000, slotBonus = 4, storageMultiplier = 1.55, security = 45, qualityBonus = 4, powerBonus = 700 },
        { tier = 4, label = "Industrial", cost = 145000, slotBonus = 7, storageMultiplier = 1.9, security = 65, qualityBonus = 7, powerBonus = 1500 },
        { tier = 5, label = "Elite", cost = 325000, slotBonus = 10, storageMultiplier = 2.35, security = 85, qualityBonus = 10, powerBonus = 3500 },
    },
    facilityUpgrades = {
        concealment = { label = "Concealment", maxTier = 4, costs = { 9000, 24000, 52000, 110000 }, heatReduction = 4, raidDefense = 3 },
        hidden_storage = { label = "Hidden Storage", maxTier = 4, costs = { 12000, 32000, 68000, 145000 }, protectedShare = 0.12, storageBonus = 15 },
        door = { label = "Door & Lock", maxTier = 5, costs = { 7000, 18000, 42000, 95000, 190000 }, raidDefense = 7 },
        keycards = { label = "Keycard System", maxTier = 3, costs = { 18000, 48000, 105000 }, raidDefense = 5 },
        cctv = { label = "CCTV", maxTier = 4, costs = { 9500, 26000, 58000, 125000 }, raidDefense = 5 },
        alarm = { label = "Alarm System", maxTier = 4, costs = { 7500, 22000, 50000, 115000 }, raidDefense = 5 },
        clean_room = { label = "Clean Room", maxTier = 4, costs = { 16000, 44000, 92000, 185000 }, qualityBonus = 2, contaminationReduction = 4 },
        worker_quarters = { label = "Worker Quarters", maxTier = 4, costs = { 11000, 30000, 65000, 135000 }, fatigueRecovery = 3 },
        worker_supplies = { label = "Food & Water", maxTier = 4, costs = { 6500, 18000, 40000, 85000 }, moraleBonus = 2, hungerReduction = 4 },
        medical_station = { label = "Medical Station", maxTier = 3, costs = { 14000, 38000, 82000 }, stressReduction = 3 },
        break_room = { label = "Break Room", maxTier = 3, costs = { 8500, 24000, 54000 }, moraleBonus = 3, stressReduction = 2 },
    },
}

With the Job Configurator enabled, open /jobconfig → Crime System → Drug System → General and check Laboratories per Character (drugMaxLaboratoriesPerCharacter) and Laboratories per Faction (drugMaxLaboratoriesPerFaction). These are central server settings, independent of the selected faction. The character limit applies separately to each character; the faction limit applies separately to each faction. Purchased and rented fixed laboratories count together. Campers and access to another owner's laboratory do not count. A stored laboratory still counts when its rental has expired. Lowering a limit blocks further acquisitions; it does not remove existing laboratories. Saved configurator overrides remain authoritative. Set or clear the two overrides there as needed and verify the effective values after a restart; editing the Lua file alone does not replace a saved override.

sky_crimesystem/config/drugs_laboratories.lua changes only two comments in the supplier block; its coordinates, heading, dealer model, stock and prices are unchanged. The complete new supplier block is:

    supplier = {
        enabled = true,
        account = "money",
        interactionDistance = 2.2,
        -- Import templates: saved Drug Creator suppliers keep their persisted positions.
        -- Move an imported supplier with Set position in the creator.
        locations = {
            {
                id = "dock_supplier",
                label = "Laboratory Supply Dealer",
                coords = { x = 1218.0, y = -3114.83, z = 5.54 },
                heading = 90.0,
                pedModel = "s_m_y_dockwork_01",
                scenario = "WORLD_HUMAN_CLIPBOARD",
                marker = true,
            },
        },
        items = {
            { id = "plant_pot", item = "plant_pot", label = "labSupplyPlantPot", category = "cultivation", price = 350, maxPurchase = 12, stockEnabled = true, stockMode = "fixed", stockAmount = 80, description = "labSupplyPlantPotDescription" },
            { id = "potting_soil", item = "potting_soil", label = "labSupplyPottingSoil", category = "cultivation", price = 180, maxPurchase = 20, stockEnabled = true, stockMode = "random", stockMin = 90, stockMax = 160, description = "labSupplyPottingSoilDescription" },
            { id = "plant_nutrients", item = "plant_nutrients", label = "labSupplyPlantNutrients", category = "cultivation", price = 240, maxPurchase = 15, stockEnabled = true, stockMode = "random", stockMin = 60, stockMax = 110, description = "labSupplyPlantNutrientsDescription" },
            { id = "water_bottle", item = "water_bottle", label = "labSupplyWater", category = "cultivation", price = 60, maxPurchase = 25, stockEnabled = false, description = "labSupplyWaterDescription" },
            { id = "trimming_shears", item = "trimming_shears", label = "labSupplyShears", category = "tools", price = 850, maxPurchase = 3, stockEnabled = true, stockMode = "fixed", stockAmount = 18, description = "labSupplyShearsDescription" },
            { id = "lab_gloves", item = "lab_gloves", label = "labSupplyGloves", category = "tools", price = 220, maxPurchase = 10, stockEnabled = false, description = "labSupplyGlovesDescription" },
            { id = "digital_scale", item = "digital_scale", label = "labSupplyScale", category = "tools", price = 950, maxPurchase = 2, stockEnabled = true, stockMode = "random", stockMin = 8, stockMax = 16, description = "labSupplyScaleDescription" },
            { id = "repair_kit", item = "repair_kit", label = "labSupplyRepairKit", category = "maintenance", price = 1200, maxPurchase = 4, stockEnabled = true, stockMode = "fixed", stockAmount = 20, description = "labSupplyRepairKitDescription" },
            { id = "fuel_can", item = "fuel_can", label = "labSupplyFuel", category = "maintenance", price = 500, maxPurchase = 6, stockEnabled = true, stockMode = "random", stockMin = 24, stockMax = 48, description = "labSupplyFuelDescription" },
            { id = "machine_oil", item = "machine_oil", label = "labSupplyOil", category = "maintenance", price = 420, maxPurchase = 8, stockEnabled = true, stockMode = "fixed", stockAmount = 45, description = "labSupplyOilDescription" },
            { id = "drug_packaging", item = "drug_packaging", label = "labSupplyPackaging", category = "processing", price = 180, maxPurchase = 25, stockEnabled = false, description = "labSupplyPackagingDescription" },
            { id = "lab_shelf_small", item = "lab_shelf_small", itemLabel = "Small Shelf", label = "labSupplyShelfSmall", category = "storage", price = 8000, maxPurchase = 2, stockEnabled = true, stockMode = "fixed", stockAmount = 10, description = "labSupplyShelfSmallDescription" },
            { id = "lab_shelf_medium", item = "lab_shelf_medium", itemLabel = "Industrial Shelf", label = "labSupplyShelfMedium", category = "storage", price = 18000, maxPurchase = 1, stockEnabled = true, stockMode = "random", stockMin = 3, stockMax = 7, description = "labSupplyShelfMediumDescription" },
            { id = "lab_shelf_large", item = "lab_shelf_large", itemLabel = "Secured Storage Rack", label = "labSupplyShelfLarge", category = "storage", price = 42000, maxPurchase = 1, stockEnabled = true, stockMode = "random", stockMin = 1, stockMax = 3, description = "labSupplyShelfLargeDescription" },
        },
    },

Supplier entries already imported into the Drug Creator keep their saved settings and position. To move one, open the Drug Creator (default command /drugcreator) with your existing creator permission, select the saved laboratory supplier, choose Set position, and confirm the new position and heading. The saved entry changes; its other settings remain intact. Editing the supplier template or restarting the resource does not move the saved entry. If you deliberately need to replace it from a template, select only that supplier in the import preview and enable replacement of existing entries; this also replaces its other imported settings, so review products and prices first. Keep Heist Creator imports separate.

No other released plaintext option, init/provider setting or command default changes in this follow-up. Update the resource's complete locale folder for new equipment and ownership messages, and update Jobs Base for the matching configurator labels.

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

No new SQL schema, manual SQL import, database reset, item definition, inventory icon or streamed model is required by these follow-up changes. Existing laboratory, equipment, inventory, construction-node and production tables are reused. Keep your existing items and assets. Equipment removal returns the already configured installation item to laboratory storage, including its condition, fuel and oil where applicable. If you use custom equipment, check that its existing return item is configured and available; a missing return item blocks removal. Your inventory integration must preserve item metadata when transferring the returned item if you want its saved equipment state to survive that transfer. Do not reimport the full seed SQL or overwrite all creator defaults to apply these fixes. Keep the existing database migration/provider setup from the 0.8.1 instructions; these changes add no new provider selection or credentials.

5. Restart and check

Perform a full server restart to reload the source and manifest file lists, then reconnect clients. Start the framework, database connector and selected providers first, then refreshed Base 1.45.1, Jobs Base 1.48.1 and Crime 0.8.1. Stop Crime System before replacing files. Start the updated Sky Base first, then Sky Jobs Base, then Crime System; restore other resources stopped with their dependencies in their normal dependency order. Confirm that both libraries complete startup and Crime System finishes registration. Read the console for actual startup errors and new warnings about invalid saved ATM/shop settings. This follow-up uses the existing startup and automatic migration owners; a successful file copy alone does not prove the running resource or database state.

1. Open /jobconfig → Crime System → Drug System → General. Confirm both new limits, save your intended values and check them after restart. With a temporary limit of one on a test owner, purchase or rent one fixed laboratory, then check that a second acquisition is refused without charging the owner. Check character and faction owners separately; confirm existing ownership is preserved and camper/shared-access cases do not consume the fixed-laboratory limit. Restore your intended values.
2. In an idle laboratory, approach an installed machine, generator or additional storage shelf and open its interaction/status menu. Use Remove, check that exactly one installation item appears in laboratory storage, the prop and linked construction slot are freed, and condition/fuel/oil survive reinstallation. Check keyboard interaction and your configured target provider. The starting storage must remain; queued/running production and insufficient remaining storage capacity must refuse removal without losing equipment or stored contents. Users need the existing laboratory equipment capability.
3. Let a planted pot change between small, medium and large growth stages on the same placement surface. Check that its pot remains on that surface and existing saved plant positions are preserved. If you use custom plant models, check their alignment separately.
4. Open the Drug Creator import preview for an already imported supplier. It must be marked as existing, remain selectable and be skipped when replacement is off; do not overwrite it just to test the preview. If you move a saved supplier with Set position, check its saved heading and NPC on connected clients.
5. Open the regular Crime location editing tools and ATM/shop configuration. Invalid saved robbery entries should produce useful warnings while remaining location tools register; repair the warned entries in the configurator. If applicable, confirm robbery alerts and clerk code handoff no longer add a logging error when the underlying action is rejected.
6. Open drug contact and market views with inventory-backed batches. Change the player's carried quantity and reopen/refresh through the normal flow; quantities and eligible batches must reflect the current player's inventory, including separate characters. Complete ordinary laboratory/storage/production checks before allowing normal play. A long dependency wait no longer aborts at 60 seconds. Repair the original error behind any migration warning; failure to read saved settings remains an initialization error. Check the existing Ambulance death-handling integration on staging when installed.

1. Prepare

These instructions cover sky_crimesystem 0.7.1 → 0.8.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 0.8.0 release package. Delete the entire sky_crimesystem/source/ folder and insert its new version; do not merge old generated interface files. Replace sky_crimesystem/fxmanifest.lua from the same package. Refresh the complete sky_crimesystem/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_crimesystem/config/config.lua
• sky_crimesystem/config/functions.lua
• sky_crimesystem/config/heist_exports/heist_4_v1.json
• sky_crimesystem/config/init.lua
• sky_crimesystem/config/locales/*
• sky_crimesystem/config/reputation.lua
• sky_crimesystem/fxmanifest.lua
• sky_crimesystem/import.sql
• sky_crimesystem/source/* — delete and reinsert

Remove these obsolete files outside source/:

• sky_crimesystem/items_esx.sql

Merge the supplied config folder with your existing settings, retaining all newly supplied files and your saved overrides. Drug Creator and Heist Creator content use their separate steps in this guide.

3. Merge configuration

Install the matching updated sky_base and sky_jobs_base first, then sky_crimesystem. Keep ensure sky_base, ensure sky_jobs_base, ensure sky_crimesystem in that order. Replace the complete sky_crimesystem/source/ folder and sky_crimesystem/fxmanifest.lua from the same download; merge personal edits in configuration files and replace all bundled locale files.

Named reputation rules — plaintext configuration. In sky_crimesystem/config/reputation.lua, Config.Reputation.rules did not exist in 0.7.1. Its new shipped value is an empty table. Add the complete new table without changing existing reward amounts; either add rules = {}, inside the existing Config.Reputation = { ... } table or add this assignment after that table:

Config.Reputation.rules = {}

An empty list preserves the normal rewards. Each optional rule uses name, action, target, points, and enabled. An empty target applies to its activity; a nonempty target is supported for heist (the heist ID) and drug_sale (the drug type). A matching target rule takes priority over a general rule, which takes priority over the normal reward. Changing a rule affects future completions and does not recalculate existing reputation history.

Saved Job Configurator settings. With Config.UseJobConfigurator = true, open /jobconfig → Crime System → Reputation → Reputation. The new table key is reputationRules, initially []; keep your existing reputationRewards, reputationEnabled, reputationPointsPerLevel, and reputationMinimumJoinPoints values. Review and save the new named rules there. Saved overrides remain authoritative; changing a file default does not replace an already saved value.

ATM drilling and locations. Open /jobconfig → Crime System → Robbery → ATM Robbery. In the equipment group, review the new atmDrillItem, atmDrillItemAmount, and atmConsumeDrill settings. Previously these controls were absent; new missing keys use Config.ATMRobbery.items.drill, whose shipped values remain key = "vault_drill", amount = 1, and consume = false.

Config.ATMRobbery.items.drill = { key = "vault_drill", amount = 1, consume = false }

This existing plaintext block is unchanged from 0.7.1; no new drill block is needed when /jobconfig is disabled. Keep an existing custom item ID, quantity, or consumption choice. Consumption applies after each successfully completed ATM drilling point. Shop safes remain separate and use Config.ShopRobbery.drillItem, with the same unchanged shipped values; changing ATM settings does not change safe settings. The atmLocations editor now creates missing internal IDs automatically. Keep existing saved IDs, locations, and customizations; no ID rewrite or database reset is required. Robbery → NPC Pickpocketing now groups its existing settings under one subsection, preserving their keys and saved values.

Drug Creator content. The saved Drug Creator catalogue and its gameplay defaults do not require a new import. Keep existing entries and any template links. The default-import screen still lets you choose categories and entries, but now uses a compact grouped layout without its search field. Import defaults only when you intentionally want to add or update those selected templates; do not use a bulk reset as an update step.

Heist Creator content. Preserve saved drafts, published definitions, plans, and custom JSON files. Merge the supplied sky_crimesystem/config/heist_exports/heist_4_v1.json separately if you customized that built-in heist. Its definition.planningMap was absent in 0.7.1 and now contains the full block below. It also changes one keycard preparation description from the German wording for blockade to the wording for obstacle; the supplied missions, rewards, gas geometry, alarms, and crew limits are unchanged.

"planningMap": {
  "target": {
    "x": 255.2282562255859,
    "y": 223.97601318359375
  },
  "locationLabel": ""
}

Place this property inside the JSON definition object. Updating the supplied JSON file does not overwrite separately stored Creator definitions. New gas-zone placement now needs at least four corners before confirmation; existing saved gas zones remain valid.

Optional Heist development tools. The detached built-in export browser and developer export action previously followed Config.HeistCreator.builtinExport.enabled alone. They now also need the server setting sky_crimesystem_developer to equal the string true; its default is false. Existing registered built-in editing remains available without enabling developer exports. If you use these development tools, add the following before the Sky ensure lines in server.cfg and restart the resource:

set sky_crimesystem_developer true

Keep Config.HeistCreator.builtinExport.enabled = true and grant the existing Creator permission sky_crimesystem.crimecreator to the administrator. The optional /heisttest command uses the same opt-in and permission, lets an administrator select a saved or registered heist, and lets them stop their active test. Use it on a development or staging server: it grants real inventory equipment and uses the normal heist execution and reward handling. Reopening /heisttest offers cancellation; stopping a test does not promise to remove all equipment or rewards already received. To disable developer tools again, use set sky_crimesystem_developer false and restart.

Install Sky Base 1.45.0 and Sky Jobs Base 1.48.0 from this release set before installing Crime System 0.8.0. Start them in this order: sky_base → sky_jobs_base → sky_crimesystem. The new item-catalog reads and Job Configurator update event require those companion versions. These additional runtime changes introduce no new editable setting or changed default. Keep all saved /jobconfig overrides, crime jobs, Drug Creator entries and heist plans.

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

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

4. Data, items and dependencies

SQL. Back up the database. Reputation rules and the handbook reuse the existing sky_crime_reputation table; do not reset its records. Copy the updated sky_crimesystem/import.sql. With the existing Config.AutoExecuteQuery = true, main resource tables continue to be handled at startup. If you keep Config.AutoExecuteQuery = false, apply the updated main import.sql manually through your normal database process, preserving existing data. This main SQL path is separate from Heist persistence: keep the existing Config.HeistPersistence.enabled and Config.HeistPersistence.autoMigrate choices. The documented active features introduce no changes to the existing reputation, PvP, base-raid, interrogation, or separate Heist table schemas. /jobconfig does not install SQL.

Items. Remove only the obsolete sky_crimesystem/items_esx.sql file from the resource folder; retain all existing inventory items and database item rows. Do not run a deleted import file or delete items because the file disappeared. No new mandatory item definitions are introduced for the documented features. ATM and shop-safe drilling still require the configured vault_drill item by default, with ATM quantity/consumption controlled independently. Keep the existing base-raid requirements from config/base_raids.lua: baseraidkit, police_raidram, and search_warrant (consumed on a valid police raid start). Keep interrogation definitions from config/interrogation_core.lua and config/interrogation_tools.lua: interrogation_chair, interrogation_cart, cable_tie, blindfold, reusable torture_pliers and car_battery, and consumed blowtorch and water_canister. Preserve your custom IDs if you changed these settings. Supported inventories retain the existing automatic fixed-item registration controlled by Config.InventoryItems.autoRegisterItems; the default preserveExisting = true keeps server-owned definitions. With automatic registration disabled or an unsupported inventory, retain or install the required definitions using your inventory's normal setup. For ox_inventory, missing supplied entries still need to be copied from sky_crimesystem/config/inventory/items_ox.lua into ox_inventory/data/items.lua before restarting the inventory. Existing QB examples remain in sky_crimesystem/config/inventory/items_qb.lua. Qbox still needs its existing configured black_money item.

Assets. Replace the complete source/ folder so the rebuilt interface includes the reputation handbook artwork and Crime storage background. Keep fxmanifest.lua and that folder from the same download. Existing config/inventoryimages/png/ and config/inventoryimages/webp/ mappings and streamed models are unchanged by this release; no new inventory-image or stream migration is required. If an existing mandatory item's image is missing, use the matching supplied image in your inventory image folder. Replace all sky_crimesystem/config/locales/* files; the existing global language selection still controls the resource and an explicit selection is preserved.

These additional runtime changes require no extra SQL, item, image or model migration. Preserve the item definitions and creator data required by the main Crime update instructions.

5. Restart and check

Start your framework, database connector and configured providers first, then Base, Jobs Base and the updated job resources in dependency order. Reconnect clients. After restarting in dependency order, open the Crime tablet and creators during a fresh connection, then reload an already open interface and check that its menu, context, and focus return.

Open /crimerep and check your character's progress, reward list, recent activity, page navigation, close control, and zoom controls. Test one new named rule on a future matching completion; confirm an unmatched completion keeps its normal reward and old history remains unchanged.

In /jobconfig → Crime System → Robbery → ATM Robbery, create an ATM location without entering an ID, save, reopen, and reorder it; confirm the location remains valid. Check the exact configured drill item and consumption at each successful drilling point. Confirm NPC Pickpocketing appears once.

Enter a faction laboratory, change membership through the normal server workflow, and confirm access is revoked. Check that a laboratory sale identifies the refund account and faction refunds go to that account; acquisition costs should not appear as treasury spending.

Enter a camper laboratory and try a permitted shelf transfer, a rejected transfer, and the normal raid access workflow. Check the rejection message explains the cause.

Check planted models remain on their placement surface through growth stages, the player stays visible during harvesting, and interrogation dummies, seats, and tool scenes align.

In the Heist Creator, test four-corner gas placement, movement while choosing an obstacle, contextual input hints, preparation links to multiple obstacles, readable field examples, and inspector visibility. Preserve existing saved definitions.

If you explicitly enable the optional development setting on a staging server, check the export browser and permission-controlled /heisttest selection/cancellation; leave it disabled for normal operation when not needed.

While the planning interface is closed or another app is open, issue a catalog or access update and confirm that it does not request a planning snapshot; reopen Heist Planning and confirm it loads current data. Enter, leave and re-enter a laboratory and confirm that workers continue to refresh while present. Trigger overlapping smoke and fire effects and confirm that each effect stops at expiry. Start two interrogation sessions, end one and then the other, and confirm that active warnings, binding timeout and release deadlines continue to work. Save Crime settings in /jobconfig and verify the configured crime jobs, tablet apps and base-raid command update immediately. Restart once with the matching Sky Base and Jobs Base versions and check item registration warnings.

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_crimesystem 0.7.0 → 0.7.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 0.7.1 download. Delete the entire sky_crimesystem/source/ folder and insert the new folder. Replace sky_crimesystem/fxmanifest.lua from that same package. Refresh the complete sky_crimesystem/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 the Crime tablet, then check a configured crime activity. 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_crimesystem 0.6.0 → 0.7.0. Complete earlier required migrations first when upgrading from an older version. Before stopping the server, finish active base raids and back up the database, installed resource, customized configuration and saved Job Configurator, Drug Creator and Heist Creator data. Then stop the server for the coordinated update; raids do not resume after a resource restart.

Install Base 1.44.0 first, Jobs Base 1.47.0 second and Crime 0.7.0 afterward, together with the matching updates for your other installed Sky jobs. The new raid interfaces and laboratory worker support require these matching dependencies. Keep your current framework, inventory and vehicle-key providers configured and running before the Sky resources.

2. Replace the package files

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

Merge each configuration change below into your own files. Copy the optional sky_crimesystem/config/heist_exports/heist_4_v1.json when you want the revised bundled export; copying it does not replace a saved heist. No files outside source/ are removed or renamed, and this release adds no new streamed model or inventory image.

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.

Prepare file edits while the server is stopped. Perform the /jobconfig, Creator imports and in-game checks described below only after starting the updated resources during maintenance, before admitting players.

Keep your existing jobs, coordinates, prices, providers and saved overrides. The following changes cover every modified configuration file for this version. Each Lua assignment shown below belongs after its existing parent table in the named file; do not paste a Config... = assignment inside a table.

ATM hand placement — sky_crimesystem/config/config.lua

Previously, Config.ATMRobbery.drillPresentation.hands did not exist. Add this complete block while keeping your existing player, tool, camera, target and FOV calibration:

Config.ATMRobbery.drillPresentation.hands = {
    x = 0.00000,
    y = 0.00000,
    z = 0.00000,
}

This is a file-based visual calibration setting; there is no matching /jobconfig key. Recalibrate only if your existing custom ATM presentation needs it.

Protected test placement — sky_crimesystem/config/drugs.lua

Previously, Config.Drugs.Creator.debug did not exist. The new shipped default is:

Config.Drugs.Creator.debug = true

This enables test placement controls for authorized Drug Creator administrators. Set it to false if you do not want these tools enabled. It does not grant Creator permission. This value is edited in the file, not /jobconfig. Test plants, campers and laboratories create saved world assets; use a staging server for acceptance tests.

Camper locking — sky_crimesystem/config/drugs_campers.lua

Remove the old lockKey = "L" entry from Config.Drugs.Campers (or your customized value). There is no replacement Crime lock key. The former /jobconfig → Drug Operations → Labs & Camper setting drugCamperLockKey and the separate Crime camper lock action are retired. Existing saved values no longer control locking. Use the lock control supplied by your configured vehicle-key provider, and check that purchases and successful camper theft give the intended player keys.

Plant-care timing — sky_crimesystem/config/drugs_growing.lua

Change Config.Drugs.Growing.care.minigames.treat.duration from 11 to 4 and Config.Drugs.Growing.care.minigames.trim.duration from 10 to 4 for the new shipped timings. The minigame names, rounds and XP are unchanged. Preserve intentional custom timings if desired. There are no matching /jobconfig fields for these two durations.

Config.Drugs.Growing.care.minigames.treat.duration = 4
Config.Drugs.Growing.care.minigames.trim.duration = 4

Interior contents — sky_crimesystem/config/drugs_laboratories.lua

Replace only the two emptyInterior tables below. The vehicle warehouse previously disabled the five listed entity sets; it must now enable them. The small warehouse previously disabled styles 1–5; it must now disable only 1–4 and enable style 5. Keep each preset's existing entrance, exit, bounds and nodes.

Config.Drugs.Laboratories.interiorPresets.criminal_enterprise_vehicle_warehouse.emptyInterior = {
    ipls = {
        "reh_int_placement_sum2_interior_0_dlc_int_03_sum2_milo_",
    },
    enable = {
        "entity_set_office",
        "entity_set_light_option_1",
        "entity_set_light_option_2",
        "entity_set_light_option_3",
        "entity_set_tint_options",
    },
}

Config.Drugs.Laboratories.interiorPresets.criminal_enterprise_warehouse.emptyInterior = {
    ipls = {
        "reh_int_placement_sum2_interior_1_dlc_int_04_sum2_milo_",
    },
    disable = {
        "entity_set_style_1",
        "entity_set_style_2",
        "entity_set_style_3",
        "entity_set_style_4",
    },
    enable = { "entity_set_style_5" },
}

These are preset definitions in the file. Existing saved Creator layouts and placed laboratories should be retained; do not reimport all defaults to apply this fix.

Laboratory worker activity — sky_crimesystem/config/drugs_labs_power_workers.lua

Previously, Config.Drugs.Workers.ai did not exist. Add the complete block:

Config.Drugs.Workers.ai = {
    enabled = true,
    refreshIntervalMs = 10000,
    idleRadius = 3.5,
    securityPatrolRadius = 7.0,
    scenarios = {
        chemist = "WORLD_HUMAN_CLIPBOARD",
        grower = "WORLD_HUMAN_GARDENER_PLANT",
        packager = "WORLD_HUMAN_CLIPBOARD",
        security = "WORLD_HUMAN_GUARD_STAND",
    },
    stationRoles = {
        chemist = { "chemistry", "heating", "testing" },
        grower = { "growing", "planting", "trimming", "drying" },
        packager = { "packaging", "pressing" },
    },
}

The existing /jobconfig → Drug Operations → Workers settings, including drugWorkersEnabled, still control the worker system. The new ai block is file-based and has no separate /jobconfig fields. Existing hired workers are retained.

Tablet buyer and dealer defaults — sky_crimesystem/config/drugs_market_threat_processing.lua

The existing Config.Drugs.Market.buyers rows gain tabletEnabled, starter/unlock settings, request minimum/maximum quantities and cooldowns. The existing dealer rows gain tablet availability, starter/unlock settings, hire availability and the recruitment values shown below. These fields were absent in the previous stock tables. Merge the new fields into matching custom rows and keep any additional entries; the full new stock tables are:

Config.Drugs.Market.buyers = {
    street_random = {
        label = "Street Buyer", channel = "street", minScore = 0,
        maxContamination = 45, priceMultiplier = 1.0, demandBonus = 0,
        tabletEnabled = true, starterContact = true,
        requestMinAmount = 1, requestMaxAmount = 8, cooldownMinutes = 45,
    },
    club_buyer = {
        label = "Club Buyer", channel = "premium", minScore = 70,
        maxContamination = 18, priceMultiplier = 1.35, demandBonus = 12,
        preferredPackaging = { "jar", "vacuum", "premium_seal" },
        tabletEnabled = true, unlockReputation = 20,
        requestMinAmount = 4, requestMaxAmount = 12, cooldownMinutes = 60,
    },
    wholesale_contact = {
        label = "Wholesale Contact", channel = "wholesale", minScore = 50,
        maxContamination = 30, priceMultiplier = 0.82, demandBonus = 5,
        bulkOnly = true, tabletEnabled = true, unlockReputation = 35,
        requestMinAmount = 15, requestMaxAmount = 60, cooldownMinutes = 120,
    },
}

Config.Drugs.Market.dealers = {
    corner_dealer = {
        label = "Corner Dealer", channel = "street", speedMultiplier = 1.0,
        priceCut = 0.18, minScore = 0, tabletEnabled = true,
        starterContact = true, hireEnabled = true, hirePrice = 35000,
        initialLoyalty = 60, dealerSkill = 40, dealerRisk = 35,
        dailyCapacity = 24,
    },
    network_dealer = {
        label = "Network Dealer", channel = "wholesale", speedMultiplier = 1.25,
        priceCut = 0.24, minScore = 45, tabletEnabled = true,
        unlockReputation = 25, hireEnabled = true, hirePrice = 65000,
        initialLoyalty = 68, dealerSkill = 58, dealerRisk = 42,
        dailyCapacity = 36, defaultStyle = "balanced",
    },
    premium_broker = {
        label = "Premium Broker", channel = "premium", speedMultiplier = 0.85,
        priceCut = 0.3, minScore = 75, tabletEnabled = true,
        unlockReputation = 55, hireEnabled = false,
    },
}

Saved Drug Creator entries are separate from these file defaults. Review Buyers and Dealers in Drug Creator for existing content; a file update alone does not replace those definitions. Retain your /jobconfig overrides under Market & Risk → Market & Distribution and Drug Networks → Contact Network. The per-entry values above are Creator content, not new global /jobconfig keys.

Supplier item order — sky_crimesystem/config/drugs_supply_chain.lua

Previously, Config.Drugs.SupplyChain.supplierPriceOrder did not exist and default supplier products were collected from supplierPrices. The new default supplier import follows this explicit order:

Config.Drugs.SupplyChain.supplierPriceOrder = {
    "label_printer",
    "lab_supply_kit",
    "empty_baggy",
    "mountain_coca_seed",
    "blue_dream_seed",
}

Keep your existing supplierPrices. Add every custom key from that table that you want included in generated default suppliers to supplierPriceOrder; an omitted custom key will not be included in a future default supplier import. Existing saved supplier products are retained and can be edited in Drug Creator → Laboratory Suppliers. There is no global /jobconfig key for this order.

Crime membership reputation — sky_crimesystem/config/reputation.lua

The shipped value Config.Reputation.minimumJoinPoints changes from 100 to 0; 0 disables the admission requirement and positive values keep it enabled. pointsPerLevel stays 100.

Config.Reputation.minimumJoinPoints = 0

With /jobconfig, open Reputation → Crime Membership and review reputationMinimumJoinPoints. An explicit saved or imported positive value is retained; change/reset that value to 0 only if you want the new disabled-by-default behavior. Do not reset reputation points or reward settings.

Base raid settings and locations

sky_crimesystem/config/base_raids.lua has no changed keys or defaults. Keep existing settings and /jobconfig → Base Raids overrides. The existing baseRaid_breachTimeoutSeconds now limits each breach attempt at an interaction point; baseRaid_interactionDistance, baseRaid_difficulty and baseRaid_requiredHits govern that attempt. baseRaid_protectionHours and baseRaid_failedCooldownMinutes still govern protection and failed attempts. Each crime job needs its correctly placed baseZone in Config.Jobs or /jobconfig → Mainbase. Check that intended storage, locker and heist-storage interaction points lie inside it. Do not create arbitrary replacement coordinates.

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

4. Apply SQL, inventory and asset updates

Database and existing raids

This version adds no table, SQL column, column type or SQL default, and requires no manual SQL migration from a complete 0.6.0 installation. Preserve your existing database. The main Crime tables, PvP tables, interrogation consent/objects/logs, base-raid tables and heist-screen table remain covered by the existing import.sql and their existing automatic migration paths. With Config.AutoExecuteQuery = true, keep the normal automatic route; with false, retain the already installed schema. Do not rerun the full SQL import merely for this update.

Heist definitions, plans and planning locations use the separate sky_crimesystem:heist migration controlled by Config.HeistPersistence.autoMigrate; their schema is unchanged. Heist screen persistence has its own existing migration. The new heist planning-map data and laser-wall grouping are saved inside the existing heist definition payload, not new SQL columns.

Base raids continue using sky_crime_base_raids (job, data) and sky_crime_base_raid_log. The saved session now records which interaction points were breached. On restart, any saved raid is ended: an older active session, or a new session with a breached point, receives normal protection; a new session with no breached point receives the failed-raid cooldown. Existing longer cooldowns are retained. No table reset or hand-edited raid JSON is required.

Drug Creator content

Keep your saved definitions. Updating resource files does not import defaults or replace custom entries. Open each affected Buyer, Dealer, Street Sale, Laboratory Supplier, Laboratory, Interior Template, Drug Field or Processing Location only when you want to review its newly exposed settings. Simple/Advanced mode changes the editing view; Advanced remains the default. Street-sale opening hours use the server's real local clock, and hourly street-sale limits restart with the resource.

If you deliberately want revised stock buyer, dealer or supplier content, first export/back up the existing entries, then use Drug Creator's Import Defaults and select only the entries you intend to replace. Review the selection before importing; replacement changes those saved definitions. Do not import every default just to update the script. Add custom supplier-price keys to the new order before generating/importing default suppliers.

The new Release laboratory action is a deliberate ownership reset, not an update step. It makes the site available and deletes the previous laboratory's storage, equipment, plants, workers, treasury, upgrades, production and associated activity; it does not refund the owner. Ordinary laboratory sales now perform the same contents cleanup. Back up and remove anything you intend to keep before using these actions. Do not release existing laboratories as part of installation.

Heist Creator content

Keep existing heists and plans. Existing definitions infer their planning-map target from their configured world locations; review the map target and label in Heist Creator when a different location is needed. Laser walls retain their individual beams and can be managed as a group.

The optional config/heist_exports/heist_4_v1.json changes the four Pacific cash pickups from 50,000, 50,000, 50,000 and 1,000 to 200,000 each, and adds an explicit always-allowed requirement to its keycard preparation objective. This does not update a saved Pacific heist automatically. Back up/export your current definition and import the revised file separately through Heist Creator only if you want those changes; otherwise retain your existing payout and settings. Drug Creator default imports do not import heists.

Inventory items and assets

No new item definition, inventory image or streamed asset is introduced. Keep the existing item mappings and image provider. Base raids still require the configured police_raidram or baseraidkit; police raid starts also require and consume search_warrant. Verify your customized names from Config.BaseRaids, not only the standard item import list.

If interrogations are enabled, retain the configured interrogation_chair, interrogation_cart, cable_tie, blindfold, torture_pliers, car_battery, blowtorch and water_canister, plus any item you configured for rescue. Check their existing images in your inventory resource. These are existing requirements, not new items for this version.

Money Wash and the Online Heist Hub remain disabled, jewel-case creation remains locked in the Creator, and NPC police reinforcement remains disabled by default.

5. Restart and verify

Start the database, framework and configured providers, then Base 1.44.0, Jobs Base 1.47.0 and Crime 0.7.0, and reconnect before admitting players. Resolve startup or migration errors first. Perform the following checks on your staging or maintenance server:

• Open Drug Creator, switch Simple/Advanced modes and confirm a saved custom entry remains intact. Check a buyer's request amount/cooldown and a dealer's hiring settings. Confirm custom supplier products are present before importing any defaults.
• Enter both affected warehouse interiors. Check item images after a storage action, install one compatible equipment item, verify staff appear, and confirm storage upgrades and full-storage production behavior. Confirm an emergency exit only exits.
• Buy or use a test camper and verify locking, unlocking and key handover with your actual vehicle-key provider. Test permitted and denied access.
• Place one plant and check its height and immediate visibility, then try treatment, trimming and harvesting. Confirm the activity display stays on screen.
• Start a base raid from the tablet, travel to a valid world interaction point, breach it, and withdraw an allowed item through shared storage. Check a second point stays locked until separately breached, unrelated jobs cannot use it, and raid access does not offer depositing or returning vehicles. Verify configured vehicle permissions and expected cooldowns.
• Open an existing heist planning map, confirm its target, check one grouped laser wall and verify the buyer disappears when its plan ends. If you imported the Pacific export, confirm all four configured payout amounts.
• Check crime-job admission with your intended saved reputation threshold. Test an ATM drilling attempt with your existing presentation profile.

These checks must be performed against the installed FiveM server and its providers. Source tests, interface builds and copied packages alone do not verify live gameplay.

1. Prepare the update

This is the complete 0.6.0 package. If you already installed an earlier 0.6.0 download, apply these instructions again; checking the version alone cannot distinguish the packages. The current package has nui_build '05d656cdde7d2846' in its manifest and includes the stream/heist-screen/ assets and the new screen configuration. Read every step before stopping the server.

Back up stored Creator definitions before importing any defaults. The new selection page replaces selected existing entries with the supplied versions.

If Fire Job is installed and you are also updating an older Fire version, take all breathing bottles out of vehicle bottle storage before stopping that old version. 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_crimesystem 0.5.0 → 0.6.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 0.6.0 package. Delete the old sky_crimesystem/source/ directory completely and insert the new directory. Replace sky_crimesystem/fxmanifest.lua from the same package. Refresh the entire sky_crimesystem/config/locales/ tree and merge your custom translations back. Merge the four changed files config/drugs.lua, config/drugs_growing.lua, config/drugs_laboratories.lua and config/drugs_supply_chain.lua using the exact blocks in this view. The new model-preview images are included in source/; no separate inventory image installation is needed.

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

Also merge sky_crimesystem/config/config.lua using the new screen and ATM blocks below. Add every file from sky_crimesystem/stream/heist-screen/ and the optional sky_crimesystem/config/heist_exports/heist_4_v1.json without removing your other custom exports or stream assets. Update sky_crimesystem/import.sql and apply the targeted table migration in step 4. Existing 0.6.0 installations must replace the full source/, matching manifest and listed new files too; do not keep the earlier interface bundle.

3. Merge configuration and saved overrides

Prepare file changes while stopped. Perform /jobconfig, Creator and other in-game actions only after step 5 starts the updated resources, during maintenance before admitting players.

Configuration and stored Creator content

The complete release also changes sky_crimesystem/config/config.lua; its required screen and ATM additions follow the drug blocks below. Keep custom values when merging the four changed drug files. The supplied catalog is now centered on Weed and Cocaine; keep your intentional extra-drug definitions, harvesting, supply-chain entries and saved Creator content if those workflows remain in use. Updating files alone does not delete existing Creator entries from the database.

Remove the obsolete Config.Drugs.Creator.autoImportDefaults field from config/drugs.lua. Defaults are no longer imported during startup. Existing servers may keep their current Creator content. After the maintenance restart in step 5, to adopt supplied defaults, open /drugcreator → Import Defaults, globally or in the wanted section, review the selection and import only entries you intend to replace. Selected existing entries are overwritten; unselected entries are preserved. Include required Drug, Interior, Process and Camper definitions in a global selection, or create/import those dependencies first. An incomplete selection is rejected before any entries change; missing dependencies are not imported silently.

Normal laboratories still use their configured interior templates. Campers now use the fixed Drug Wars interior; an old custom camper-interior selection no longer chooses a different runtime interior. The manager focuses on processing, but this does not categorically disable the shared seed-placement path inside a converted camper. Existing plant data remains; use inventory placement to place new laboratory pots freely.

The process-step editor exposes basic production fields, action label, required tool, input/count and consumption, ordering, duplication and presets. Advanced step keys, tool-consumption, interaction/marker/help/target settings, scenario/distances and heat/risk/environment/quality modifiers are no longer directly editable in that panel. Editing another field preserves existing advanced values. Applying a preset replaces that preset's step set, so review it before saving.

In QBCore or Qbox framework organization mode, every configured Crime organization must exist as a framework gang. Keep ESX job-based organization names and intentional independent membership mode. Do not reset memberships or change a primary job merely to apply this release.

Job Configurator and saved overrides

Affected route: Crime System → Drug Operations → Cultivation Levels. Saved settings override their stock defaults; editing Lua alone is insufficient where a saved override exists. Check/reset the applicable override deliberately and preserve all unrelated customization. Drug Creator definitions are stored separately and are not replaced by changing /jobconfig defaults.

Crime configurator labels are supplied by Jobs Base, so update its complete locale tree too. Creator definitions are a separate stored-content layer; changing /jobconfig defaults does not replace them.

Exact stock-file changes

The following blocks show each affected stock path before and after this version step. Merge the new blocks into their named files while preserving deliberate custom workflows. These are partial sections of the four files, not complete replacement files.

Where to paste: a full path such as Config.Drugs.Growing.progression.unlocks.strains = { ... } identifies the table. If replacing it inside the existing parent table, keep its local strains = { ... }, key and trailing comma and replace only its contents. Never paste a full Config... = assignment inside another Lua table. Alternatively, a full assignment shown here can be placed at the file's top level after that table's existing declaration. Use only the New stock block, not both old and new. Where a block is removed, delete that named obsolete stock entry when adopting this stock workflow; preserve intentional custom replacements. Remove the obsolete trailing mushroom/herbal aliases explicitly as shown.

sky_crimesystem/config/drugs.lua: Config.Drugs.Creator

Old stock block:

Config.Drugs.Creator = {
    enabled = true,
    permission = "sky_crimesystem.drugcreator",
    command = "drugcreator",
    autoImportDefaults = true,
    autoSyncWorldPoints = true,
    autoRegisterItems = true,
    persistFrameworkItems = true,
    warnMissingItems = true,
    defaultItemWeight = 1,
}

New stock block:

Config.Drugs.Creator = {
    enabled = true,
    permission = "sky_crimesystem.drugcreator",
    command = "drugcreator",
    autoSyncWorldPoints = true,
    autoRegisterItems = true,
    persistFrameworkItems = true,
    warnMissingItems = true,
    defaultItemWeight = 1,
}

sky_crimesystem/config/drugs_growing.lua: Config.Drugs.Growing.progression.unlocks.strains

Old stock block:

Config.Drugs.Growing.progression.unlocks.strains = {
    og_kush = 1,
    blue_dream = 1,
    mountain_coca = 3,
    dryland_root = 3,
    white_widow = 5,
    desert_ephedra = 5,
    purple_poppy = 5,
    gelato = 7,
    blue_spore = 7,
    purple_haze = 9,
}

New stock block:

Config.Drugs.Growing.progression.unlocks.strains = {
    blue_dream = 1,
    mountain_coca = 3,
}

sky_crimesystem/config/drugs_growing.lua: Config.Drugs.Growing.harvestParts.lsd

Old stock block:

Config.Drugs.Growing.harvestParts.lsd = {
    defaultMethod = "spore_cut",
    partsMin = 3,
    partsMax = 7,
    { key = "cap", label = "Pilzkappen schneiden", method = "spore_cut", outputItem = "wild_mushroom", tool = "trimming_shears", qualityDelta = 4, potencyDelta = 3, amountMultiplier = 0.22, plantDamage = 12, minigame = "spore_cut", propModel = "prop_stoneshroom1" },
    { key = "spore", label = "Sporenprobe sichern", method = "careful_cut", outputItem = "blue_spore_sample", tool = "precision_scissors", qualityDelta = 8, potencyDelta = 6, amountMultiplier = 0.08, plantDamage = 18, minigame = "precision_cut", propModel = "prop_stoneshroom1" },
}

New stock block:

Removed; no replacement block.

sky_crimesystem/config/drugs_growing.lua: Config.Drugs.Growing.harvestParts.herbal_stimulant

Old stock block:

Config.Drugs.Growing.harvestParts.herbal_stimulant = {
    defaultMethod = "uproot",
    partsMin = 2,
    partsMax = 4,
    { key = "root", label = "Wurzel freilegen", method = "uproot", outputItem = "desert_root", tool = "small_shovel", qualityDelta = 3, potencyDelta = 2, amountMultiplier = 0.34, plantDamage = 35, minigame = "precision_cut", propModel = "prop_plant_fern_02a" },
    { key = "golden_root", label = "Goldene Wurzel trennen", method = "careful_cut", outputItem = "golden_root", tool = "precision_scissors", qualityDelta = 9, potencyDelta = 5, amountMultiplier = 0.12, plantDamage = 22, minigame = "precision_cut", propModel = "prop_plant_fern_02a" },
}

New stock block:

Removed; no replacement block.

sky_crimesystem/config/drugs_growing.lua: Config.Drugs.Growing.strains

Old stock block:

Config.Drugs.Growing.strains = {
    {
        key = "og_kush",
        label = "OG Kush",
        drug = "weed",
        growthSpeed = 0.95,
        yield = 1.05,
        potency = 78,
        stability = 72,
        mutationChance = 1.5,
        pestResistance = 18,
        moldResistance = 12,
    },
    {
        key = "blue_dream",
        label = "Blue Dream",
        drug = "weed",
        growthSpeed = 1.05,
        yield = 1.0,
        potency = 72,
        stability = 82,
        mutationChance = 2.0,
        pestResistance = 10,
        moldResistance = 20,
    },
    {
        key = "white_widow",
        label = "White Widow",
        drug = "weed",
        growthSpeed = 1.0,
        yield = 0.95,
        potency = 84,
        stability = 76,
        mutationChance = 1.2,
        pestResistance = 22,
        moldResistance = 16,
    },
}

New stock block:

Config.Drugs.Growing.strains = {
    {
        key = "blue_dream",
        label = "Blue Dream",
        drug = "weed",
        growthSpeed = 1.05,
        yield = 1.0,
        potency = 72,
        stability = 82,
        mutationChance = 2.0,
        pestResistance = 10,
        moldResistance = 20,
    },
    {
        key = "mountain_coca",
        label = "Mountain Coca",
        drug = "coke",
        growthSpeed = 0.86,
        yield = 0.88,
        potency = 70,
        stability = 74,
        mutationChance = 0.8,
        pestResistance = 12,
        moldResistance = 14,
    },
}

sky_crimesystem/config/drugs_laboratories.lua: Config.Drugs.Laboratories.interiorPresets.weed_small

Old stock block:

Config.Drugs.Laboratories.interiorPresets.weed_small = {
    label = "Small Grow Laboratory",
    size = "small",
    allowLaboratories = true,
    allowCampers = true,
    entry = { x = 1066.11, y = -3183.47, z = -39.16, heading = 92.0 },
    exit = { x = 1066.11, y = -3183.47, z = -39.16, heading = 92.0 },
    backdoors = {},
    emptyInterior = {
        disable = {
            "weed_standard_equip", "weed_upgrade_equip", "weed_low_security", "weed_security_upgrade",
            "weed_production", "weed_set_up", "weed_drying", "weed_chairs",
            "weed_growtha_stage1", "weed_growtha_stage2", "weed_growtha_stage3",
            "weed_growthb_stage1", "weed_growthb_stage2", "weed_growthb_stage3",
            "weed_growthc_stage1", "weed_growthc_stage2", "weed_growthc_stage3",
            "weed_growthd_stage1", "weed_growthd_stage2", "weed_growthd_stage3",
            "weed_growthe_stage1", "weed_growthe_stage2", "weed_growthe_stage3",
            "weed_growthf_stage1", "weed_growthf_stage2", "weed_growthf_stage3",
            "weed_growthg_stage1", "weed_growthg_stage2", "weed_growthg_stage3",
            "weed_growthh_stage1", "weed_growthh_stage2", "weed_growthh_stage3",
            "weed_growthi_stage1", "weed_growthi_stage2", "weed_growthi_stage3",
            "light_growtha_stage23_standard", "light_growtha_stage23_upgrade",
            "light_growthb_stage23_standard", "light_growthb_stage23_upgrade",
            "light_growthc_stage23_standard", "light_growthc_stage23_upgrade",
            "light_growthd_stage23_standard", "light_growthd_stage23_upgrade",
            "light_growthe_stage23_standard", "light_growthe_stage23_upgrade",
            "light_growthf_stage23_standard", "light_growthf_stage23_upgrade",
            "light_growthg_stage23_standard", "light_growthg_stage23_upgrade",
            "light_growthh_stage23_standard", "light_growthh_stage23_upgrade",
            "light_growthi_stage23_standard", "light_growthi_stage23_upgrade",
            "weed_hosea", "weed_hoseb", "weed_hosec", "weed_hosed", "weed_hosee",
            "weed_hosef", "weed_hoseg", "weed_hoseh", "weed_hosei",
        },
    },
    cameraBounds = {
        min = { x = 1036.5, y = -3208.0, z = -39.0 },
        max = { x = 1066.5, y = -3182.0, z = -34.8 },
    },
    nodes = {
        { key = "grow_01", type = "cultivation", label = "Plant Position 1", coords = { x = 1053.95, y = -3196.65, z = -39.15 }, heading = 0.0 },
        { key = "grow_02", type = "cultivation", label = "Plant Position 2", coords = { x = 1056.15, y = -3196.65, z = -39.15 }, heading = 0.0 },
        { key = "grow_03", type = "cultivation", label = "Plant Position 3", coords = { x = 1058.35, y = -3196.65, z = -39.15 }, heading = 0.0 },
        { key = "grow_04", type = "cultivation", label = "Plant Position 4", coords = { x = 1060.55, y = -3196.65, z = -39.15 }, heading = 0.0 },
        { key = "machine_01", type = "machine", label = "Processing Position", coords = { x = 1038.9, y = -3205.4, z = -38.17 }, heading = 270.0 },
        { key = "storage_01", type = "storage", label = "Storage Position", coords = { x = 1040.4, y = -3199.2, z = -38.17 }, heading = 180.0 },
        { key = "utility_01", type = "utility", label = "Utility Position", coords = { x = 1044.2, y = -3194.8, z = -38.17 }, heading = 0.0 },
    },
}

New stock block:

Config.Drugs.Laboratories.interiorPresets.weed_small = {
    label = "Medium Cultivation Laboratory",
    size = "medium",
    allowLaboratories = true,
    allowCampers = true,
    entry = { x = 1066.11, y = -3183.472, z = -39.162, heading = 92.0 },
    exit = { x = 1066.11, y = -3183.472, z = -39.162, heading = 92.0 },
    backdoors = {
        { key = "backdoor_01", label = "Back door 1", x = 1039.132, y = -3195.771, z = -38.225, heading = 0.0 },
    },
    emptyInterior = {
        disable = {
            "weed_standard_equip", "weed_upgrade_equip", "weed_low_security", "weed_security_upgrade",
            "weed_production", "weed_set_up", "weed_drying", "weed_chairs",
            "weed_growtha_stage1", "weed_growtha_stage2", "weed_growtha_stage3",
            "weed_growthb_stage1", "weed_growthb_stage2", "weed_growthb_stage3",
            "weed_growthc_stage1", "weed_growthc_stage2", "weed_growthc_stage3",
            "weed_growthd_stage1", "weed_growthd_stage2", "weed_growthd_stage3",
            "weed_growthe_stage1", "weed_growthe_stage2", "weed_growthe_stage3",
            "weed_growthf_stage1", "weed_growthf_stage2", "weed_growthf_stage3",
            "weed_growthg_stage1", "weed_growthg_stage2", "weed_growthg_stage3",
            "weed_growthh_stage1", "weed_growthh_stage2", "weed_growthh_stage3",
            "weed_growthi_stage1", "weed_growthi_stage2", "weed_growthi_stage3",
            "light_growtha_stage23_standard", "light_growtha_stage23_upgrade",
            "light_growthb_stage23_standard", "light_growthb_stage23_upgrade",
            "light_growthc_stage23_standard", "light_growthc_stage23_upgrade",
            "light_growthd_stage23_standard", "light_growthd_stage23_upgrade",
            "light_growthe_stage23_standard", "light_growthe_stage23_upgrade",
            "light_growthf_stage23_standard", "light_growthf_stage23_upgrade",
            "light_growthg_stage23_standard", "light_growthg_stage23_upgrade",
            "light_growthh_stage23_standard", "light_growthh_stage23_upgrade",
            "light_growthi_stage23_standard", "light_growthi_stage23_upgrade",
            "weed_hosea", "weed_hoseb", "weed_hosec", "weed_hosed", "weed_hosee",
            "weed_hosef", "weed_hoseg", "weed_hoseh", "weed_hosei",
        },
    },
    cameraBounds = {
        min = { x = 1036.5, y = -3208.0, z = -39.0 },
        max = { x = 1066.5, y = -3182.0, z = -34.8 },
    },
    nodes = {
        { key = "machine_01", type = "machine", label = "Machine Position 1", coords = { x = 1045.42, y = -3197.04, z = -39.146 }, heading = 179.932 },
        { key = "machine_02", type = "machine", label = "Machine Position 2", coords = { x = 1042.493, y = -3197.036, z = -39.151 }, heading = 179.932 },
        { key = "storage_01", type = "storage", label = "Storage Position 1", coords = { x = 1050.953, y = -3194.373, z = -40.119 }, heading = 179.932 },
        { key = "storage_02", type = "storage", label = "Storage Position 2", coords = { x = 1050.921, y = -3196.971, z = -40.119 }, heading = 179.932 },
        { key = "storage_03", type = "storage", label = "Storage Position 3", coords = { x = 1050.793, y = -3199.505, z = -40.119 }, heading = 179.932 },
        { key = "utility_01", type = "utility", label = "Utility Position 1", coords = { x = 1051.303, y = -3190.988, z = -40.159 }, heading = 179.932 },
    },
}

sky_crimesystem/config/drugs_laboratories.lua: Config.Drugs.Laboratories.interiorPresets.meth_medium

Old stock block:

Config.Drugs.Laboratories.interiorPresets.meth_medium = {
    label = "Medium Chemical Laboratory",
    size = "medium",
    allowLaboratories = true,
    allowCampers = true,
    entry = { x = 996.91, y = -3200.68, z = -36.39, heading = 270.0 },
    exit = { x = 996.91, y = -3200.68, z = -36.39, heading = 270.0 },
    backdoors = {},
    emptyInterior = {
        disable = {
            "meth_lab_basic", "meth_lab_upgrade", "meth_lab_production",
            "meth_lab_security_low", "meth_lab_security_high", "meth_lab_setup",
        },
        enable = { "meth_lab_empty" },
    },
    cameraBounds = {
        min = { x = 996.5, y = -3201.8, z = -38.0 },
        max = { x = 1015.5, y = -3193.2, z = -33.8 },
    },
    nodes = {
        { key = "machine_01", type = "machine", label = "Chemistry Position", coords = { x = 1005.77, y = -3200.36, z = -38.52 }, heading = 180.0 },
        { key = "machine_02", type = "machine", label = "Heating Position", coords = { x = 1011.14, y = -3195.97, z = -38.99 }, heading = 0.0 },
        { key = "machine_03", type = "machine", label = "Packaging Position", coords = { x = 1014.1, y = -3194.95, z = -38.99 }, heading = 0.0 },
        { key = "storage_01", type = "storage", label = "Storage Position 1", coords = { x = 1001.5, y = -3194.86, z = -38.99 }, heading = 180.0 },
        { key = "storage_02", type = "storage", label = "Storage Position 2", coords = { x = 1001.5, y = -3197.1, z = -38.99 }, heading = 180.0 },
        { key = "utility_01", type = "utility", label = "Generator Position", coords = { x = 1004.75, y = -3194.96, z = -38.99 }, heading = 180.0 },
    },
}

New stock block:

Config.Drugs.Laboratories.interiorPresets.meth_medium = {
    label = "Medium Chemical Laboratory",
    size = "medium",
    allowLaboratories = true,
    allowCampers = true,
    entry = { x = 996.91, y = -3200.682, z = -36.392, heading = 270.0 },
    exit = { x = 996.91, y = -3200.682, z = -36.392, heading = 270.0 },
    backdoors = {},
    emptyInterior = {
        disable = {
            "meth_lab_basic", "meth_lab_upgrade", "meth_lab_production",
            "meth_lab_security_low", "meth_lab_security_high", "meth_lab_setup",
        },
        enable = { "meth_lab_empty" },
    },
    cameraBounds = {
        min = { x = 996.5, y = -3201.8, z = -38.0 },
        max = { x = 1015.5, y = -3193.2, z = -33.8 },
    },
    nodes = {
        { key = "machine_01", type = "machine", label = "Chemistry Position", coords = { x = 1007.14, y = -3200.362, z = -40.0 }, heading = 180.0 },
        { key = "machine_02", type = "machine", label = "Heating Position", coords = { x = 1010.442, y = -3200.56, z = -40.0 }, heading = 0.0 },
        { key = "machine_03", type = "machine", label = "Packaging Position", coords = { x = 1010.439, y = -3197.608, z = -40.0 }, heading = 0.0 },
        { key = "storage_01", type = "storage", label = "Storage Position 1", coords = { x = 1001.218, y = -3197.604, z = -40.0 }, heading = 180.0 },
        { key = "storage_02", type = "storage", label = "Storage Position 2", coords = { x = 1001.5, y = -3201.762, z = -40.0 }, heading = 180.0 },
        { key = "utility_01", type = "utility", label = "Generator Position", coords = { x = 1015.5, y = -3199.942, z = -40.0 }, heading = 180.0 },
    },
}