Changelog

1. Back up and stop

These steps update sky_base from 1.51.1 to 1.52.0. If your installed version is older, complete its intervening update guides first.

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

2. Install the matching files

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

Replace the listed framework adapters, phone adapters, target adapters, vehicle-key adapters, voice adapters and garage adapters with the new supplied files. If you customized one, compare its backed-up version and reapply only those custom changes to the matching new adapter. Copy the new config/integration/weather/helpers/native.lua before using the matching weather adapters and manifest. Replace config/vehicle_storage.lua, config/README.md and import.sql; preserve your existing configuration selections as explained next.

3. Keep settings and configure the update

Keep your current selections. In sky_base/config/config.lua, the existing garage = "auto" and vehiclekeys = "auto" values are unchanged; only their available-provider comments gained "rcore" and "jg". Keep your existing framework, phone, voice, weather, inventory and other provider choices. Base settings are file-owned; /jobconfig does not manage them.

The replacement config/vehicle_storage.lua adds the complete registration-defaults table below. Keep this table in the new file. If you use customized garage destinations, edit only the corresponding destination values in this table to match the installed garage, while keeping the new ownership-import functions in the supplied file. For example, the jg destination is "Legion Square"; rcore's job must match its own Config.DefaultGarageJob ("civ" by default). No vehicle is spawned by these defaults.

Sky.VehicleStorage.registrationDefaults = {
    esx = { type = "car", stored = 1 },
    qb = { state = 1, garage = "pillboxgarage" },
    qbox = { state = 1, garage = "pillboxgarage" },
    garages = {
        msk = { type = "car", stored = 1, garage = "A" },
        cd = { in_garage = 1, garage_id = "A", garage_type = "car", impound = 0, impound_data = "{}" },
        jg = { type = "vehicle", in_garage = 1, garage_id = "Legion Square" },
        codem = { parking = "Garage A" },
        rcore = { job = "civ", type = "car" }, -- Match rcore's Config.DefaultGarageJob.
        okok = { parking = "Legion Square" },
        quasar = { type = "vehicle", garage = "Legion Square" },
        op = { parking = "Würfelpark" },
    },
}

Optional — rcore Garage: install and configure rcore_garage for ESX or QBCore, including its own database setup. In config/config.lua, keep garage = "auto" or replace the current garage value with "rcore". Start rcore before Base. This integration does not support Qbox or VRP. New vehicles do not have an assigned parking location until parked; rcore controls its own collection/transfer fees. Keep the key provider configured separately.

Optional — JG Vehicle Keys: follow JG's inventory setup and use one active key system. In config/config.lua, keep vehiclekeys = "auto" or replace its value with "jg"; start jg-vehiclekeys before Base. Preserve existing registered vehicles and keys. Removing a held key does not invalidate copies that were transferred or stored elsewhere.

No new voice setting is required in Base. Gag/hostage gameplay is configured in Jobs Base's own guide.

4. Database, items and assets

Base automatically creates sky_base_citizen_numbers on startup using its existing database migration system. Keep the table and its rows: fallback citizen display numbers must remain stable. Framework SSNs/citizen IDs remain preferred where available, and existing character identifiers still control records and permissions.

No separate SQL import is needed when the database account can perform the automatic creation. If your administrator provisions tables manually, select the same FiveM database and execute only the sky_base_citizen_numbers creation block at the top of the supplied sky_base/import.sql before starting Base:

CREATE TABLE IF NOT EXISTS `sky_base_citizen_numbers` (
    `id` BIGINT UNSIGNED NOT NULL AUTO_INCREMENT,
    `identifier` VARBINARY(128) NOT NULL,
    PRIMARY KEY (`id`),
    UNIQUE KEY `uniq_citizen_number_identifier` (`identifier`)
) ENGINE=InnoDB;

This release adds no inventory item, item image or streamed model. Preserve existing vehicle ownership, account balances, phone data and custom provider configuration.

For the coordinated Jobs Base configurator migration, Crime Camper ownership migration, protected Coinshop subscriptions or optional Mechanic seasonal-tyre checkout: use oxmysql transactions. In this resource's config/config.lua, find the existing sql selector and set sql = "oxmysql", keeping the same database connection. Start oxmysql before Base. Other Base-only installations keep their existing supported SQL selector.

5. Start and check the result

Start the database connector, framework, inventory and configured phone/target/voice/garage/key providers first, then sky_base 1.52.0, then sky_jobs_base 1.55.0 if installed, followed by your installed consumers. Reconnect after the full restart; confirm the console has no provider or migration error.

Check an existing interaction NPC at its authored location and its configured target distance. During maintenance, check that interactions return after a planned target-provider restart. With LB Phone, check the existing Dispatch app after the phone starts again and with a newly connected player. On a supported garage/key setup, check an awarded vehicle's ownership and key access. Where citizen numbers are displayed, confirm the same person's number remains stable after reconnecting. Keep your existing providers if you do not use the new optional integrations.

1. Back up and stop the server

These steps update sky_base from 1.51.0 to 1.51.1. Complete the earlier update instructions first if your installed version is older.

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

2. Install the matching files

1. Delete the installed source/ folder and copy the complete new source/ folder into its place, including all interface files.
2. Replace fxmanifest.lua from the same download.
3. Replace the complete config/locales/ folder. Transfer only your custom wording into matching new entries; keep every supplied key and language file.
4. Replace config/integration/phone/gks.lua. Compare any custom edits with the new adapter before reapplying them; keep the new version's notification handling.

3. Keep settings and apply the required configuration

Keep your existing config/config.lua, framework selection and providers. This patch adds no configuration value. Base settings remain file-based; /jobconfig does not manage them.

If you use GKS, retain your working phone = "gks" or automatic provider selection. The adapter chooses the available GKS notification interface; no switch between legacy and V2 is required in Base. Other phone providers need no configuration change.

4. Preserve data, items and assets

No SQL import, inventory item, image, streamed asset or provider replacement is required. Preserve your database and all existing account and phone records.

5. Start and check the result

Start the database connector, framework and configured providers before sky_base 1.51.1, then start Jobs Base and installed consumers. Reconnect players after the server starts.

With GKS, trigger an existing app notification and confirm that it appears once with its normal title, message and icon. Keep your current phone version. Check that existing job and phone features still open normally.

1. Back up and stop the server

These steps update sky_base from 1.50.0 to 1.51.0. Complete earlier update instructions first if your installed version is older.

1. Download and extract sky_base 1.51.0 on your computer.
2. Back up the complete installed sky_base folder and your game database. Keep a separate copy of custom translations and edited provider adapters.
3. Stop the server before replacing files.

If you use the updated workplace-object editors, install the matching current sky_jobs_base 1.54.0 download with this Base package. If Creator is installed, use the matching current sky_jobcreator 1.0.0 package too. Take these downloads together; do not combine new editor files with an older saved Base or Jobs Base archive.

2. Install the matching files

Use files from the same 1.51.0 download throughout. All paths below are inside the installed sky_base folder.

1. Delete the old source/ folder and copy the complete new source/ folder into its place, including its interface files.
2. Replace fxmanifest.lua with the new file.
3. Replace the complete config/locales/ folder. Copy only your custom wording into the matching entries in the new language files; retain all bundled keys.
4. Replace config/framework/esx.lua, config/framework/qb.lua and config/framework/qbox.lua.
5. In config/integration/banking/, replace devmosaic.lua, esx.lua, okok.lua, oxlyn.lua and qb.lua, then add the new ars.lua.
6. Replace config/integration/inventory/ox.lua. In config/integration/target/, replace _init.lua and add g_interact.lua.
7. In config/integration/phone/, replace 17mov.lua, codem.lua, custom.lua, esx.lua, gks.lua, lb.lua, npwd.lua, okok.lua, qb.lua, qs.lua, roadphone.lua, sd.lua, sky_phone.lua and yseries.lua.

Compare any custom adapter edits with these new versions before reapplying them. Do not restore an entire old adapter over the new file.

3. Keep settings and configure optional features

Keep your existing settings. config/config.lua changes only the comment lists beside banking and target; it adds no required value or new configuration block. Base settings remain file-based, and /jobconfig does not manage them. The default target = "none" still uses the normal marker and help notification.

Optional — ARS Banking: install and configure ars_banking, then start it before Base. Open sky_base/config/config.lua, find the existing banking entry and change its value to "ars". A working "auto" selection can detect the started provider. Keep useSkyBankingFallback = false if ARS is your only company ledger. Do not change your banking provider if you are keeping your existing setup.

If you already use Oxlyn: open your installed oxlyn-banking configuration and confirm Config.Business.enabled is enabled. Keep the existing Config.Business.accountSource and existing company balances. In Base, keep banking = "oxlyn" or your working "auto" selection. The integration now uses Oxlyn's own company and personal-bank operations; no account transfer is required.

Optional — g-interact: install and start g-interact before Base. In sky_base/config/config.lua, find target = "none" or your existing target selection and change only its value to "g-interact". Keep "none" for normal marker interactions. If several target or banking providers are running, set the provider you want explicitly instead of relying on "auto".

The new phone-directory support needs no new setting. Keep the phone provider you already use. Phones that expose only online numbers still return only online characters; this update does not add offline storage to those providers.

No new Base setting is required for the updated existing-object editor. Keep your current configuration. Existing workplace props and saved placements do not need resetting or replacing to install this support.

4. Database, items and assets

No new Base database schema, inventory item, image or streamed asset is required. Do not reimport Base SQL or clear existing account tables.

For native okokBanking societies, keep the provider's installed SQL and start okokBanking before Base. Supported job setup can now create a missing job account with zero funds in the existing society table. Existing account balances, names and IBANs remain intact. If your okok setup stores society money in ESX addonaccount instead, keep banking = "esx"; selecting okokBilling alone does not require changing the bank provider. A provider-table or duplicate-account error needs that specific configuration corrected, not a database reset.

The phone integration reads each supported provider's existing records. Do not import a new phone schema or move SIM ownership to apply this update.

5. Start and check the result

Start the database connector, framework and the providers you use first, then sky_base 1.51.0, then Jobs Base and installed consumers. For this shared update, install sky_jobs_base 1.54.0 if you use the Sky jobs and start it after Base.

Confirm Base reports 1.51.0 without startup errors. With your actual provider, check one company balance and a small payment or refund. If you enabled g-interact, confirm an interaction appears and works. On ESX, switch characters and confirm the previous character's job state clears. With ox_inventory, check a weapon list in the installed feature that uses it. Keep the backups until these checks pass.

If you use the matching Jobs Base or Creator object editor, check one saved bell or workplace object through that resource's update guide. Use the complete current matching packages before evaluating placement.

1. Back up and stop the server

These steps update sky_base from 1.49.0 to 1.50.0. Complete earlier update instructions first if you are on an older release.

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

2. Install the matching files

Use files from the same 1.50.0 download throughout. Paths below are inside your installed sky_base folder.

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

Replace config/integration/banking/qb.lua, config/integration/inventory/native/esx.lua, config/integration/vehiclekeys/server/_init.lua and config/integration/vehiclekeys/server/qb.lua. Copy the new config/integration/inventory/client/holster.lua and config/integration/vehiclekeys/tgiann.lua to those exact paths. Refresh config/README.md. Retain custom adapter changes from your backup only after comparing them with these new versions.

Replace config/integration/helpnotify/default.lua with its matching new version. Keep your chosen help provider and compare any custom adapter edits with the new file before restoring them.

3. Keep settings and configure optional features

Keep your existing settings. This update changes no executable default in config/config.lua. Base settings are edited in files; /jobconfig does not manage them.

If you use ox_inventory, open sky_base/config/config.lua, find the existing inventory entry and use inventory = "ox" or your working "auto" selection. "ox_inventory" is not a supported selector value. Keep the provider you already use if it is valid.

Optional — Tgiann Hotwire: start tgiann-hotwire before Base. In the same file, find vehiclekeys = "auto"; retain "auto" for detection or replace its value with "tgiann" for an explicit selection. Keep every other setting. Restart the complete server after changing the selector. Existing physical keys remain valid; Tgiann does not provide a key-removal operation, so removing a Sky key grant does not remove those inventory or ignition keys.

4. Database, items and assets

No new database schema, inventory item, image or streamed asset is required. Do not rename, recreate or clear society accounts to apply the banking correction; existing balances must remain.

On QB/Qbox, a Creator catalogue conflict now identifies the affected group in the console and leaves that group’s conflicting records unchanged while restoring the rest. If reported, keep the database backup and resolve that specific stale definition or deletion marker with support; do not reset all jobs.

5. Start and check the result

Start the database connector, framework and selected providers before sky_base 1.50.0; start Jobs Base and installed consumers afterward. Confirm the Base version and inspect the first startup error before opening the server.

Check a company balance/payment with your selected banking provider, an item with slot metadata and the vehicle-key provider you actually use. For Creator installations, confirm existing jobs and account balances still load. If using DJ announcements, check speaker coverage and normal voice range after ending an announcement.

1. Back up and stop the server

Update sky_base from 1.48.0 to 1.49.0. If you are on an older version, complete its earlier update instructions first.

1. Download 1.49.0 and extract the ZIP on your computer.
2. Back up your installed sky_base folder, the other resources being updated and your game database. Keep the backup outside the server's resources folder.
3. Stop the whole server in txAdmin or your hosting panel. Complete the other installed Sky updates before starting it again.

2. Copy the matching files

Open the installed sky_base folder and the extracted 1.49.0 folder side by side.

1. Delete the installed source/ folder and copy the complete new source/ folder into its place.
2. Replace fxmanifest.lua with the file from the same download.
3. Replace the complete config/locales/ folder. If you edited translations, copy your own wording from the backup into the matching new entries; keep all new keys.
4. Replace config/framework/esx.lua, qb.lua and qbox.lua with the matching new files. If you edited an adapter, start from its new file and transfer only your own changes from the backup.
5. Copy every file under config/integration/ listed in Changed Files to the same installed path, including the new medical/custom.lua, medical/none.lua, medical/visn_are.lua, phone/none.lua, phone/npwd.lua and vehiclekeys/none.lua. For a customized adapter, start from the downloaded file and transfer your custom provider calls into it. Keep the downloaded loading guards and result handling, including the updated banking/qb.lua and voice adapters. Copying the entire old adapter back would discard the fixes.
6. Keep your existing config/config.lua and all other unchanged configuration files. The settings step explains the optional new provider choices.

3. Keep your settings and review optional provider choices

All Base settings are file-based. /jobconfig does not manage them.

Open sky_base/config/config.lua. Keep your current framework, language and provider values. This release adds the optional medical selector; the other edits to this file update provider-list comments. Keep your configuration instead of replacing it wholesale.

New medical selector: inside the existing Config = { ... } table, find weather = .... Immediately after that line, add this entry if medical is missing:

medical = "auto",

Keep an existing medical entry instead of adding a duplicate. "auto" selects a started visn_are resource when Base starts, otherwise "none"; an older configuration without this entry also uses that automatic fallback. Set medical = "none", if you deliberately want no external injury-buffer reset. To select VISN ARE explicitly, use medical = "visn_are", and start visn_are before Base in server.cfg. Keep your existing revival resource in charge of reviving players. This adapter lets compatible consumers reset the external injury buffer after revival; it does not replace that medical resource. Unknown values fail startup, and an explicitly selected but stopped VISN ARE resource reports an error when a reset is requested. Choose "custom" only after implementing sky_base/config/integration/medical/custom.lua; the supplied template deliberately reports that it is not implemented.

Optional — NPWD: find phone = ... inside Config = { ... }. With phone = "auto",, start npwd and its framework bridge before Base; automatic detection can then select it. To select it explicitly, replace only that value with phone = "npwd",. This integration reads phone numbers; number changes, custom phone apps and call control are not supplied by NPWD's supported integration.

Optional — no external phone or key system: replace the existing phone value with phone = "none", and/or the existing vehiclekeys value with vehiclekeys = "none",. Keeping "auto" also selects these fallbacks when no matching provider is started. Do not add duplicate entries.

Only for a custom integration you wrote: update your customized files against the downloaded templates at the same paths, especially config/integration/banking/custom.lua, config/integration/license/custom.lua and config/integration/progress/custom.lua. Keep your existing selected provider. Banking must supply its read-only account probe; license methods are now bound directly by the selected adapter. Finish this integration comparison before starting the server.

Optional — announcement consumers: keep your existing voice selection. Compatible pma-voice microphone/announcement resources can use the new scoped announcement support; Base adds no new announcement setting to config/config.lua. Start pma-voice before Base. SaltyChat and YACA do not provide this announcement API, so installing Base does not require changing your voice provider. If you enable an announcement consumer, avoid combining it with another script that replaces pma's proximity-check function: this integration restores pma's standard check when cleared.

Only for developers integrating announcements or medical resets: the client call Sky.Voice.SetAnnouncementOverride(scopeId, range) accepts 1–300 metres with pma-voice. The consumer must check its result, keep ownership of its scope and call Sky.Voice.ClearProximityOverride(scopeId) when it finishes or stops. This controls recipients around the speaking player; microphone capture and speaker-position audio remain the consumer's responsibility. A medical owner can call Sky.Functions.ResetMedicalState() after completing its own revive; the VISN event dispatch is not a vendor-completion acknowledgement.

QB banking: keep your current banking provider and company-account names, with qb-banking started before Base when it is the selected backend. The corrected adapter confirms the provider's successful affected-row response and checks the balance before withdrawals. Legacy codem-bank automatic detection on QBCore also uses the QB bridge; the CodeM name alone does not identify every installed backend. No balance reset, account migration, retry or automatic release of old orders is included. For an existing order stuck in paying, have the owner or support compare the bank's ledger with that order before reconciling it. Do not blindly retry or refund a payment whose outcome is uncertain.

4. Preserve database, items and assets

No new Base SQL, item registration, inventory images or streamed models are required from 1.48.0 to 1.49.0. Keep all existing accounts, items and licenses. This update does not require deleting or resetting data.

If you are also updating Jobs Base, complete its separate database step. On older native ESX versions without runtime item-registration support, new item definitions still require the framework's normal database setup and a full server restart; this Base update does not change that requirement.

5. Start and check the server

1. Start the framework, database connector and your selected providers first. Keep ensure sky_base before ensure sky_jobs_base and your installed Sky scripts in server.cfg.
2. Start the server and check that Base reports 1.49.0. If updating Jobs Base too, use 1.52.0 and finish its update instructions before reopening the server.
3. Check the first startup/database error before continuing, then reconnect.
4. Test the inventory, license actions, company banking and vehicle keys used on your server. For QB/Qbox, check ownership with the character who actually owns the vehicle. If using NPWD, check that the loaded character's phone number is available.
5. If you use the QB banking bridge, make one small new company payment and check that the order completes and the account is debited once. Keep historical uncertain payments for ledger reconciliation rather than using them as a repeat-payment test.
6. If a compatible resource uses the VISN reset bridge, complete its normal revive flow and check the player's injury state and UI. If you use pma announcements, test an announcement with another player in range, then confirm normal voice proximity returns when it ends. These optional integrations need acceptance with your actual provider and connected players.

Keep the backup until these checks pass.

1. Back up and stop the server

These steps update sky_base from 1.47.0 to 1.48.0. If you are on an older version, complete its earlier update steps first.

1. Download 1.48.0 and extract the ZIP on your computer.
2. Make a full backup of your server files and game database. Also keep a separate copy of the installed sky_base folder.
3. Stop the server before replacing files. Put away equipped custom weapons first. Keep the backup until the update has been checked.

If you also install one of the job updates, complete its Jobs Base and job-specific instructions before restarting.

2. Copy the new files

Use the files from the 1.48.0 download throughout these steps. All paths below are inside your installed sky_base folder.

1. Delete the old source/ folder. Copy the complete new source/ folder into its place, including its interface files.
2. Replace fxmanifest.lua with the file from the same download.
3. Replace the complete config/locales/ folder with the new one. If you changed any wording, open the backed-up language file beside the new file and copy your edited text into the matching entries. Keep the new translation keys and folders.
4. Keep your existing config/config.lua; make only the settings changes described in step 3 below. Do not overwrite your configured jobs or locations with the download's defaults.

Copy the changed files under config/framework/ and config/integration/ shown in Changed Files to the same paths in your installed resource. Include the new config/integration/weather/ folder. If you have customized any of these adapters, use the adapter instructions in step 3 before replacing them.

3. Check your settings

Base settings are changed in files, not in /jobconfig.

1. Open your installed sky_base/config/config.lua. Keep your framework, inventory, banking and other existing selections. Keep your chosen locale; the new English default does not require changing a German server to English.
2. Find the existing Config = { table. Add the following line inside that table, for example directly below the fuel = ... line. Keep the comma at the end. If weather already exists, edit that entry instead of adding a second one.

weather = "auto",

3. Save the file. Start your weather resource before Base. Automatic selection checks CD EasyTime, Renewed, ESX Weather, QB WeatherSync, WeatherSync, then native weather.

Only if using QB WeatherSync or CD EasyTime with local weather: complete the provider changes in Weather integrations. Adding sky_weather_pause '1' alone does not install those changes.

Only if you customized a provider adapter: open your backed-up adapter beside the new file at the same path. Use the new file as the starting point and transfer only your own integration changes. Do not restore the entire old adapter, because that would remove this update's fixes. Leave the existing inventory selection in place for SMX; there is no new "smx" selector.

Only if a custom integration used the old Activities weather settings: follow the same weather guide to move the provider choice to Base. A custom provider also needs its implementation in config/integration/weather/custom.lua. Ordinary servers do not need to create this integration.

4. Update database, items and models

Nothing to import for Base. This version needs no new SQL, inventory items or models. Keep your database and provider account configuration. Follow the separate Jobs Base database step if you are also updating Jobs Base.

5. Start the server and check

1. Finish the file copies, required Lua edits and database steps, then start the server. Start the framework, database connector and your selected inventory/weather/phone/banking/voice/key providers first. Start sky_base 1.48.0, then sky_jobs_base 1.51.0, then the installed jobs. Wait for database updates to complete. If used together, start DOJ 0.6.0 before Police 1.40.0, and Ambulance 2.47.0 before Crime 0.11.0.
2. Check the server console for startup or database errors. If an error appears, resolve the first error before testing further. Check that this resource reports version 1.48.0.
3. Reconnect so the new interface and models load. If step 3 listed in-game settings, open the named configurator, make those changes and save. Then check your saved jobs and the features you use before reopening the server to everyone.

What to check for this resource: Open a job tablet and check your radio key. Test the inventory, bank and vehicle keys used on your server. If using local weather, check that it returns to normal when the activity ends.

1. Prepare

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

2. Replace files

Use the complete 1.47.0 customer package. Delete the entire sky_base/source/ folder and insert the new one, then replace sky_base/fxmanifest.lua from that same download. Refresh the complete sky_base/config/locales/ tree and merge your translations while keeping your chosen language.

Merge config/config.lua, add config/qb_money.lua, and update every supplied framework, banking, billing, inventory, license, phone and server vehicle-key adapter listed in Changed Files. Install the new config/integration/phone/_init.lua, client Sky Phone adapter and all three server vehicle-key files. Preserve deliberate custom integration branches and schema mappings, while retaining the supplied fixes.

Use the source folder and manifest together even when diagnostics are disabled. If an older profiler package changed files outside source/, restore those files from the current package once and reapply your own settings; future profiler-only updates change only source Lua and the manifest.

3. Merge settings

All Base settings remain file-based. /jobconfig manages none of the Base language, provider, currency or dirty-money values.

Language: In sky_base/config/config.lua, Config.locale changes from the old shipped "en" to "de". Keep "en" or another supported language if that is your server's choice; Sky job resources that inherit Base's locale use this shared selection. Treasure Hunt keeps its own Config.Locale choice.

QBCore dirty money: Add the complete new sky_base/config/qb_money.lua file; it did not exist previously:

Config.QBBlackMoney = {
    mode = "account",
    item = "black_money",
    worthKey = "worth",
}

The previous QB adapter's editable choices were black_money_mode = "account", black_money_item = "markedbills" and black_money_worth_key = "worth"; move any custom choices to the new Config.QBBlackMoney.mode, .item and .worthKey fields. The new default mode = "account" retains QB's existing black-money account and does not require an inventory item. Optional mode = "item" counts one configured item as one dollar; register that exact item in your selected inventory first. Optional mode = "markedbills" requires item = "markedbills", worthKey = "worth" and the provider's unique bags with worth metadata. These modes are alternatives: balances are not combined, and switching modes does not convert old money. Qbox's separate handling is unchanged.

Society banking: Config.banking = "auto" is unchanged; this release adds explanatory comments, not a new default. If your society balances belong to okok's own society tables, select Config.banking = "okok" and start okokBanking before Base. If okok uses ESX addon accounts (UseAddonAccount = true or SocietyResource = "esx_addonaccount"), select Config.banking = "esx" and start the loaded shared-account provider before Base. Configured job accounts must already exist. Automatic detection follows started resources and cannot inspect private okok account ownership. Keep existing balances and provider SQL. Config.billing = "okok" can remain independent of the society banking selection.

Licenses and optional providers: Config.license = "auto" and the existing Config.Licenses.catalog default { { type = "firstaidcourse", label = "First Aid Course" } } remain unchanged; CodeStudio guidance is comment-only. When using CodeStudio, start cs_license first, prepare its vendor card templates and inventory items, and use their exact item names in the catalogue and any first-aid license setting. Job badges use the job name. No mandatory new Sky item is introduced. Keep your current inventory, key and other provider selections; start the selected providers before Base. Custom frameworks can supply character height through the updated custom bridge; a framework without stored height leaves it unavailable.

Sky Phone: Number changes need a matching Phone package that exposes both number-change and number-validation support. The current matching Phone implementation is 1.1.7; do not assume an older package supports these actions from its version number alone. Phone is maintained separately from this release set. Update all three supplied Sky Phone/common phone adapters together.

Reward compatibility: Treasure Hunt 1.1.0 event claims require Base 1.47.0 so a rejected item/weapon grant is returned to the claim workflow. This change adds no new reward setting.

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

4. Database, items and assets

SQL: This Base update adds no table, column or manual SQL migration. Keep the existing schema and migration policy; the improved inspection remains part of normal startup.

Items and images: No new mandatory inventory item or image is added. Only the optional QBCore item/marked-bill mode and optional CodeStudio provider setup require the matching existing/custom inventory definitions described in the settings step. This update does not convert dirty-money balances or create society accounts.

Assets and permissions: No new Base streamed model, map or permission migration is required. Existing configured interaction objects continue to use their own GTA/custom models. Preserve job records, balances and stored grants.

5. Restart and check

Perform a full server restart to load the new manifest/file lists, then reconnect clients. Start the framework, database connector and selected inventory, keys, license, phone, banking and UI providers first, then Base 1.47.0, then Jobs Base 1.50.0 and wait for successful initialization. Start DOJ 0.5.0 before Police 1.39.0 for shared catalogue and court features, and Ambulance 2.46.0 before Crime 0.10.0 when using their medical integration. Mechanic 1.36.0 and Fire 1.18.0 follow both libraries. Treasure Hunt 1.1.0 and Pets 1.1.0 follow Base and their own listed dependencies. Install and start only resources you use. Check actual installed versions, successful Jobs Base initialization and the first startup/database error before gameplay checks.

On staging, test login and identity height if stored, the selected inventory and any live item registration. On QBCore, test the selected dirty-money mode, including multiple slots where relevant, and confirm that a rejected item or weapon reward does not appear successful, without altering real balances to force a test. With CodeStudio, verify license issuance, removal and an offline character; verify the actual vendor item/template names. With supported QB/Jaksam keys, verify grant/removal and provider restart behavior.

If using Sky Phone, test an allowed number change and reject a taken/reserved number before charging. Check the resulting SIM/device number and payment; a changed display alone is insufficient. With okok/ESX society banking, check the actual existing account, debit/credit and player balance. With external billing, verify the rejection display and the provider's actual paid state; invoice submission alone does not establish settlement. For configured props, check ground placement, full rotation and removal when the location or owner stops. Investigate unknown banking or billing outcomes before retrying; do not reset balances or jobs.

1. Prepare

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

2. Replace files

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

Merge config/config.lua, update the supplied ESX/QB/Qbox framework bridges, config/vehicle_storage.lua, and the supplied inventory, phone and built-in help adapters listed above. Add the new banking, progress, notification, help and client-phone adapters from this package. Preserve deliberate schema mappings and custom providers, but keep updated supplied adapter logic.

Merge the updated supplied config/functions.lua, including the Sky Ambulance branch of Functions.IsPlayerDead, while preserving intentional custom integration branches.

3. Merge settings

Base remains file-based; /jobconfig does not manage Base provider selection. No existing default is changed: Config.progressbar = "auto", Config.notification = "default", Config.helpnotify = "default" and Config.banking = "auto" remain. New choices include Config.progressbar = "lation_ui", Config.progressbar = "ZSX_UIV2" and Config.banking = "codem-supreme-banking". ZSX notification choices are "ZSX_UIV2" and "ZSX_UIV2_default"; help choices are "ZSX_UIV2" and "ZSX_UIV2_help". Keep intentional provider selections; automatic detection can select a newly started supported provider. For example, add these assignments after the existing Config table if selecting ZSX:

Config.progressbar = "ZSX_UIV2"
Config.notification = "ZSX_UIV2"
Config.helpnotify = "ZSX_UIV2"

Start the selected provider before Base. Installing an optional provider is unnecessary when retaining another supported selection. ZSX supports player cancellation; do not assume a programmatic stop export. Phone call observation depends on the selected provider's actual call API; configured dispatch access alone does not establish call acceptance. Retain existing phone configuration. Install Mechanic 1.35.0 together with Base 1.46.0 for the Qbox initial-property save correction. Valid saved vehicle properties remain intact; malformed nonempty data needs its original error corrected.

When merging a custom config/functions.lua, update only the existing elseif GetResourceState("sky_ambulancejob") == "started" then branch in Functions.IsPlayerDead. Replace:

return exports["sky_ambulancejob"]:isDead()

with:

return Sky.FW.GetPlayerState("skyAmbulanceDead") == true

Keep the surrounding framework checks and intentional custom/provider branches. Leaving the old return retains the export dependency. No new setting or default is introduced.

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

4. Database, items and assets

SQL: No new Base table or column and no manual SQL change. Keep your existing schema and automatic/manual migration policy. Items: No new item definitions or registrations. Assets: No new inventory images or streamed models; optional location props use configured existing GTA/custom models, whose own resource must be installed. Do not clear working vehicle records or saved jobs to activate a fix.

5. Restart and check

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

Check login, native job/gang updates and the selected inventory/provider. If using ZSX or Lation, test progress completion and cancellation; check notifications and help for ZSX. With an integrated phone, place and accept a test service call and confirm that its dispatch entry follows the real call. On Qbox, test tuning and garage retrieval on an already-owned vehicle with naturally empty properties, retaining plate, fuel and damage. Do not empty a valid record to force this path. Optional props must disappear when their location is removed or the owner stops. Callback diagnostics observe requests; stopping the recording does not cancel the request.

With Sky Ambulance installed, check interaction blocking while the staging character is alive and dead, and inspect the first error if its death state is unavailable. If support needs startup evidence, run sky_deathdiagnose in both F8 and the server console. It reports resource versions/states and Jobs Base readiness; the client also distinguishes unavailable Ambulance exports from valid false/nil results. It does not restart resources or revive a player.

1. Prepare

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

2. Replace files

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

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

Merge the provider choices in sky_base/config/config.lua and update the supplied framework bridges sky_base/config/framework/esx.lua, sky_base/config/framework/qb.lua and sky_base/config/framework/qbox.lua. Update sky_base/config/vehicle_storage.lua, preserving intentional garage schema mappings. Add the three supplied ZSX_UIV2.lua adapters under config/integration/progress/, notification/ and helpnotify/. Keep deliberate custom integrations; do not restore an older supplied bridge or storage implementation over these updates.

3. Merge settings

Base settings remain file-based in sky_base/config/config.lua; /jobconfig does not manage them. No existing key or shipped default is changed. The existing defaults remain Config.progressbar = "auto", Config.notification = "default" and Config.helpnotify = "default". Keep your intentional selections.

New supported choices: Config.progressbar = "ZSX_UIV2" for progress bars; Config.notification = "ZSX_UIV2" for notifications or "ZSX_UIV2_default" for above-minimap notifications; Config.helpnotify = "ZSX_UIV2" for TextUI prompts or "ZSX_UIV2_help" for top-left help notifications. These names are case-sensitive. For all three standard ZSX views, put these assignments after your existing Config = { ... } table in this file, preserving its other values:

Config.progressbar = "ZSX_UIV2"
Config.notification = "ZSX_UIV2"
Config.helpnotify = "ZSX_UIV2"

Start the installed ZSX_UIV2 provider before Base when selecting it. Existing progress auto selection can now detect a started ZSX provider; notification and help defaults still use Sky's built-in views. No provider installation is required if you keep another supported selection. ZSX supports player cancellation; do not assume it provides a programmatic stop export.

Keep saved job configuration, jobs, grades and locations. No configurator import or reset is required. Install the refreshed Mechanic 1.34.1 with this refreshed Base package for the Qbox first-save correction. This preserves existing vehicle ownership and stored properties; it does not repair malformed nonempty property data.

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

4. Database, items and assets

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

5. Restart and check

Perform a full server restart after replacement so the changed manifests and file lists are reloaded. Start the framework, database connector and selected providers first, then Base 1.45.1, Jobs Base 1.48.1 and the installed consumers. Unrelated clothing, vehicle and map packs can remain after Sky in server.cfg. Reconnect clients. Check normal login and the first Base and job startup messages. A long dependency wait now continues until initialization completes; it no longer aborts at 60 seconds. Database migration warnings remain actionable, and failure to read saved settings remains a visible initialization error. Collect the first error, preceding lines and actual installed versions if a feature remains unavailable. If ZSX is selected, check its progress completion and player cancellation, notifications and help prompts. On staging, check a permitted faction invitation and confirm the resulting job. On Qbox, complete and save tuning on an already-owned vehicle with naturally empty properties, then store and retrieve it through your configured garage. Keep the existing plate, fuel and damage data; do not clear a working record to trigger this path. Callback tracing is opt-in support observation; stopping a trace does not cancel the underlying request.

1. Prepare

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

2. Replace files

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

• sky_base/config/config.lua
• sky_base/config/framework/compatibility/hex.lua
• sky_base/config/framework/custom.lua
• sky_base/config/framework/esx.lua
• sky_base/config/framework/qb.lua
• sky_base/config/framework/qbox.lua
• sky_base/config/framework/vrp.lua
• sky_base/config/integration/banking/_init.lua
• sky_base/config/integration/banking/esx.lua
• sky_base/config/integration/banking/jaksam.lua
• sky_base/config/integration/banking/qb.lua
• sky_base/config/integration/banking/renewed.lua
• sky_base/config/integration/banking/sky.lua
• sky_base/config/integration/billing/codemv2.lua
• sky_base/config/integration/billing/hex.lua
• sky_base/config/integration/billing/sky.lua
• sky_base/config/integration/inventory/codem.lua
• sky_base/config/integration/inventory/codemv2.lua
• sky_base/config/integration/inventory/jaksam.lua
• sky_base/config/integration/inventory/native/esx.lua
• sky_base/config/integration/inventory/native/qb.lua
• sky_base/config/integration/inventory/native/qbox.lua
• sky_base/config/integration/inventory/native/vrp.lua
• sky_base/config/integration/inventory/one.lua
• sky_base/config/integration/inventory/origen.lua
• sky_base/config/integration/inventory/ox.lua
• sky_base/config/integration/inventory/ps.lua
• sky_base/config/integration/inventory/qs.lua
• sky_base/config/integration/inventory/tgiann.lua
• sky_base/config/integration/phone/codem.lua
• sky_base/config/integration/phone/sky_phone.lua
• sky_base/config/integration/phone/yseries.lua
• sky_base/config/locales/*
• sky_base/fxmanifest.lua
• sky_base/import.sql
• sky_base/source/* — delete and reinsert

3. Merge configuration

All Base settings are maintained in files. /jobconfig does not manage Base settings, providers or diagnostic options.

In sky_base/config/config.lua, the shipped default Config.billing changes from "auto" to "sky":

-- Previous shipped value
billing = "auto",
-- New shipped value
billing = "sky",

Sky Billing requires the matching Jobs Base 1.48.0 release and uses its central invoice storage. If you want to keep an external billing provider, retain its explicit provider value instead of replacing it with "sky". The added provider names in the adjacent comment are documentation changes, not new runtime configuration values or an automatic invoice import.

Also add the new startup option Config.hideCallbackEventNames beside Config.defaultCallbackTimeout in the same table:

-- Previous release: this option did not exist.
hideCallbackEventNames = true,

The default keeps callback names hidden in network event names. Set it to false only when you want callback names included for network diagnostics. Changing it requires a full server restart and clients to reconnect. It does not start a profiler recording. Config.defaultCallbackTimeout remains 300000; its value has not changed in this release.

Replace the updated framework and provider adapters from the same download, then port your own adaptations into the new copies. Do not restore complete old adapter files over the new ones. The executable adapter updates are in sky_base/config/framework/custom.lua, esx.lua, qb.lua, qbox.lua, vrp.lua and the new config/framework/compatibility/hex.lua; banking _init.lua, esx.lua, jaksam.lua, qb.lua, renewed.lua, sky.lua; billing codemv2.lua, hex.lua and new sky.lua; inventory codem.lua, codemv2.lua, jaksam.lua, native/esx.lua, native/qb.lua, native/qbox.lua, native/vrp.lua, one.lua, origen.lua, ox.lua, ps.lua, qs.lua, tgiann.lua; and phone codem.lua, sky_phone.lua, yseries.lua. These files contain provider code updates, not additional user option migrations. sky_base/config/init.lua, sv_config.lua and sv_functions.lua have no net release change.

Update all sky_base/config/locales/* from the download. Keep the existing global language selection and merge your custom translations into the refreshed locale files.

The additional adapter and item-catalog changes add no further Base configuration values or Job Configurator settings. Replace the updated config/framework/esx.lua, qb.lua and qbox.lua adapters and reapply your own provider modifications to the new files; their job administration implementation now ships inside the resource. Replace config/integration/billing/hex.lua as well. For Hex billing, keep Config.billing = "hex" only if you use that provider and ensure hex_jobscreator is started before sky_base, then sky_jobs_base is initialized before invoices are issued. The issuing player must have a cached job; the account name no longer selects the Hex job. For example, an issuer with job lspd and account society_police now bills through lspd. System issuers without a player job remain unsupported. These changes introduce no new provider parameters. Restart the updated Base and Jobs Base resources together using the existing dependency order and reconnect clients after Base is replaced.

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

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

4. Data, items and dependencies

SQL: Back up the active database before the release update. Base performs its own startup migrations for shared job definitions, the durable managed-job registry and private Creator log preferences. The Jobs Base Config.AutoExecuteQuery switch does not control these Base migrations. The new sky_base/import.sql is an optional additive manual schema mirror; a successful automatic setup does not need a duplicate manual import.

For a database team applying the Base schema mirror manually, the exact new file contains the following DDL. It creates missing definition/registry/log tables and adds missing registry or log fields; it does not import vendor jobs, members, invoices or balances. Existing ESX job tables are retained, while QB/Qbox receive the minimal shared job-definition projection. Creator owns its extended schema and compatibility setup separately.

-- Optional manual mirror of the automatically migrated durable framework registry.
-- Inherit the active database character set and collation; retain existing definitions.
-- Common ESX-shaped definition projection for QBCore/Qbox. These are the existing
-- native tables on ESX; never replace rows belonging to another creator.
CREATE TABLE IF NOT EXISTS `jobs` (
    `name` VARCHAR(50) NOT NULL,
    `label` VARCHAR(100) NULL,
    PRIMARY KEY (`name`)
) ENGINE=InnoDB;

CREATE TABLE IF NOT EXISTS `job_grades` (
    `id` INT NOT NULL AUTO_INCREMENT,
    `job_name` VARCHAR(50) NULL,
    `grade` INT NOT NULL,
    `name` VARCHAR(50) NOT NULL,
    `label` VARCHAR(100) NOT NULL,
    `salary` INT NOT NULL,
    `skin_male` LONGTEXT NULL,
    `skin_female` LONGTEXT NULL,
    PRIMARY KEY (`id`),
    INDEX `idx_sky_job_grades_level` (`job_name`,`grade`)
) ENGINE=InnoDB;

SET @sky_managed_migration = IF(
    (SELECT COUNT(*) FROM INFORMATION_SCHEMA.COLUMNS WHERE TABLE_SCHEMA = DATABASE()
        AND TABLE_NAME = 'job_grades' AND COLUMN_NAME = 'skin_male') = 0,
    'ALTER TABLE `job_grades` ADD COLUMN `skin_male` LONGTEXT NULL', 'SELECT 1');
PREPARE sky_managed_migration FROM @sky_managed_migration;
EXECUTE sky_managed_migration;
DEALLOCATE PREPARE sky_managed_migration;

SET @sky_managed_migration = IF(
    (SELECT COUNT(*) FROM INFORMATION_SCHEMA.COLUMNS WHERE TABLE_SCHEMA = DATABASE()
        AND TABLE_NAME = 'job_grades' AND COLUMN_NAME = 'skin_female') = 0,
    'ALTER TABLE `job_grades` ADD COLUMN `skin_female` LONGTEXT NULL', 'SELECT 1');
PREPARE sky_managed_migration FROM @sky_managed_migration;
EXECUTE sky_managed_migration;
DEALLOCATE PREPARE sky_managed_migration;

CREATE TABLE IF NOT EXISTS `sky_managed_job_definitions` (
    `job_name` VARCHAR(64) NOT NULL,
    `owner` VARCHAR(64) NOT NULL,
    `origin` VARCHAR(16) NOT NULL,
    `definition` LONGTEXT NOT NULL,
    `baseline` LONGTEXT NOT NULL,
    `status` VARCHAR(16) NOT NULL DEFAULT 'pending',
    `last_error` TEXT NULL,
    `activation_stage` VARCHAR(32) NULL,
    `error_code` VARCHAR(64) NULL,
    `account_attempted` TINYINT(1) NULL,
    `member_updates` LONGTEXT NULL,
    `rename_state` LONGTEXT NULL,
    `updated_at` TIMESTAMP NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,
    PRIMARY KEY (`job_name`),
    INDEX `idx_managed_owner` (`owner`)
) ENGINE=InnoDB;

SET @sky_managed_migration = IF(
    (SELECT DATA_TYPE = 'varchar' AND CHARACTER_MAXIMUM_LENGTH = 50 FROM INFORMATION_SCHEMA.COLUMNS
        WHERE TABLE_SCHEMA = DATABASE() AND TABLE_NAME = 'sky_managed_job_definitions' AND COLUMN_NAME = 'job_name'),
    'ALTER TABLE `sky_managed_job_definitions` MODIFY `job_name` VARCHAR(64) NOT NULL', 'SELECT 1');
PREPARE sky_managed_migration FROM @sky_managed_migration;
EXECUTE sky_managed_migration;
DEALLOCATE PREPARE sky_managed_migration;

-- Private server-only override for the existing Creator audit route.
CREATE TABLE IF NOT EXISTS `sky_creator_log_settings` (
    `channel` VARCHAR(64) NOT NULL,
    `revision` BIGINT UNSIGNED NOT NULL DEFAULT 0,
    `enabled` TINYINT(1) NOT NULL DEFAULT 1,
    `webhook_mode` VARCHAR(8) NOT NULL DEFAULT 'default',
    `webhook_url` VARCHAR(2048) NOT NULL DEFAULT '',
    `routes` LONGTEXT NULL,
    PRIMARY KEY (`channel`)
) ENGINE=InnoDB;

SET @sky_creator_log_migration = IF(
    (SELECT COUNT(*) FROM INFORMATION_SCHEMA.COLUMNS WHERE TABLE_SCHEMA = DATABASE()
        AND TABLE_NAME = 'sky_creator_log_settings' AND COLUMN_NAME = 'routes') = 0,
    'ALTER TABLE `sky_creator_log_settings` ADD COLUMN `routes` LONGTEXT NULL', 'SELECT 1');
PREPARE sky_creator_log_migration FROM @sky_creator_log_migration;
EXECUTE sky_creator_log_migration;
DEALLOCATE PREPARE sky_creator_log_migration;

SET @sky_managed_migration = IF(
    (SELECT COUNT(*) FROM INFORMATION_SCHEMA.COLUMNS WHERE TABLE_SCHEMA = DATABASE()
        AND TABLE_NAME = 'sky_managed_job_definitions' AND COLUMN_NAME = 'activation_stage') = 0,
    'ALTER TABLE `sky_managed_job_definitions` ADD COLUMN `activation_stage` VARCHAR(32) NULL', 'SELECT 1');
PREPARE sky_managed_migration FROM @sky_managed_migration;
EXECUTE sky_managed_migration;
DEALLOCATE PREPARE sky_managed_migration;

SET @sky_managed_migration = IF(
    (SELECT COUNT(*) FROM INFORMATION_SCHEMA.COLUMNS WHERE TABLE_SCHEMA = DATABASE()
        AND TABLE_NAME = 'sky_managed_job_definitions' AND COLUMN_NAME = 'error_code') = 0,
    'ALTER TABLE `sky_managed_job_definitions` ADD COLUMN `error_code` VARCHAR(64) NULL', 'SELECT 1');
PREPARE sky_managed_migration FROM @sky_managed_migration;
EXECUTE sky_managed_migration;
DEALLOCATE PREPARE sky_managed_migration;

SET @sky_managed_migration = IF(
    (SELECT COUNT(*) FROM INFORMATION_SCHEMA.COLUMNS WHERE TABLE_SCHEMA = DATABASE()
        AND TABLE_NAME = 'sky_managed_job_definitions' AND COLUMN_NAME = 'account_attempted') = 0,
    'ALTER TABLE `sky_managed_job_definitions` ADD COLUMN `account_attempted` TINYINT(1) NULL', 'SELECT 1');
PREPARE sky_managed_migration FROM @sky_managed_migration;
EXECUTE sky_managed_migration;
DEALLOCATE PREPARE sky_managed_migration;

SET @sky_managed_migration = IF(
    (SELECT COUNT(*) FROM INFORMATION_SCHEMA.COLUMNS WHERE TABLE_SCHEMA = DATABASE()
        AND TABLE_NAME = 'sky_managed_job_definitions' AND COLUMN_NAME = 'member_updates') = 0,
    'ALTER TABLE `sky_managed_job_definitions` ADD COLUMN `member_updates` LONGTEXT NULL', 'SELECT 1');
PREPARE sky_managed_migration FROM @sky_managed_migration;
EXECUTE sky_managed_migration;
DEALLOCATE PREPARE sky_managed_migration;

SET @sky_managed_migration = IF(
    (SELECT COUNT(*) FROM INFORMATION_SCHEMA.COLUMNS WHERE TABLE_SCHEMA = DATABASE()
        AND TABLE_NAME = 'sky_managed_job_definitions' AND COLUMN_NAME = 'rename_state') = 0,
    'ALTER TABLE `sky_managed_job_definitions` ADD COLUMN `rename_state` LONGTEXT NULL', 'SELECT 1');
PREPARE sky_managed_migration FROM @sky_managed_migration;
EXECUTE sky_managed_migration;
DEALLOCATE PREPARE sky_managed_migration;

SET @sky_managed_migration = IF(
    (SELECT ENGINE FROM INFORMATION_SCHEMA.TABLES WHERE TABLE_SCHEMA = DATABASE()
        AND TABLE_NAME = 'sky_managed_job_definitions') <> 'InnoDB',
    'ALTER TABLE `sky_managed_job_definitions` ENGINE=InnoDB', 'SELECT 1');
PREPARE sky_managed_migration FROM @sky_managed_migration;
EXECUTE sky_managed_migration;
DEALLOCATE PREPARE sky_managed_migration;

Items and assets: This Base release adds no inventory item definitions or external item/image installation. Replace source/* and fxmanifest.lua together from the same download.

Providers: Keep your configured banking, inventory, phone and billing provider choices unless you deliberately change them. Inventory weight/capacity displays use the selected inventory's supported values; unavailable values are not invented. Sky Phone custom app input requires its compatible input ownership support. The optional Hex/Jaksam compatibility routes are limited integration interfaces, not a complete replacement of those vendor resources. Their original resource must be stopped for switch compatibility, external caller addresses must be adapted, and existing Hex/Jaksam banking or billing choices still require a validated replacement before stopping their provider.

Dependency order: Install matching Base 1.45.0 and Jobs Base 1.48.0 release files together, followed by affected job resources. Start the database/framework and any selected external providers first, then sky_base, sky_jobs_base and the job resources. If using the optional Jobs Creator, install a compatible Creator build as well; its UI and extended database setup are not supplied by this Base update. Restart the server and reconnect clients so both ends use the new callback transport.

No additional SQL, inventory definitions, item icons or streamed assets are introduced by these Base changes. The Base schema instructions in this guide still apply. Jobs Creator remains a separate unreleased resource.

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 the release server restart, check that Base and Jobs Base report the expected installed versions and finish startup without database/readiness errors. Reopen /jobconfig and confirm that completed version checks appear, including DOJ when installed. Test one supported invoice through the selected provider, one Quasar usable item if used, and custom app typing/focus with the configured phone. Verify inventory weight/capacity against the actual inventory. For optional Creator workflows, verify current ranks, memberships, duty and society balances using that compatible build. These are recommended acceptance checks; no new live FiveM/provider acceptance is claimed by this publication.

With Hex selected, issue one society invoice from a connected staff member whose job ID differs from the society-account name and verify that Hex records the staff member's actual job. Confirm a personal invoice is rejected and a missing issuer job is reported. Confirm the selected inventory still supplies ordinary item labels and usable items after the adapters are replaced. If you use managed jobs, restart in dependency order and confirm that their runtime owner completes registration without a false startup failure. Source and isolated regression checks do not establish live Hex or FiveM acceptance.

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_base 1.44.0 → 1.44.1. Complete earlier migrations first if upgrading from an older version. Back up the database, resources, custom configuration and saved job/Creator data. Stop the server for the coordinated update. Install Base 1.44.1, then Jobs Base 1.47.1, then the matching hotfixes for your installed Sky jobs and Crime.

2. Replace files

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

Replace sky_base/config/framework/custom.lua, esx.lua, qb.lua, qbox.lua and vrp.lua from the new package. Merge intentional custom adapter changes carefully into the new versions; keeping an old adapter would retain the startup changes being rolled back.

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. Base settings remain file-based; /jobconfig does not manage them.

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. Check normal login and the first startup errors from Base and the installed jobs. 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_base 1.43.0 → 1.44.0. Complete earlier migrations first when upgrading from an older version. Back up your resources, database, customized provider/framework files and saved Job Configurator/Creator data. Stop the server for the coordinated update. Install Base 1.44.0, Jobs Base 1.47.0 and the matching installed jobs together; the new database startup contract requires matching Base and consumer files.

2. Replace the package files

Use the 1.44.0 package. Delete sky_base/source/ completely and insert the new directory. Replace sky_base/fxmanifest.lua from that same package and refresh all of sky_base/config/locales/, merging custom translations back.

Replace every other file listed under Changed Files, merging deliberate local modifications into the new versions. This includes all five framework adapters in config/framework/, the listed banking and license adapters, the Jaksam/AK47 inventory adapters, the GKS/Sky Phone adapters and config/integration/progress/esx.lua. Add the new config/integration/billing/hex.lua and config/integration/banking/hex.lua. Merge the provider-list comments in config/config.lua. Do not keep an old selected framework adapter with the new source: the new startup checks require its completion marker.

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.

All Base configuration is maintained in files. /jobconfig does not manage Base values. No existing executable default in sky_base/config/config.lua changes, and no option is removed: Config.billing = "auto" and Config.banking = "auto" remain "auto". Their comments now also list "hex". No new configuration table is required.

Optional Hex Jobs Creator integration

Install/configure hex_jobscreator and its own dependencies, then start it before sky_base. To choose it explicitly, change Config.billing from your current provider or "auto" to "hex" in sky_base/config/config.lua. Independently set Config.banking to "hex" if Hex should own your society money. Keep your current explicit values when using other providers. Automatic detection selects Hex only when it is started and no earlier supported provider wins; use explicit selections on servers running several providers.

Hex billing requires a connected employee issuer and connected recipient, enabled job billing and the employee's permitted grade. Hex chooses the sending society from the issuer's current job; the Sky account argument cannot redirect that invoice. Personal/player invoices and unattended issuer-less bills are unsupported. Hex validates the amount and permissions; the calling resource still owns distance checks. Verify that an invoice actually appears in Hex before treating it as delivered.

Society operations use Hex's "legal" account. Both police and society_police address the police job. Illegal/black accounts, automatic society account provisioning and account investigations are not provided by this adapter. Configure the job's own banking bridge in Hex; no balances are moved between banks by switching this setting. With the unchanged Config.useSkyBankingFallback = false default, a refused Hex withdrawal remains refused. Keep this value false when operations must stay exclusively in Hex. An existing true value can still route failed operations for accounts not managed by Sky into the separate internal Sky ledger; it does not synchronize those balances. Custom coordinated transfers can request { strict = true } through the existing Sky shared-account API to use only the selected provider. Use the Hex billing instructions and society money instructions for the provider's required setup.

Framework startup and custom adapters

Start the database and framework before Base. The shipped ESX, QB, Qbox, vRP and custom adapters now signal completion. For a customized sky_base/config/framework/custom.lua, preserve your implementation while adding SkyFrameworkReady = true immediately before the client-side return and after all server-side definitions at the end. These markers were previously absent; set them only after synchronous setup has completed. Other customized framework adapters must likewise be merged with their new package versions.

Progress compatibility

The existing Config.progressbar default is unchanged. MSK progress now requires msk_core 4.1.0 or newer. "auto" skips an older or unrecognized version and selects another supported running provider. If your explicit value is "msk_core", update MSK or change it to a supported installed provider such as "esx" or "ox"; do not leave an incompatible explicit selection. ESX progress waits for the provider's actual finish/cancel callbacks.

Banking and licenses

Keep your existing banking selection unless deliberately changing providers. CRM, Bablo and Wasabi can create missing supported society accounts without resetting existing balances. Account listing, statements and freezing are separate capabilities: PC supports all three; TGG supports account listing and freezing but no integrated direct player debit/refund; CRM supports account listing only; Wasabi supports account listing and freezing but no statements; Bablo, FD and Hex do not expose account investigations through this release. Unsupported operations must not be presented as empty results or successful transfers.

For a custom license provider, sky_base/config/integration/license/custom.lua adds this optional member to SkyLicenseProviders.custom; preserve the comma after the preceding member:

Holders = function(license_type)
    -- Return ALL current holders (online and offline), or report unsupported.
    -- A successful result is { { identifier = "character-id" }, ... }.
    return nil, "license_holders_unsupported"
end

Previously that hook was absent. Leaving the new default reports unsupported; implement it only when the provider can return a complete snapshot. Do not substitute {} for a failed or partial lookup.

Optional performance diagnostics

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

Keep source/ and fxmanifest.lua from the same package. Profiler processing changes only source Lua and the manifest. If an older profiler package modified files outside source/, restore those once from the current package and reapply your customizations.

4. Apply SQL, inventory and asset updates

No new Base SQL schema, inventory item or stream asset is introduced. Hex retains its own provider setup, schema and account balances. This release does not import invoices, transfer existing balances or convert an economy. Do not reinstall the whole Base SQL dump over existing data. Apply the separately documented Jobs Base and job-specific SQL/item steps before reopening the server.

5. Restart and verify

Start database/framework dependencies, selected inventory/billing/banking/progress providers, Base 1.44.0, Jobs Base 1.47.0, then matching installed jobs. Reconnect clients and check selected providers, manifest versions and the first startup error if initialization fails. Test duty changes, a storage interaction and completed/cancelled progress. Verify customized map icons, markers and NPCs after a saved edit. With Hex, issue a small society invoice between authorized online players, confirm it appears, then check a known society balance, a small deposit/withdrawal and insufficient-funds rejection. Check the provider's legal account rather than a different bank. With supported license listings, verify a known offline holder. A successful build does not replace these live checks.

1. Prepare the update

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

These instructions cover sky_base 1.42.0 → 1.43.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 before Jobs Base 1.46.0 and the matching installed job releases.

2. Replace the package files

Use the matching 1.43.0 package. Delete the old sky_base/source/ directory completely and insert the new directory. Replace sky_base/fxmanifest.lua from the same package. Refresh the entire sky_base/config/locales/ tree and merge your custom translations back. Replace the changed framework files config/framework/qb.lua and config/framework/qbox.lua, and the changed inventory adapters config/integration/inventory/native/qb.lua, qb-inv.lua and tgiann.lua. Add config/integration/inventory/codemv2.lua and config/integration/billing/lore.lua. Merge deliberate provider customizations into the new files. In config/config.lua, the provider comments gain CodeM V2 and Lore; the existing default values inventory = "auto" and billing = "auto" are unchanged.

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

3. Merge configuration and saved overrides

All Base values are file-based. /jobconfig does not manage Base configuration.

Optional CodeM Inventory V2

In sky_base/config/config.lua, choose inventory = "codemv2" to select V2 explicitly, or keep inventory = "auto". Automatic detection recognizes the actual codem-inventoryv2 resource before the legacy CodeM and Ox compatibility choices. Keep inventory = "codem" for the older CodeM inventory; these are separate providers. Start the framework/database, then codem-lib, codem-inventory-images, codem-inventoryv2, Base and Jobs Base. Do not run ox_inventory alongside V2, which provides that compatibility name itself. Existing installations of another inventory need no provider switch.

For V2, select CodeM Inventory V2 on the matching Sky Inventory Items page and merge its definitions into codem-inventoryv2/data/items.lua. Keep names, weights and stacking; use consume = 0 and omit the item client block for Sky-owned actions. Copy images to codem-inventory-images/images/<item>.png, then restart the inventory and Sky resources. For Fire's hydrualic_spreader item, copy the supplied hydraulic_spreader.png as hydrualic_spreader.png. Also merge WEAPON_SKY_HOSE into CodeM's existing Config.ignoreWeapons in codem-inventoryv2/shared/config.lua, preserving other entries. Follow the CodeM Inventory V2 setup guide for custom image hosting and provider limits.

Optional Lore Billing

Install and configure the existing lore-billing provider and its own database setup, then start it before Base. The verified Lore version requires Qbox (qbx_core), ox_lib, oxmysql and Renewed-Banking; install/start those dependencies first. This adapter does not add other framework support to Lore itself. In sky_base/config/config.lua, select billing = "lore", or retain "auto" when Lore is the intended detected provider. When several billing resources are running, explicit "lore" selects the intended one. Keep existing billing unchanged on servers using another provider.

Lore supports society invoices through an online issuer and recipient. Use a configured department society account and a positive whole amount. The adapter supports amounts from 1 to 2147483647 and nonempty UTF-8 reason/account text up to 255 characters; the calling job may impose a lower limit. Sending the request is not confirmation that Lore stored or paid the invoice: check its actual invoice list. Lore’s own permissions, payment processing and database remain the provider’s responsibility.

For Fire, the existing default Config.Billing.mode = "consent" does not use an external billing provider. Choose "framework" in sky_firejob/config/config.lua while preserving its existing range, maximum and reasons. With /jobconfig, use Fire’s Billing mode key fireBillingMode = "framework" and enable fireBillingEnabled; a saved override takes precedence over the Fire file. These are existing Fire settings, not new Base /jobconfig fields.

Optional QBCore marked bills

The new editable locals at the top of sky_base/config/framework/qb.lua are:

local black_money_mode = "account"
local black_money_item = "markedbills"
local black_money_worth_key = "worth"

Previously QBCore black money always used its black money account. The new shipped "account" mode preserves that behavior. Only if your server deliberately uses separate marked-bills bags, change black_money_mode to "markedbills"; set the item and metadata key to the actual inventory definition. Each unique single-item bag must store a positive whole cash value in info.worth or metadata.worth; stacked bags and invalid values are rejected. Merely switching this mode does not convert existing account balances or old item contents. Keep "account" unless your economy and inventory already use that bag model. No setting is removed.

Optional performance diagnostics

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

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

4. Apply SQL, inventory and asset updates

No Base SQL migration, new stream asset or automatic economy conversion is required. CodeM V2 users must install the definitions/images from its setup guide in their actual inventory; the adapter does not add missing items to that provider’s catalog at runtime. Lore’s own schema belongs to its existing installation instructions. Other inventories and billing systems require no new item or SQL step for this Base release.

5. Restart and verify

Start the database, framework and selected inventory/billing providers, then Base 1.43.0, Jobs Base 1.46.0 and the installed matching jobs. Check the startup log and selected providers. Test a tablet callback and an item ownership check. On QBCore, verify gang assignment leaves the main job unchanged; if marked bills are enabled, test a partial spend and the remaining bag value. For CodeM V2, check item use, metadata and storage. For Lore, have authorized online staff issue a small society invoice to another online player and confirm it appears in Lore before treating delivery as successful.

1. Prepare the update

These instructions cover Base 1.41.0 → 1.42.0. Complete earlier update steps first when upgrading from an older version. Stop the server and back up the resource, database and customized files. Install Base 1.42.0 before Jobs Base 1.45.0 and the matching job releases.

2. Replace the package files

Use the matching 1.42.0 download. Delete the old sky_base/source/ directory and copy the complete new directory. Replace sky_base/fxmanifest.lua and all of sky_base/config/locales/. Replace sky_base/config/integration/notification/default.lua and sky_base/config/integration/progress/esx.lua, merging any deliberate provider customizations. Merge the config.lua change described in this view instead of overwriting your server settings.

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

3. Merge configuration

All Base settings are file-based. /jobconfig does not manage Base configuration.

In sky_base/config/config.lua, add the following field inside the existing Config = { ... } table:

notificationPosition = "middle-left",

Config.notificationPosition was previously absent; the notification position was fixed. The new shipped value is "middle-left", preserving the previous default placement. Accepted values are "top-left", "top-center", "top-right", "middle-left", "middle-right", "bottom-left", "bottom-center" and "bottom-right". This affects only Config.notification = "default"; other notification providers control their own placement. Config.notification, Config.helpnotify and Config.progressbar keep their existing values. No setting or config block is removed, and no new provider selection is required for the ESX animation fix.

The ESX vehicle-colour correction uses the installed es_extended manifest version. Keep its version metadata accurate; do not change the version to disguise a customized framework. Standard ESX before 1.13 uses separate custom-colour fields, while 1.13 and later use RGB values in the main colour fields. No framework-source patch or reset of saved vehicles is required. Validate compatibility separately if your ESX fork changes that contract.

Optional performance diagnostics

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

4. Apply SQL, inventory and asset updates

No SQL migration, inventory-item registration or additional stream asset is required for this Base update. Keep existing vehicle data. The public provider files and built interface are installed with the package-file step.

5. Restart and verify

Start the database, framework and selected external providers, then Base 1.42.0, Jobs Base 1.45.0 and the installed matching jobs. Check the startup log before admitting players. Test the configured built-in notification position, an ESX progress action including its animation and cancellation, and garage retrieval with both standard and custom vehicle colours. If startup reports a migration wait error, inspect the named waiting resource and the earlier database/startup errors; do not reset tables to hide the error.

1. Prepare the update

Install Base 1.41.0 before Jobs Base 1.44.0 and the matching job updates. These instructions cover 1.40.1 → 1.41.0; complete earlier migrations first when upgrading from an older version. Stop the server and back up the resource, database, customized files and saved configurator/creator data.

2. Replace the package files

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

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

3. Merge configuration

All Base settings are maintained in sky_base/config/config.lua and the public integration files. /jobconfig does not manage them.

Add these fields inside the existing Config = { ... } table; do not replace the rest of your configuration:

notification = "default",
helpnotify = "default",

"default" uses the Sky interface. "auto" selects a supported provider at startup; start that provider before Base. Select a provider that depends on Base explicitly. Provider names are case-sensitive; the complete supported choices are listed beside each field in the new config/config.lua. Notification and help choices differ: for example, cp_notify is a notification provider, not a help provider. The new progress selections are codem-supreme-hud, aty_uikitv2, 17mov_Hud, risk-notify, prism_uipack, frkn-uikit and msk_core. Their cancellation and display options depend on the provider. Restart after changing a selection.

Notification and single-action help customizations previously placed in sky_base/config/functions.lua must move to the matching sky_base/config/integration/notification/custom.lua or sky_base/config/integration/helpnotify/custom.lua; implement the supplied template before selecting "custom". Multi-action help remains in config/functions.lua. Replace the new stock adapter files, or merge their behavior into your customized adapters. Keep the new manifest together with the integrations because it loads their shared progress helper and Ox usable-item support in the required order.

If you use qb-inventory 2.0 and want individual item names in its UI, the optional patch and instructions are shipped in sky_base/install/qb-inventory/. Back up that inventory, run the documented patch check from its directory, and apply only if the check succeeds. This is optional and is not a database migration. Other inventory interfaces must support their own per-item names. No Base setting is removed.

Optional performance diagnostics

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

4. Apply data and inventory updates

No database migration or new inventory item is required for this Base update. Keep existing vehicle records and their properties; the HEX correction affects subsequent vehicle creation and plate changes. Existing records are not recreated or reset.

5. Restart and verify

Restart the database, framework and any edited inventory first, then Base, Jobs Base and the installed job resources. Confirm 1.41.0 and resolve startup errors before admitting players. Check your selected notification, interaction-prompt and progress providers, including completion and cancellation. Use a reusable Ox item and check individually named items if your inventory supports them. On HEX garages, create, park and retrieve a vehicle and verify its plate and saved properties. When using Dispatch phone-app updates, verify the selected supported phone provider.

1. Prepare the update

These instructions cover 1.40.0 to 1.40.1. Complete earlier update instructions first when upgrading from an older version. Stop the server and back up the resource, database and customized files. Install Base 1.40.1 before Jobs Base 1.43.1, Mechanic 1.29.1 and Ambulance 2.39.1 when using those resources.

2. Replace source and integration files

Delete the old sky_base/source folder and insert the complete replacement from the 1.40.1 package. Replace sky_base/fxmanifest.lua, sky_base/config/framework/esx.lua and sky_base/config/integration/banking/_init.lua. In sky_base/config/integration/progress/, replace esx.lua, hex.lua, jaksam.lua, mythic.lua, ox.lua, qb.lua and wasabi.lua. Merge any custom adapter or integration changes into the new files. Delete the obsolete sky_base/config/banking_init.lua; its initialization now lives in sky_base/config/integration/banking/_init.lua. Keep all other configuration and persistent data.

3. Keep existing settings and vehicles

No configuration values, SQL, items or locales need migration. Base settings remain file-based and are not managed by /jobconfig. Keep saved vehicle records. If an affected vehicle was saved again with incorrect extras, restore its desired equipment once; the update preserves intentional disabled extras and cannot reconstruct an earlier selection.

4. Restart and verify

Restart the server and confirm Base 1.40.1. Reconnect an affected player and check that job/duty updates settle. Complete and cancel an action with your configured progress provider. Park and retrieve a helicopter with mixed enabled and disabled extras after installing Jobs Base 1.43.1. If FXServer stays running during file replacement, stop the affected resources, run refresh after copying, then start them again so the new manifest is loaded. Check that the removed banking file produces no startup warning.

1. Prepare the update

Install Base 1.40.0 first. The new shared vehicle services use Jobs Base 1.43.0, Mechanic 1.29.0 and Police 1.32.0 together. These instructions cover 1.39.0 → 1.40.0; complete earlier migrations first when upgrading from an older version. Stop the server and back up the resource, database, customized files and saved configurator/creator data.

2. Replace the package files

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

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

3. Merge configuration

No values in sky_base/config/config.lua change. All Base configuration is maintained in files; /jobconfig manages none of it.

Merge the new schema function from sky_base/config/vehicle_storage.lua into any custom adapter. Previously the table mapping was embedded in tuning storage; it is now shared with the vehicle register. Standard mappings remain:

The shipped Sky.VehicleStorage.GetSchema() function is new. Copy its complete implementation from the new public adapter and reapply your actual table/column names there. Preserve custom read/write logic and Qbox's vehicle-provider integration.

The changed ESX, QBCore and Qbox framework adapters, banking adapters, inventory adapters and Ox progress adapter are functional updates, not new Config.* values. Update sky_base/config/integration/banking/_init.lua and the matching manifest. Remove the obsolete sky_base/config/banking_init.lua if present. Replace stock adapter versions or merge their changed functions into customized versions. ESX banking now updates the live society account. Inventory registration preserves existing definitions when requested; Ox Inventory and native Qbox inventories cannot create missing definitions through this registration path. Add those missing items to the inventory's item file. No existing Base setting is removed, renamed or reset.

Managed job definitions support compatible configurators on ESX, QBCore and Qbox. This Base update provides the shared support; it does not create departments or expose a new creator screen by itself. Existing departments are not adopted automatically. Missing society-account creation is supported by ESX addonaccount, qb-banking, Renewed-Banking and Sky internal banking. Keep the selected banking provider and existing balances. Unsupported account creation or an unavailable account must be resolved in that provider; do not enable a fallback to create a second account for the same managed job.

For Qbox servers using managed jobs, add set qbx:cleanPlayerGroups "false" to server.cfg before ensure qbx_core and restart the server. Qbox's documented default is "true"; disabling that startup cleanup preserves memberships while Base restores runtime job definitions afterward. This is a Qbox server convar, outside /jobconfig, and does not change a shipped Base default. See the official Qbox convar reference.

Optional performance diagnostics

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

4. Apply data and inventory updates

The vehicle register uses the existing owned-vehicle table. With Jobs Base Config.AutoExecuteQuery = true, registry initialization can add its identifier column and unique index automatically. Before enabling inspections or registrations, back up that table and check the actual framework/garage mapping in sky_base/config/vehicle_storage.lua.

With automatic SQL disabled, select the active game database and run this upgrade. Keep owned_vehicles for standard ESX; change the first value to player_vehicles for standard QBCore/Qbox, or to the custom table returned by your adapter. This adds a nullable sky_registry_id CHAR(36) and uniq_sky_registry_id without replacing vehicle records:

SET @sky_vehicle_table = 'owned_vehicles';
SET @sky_registry_sql = IF(
    EXISTS(SELECT 1 FROM information_schema.COLUMNS WHERE TABLE_SCHEMA = DATABASE() AND TABLE_NAME = @sky_vehicle_table AND COLUMN_NAME = 'sky_registry_id'),
    'SELECT 1', CONCAT('ALTER TABLE `', REPLACE(@sky_vehicle_table, '`', '``'), '` ADD COLUMN `sky_registry_id` CHAR(36) NULL')
);
PREPARE sky_registry_migration FROM @sky_registry_sql;
EXECUTE sky_registry_migration;
DEALLOCATE PREPARE sky_registry_migration;
SET @sky_registry_sql = IF(
    EXISTS(SELECT 1 FROM information_schema.STATISTICS WHERE TABLE_SCHEMA = DATABASE() AND TABLE_NAME = @sky_vehicle_table AND INDEX_NAME = 'uniq_sky_registry_id'),
    'SELECT 1', CONCAT('CREATE UNIQUE INDEX `uniq_sky_registry_id` ON `', REPLACE(@sky_vehicle_table, '`', '``'), '` (`sky_registry_id`)')
);
PREPARE sky_registry_migration FROM @sky_registry_sql;
EXECUTE sky_registry_migration;
DEALLOCATE PREPARE sky_registry_migration;

Do not delete or regenerate existing registry IDs. A custom garage that replaces a vehicle row must preserve its ID, including during plate changes. No certificates are invented for old vehicles. The register currently supports the ESX, QBCore and Qbox vehicle-storage adapters and requires oxmysql; use OneSync for the physical vehicle workflow. There are no separate Base framework SQL files to import for this release.

Managed job storage

Base startup automatically creates sky_managed_job_definitions and restores the definitions stored there. This migration runs independently of Jobs Base Config.AutoExecuteQuery. Preserve this table, framework memberships and banking data when upgrading or restoring a backup. A failed framework activation remains pending for recovery; do not clear the saved definition to hide the error.

For administrators who provision schemas manually, create this new table in the active game database before starting Base. There is no additional Base SQL file to import. The table inherits the database character set and collation:

CREATE TABLE IF NOT EXISTS `sky_managed_job_definitions` (
    `job_name` VARCHAR(50) NOT NULL,
    `owner` VARCHAR(64) NOT NULL,
    `origin` VARCHAR(16) NOT NULL,
    `definition` LONGTEXT NOT NULL,
    `baseline` LONGTEXT NOT NULL,
    `status` VARCHAR(16) NOT NULL DEFAULT 'pending',
    `last_error` TEXT NULL,
    `member_updates` LONGTEXT NULL,
    `updated_at` TIMESTAMP NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,
    PRIMARY KEY (`job_name`),
    INDEX `idx_managed_owner` (`owner`)
) ENGINE=InnoDB;

No Base item catalog needs a blanket replacement. Install the item definitions required by each updated resource for your actual inventory provider.

5. Restart and verify

Start the framework, database and configured inventory before Base; start Jobs Base and job resources afterward. Confirm version 1.40.0 and no adapter/schema errors. Test an ESX society credit against the actual balance, a progress action with no animation, and character reload on Qbox where applicable. For the registry, test an owned vehicle with the actual garage, issue a signed document through Mechanic, then verify that a supported plate change retains its history. If a compatible configurator manages framework jobs, test a dedicated job across a server restart, a grade change for online and offline members, and recovery after a failed activation. Verify that a new supported society account starts empty and an existing account retains its balance. On Qbox, confirm the cleanup convar is set before core startup and memberships survive that restart.

1. Prepare the update.

Install Base 1.39.0, Jobs Base 1.42.0, and Mechanic 1.28.0 together when using the new vehicle-tuning storage. These steps cover 1.38.0 → 1.39.0. Follow earlier update instructions first when upgrading from an older version. Stop the server and back up the resource, database, custom settings, and saved configurator data.

2. Replace the package files.

Install the matching 1.39.0 package. Update every path listed in Changed Files, delete and reinsert sky_base/source/*, and replace sky_base/config/locales/* completely. Merge the configuration changes in this tab into your customized files. Preserve writable data and generated user content. Move custom integration edits to the new locations and remove the obsolete paths listed under Renamed Files.

Required profiler files

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

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

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

3. Merge and review configuration.

All Sky Base settings are maintained in files. /jobconfig does not manage them.

In sky_base/config/config.lua, merge these two changed defaults:

The timeout now applies to requests in both directions. A timeout does not cancel an operation that is already running. Keep an intentional custom timeout if your server needs one. callbackPerformance.enabled = true, warningThreshold = 500, and warningCooldown = 300000 remain unchanged. Set warningsEnabled = true only if you want automatic slow-operation warnings; actual errors remain visible either way.

The provider lists gain apex for billing and apex / oxlyn for banking. Their default selections remain "auto"; the updated path comments do not change runtime settings. Keep your chosen provider, or select Config.billing = "apex", Config.banking = "apex", or Config.banking = "oxlyn" when installing that integration. Start the selected provider before Sky Base.

If using Oxlyn, set Config.Business.accountSource = "society" in your Oxlyn configuration. Use esx_addonaccount on ESX or qb-banking on QBCore/Qbox and create the required society accounts there. This connects existing society balances; it does not transfer balances from Oxlyn's standalone ledger. Apex society invoices use the issuing player's job and billing permissions; payment is handled separately in Apex.

Integration folders move from sky_base/config/<feature>/ to sky_base/config/integration/<feature>/ for banking, billing, fuel, garage, housing, inventory, license, phone, progress, tablet, target, vehiclekeys, and voice. Copy your custom edits into the matching new files, then remove the old copies listed under Renamed Files. Keep sky_base/config/framework/ in its existing location. Update any custom resource that explicitly imports an old integration path.

Install the new sky_base/config/vehicle_storage.lua in full; it was absent in the previous package. Merge custom edits in sky_base/config/vehicle_functions.lua with the new file: its old vehicle-property reader and writer have been removed because the framework now supplies them. Use the Garage Integration guide and its ESX, QBCore, or Ox instructions to check the required vehicle-property fields for your exact framework version. Custom framework adapters need the same vehicle-property connection before use. Do not copy an old complete vehicle helper back over the new file.

Optional performance diagnostics

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

setr sky_profiler 1

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

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

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

4. Apply database and item changes.

No SQL schema migration is added by this Base update. On Qbox servers using black money, register a stackable inventory item named black_money before using those payments. Existing framework cash and bank balances keep their normal storage. Replace all Base locales. Preserve integration credentials and custom callbacks in the files you merge.

5. Start and verify the update.

Start your framework and providers, then Base, Jobs Base, and the job resources. Verify the selected bank balance and an invoice without forcing payment. On Qbox, test a black-money payment against the inventory item. Complete the garage round-trip checks from the linked integration guide before enabling the new Mechanic save path for players.

1. Stop the server and back up the complete sky_base resource, its database and inventory data, saved Job Configurator settings where applicable, and intentional public configuration edits. Preserve writable reports and other generated data outside the replaceable source files.
2. Install 1.38.0 as a consistent package. Replace every file listed in Changed Files, delete and reinsert sky_base/source/*, and replace sky_base/config/locales/* completely. Merge the public configuration changes listed in this tab into your customized files; do not copy old configuration files over the new package wholesale. Keep the manifest, built UI, runtime and dependencies from the matching release set.
3. Apply the following configuration changes before starting the resource.

All Base settings are maintained in files. /jobconfig does not manage any of them. config/config.lua has no executable value or selector change in this release.

In sky_base/config/currency.lua, add these two entries. Both paths were absent in 1.37.0. Keep all existing formatters and currencies:

Config.Currency.formatters.black_money = {
    type = "money",
    symbol = "$",
    symbolPosition = "before",
    spaceBetween = false,
    thousandsSeparator = ",",
    decimalSeparator = ".",
    precision = 0
}

Config.Currency.currencies.black_money = {
    formatter = "black_money",
    get = function(source)
        if not IsDuplicityVersion() then return 0 end
        return Sky.FW.GetAccountMoney(source, "black_money") or 0
    end,
    add = function(source, amount)
        if not IsDuplicityVersion() then return false end
        return Sky.FW.AddAccountMoney(source, "black_money", amount) ~= false
    end,
    remove = function(source, amount)
        if not IsDuplicityVersion() then return false end
        return Sky.FW.RemoveAccountMoney(source, "black_money", amount)
    end
}

Replace the changed public banking, framework, inventory, and RoadPhone adapters listed in Changed Files, preserving intentional local provider customizations. For ESX banking, every used society must have its existing society_<job> account registered in addon_account with shared = 1 and loaded by esx_addonaccount. Missing accounts now fail explicitly; keep existing balances in addon_account_data. If you use vRP name changes, keep your distribution-specific identity implementation and return success only after persistence. These adapter changes are executable integration changes, not new provider selector defaults.

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

No Base schema migration, new inventory item, image, stream file, or provider secret is introduced. The black_money currency uses the configured framework account; confirm that account is supported before enabling dependent faction features. The ESX society-account requirement concerns existing account data, not a reset or replacement SQL import.

5. Start providers and Base before Jobs Base and the jobs. Check the manifest version, an online and offline character rename on the active supported framework, legacy ESX item refresh if applicable, an accepted and rejected society withdrawal, Jaksam updates on the selected item slot, and empty versus unavailable vehicle storage. In RoadPhone, type in the emergency form and confirm gameplay shortcuts remain inactive until focus is released.

1. Stop the server and back up the complete sky_base resource plus every intentional provider-adapter edit.
2. Delete the old resource and install the complete 1.37.0 package. Do not mix 1.36.0 adapters, manifest, or source files with this release.
3. Start from the new config/config.lua and transfer only deliberate local settings. /jobconfig does not manage Base configuration. The executable defaults remain automatic; only the documented selector choices add Config.phone = "sky" and Config.fuel = "qb".
4. Reapply intentional custom integrations only after retaining the new provider contracts. Add no SQL, inventory item, image, or stream asset for this release.
5. Restart sky_base before every dependent resource and verify the selected phone, fuel, housing, target, voice, billing, banking, progress, inventory, and vehicle-key providers.

1. Stop the server and back up the complete sky_base folder plus every intentional provider-adapter edit.
2. Delete the old resource and install the complete 1.36.0 package. Do not mix 1.35.1 framework, provider, manifest, or source files with this release.
3. /jobconfig does not manage any Base value. Start from the new config/config.lua and transfer only deliberate local choices. No executable default changed between 1.35.1 and 1.36.0; these selector values remain unchanged:
   config/config.lua

   Config.garage = "auto"
   Config.license = "auto"
   Config.fuel = "auto"
   

   
   Only the documented choices changed: Config.garage adds "msk", Config.license adds "quasar", and Config.fuel adds "msk".
4. Use Config.garage = "msk" with msk_garage, Config.fuel = "msk" with msk_fuel, and Config.license = "quasar" with qs-licenses. MSK Garage is an ESX integration. Its shipped fallback garage identifiers are A for land vehicles, boat_A for boats, and heli_A for aircraft; edit config/garage/msk.lua only when your MSK installation uses different identifiers.
5. Replace config/locales completely even though this release adds no new customer-facing locale key. No Base SQL migration, inventory item, image, or stream asset is required.
6. Restart sky_base before every dependent resource. Verify framework duty changes, the selected providers, player logout/relogin, invoice creation, vehicle plate/key operations, and database calls. Sky.DB.Transaction requires oxmysql in this release; mysql-async users must not rely on transaction support.

1. Stop the server and back up the complete sky_base resource plus intentional framework-adapter edits.
2. Delete the old resource and install the complete 1.35.1 package. Replace all three framework adapters, fxmanifest.lua, config/locales, and the complete source directory together; do not retain the removed duty-index file.
3. /jobconfig does not manage Base. No public config value changed, and no SQL, item, image, or stream migration is required.
4. Restart Base before Jobs Base and every job resource. Verify QB/Qbox duty changes and counts. On ESX, do not rely on Sky.FW.SetDuty, ToggleDuty, or GetOnDutyCount for a native duty system in this patch.

1. Stop the server and back up the complete sky_base folder plus every intentional provider-adapter edit.
2. Delete the old resource and install the complete 1.35.0 package. Do not mix 1.34.0 adapters, manifest, or source files with this release.
3. /jobconfig does not manage any Base value. Start from the new config/config.lua and transfer only deliberate local choices. The only changed executable default is:
   config/config.lua

   Config.defaultCallbackTimeout = 10000
   

   
   This value was 5000 in 1.34.0. The selectors Config.phone = "auto", Config.tablet = "default", Config.fuel = "auto", and Config.garage = "auto" keep their previous shipped values.
4. The selector comments add these choices: Config.phone = "sd", Config.tablet = "sd" or "auto", and Config.fuel = "cdn". Config.garage = "op" is unchanged but now supports OP Garages V2 and V3 automatically. For SD tablet auto-detection, start sd-tablet; the adapter also calls sd-phone, so both SD resources must be available. CDN Fuel requires cdn-fuel; OP requires op-garages.
5. Replace config/locales completely even though this release adds no new locale key. No SQL migration, Base-owned item, image, or stream asset is required.
6. Restart sky_base before every dependent resource. Verify callback-heavy actions, the selected phone/tablet/fuel provider, OP vehicle storage on the installed OP major version, Jobs Creator duty changes, and the missing-JSON diagnostic.

1. Stop the server. Back up the complete sky_base resource, intentional adapter edits, and SaltyChat's external config.json when that provider is installed.
2. Delete the old folder and install the complete 1.34.0 package. Do not mix the new manifest, provider adapters, locales, or source directory with 1.33.0 files.
3. /jobconfig does not manage any Base value. Start from the new config/config.lua, transfer only deliberate server-specific values, and apply these complete executable changes after the main Config table if you merge manually:
   config/config.lua

   Config.voice = "auto"
   Config.voiceRadioSounds = {
       enabled = false,
       transmitStartVolume = 18,
       transmitEndVolume = 8,
   }
   Config.tablet = "default"
   Config.target = "none"
   Config.maxPing = 5000
   

   
   Config.voice and Config.voiceRadioSounds did not exist in 1.33.0. Config.tablet changed from "auto" to "default", Config.target changed from "auto" to "none", and Config.maxPing changed from 1000 to 5000. Keep Config.tablet = "default" for the bundled Jobs Base tablet; set "lb" or "roadpad" only as a deliberate external-tablet opt-in. Keep Config.target = "auto" only when automatic target-provider selection remains intentional.
4. The existing selector values remain Config.license = "auto", Config.billing = "auto", Config.fuel = "auto", and Config.banking = "auto". New explicit choices are "stg-walletv2" for licenses, "retro" for billing, "stg-van" for fuel, and "devmosaic" or "retro" for banking. Fuel auto-detection now recognizes the started stg-vanaheimfuel resource as "stg-van". Retro Billing is detectable but cannot create invoices.
5. Start the selected external providers before sky_base. For SaltyChat incoming-traffic activity, merge this property into its existing external file; keep every other property already present:
   saltychat/config.json

   {
     "RequestRadioTrafficStates": true
   }
   

   
   Keep Config.voiceRadioSounds.enabled = false when another interface already plays radio clicks. SaltyChat needs the external property above; Base cannot set it.
6. Replace the complete config/locales directory. Italian is now available through Config.locale = "it"; every bundled locale now contains notifications.streamerModeTitle, notifications.enabled, notifications.disabled, notifications.rewardTitle, notifications.commandTitle, plus commandErrors.missingParameter, tooManyParameters, mustBeNumber, cannotUseMeFromConsole, invalidPlayerId, playerNotFound, invalidPercentage, invalidSelection, and invalidBoolean.
7. No Base SQL migration or Base-owned inventory item is required. Restart sky_base before sky_jobs_base and every dependent resource. Verify voice joining/leaving and activity, the selected banking/license/fuel action, JackSam and RxBilling invoice direction, target interactions, high-ping events, duty changes, inventory updates, and localized command feedback.

1. Download sky_base 1.33.0 and back up the complete current resource plus intentional provider customizations.
2. Delete the old resource folder and install the complete new package, including every new adapter and the updated manifest.
3. /jobconfig does not manage Base. In the new config/config.lua, add Config.tablet = "auto" and change Config.target from "none" to "auto" unless marker-only interaction is intentional.
4. Keep Config.license, Config.billing, and Config.banking at "auto" unless one provider is selected explicitly. license now also accepts "standalone" and "qbox"; billing and banking now also accept "synz".
5. Add these complete new runtime-control tables next to the existing debug and defaultCallbackTimeout values:
   config/config.lua

   debugLevels = {
       all = false,
       debug = false,
       info = true,
       warn = true,
       error = true,
   },
   debugQueue = {
       maxEntries = 1000,
       batchSize = 10,
       batchDelay = 0,
   },
   callbackPerformance = {
       enabled = true,
       warningsEnabled = true,
       warningThreshold = 500,
       warningCooldown = 300000,
   },
   

6. Keep Config.debug = false and Config.defaultCallbackTimeout = 5000 unless deliberately customized. Config.Licenses.catalog remains the additional catalogue for the one selected license provider and still contains firstaidcourse by default.
7. No SQL migration or inventory item is required by Base itself. Restart sky_base before sky_jobs_base and every dependent resource.

1. Download sky_base 1.32.1 and back up your current resource.
2. Delete the old resource folder and install the complete new folder.
3. Keep the new framework, fuel, inventory, interaction, and documentation files.
4. Reapply only intentional custom provider changes to the matching new files.
5. No config value, SQL migration, or inventory item is required.
6. Restart sky_base before sky_jobs_base and every dependent resource.

1. Download sky_base 1.32.0 and create a resource backup.
2. Delete the old resource folder and install the complete new folder.
3. Keep the new fxmanifest.lua, /source, provider folders, framework adapters, and config/vehicle_functions.lua.
4. Transfer only your intentional provider selections and custom adapter changes into the new config files.
5. No SQL migration or new inventory item is required.
6. Restart sky_base before restarting sky_jobs_base and all dependent resources.