Changelog

These instructions cover sky_firejob 1.16.0 → the refreshed 1.16.1 package. If you installed an earlier 1.16.1 download today, download the current 1.16.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.

Use the complete 1.16.1 package. Delete the entire sky_firejob/source/ folder and insert its new version, then replace sky_firejob/fxmanifest.lua from the same package. Do not merge old generated interface files. Refresh the complete sky_firejob/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.

No plaintext configuration options, Job Configurator keys or defaults are added, removed or reset by this hotfix. Keep your existing configuration, jobs, grades, locations and saved overrides. /jobconfig does not replace runtime files, install schema or reload changed manifests. No configuration import or reset is required.

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

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.

Perform a full server restart after replacement so the changed manifests and file lists are reloaded. Start the framework, database connector and selected providers first, then Base 1.45.1, Jobs Base 1.48.1 and the installed consumers. Unrelated clothing, vehicle and map packs can remain after Sky in server.cfg. Reconnect clients. Open the Fire tablet and check your configured locations and normal duty workflow. 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.

These instructions cover sky_firejob 1.15.1 → 1.16.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.

Use the complete 1.16.0 release package. Delete the entire sky_firejob/source/ folder and insert its new version; do not merge old generated interface files. Replace sky_firejob/fxmanifest.lua from the same package. Refresh the complete sky_firejob/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_firejob/config/config.lua
• sky_firejob/config/init.lua
• sky_firejob/config/inventory/fire_dividing_breeching.png
• sky_firejob/config/locales/*
• sky_firejob/config/sv_functions.lua
• sky_firejob/fxmanifest.lua
• sky_firejob/meta/pedpersonality.meta
• sky_firejob/meta/weaponanimations.meta
• sky_firejob/meta/weaponarchetypes.meta
• sky_firejob/meta/weapons.meta
• sky_firejob/source/* — delete and reinsert
• sky_firejob/stream/dividing_breeching/sky_dividing_breeching.ydr
• sky_firejob/stream/dividing_breeching/sky_dividing_breeching.ytyp
• sky_firejob/stream/dividing_breeching/sky_dividing_tap_1.ydr
• sky_firejob/stream/dividing_breeching/sky_dividing_tap_2.ydr
• sky_firejob/stream/dividing_breeching/sky_dividing_tap_3.ydr
• sky_firejob/stream/w_am_hohlstrahlrohr.ydr

In sky_firejob/config/config.lua, preserve your existing vehicle placements, job lists, incident settings and rewards. No old configuration block or option is removed in this release.

If you manage settings through /jobconfig, select Firejob and review Billing, Hose, Vehicle Fires, Oil Cleanup, Interior Extinguishers, Water Monitor, Water Bucket and Rescue Cushion. Existing saved settings remain effective; replacing config.lua does not overwrite them. Save the values you want there. For installations without /jobconfig, merge the following exact changes into config.lua.

Billing. The shipped Config.Billing.mode changes from "consent" to "framework". "framework" uses the provider selected by Config.billing in sky_base/config/config.lua; with "sky", invoices use Sky Billing. "consent" remains available for the existing local cash/card prompt. Keep your enabled/range/maxAmount/reasons values. The old default block was:

Config.Billing = {
    enabled = true,
    mode = "consent",
    range = 6.0,
    maxAmount = 50000,
    reasons = {}
}

The new complete default block is:

Config.Billing = {
    enabled = true,
    mode = "framework",
    range = 6.0,
    maxAmount = 50000,
    reasons = {}
}

In /jobconfig → Firejob → Billing, the equivalent setting is fireBillingMode; choose "framework" to adopt the provider flow or keep "consent" intentionally. The other existing settings are fireBillingEnabled, fireBillingRange, fireBillingMaxAmount and fireBillingReasons. Invoices being issued are distinct from their being paid; only confirmed payment becomes society income.

Hose. Three settings were absent from the old Config.Hose table. Add these complete new entries inside that existing table; retain every other hose field:

nozzleModel = "normal", -- "normal" or "hohlstrahlrohr"
dividing = false,
hollowNozzleGroundOffset = 0.0,

The default nozzle remains the normal nozzle. Set nozzleModel = "hohlstrahlrohr" for the EU nozzle. Set dividing = true only when you want the three-way divider. hollowNozzleGroundOffset is the EU nozzle's vertical ground correction; the existing groundedNozzleOffset = -0.38 remains the normal nozzle correction. In /jobconfig → Firejob → Hose, use hoseNozzleModel under Nozzle, hoseDividing under General and hoseHollowNozzleGroundOffset under Nozzle → Ground Placement. The model selector offers Normal nozzle and EU nozzle; custom model names are not accepted. Changing the nozzle model returns deployed attack hoses, so switch it while equipment is not in use. Config.Hose.vehicles, its pump panel/intake/outlet geometry and all existing vehicle definitions have no net configuration change in this release; keep the model-specific coordinates you already configured.

Vehicle fuel fires. In Config.FireSystem.materials.vehicle_fuel, the old complete public override was:

vehicle_fuel = {
    allowedExtinguishAgents = { water = false, foam = true, water_monitor = false, extinguisher = true },
    waterEffectiveness = 0.0,
    foamEffectiveness = 1.35
}

Replace that override with this complete new public block:

vehicle_fuel = {
    allowedExtinguishAgents = { water = true, foam = true, water_monitor = false, extinguisher = true },
    waterEffectiveness = 0.65,
    foamEffectiveness = 1.35,
    waterReaction = { enabled = false }
}

The new waterReaction table is fully shown above; the previous public block had no such table and inherited an enabled water reaction. Only its enabled value changes; preserve any intentional custom reaction tuning. Water means the hose/nozzle, firetruck cannon and helicopter bucket. Portable Water Monitor water remains disabled for this material. The effective default changes are water false → true, waterEffectiveness 0.0 → 0.65, waterReaction.enabled true → false; foam, Water Monitor and extinguisher permissions remain unchanged. In /jobconfig → Firejob → Vehicle Fires, set vehicleFiresCanExtinguishWater = true, vehicleFiresWaterEffectiveness = 0.65 and vehicleFiresWaterReactionEnabled = false to adopt those defaults. Keep vehicleFiresCanExtinguishFoam = true, vehicleFiresCanExtinguishExtinguisher = true, vehicleFiresCanExtinguishWaterMonitor = false and vehicleFiresFoamEffectiveness = 1.35, unless you intentionally customized them. Existing reaction tuning keys vehicleFiresWaterReactionChance, vehicleFiresWaterReactionInterval, vehicleFiresWaterReactionExplosionChance, vehicleFiresWaterReactionSpreadCount and vehicleFiresWaterReactionSmokeIncrease retain their meaning. If you selected another material for Config.VehicleFires.material, these settings affect that selected material rather than automatically replacing it with vehicle_fuel.

Optional gang access. Existing exact job names and job groups remain valid. The following existing selector lists now also accept gang:<internal_name> where your configured gang integration supplies membership:

• Config.OilSpills.cleanup.allowedJobs ↔ oilCleanupAllowedJobs: additional access alongside all configured Firejob jobs. An empty list grants no additional selectors; it does not remove configured Firejob access.
• Config.InteriorExtinguishers.allowedJobs ↔ interiorExtinguishersAllowedJobs: an empty list allows every job, with requireOnDuty still enforced.
• Config.InteriorExtinguishers.noDutyJobs ↔ interiorExtinguishersNoDutyJobs: exempt selectors may take/restock extinguishers without job duty; an empty list provides no exemptions.
• Config.InteriorExtinguishers.maintenance.allowedJobs ↔ interiorExtinguishersMaintenanceAllowedJobs: additional access alongside configured Firejob jobs; an empty list adds nobody.
• Config.InteriorExtinguishers.placement.allowedJobs ↔ interiorExtinguishersPlacementAllowedJobs: an empty list allows every job, with placement.requireOnDuty still enforced.
• Config.WaterMonitor.allowedJobs ↔ waterMonitorAllowedJobs: an empty list uses configured Firejob jobs.
• Config.HeliBucket.allowedJobs ↔ heliBucketAllowedJobs: an empty list uses configured Firejob jobs.
• Config.RescueCushion.allowedJobs ↔ rescueCushionAllowedJobs: an empty list uses configured Firejob jobs.

Keep the corresponding requireOnDuty settings for job-based access. Gang membership is checked independently of job duty. No selector/default list migration is required; only add gang selectors if desired. This equipment access does not grant the new divider workflow to gangs: that workflow requires an on-duty configured Firejob job.

Replace sky_firejob/config/init.lua from the same download. If you customized sky_firejob/config/sv_functions.lua, retain your dispatch hook while merging its new leading readiness line:

if not Citizen.Await(SkyJobsReady) then return end

Do not copy an older init or hook file back over the updated dependency initialization.

Use the matching updated sky_jobs_base together with Firejob. The additional configuration update routing does not change Firejob setting keys, defaults, saved overrides, inventory setup or SQL requirements.

Truck pump connections required by the divider. The vehicle geometry fields in Config.Hose.vehicles retain their existing names and defaults. Configure each intended truck in /jobconfig → Firejob → Pump Panel → Vehicles (table hoseVehicles). In its row, use Hose Control access (pumpPanelAccess) to place the operating panel; this writes pumpPanelConfigured, pumpPanelX, pumpPanelY, pumpPanelZ and pumpPanelSize. Set pumpIntakeCount (up to 2) and place each enabled pumpIntakeN* connection; set pumpDischargeCount (up to 4) and place each enabled pumpOutletN* connection. Preserve your truck-specific coordinates. In plaintext mode merge these same panel/intake/outlet fields from the supplied vehicle definition and set their coordinates for that actual vehicle. Do not copy example coordinates from a different truck. A divider requires the configured supply connection and pump; installing the item alone does not configure a truck.

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.

Database. Firejob has no new database table, column or manual SQL migration in this release. Do not re-import or reset its existing database for the divider/nozzle update.

Equipment assets. Replace the four weapon metadata files sky_firejob/meta/pedpersonality.meta, weaponanimations.meta, weaponarchetypes.meta and weapons.meta together. Install sky_firejob/stream/w_am_hohlstrahlrohr.ydr and all five files in sky_firejob/stream/dividing_breeching/: sky_dividing_breeching.ydr, sky_dividing_breeching.ytyp, sky_dividing_tap_1.ydr, sky_dividing_tap_2.ydr and sky_dividing_tap_3.ydr. The EU nozzle now uses weapon name WEAPON_SKY_HOSE_EU and streamed model w_am_hohlstrahlrohr; the configuration choice stays "hohlstrahlrohr". Update any custom code that references the earlier development name WEAPON_SKY_HOHLSTRAHLROHR. Keep the original normal-nozzle model. Update the complete source folder and fxmanifest.lua from that same download even if you keep the normal nozzle and divider disabled.

Divider placement and items. Keep the divider disabled until your inventory has registered an item named fire_dividing_breeching. Copy sky_firejob/config/inventory/fire_dividing_breeching.png from the download to your inventory's item-image directory and associate it with that exact item name. Firejob supplies the icon but no provider-specific item-definition template; register the item using your inventory's normal item catalogue rather than replacing that catalogue or copying an unrelated Jobs Base item. Do not configure a second usable-item handler: Firejob registers its own through Sky Base. Once enabled, an on-duty configured Firejob member uses that item to place the divider; placement consumes one item and radial removal returns one. The former /dividing placement command is no longer available. At a configured operational fire vehicle, take its supply hose through the radial menu, connect it to the divider, take an attack hose from the same vehicle and connect an available branch. Operate the divider's valves and the supplying truck pump; the nearby checklist shows the remaining connection/valve steps. Close unused open outlets to avoid wasting water. Do not assume /jobconfig installs the inventory item, its icon or the streamed assets.

Billing provider. For Sky Billing, use the coordinated sky_base 1.45.0 and sky_jobs_base 1.48.0 updates and select Config.billing = "sky" in sky_base/config/config.lua. Explicit external providers stay supported through mode = "framework"; the local mode = "consent" remains available. The shared invoice catalogue and installment eligibility come from Jobs Base's Billing settings, not a new Firejob SQL table. Install/update Jobs Base's billing database using its own instructions before testing Fire invoices. Installments are only offered for eligible invoices; do not promise them for every provider or invoice.

Locales and interface assets. Replace sky_firejob/config/locales/* completely, preserving any custom wording separately, and install the NUI build in the same source-folder replacement. The global language continues to come from Sky Base's Config.locale. The new HUD artwork is included in the built interface; it is not an inventory-image install. This release does not newly add Hungarian as a language.

Manual ox_inventory example for the optional divider. If you enable Config.Hose.dividing, merge the following entry into ox_inventory/data/items.lua. This is an example, not a supplied installer or mandatory label/weight; choose those two values for your server. Keep consume = 0, omit a second client Use handler, and let Sky consume one divider only after placement succeeds and return it when it is removed. Copy sky_firejob/config/inventory/fire_dividing_breeching.png to ox_inventory/web/images/fire_dividing_breeching.png, then restart the inventory before the dependent Sky resources.

['fire_dividing_breeching'] = {
    label = 'Fire hose divider',
    weight = 1000, -- Example weight: choose your server value.
    stack = true,
    close = true,
    consume = 0,
},

For a different inventory, use its installed catalogue format and image path while retaining the same item ID and reusable Use behavior. The EU hose nozzle does not need an additional inventory weapon entry: the hose runtime equips the selected nozzle weapon.

Start your framework, database connector and configured providers first, then Base, Jobs Base and the updated job resources in dependency order. Reconnect clients. After a complete restart, check an on-duty Firejob character can open the tablet and mission editor without startup errors. Confirm the effective Billing and Vehicle Fires settings in /jobconfig if enabled; issue one test invoice and verify its confirmed payment appears in the correct society account. With the divider enabled, give one registered fire_dividing_breeching item to an on-duty Firejob character, place it by using the item, connect its supply and one attack hose, open the appropriate valves and test water flow; remove it through the radial menu afterward and confirm the inventory item is returned. Switch between normal and EU nozzles when hoses are not deployed and check the held/grounded nozzle model. Test a moving burning vehicle, a failed Mission Hub request with its retry action and an interface reload during mission editing. Existing job selectors should retain their previous access/duty behavior; test any optional gang selector with an actual member.

After deploying the matching Jobs Base and Firejob, save one Firejob setting, then one unrelated resource's setting. Confirm Fire equipment settings, item availability and Fire tablet access still follow the Firejob profile. Restart Firejob and recheck the saved value.

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.

These instructions cover sky_firejob 1.15.0 → 1.15.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.

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

No configuration values or Job Configurator setting keys are added, removed or reset by this hotfix. Keep your current settings and saved overrides. Hungarian uses the existing Config.locale = "hu" setting in sky_base/config/config.lua; leave your selected language unchanged if you do not want to switch. Update the matching Base, Jobs Base and installed resource locale folders together.

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

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.

Start your framework, database connector and configured providers first, then Base 1.44.1, Jobs Base 1.47.1 and the updated jobs/Crime. Reconnect clients. Open the Fire file explorer from the shared tablet and check hose aiming with another player, pump pickup and scenario-preview cleanup. If startup still fails, collect the first error and its preceding log lines together with the installed versions.

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

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

Merge the new SCBA interaction definition into sky_firejob/config/config.lua as described below. No SQL file, inventory definition or stream asset changes in this release, and no files outside source/ are removed or renamed.

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.

New plaintext block: In sky_firejob/config/config.lua, Config.Interactions.air_refill_station was previously absent because the SCBA refill point was defined internally. Add this full block after Config.FireStationBlip if you do not already have a Config.Interactions table:

Config.Interactions = {
    air_refill_station = {
        marker = {
            enabled = true,
            type = 1,
            offset = vector3(0.0, 0.0, 0.0)
        },
        blip = {
            enabled = false,
            sprite = 361,
            color = 1
        },
        npc = {
            enabled = false
        },
        interactionDistance = 1.8
    }
}

If your file already defines Config.Interactions, insert only the air_refill_station entry into that table; do not replace your other entries. These values preserve the previous SCBA defaults: marker on, blip/NPC off, range 1.8. Labels continue to come from the installed locale unless deliberately customized. No existing config block is removed.

With /jobconfig: After starting the updated resources, open Fire → Interactions → SCBA refill station (air_refill_station). This is an interaction definition with saved interaction overrides, not a new standalone switch. Review marker, blip, NPC, label and distance in that editor; an old plaintext edit does not replace saved overrides. Existing refill locations remain in the Fire station's Locations area and do not need to be recreated.

Station blips: Existing Config.FireStationBlip and Config.Jobs[*].blip retain their values. Complete saved names, prefixes, visibility and display settings now take effect. New/imported jobs without their own blip inherit Fire Station Blip; existing per-job overrides stay authoritative. Review each department's blip in the job editor.

Fallen trees: Config.TreeIncident has no new required field or changed default. Existing marker/blip settings now render, and interactionDistance now controls the radial range instead of the old hardcoded 5.0. Its shipped value remains 2.5. Review the existing Trees settings: treeEnabled, treeRequireOnDuty, treeInteractionDistance, treeBlipSprite, treeBlipColor, treeBlipScale, treeBlipLabel, treeMarkerType, treeMarkerSize, treeMarkerHeight, treeMarkerR, treeMarkerG, treeMarkerB, treeMarkerA. An explicitly empty blip label and zero color/alpha values remain meaningful. Keep your saved overrides; tree activation stays in the radial menu.

Automatic Missions: Existing scenarioAutomaticMissions rows keep their mission keys when saved, including newly listed or differently ordered missions. No new setting key, mission import or data reset is needed. Reopen Automatic Missions, review the intended enabled states and save once if a previous attempt failed or affected the wrong row. Unrelated mission settings remain unchanged.

No Config.Hose.vehicles panel/intake/outlet changes, incident/reward configuration changes, extinguisher access-policy changes or breathing-bottle storage migration are introduced by 1.14.0 → 1.15.0. The earlier bottle retrieval and SQL instructions apply only when upgrading through 1.14.0 from an older version.

Optional performance diagnostics

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

Keep source/ and fxmanifest.lua from the same download even when diagnostics are disabled. Profiler processing changes only source Lua and the manifest. If an older profiler package changed public files outside source/, restore those files once from the clean current download and reapply your own customizations.

No Fire SQL migration, table/column type/default change, new item, inventory image, streamed model, hose-vehicle coordinate edit or permission-ID migration is required for this release. Keep existing saved missions, bottle storage and department data. The SCBA interaction block is configuration; it does not add another inventory item or require replacing refill locations.

Start providers/framework, Base 1.44.0, Jobs Base 1.47.0 and Fire 1.15.0, then reconnect. Check the installed versions and resolve startup errors. Change one department's station blip, then change an SCBA point's label/marker/NPC and range; save/reopen and verify that its existing refill action still works.

During a test tree incident, check the saved scene visuals and radial range, duty loss, clearing phase and completion. Nearby unrelated map icons must remain. In Automatic Missions, change one mission's enabled state, save, reopen and restart; verify the same mission remains selected and other rows retain their settings. Check keyboard selection in tablet dropdowns. These are installation checks for your actual provider and game environment, separate from automated source tests.

Before stopping the old version, remove every breathing bottle from vehicle bottle storage. Old live vehicle-state contents are not imported into the new storage. Already lost contents cannot be reconstructed.

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

Use the matching 1.14.0 package. Delete the old sky_firejob/source/ directory completely and insert the new directory. Replace sky_firejob/fxmanifest.lua from the same package. Refresh the entire sky_firejob/config/locales/ tree and merge your custom translations back. Replace sky_firejob/import.sql and merge the config/config.lua access-policy comment and settings described here. Merely copying SQL does not execute it.

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

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

Path: sky_firejob/config/config.lua, Config.InteriorExtinguishers.allowedJobs.

Old line:

allowedJobs = {},

New line:

allowedJobs = {}, -- Empty allows every job; requireOnDuty still applies.

The value is unchanged; behavior changes. Previously an empty list fell back to configured Fire jobs. It now accepts any job subject to duty rules. The unchanged relevant shipped values are:

requireOnDuty = true,
noDutyJobs = { "unemployed" },
allowedJobs = {},

noDutyJobs is checked first: listed jobs bypass both the duty requirement and the normal allowed-job filter. This is an explicit exception list, not just another default allowed-job list. To allow unrestricted pickup/restocking use allowedJobs = {} and requireOnDuty = false. To retain a department-only policy, provide your actual department job names in allowedJobs and review noDutyJobs; do not silently remove an intentional exception.

Exact /jobconfig resource/section: sky_firejob, Interior Extinguishers -> General -> Access. Keys: interiorExtinguishersAllowedJobs, interiorExtinguishersRequireOnDuty, interiorExtinguishersNoDutyJobs. The first and third are job rows converted to/from string lists. Saved values remain overrides; the empty saved list gets the new empty-list meaning. Placement and maintenance permissions are unchanged. No new setting key is introduced.

Optional Lore Billing

With Base 1.43.0, use the existing provider setting in sky_base/config/config.lua: change Config.billing from "auto"/your selected provider to "lore" for an explicit choice, or keep "auto" when Lore should be detected. Start lore-billing before Sky Base so automatic detection sees it. Install/retain Lore's own documented setup separately; Fire does not install the provider or its schema.

Fire's existing shipped default in sky_firejob/config/config.lua remains Config.Billing.mode = "consent". To send through Lore, deliberately select "framework" instead. This is an optional setup choice; the Fire default remains unchanged.

Without /jobconfig:

Config.Billing = {
    enabled = true,
    mode = "framework", -- previously "consent" if using the shipped default
    range = 6.0,
    maxAmount = 50000,
    reasons = {} -- Preserve your own existing presets.
}

This block shows the existing defaults with only the mode switched; keep custom range, maximum and reasons instead of replacing them. With /jobconfig, set Billing mode to Framework using exact key fireBillingMode; verify fireBillingEnabled is true. A saved fireBillingMode override takes precedence over a plaintext edit. billing.mode is not the Fire setting key.

Fire validates staff access, target distance, integer amount and reason. The configured department needs a valid society account. The new Base adapter relays a society invoice through the online issuing player's Lore client context and needs issuer and recipient online. Dispatch is not a provider persistence acknowledgment; the Sky return value alone does not confirm a stored invoice. Verify actual invoice delivery in Lore during the installation check.

The verified Lore version requires Qbox (qbx_core), ox_lib, oxmysql and Renewed-Banking. Install/start those dependencies before Lore. The Sky adapter does not add another framework bridge to the external provider.

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.

New table, created automatically or with this manual SQL block:

CREATE TABLE IF NOT EXISTS `sky_fire_air_storage` (
    `plate` VARCHAR(64) NOT NULL,
    `slots` LONGTEXT NOT NULL,
    PRIMARY KEY (`plate`)
) ENGINE=InnoDB;

Neither column has a default; neither path forces charset/collation. Existing Config.AutoExecuteQuery = true creates the table on startup. With false, run that single CREATE TABLE statement manually before starting the updated Fire resource. /jobconfig does not install SQL.

Old entity-state storage is deliberately not imported. Owners must retrieve bottles before the first update/restart of the old implementation if they want to preserve those live contents. Already lost old contents cannot be reconstructed. New storage uses the uppercase plate with all whitespace removed; stable unique plates matter. Changing the plate selects different storage; two vehicles with the same normalized plate share that storage identity. Existing vehicle model/slot-count configuration is unchanged, and slots temporarily above capacity are retained in SQL.

No Config.Hose.vehicles panel/intake/outlet edits, incident/reward changes, inventory item additions, new images, stream files or permission-ID migration occur in this release. Complete older migrations separately only when upgrading from an earlier version.

Start providers/framework, Base 1.43.0, Jobs Base 1.46.0 and Fire 1.14.0, then reconnect and check SQL startup errors. Return the retrieved bottles after startup. Store a partly used bottle in a non-first slot, restart the resource and then server, respawn the same plate and retrieve it once. Check pressure and another player attempting the same slot. Test an ordinary job against your selected extinguisher access policy. Check invoice receipts and, if selected, actual delivery in Lore. These are installation checks to perform on your server.

These instructions cover 1.12.0 → 1.13.0. Complete earlier migrations first if upgrading from an older version. Stop the server and back up the database, resource, custom configuration and saved creator/configurator data. Update sky_base to 1.42.0, then sky_jobs_base to 1.45.0, including their own migration and inventory steps, before Firejob.

Install the matching 1.13.0 download. Delete and reinsert sky_firejob/source/*; replace sky_firejob/fxmanifest.lua, sky_firejob/import.sql and the complete sky_firejob/config/locales/*. Merge the Billing block into your customized sky_firejob/config/config.lua. Preserve other customized configuration, saved scenarios and assets. There are no removed or renamed customer paths outside source/ in this release.

Use source/* and fxmanifest.lua from the same download even with diagnostics disabled. Profiler builds may instrument only Lua inside source/ and the manifest. If an older profiler package changed public files, restore those once from the clean new package and reapply your customizations. The new invoice graphics and Explorer UI are included in source/*; no separate Fire stream or inventory assets are added.

Merge the new complete block into sky_firejob/config/config.lua; Config.Billing did not exist in 1.12.0:

Config.Billing = {
    enabled = true,
    mode = "consent",
    range = 6.0,
    maxAmount = 50000,
    reasons = {}
}

enabled allows invoices; mode = "consent" lets the recipient choose Cash or Card or decline; range is the maximum recipient distance in metres; maxAmount caps a whole-number invoice total. An empty reasons list means there are no preset reasons: staff can enter a reason manually. To add presets, use entries such as { reason = "Service description", amount = 100 }; multiple presets and notes can be combined.

With /jobconfig, open Fire → Billing and review fireBillingEnabled, fireBillingMode, fireBillingRange, fireBillingMaxAmount and fireBillingReasons. Their defaults are respectively true, "consent", 6.0, 50000 and an empty list. Saved overrides remain effective. Development-era "instant" values automatically become "consent"; no automatic debit mode remains. "framework" explicitly uses the billing provider selected in Sky Base. Verify each issuing job's existing society account; internal payments need the configured banking integration to credit that account. Issuing an external invoice does not prove it was paid.

File Explorer and report access

The Fire tablet now opens File Explorer, with Incident Reports as a directory. The existing Fire job, duty and tablet-app restrictions apply; no new Fire permission ID is required. Review restrictions for fire_files and fire_reports if your server limits tablet apps by rank. Reports received from another job appear in Shared Documents and remain read-only. Save an owned incident report before using Print or Share. Share explicitly selects registered recipient jobs, and removing a recipient revokes its digital access. Existing per-report recipient lists are retained; old job-wide record-sharing rules no longer grant access. Check the recipients of existing reports rather than deleting or reimporting them. Selected civilians are linked by their verified character identity; older free-text names remain descriptive.

The Explorer itself needs no additional Fire configuration, item, asset or Creator import after installing the coordinated release and SQL. DOJ is optional: its documents appear only when the corresponding resource and authorized shares are available. Normal Fire reports, sharing and printing do not require DOJ.

For printing, complete the Jobs Base 1.45.0 printer and inventory update: register job_document with its supplied image in a metadata-capable inventory, retain or configure an accessible printer, and provide its configured paper. The printed item is a permanent copy of the saved report; revoking a digital share does not recall an already printed copy. Optional document images are configured in Jobs Base's Config.Printers.documentAppearance or the job's /jobconfig document-appearance extension, not in Fire's Config.Reports.

No Fire job lists, incident/reward settings or Config.Hose.vehicles fields change in this release. Keep existing pump panel, intake and outlet calibration. The oil-spill setting only enables spills, slipping and cleanup; automatic collision or wear triggers still require Sky Mechanic or another connected resource.

Optional performance diagnostics

The optional profiler is disabled by default. To make a support recording, put setr sky_profiler 1 in server.cfg before the Sky ensure lines and restart. Run profiler record 1000 in the server console, wait until profiler status reports completion, then run profiler saveJSON sky-release-profile.json. Share that file only when requested. Set setr sky_profiler 0 and restart to disable the extra information. This is not a /jobconfig setting and does not start recordings or upload data automatically.

SQL: The Fire report table needs a wider report ID and separate report/sharing revision counters. With Config.AutoExecuteQuery = true, allow the normal startup migration to finish. If automatic migration is disabled, run this non-destructive block from sky_firejob/import.sql against the existing database before starting Firejob:

ALTER TABLE `sky_fire_reports`
    MODIFY `report_id` VARCHAR(40) NOT NULL,
    ADD COLUMN IF NOT EXISTS `revision` INT NOT NULL DEFAULT 1,
    ADD COLUMN IF NOT EXISTS `share_revision` INT NOT NULL DEFAULT 1;

The old report_id was VARCHAR(32); both revision columns are new. Existing reports and explicit recipients remain in place. Do not clear the table. Also complete the Jobs Base 1.45.0 migrations for shared and printed documents.

Items and assets: Fire adds no standalone item, image or stream file. Optional report printing uses the Jobs Base job_document item, supplied image, metadata-capable inventory, accessible printer and its paper supply. Invoice payment uses its own on-screen receipt and does not require the report-printing item. Keep existing Fire inventories and scenario data; no Fire Creator import is required.

Start database, framework and configured inventory/provider resources first, then Base 1.42.0, Jobs Base 1.45.0, Firejob 1.13.0 and the remaining updated jobs. Resolve startup/SQL errors before allowing normal play. Confirm Fire Explorer opens, Incident Reports retains existing records, and app restrictions still apply. Save and edit a report with two authorized users: a stale save should show a conflict while retaining the draft. Share a saved report with a second job, read it there, revoke access and check that the digital copy disappears. Print a report through an available printer and open the resulting item if printing is enabled. Test Cash, Card, decline and insufficient funds with two players, checking the society balance and Boss Menu payment entry; test the external provider separately if selected. Check scenario editing and fire-extinguisher pickup/restock after reconnecting.

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

Install the matching 1.12.0 download. Update every path in Changed Files, delete and reinsert sky_firejob/source/*, and replace sky_firejob/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.

Merge these changes into sky_firejob/config/config.lua. With /jobconfig, use Fire → Settings → Fire system; the exact stored keys are listed below. Saved overrides remain authoritative. Appearance controls do not change smoke-poisoning strength.

The ambient-sound switch remains enabled by default (fireSoundFireAmbientEnabled). Wind choices are none, gentle, normal and strong; the new choice applies to packaged smoke. Add the new ignition table and render values, and change the two sound values inside their existing parents:

Config.FireSystem.render.flameScaleMultiplier = 1.0
Config.FireSystem.render.smokeScaleMultiplier = 1.0
Config.FireSystem.render.smokeDensityMultiplier = 1.0
Config.FireSystem.render.smokeWindResponse = "normal"
Config.FireSystem.ignition = {
    startScale = 0.2,
    growthSeconds = 40.0,
}
Config.FireSystem.effects.sounds.fireAmbient.volume = 0.65
Config.FireSystem.effects.sounds.fireAmbient.range = 40.0

The shared Fire defaults also add client-wide visual limits of 96 flame sources and 24 smoke sources, exposed as fireMaxFlameSources and fireMaxSmokeSources. File-based servers may override Config.FireSystem.render.maxFlameSources and Config.FireSystem.render.maxSmokeSources; otherwise the shared defaults supply them. These limit visible effects, not the number of saved incidents. Flame and smoke visibility distances remain 1000 m in the shipped file; the existing shared visibility setting controls both when /jobconfig is used.

The new sky_firejob/config/sv_functions.lua supplies the Dispatch hook. Install the complete file. Its default continues to send alerts through Jobs Base, so no external provider is required. Only customize Config.Functions.sendDispatch if forwarding alerts to another system; retain the documented success/failure result and handle that provider's alert cleanup. This Lua function remains file-based and is intentionally outside /jobconfig.

Choose flame and smoke variants in /skyfiremenu or in the mission creator. Existing saved missions keep their choices/default profiles; do not delete or reimport them to obtain the new selectors. Starting size and growth duration affect newly created menu fires. No job list, incident-reward setting or hose-vehicle geometry changes in this release.

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.

No SQL migration or new inventory item is required. Install every new particle file listed in Changed Files and the complete source/* folder, which includes the fire audio and its attribution. Keep existing missions, hydrants, vehicle/hose setup and saved configurator values. Additional languages translate the new effect controls; older text without a translation uses English.

Restart the database, framework and any edited inventory first, then Base, Jobs Base and the installed job resources. Confirm 1.12.0 and resolve startup errors before admitting players. Create a small growing fire, select each flame/smoke style and verify ground and wall contact. Check directional sound at different distances, then adjust sound and smoke settings through /jobconfig. Test a large incident with water jets, smoke exposure and extinguishing. Edit and reload a saved mission to confirm its effect choices remain intact. If using a custom Dispatch provider, test both individual fires and missions.

Update Base to 1.40.0 and Jobs Base to 1.43.0 before installing sky_firejob 1.11.0. These instructions cover 1.10.0 → 1.11.0; complete earlier migrations first when upgrading from an older version. Stop the server and back up the resource, database, customized files and saved configurator/creator data.

Install the matching 1.11.0 package. Update every path in Changed Files, delete and reinsert sky_firejob/source/*, and replace sky_firejob/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.

No public configuration values, blocks, items or Fire-specific database schema change. Keep existing /jobconfig overrides, mission settings, oil-spill behavior and HUD preferences. The HUD editor input correction and oil checks require the matching new runtime and UI files, not new settings.

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.

No Fire-specific migration or new items are required. Preserve mission and creator data. Complete any shared Jobs Base 1.43.0 database migrations as part of the dependency update; they do not require clearing Fire data.

Confirm version 1.11.0. Open the HUD editor, drag and save an element, then close it and confirm normal player/camera controls return. Test an oil spill with a nearby player, including entering its area quickly and returning after revival. Check images, saved missions and startup logs.

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

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

Required profiler files

For the profiler update, replace the complete sky_firejob/source/* tree and sky_firejob/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.

No values or blocks in sky_firejob/config/config.lua change in this release. Keep your custom configuration and saved /jobconfig settings. Replace all Fire locales and update Jobs Base to 1.42.0 for the matching dispatch explanations.

If a mission starts with a dispatch warning, it is already running. Use its active mission controls to manage or stop it. Follow the displayed instructions: open /missioncreator, select the named mission, and check its receiving department and response plan. Review the plan under that department in /jobconfig; dispatch-center coverage is maintained in sky_jobs_base/config/config.lua. Resolve the cause before starting another copy of the mission.

Optional performance diagnostics

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

setr sky_profiler 1

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

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

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

No SQL schema, inventory item, image, or provider-secret change is introduced. Keep saved mission definitions, active operational data, and department settings. Replace all Fire locales so the new guidance is available in your selected language.

Start a correctly configured mission and check its dispatch. In staging, use a mission with an invalid response-plan selection to verify that the mission remains manageable and the warning names the cause and repair steps. Correct the selection and confirm the next dispatch can be created.

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

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

No public config.lua value or new /jobconfig setting is introduced in this patch. Keep your saved automatic-mission enablement, interval and chance values. Changes to the interval now reschedule the pending check, disabling automatic missions cancels it, and the current chance is used when a check becomes due.

For a job shared with Ambulance or another service, update Jobs Base to 1.41.1 and review Config.PrimaryJobGroups in sky_jobs_base/config/config.lua using its own update guide. This global Jobs Base setting selects the shared duty and organization owner; it is not a Fire /jobconfig setting. Keep each service's existing station catalogs, and check the chosen owner's Dispatch configuration and each scenario's responsible job and response-plan selection.

Replace all sky_firejob/config/locales/* for the clearer hub/local status labels. No SQL schema, inventory item, image, stream asset or provider secret change is required. Preserve scenarios, incidents, equipment data and saved configuration.

Start providers, Base, Jobs Base and Fire in that order. Change an automatic-mission interval, disable and re-enable the scheduler, verify the selected scenario response plan and check shared-job duty behavior. Confirm the hub/local labels in the scenario manager.

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

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

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

Config.Keybinds = {
    fireInteriorExtinguishersControl38 = "E",
    fireEditorControl174 = "LEFT",
    fireEditorControl175 = "RIGHT",
    fireEditorControl14 = "MOUSE_WHEEL:IOM_WHEEL_DOWN",
    fireEditorControl15 = "MOUSE_WHEEL:IOM_WHEEL_UP",
    fireEditorControl177 = "BACK",
    fireWaterMonitorControl172 = "UP",
    fireWaterMonitorControl241 = "MOUSE_WHEEL:IOM_WHEEL_UP",
    fireWaterMonitorControl173 = "DOWN",
    fireWaterMonitorControl242 = "MOUSE_WHEEL:IOM_WHEEL_DOWN",
    fireWaterMonitorControl174 = "LEFT",
    fireWaterMonitorControl175 = "RIGHT",
    fireWaterMonitorControl24 = "MOUSE_BUTTON:MOUSE_LEFT",
    fireWaterMonitorControl25 = "MOUSE_BUTTON:MOUSE_RIGHT",
    fireWaterMonitorControl177 = "BACK",
    fireWaterMonitorControl202 = "ESCAPE",
    fireEditorControl24 = "MOUSE_BUTTON:MOUSE_LEFT",
    fireEditorControl199 = "P",
    fireEditorControl200 = "ESCAPE",
    fireEditorControl202 = "ESCAPE",
    fireEditorControl322 = "ESCAPE",
    firePropIgnitionControl177 = "BACK",
    firePropIgnitionControl38 = "E",
    fireEditorControl25 = "MOUSE_BUTTON:MOUSE_RIGHT",
    fireEditorControl21 = "LSHIFT",
    fireEditorControl36 = "LCONTROL",
    fireEditorControl32 = "W",
    fireEditorControl33 = "S",
    fireEditorControl34 = "A",
    fireEditorControl35 = "D",
    fireEditorControl44 = "Q",
    fireEditorControl38 = "E",
    fireEditorControl45 = "R",
    fireEditorControl191 = "RETURN",
    heliBucketAttachKey = "E",
    heliBucketDumpKey = "X",
    deckGunSprayGamepadKey = "PAD_ANALOGBUTTON:L1_INDEX",
    deckGunSprayKey = "MOUSE_BUTTON:MOUSE_RIGHT",
    firetruckHudToggleKey = "",
    firetruckHudCursorKey = "LCONTROL",
}

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

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

Add the new Config.Hose.vehiclePumpBehavior.engineDamageEnabled path in sky_firejob/config/config.lua:

Config.Hose.vehiclePumpBehavior.engineDamageEnabled = false

With /jobconfig, review the saved Hose → Vehicle pump behavior → Engine damage setting. Saved overrides take precedence over the default; explicitly enable it only if pump overheating and dry running should damage the vehicle. Without /jobconfig, maintain the file value. Existing neighboring values remain warningTemperature = 100.0, criticalTemperature = 115.0, damageTemperature = 110.0, and maxEngineDamagePerSecond = 12.0; temperature warnings and pump behavior still operate when engine damage is disabled. No incident job list, reward, hose model offset, or dispatch-recipient value changes in this release.

Air-cylinder storage still requires its configured bottle item and pressure saving. The refill-station feature itself may now be disabled. Keep your existing cylinder item, pressure-saving and foam-canister settings, and check their effective saved /jobconfig overrides. Foam inventory use now follows the same existing refill validation and cancellation flow. No replacement item name or new refill setting is required. Config.UseJobConfigurator, command permissions and Config.AutoExecuteQuery were only moved to the top of the file; their defaults are unchanged.

No new Fire SQL schema, inventory item, image, production stream asset, or secret is introduced. Preserve existing cylinders and pressure metadata, configured foam items, incidents and equipment data. Replace the manifest and full source folder together; the updated manifest loads the generated Fire defaults and shared key/synchronization helpers. Install Base 1.38.0 too for the Jaksam slot correction when using that inventory.

Restart Base, Jobs Base and Fire. Rebind helicopter, editor, HUD and deck-gun actions and test both mouse and controller spraying. Join after a hydrant supply hose is connected and confirm both nearby players see it. Remove equipment during synchronization and confirm it stays removed. With pressure saving and the bottle item enabled, open air storage while refill stations are disabled. Use and cancel a foam refill. Test pump overheating/dry running with engine damage disabled, then explicitly enabled, and check the effective saved setting.

Install Base 1.37.0 and Jobs Base 1.40.0, stop the server, and back up the complete resource, Job Configurator tables, configured Fire missions, Fire report data, and deliberate edits to pump, scenario, dispatch, SCBA, and external-tablet settings.

Install 1.8.0 as one clean package. Its manifest, frontend, locales, shared effects, and source files must match.

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

Mission entries below Config.FireScenarioCreator.randomTrigger.missions now support dispatchJobs in addition to key, enabled, minOnDuty, and jobs:

missions = {
    {
        key = "example_mission",
        enabled = true,
        minOnDuty = 0,
        jobs = { "fire" },
        dispatchJobs = { "fire" }
    }
}

Dispatch recipients resolve in this order:

1. A non-empty mission dispatchJobs list.
2. The global Config.FireScenarioCreator.dispatch.jobs list.
3. Every configured Fire job when both lists are empty.

The global dispatch list and other shipped defaults do not change. Job Configurator migration initializes existing mission dispatchJobs from each mission's current jobs value. Review every saved mission after the update; an explicitly empty list intentionally activates the fallback chain.

No Fire SQL schema change, new inventory item, image, or production stream asset is required. Existing Fire reports, scenarios, SCBA data, and equipment configuration are reused. The new regular-fire export is a trusted server integration and requires no database row or client event exposure.

Start Base, Jobs Base, and Fire in order. Confirm an under-staffed player cannot ignite a configured prop fire and an adequately staffed player can. From a trusted server resource, call the regular-fire export with valid and invalid data and verify validation plus synchronization. Test pump controls at configured panel/intake/outlet offsets, nozzle/deck-gun/decal/water-monitor visibility across clients, and low idle cost without an active operation. Connect a hydrant to the selected pump while briefly leaving detection range. Verify mission-specific, global, and all-Fire-job dispatch fallbacks; exact-slot SCBA restore after a config refresh; LB Tablet/RoadPad reloads; long-report scrolling; pump-panel focus release; automatic tree incidents; and a single creator refresh after saving.

Before updating, install Base 1.36.0 and Jobs Base 1.39.0, stop the server, and back up the resource, intentional config edits, Job Configurator tables, and all sky_fire_* tables.

Install 1.7.0 as one clean package. Its UI, runtime, locales, config defaults, and schema must match.

Delete and reinsert the complete resource. At minimum replace config/config.lua, import.sql, the complete config/locales and source directories, and the built UI supplied with the package.

Add the complete new report catalogue, which was absent in 1.6.1:

Config.Reports = {
    types = {
        "Structure Fire", "Vehicle Fire", "Wildfire", "Hazmat", "Rescue", "Alarm", "Other"
    },
    statuses = {
        "Active", "Contained", "Under Investigation", "Cleared"
    },
    hazards = {
        "Smoke", "Open Flame", "Structural Instability", "Hazardous Materials",
        "Electrical Hazard", "Fuel Leak", "Traffic", "Confined Space"
    },
    actionsTaken = {
        "Primary Search", "Secondary Search", "Fire Suppression", "Ventilation", "Rescue",
        "Medical Assistance", "Evacuation", "Overhaul", "Scene Secured"
    },
    equipmentUsed = {
        "SCBA", "Thermal Camera", "Attack Line", "Supply Line", "Foam Line",
        "Hydraulic Rescue Tools", "Ladder", "Water Monitor", "Fire Extinguisher"
    }
}

/jobconfig does not manage Config.Reports; edit these plaintext lists to match department procedures. Normal configured Fire jobs still come from Config.Jobs or Job Configurator. Report sharing uses the existing Jobs Base Share configuration for each job and is separate from the catalogue lists. Do not add a partner job to Config.Reports; select it in the sharing settings instead.

With Config.AutoExecuteQuery = true, the built-in migration updates report ownership and sharing. Otherwise execute the complete bundled import.sql, including:

ALTER TABLE `sky_fire_reports`
    ADD COLUMN IF NOT EXISTS `owner_job` VARCHAR(50) NULL AFTER `report_type`,
    ADD COLUMN IF NOT EXISTS `shared_with_jobs` TEXT NULL AFTER `owner_job`,
    ADD INDEX IF NOT EXISTS `idx_owner_updated` (`owner_job`, `updated_at`);

UPDATE `sky_fire_reports` reports
INNER JOIN `sky_jobs` jobs ON jobs.id = reports.job_id
SET reports.owner_job = jobs.job
WHERE reports.owner_job IS NULL OR reports.owner_job = '';

New installations create owner_job VARCHAR(50) NULL and shared_with_jobs TEXT NULL in sky_fire_reports and include KEY idx_owner_updated (owner_job, updated_at). The schema inherits the active database charset and collation. Existing rows without a matching sky_jobs.id cannot be backfilled automatically and should be reviewed before enabling sharing.

No new inventory item, image, stream asset, or provider credential is required.

• The console reports Base 1.36.0, Jobs Base 1.39.0, and Fire 1.7.0 in that order.
• sky_fire_reports contains owner_job, shared_with_jobs, and idx_owner_updated, and existing rows have the expected owner.
• Each configured report type, status, hazard, action, and equipment value appears and is searchable.
• The owning job can edit its report while a selected partner job sees the same report read-only with source context.
• Current-scene capture, evidence, people, hazards, actions, equipment, and report persistence work after restart.
• Mission form values/transforms autosave and vehicle-fire scale remains configured when progression is disabled.
• Doorless and two-door rescue cases work and repaired glass/doors synchronize.
• Storing equipped SCBA preserves bounded remaining pressure and clears active HUD/server state.
• Water-monitor and helicopter-bucket props require one-time server authorization.
• Unauthorized players cannot see or use the placeable-extinguisher pickup action.

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

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

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

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

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

• Base 1.35.1, Jobs Base 1.38.1, and Fire 1.6.1 start in order.
• Creator, pump, dispatch, mission, and tablet labels fall back to readable English when a translation key is absent.

Update Base to 1.35.0 and Jobs Base to 1.38.0. Stop the server; back up the complete Fire resource, saved scenario drafts/published scenarios, Job Configurator data, and all Fire tables.

Install 1.6.0 as one complete package. The pump/HUD logic, response-plan UI/runtime, generated defaults, locales, manifest, and SQL migration must match.

Delete and reinsert the complete resource. Replace README.md, config/config.lua, all config/locales, fxmanifest.lua, import.sql, source, and the built UI. No new item image or production stream file is added.

Replace the old flat Config.CommandPermissions.skyfiremenu = { "god", "superadmin", "admin" } with:

Config.CommandPermissions.skyfiremenu = {
    groups = { "god", "superadmin", "admin" },
    jobs = {}
}

groups uses the existing framework/admin permission bridge. An empty jobs list grants no job-based access. Each added row must be an exact current framework job name; the server rechecks the same combined permission for the command and creator callbacks. Job permission does not implicitly include every configured Fire job.

Replace only the hydrant-output member inside Config.Hose.vehiclePumpBehavior.hydraulics:

-- 1.5.0: remove this field
hydrantSupplyGpm = 1600.0,

-- 1.6.0: add this field
hydrantSupplyLitersPerSecond = 100.0,

Do not rename tankSupplyGpm or pumpSupplyGpm. For /jobconfig, remove hoseVehiclePumpHydraulicsHydrantSupplyGpm and use hoseVehiclePumpHydraulicsHydrantSupplyLitersPerSecond; the shipped migration converts a saved old-only override by × 0.0630902, preserves an already-present new value, and removes the old key.

Response-plan requirements are saved per scenario, not in config.lua or /jobconfig. Select an exact plan from the current Jobs Base catalog. Enabled stale/removed plan pairs are rejected; no requirement preserves the existing scenario minOnDuty path, and imported Hub scenarios start disabled.

Enhanced pump panels now initialize explicit intake and tank-to-pump valves closed and keep controls locked while the pump is off. Simple panels retain their compact defaults. No configuration migration is needed for those state semantics.

With automatic migration disabled, execute the complete new import.sql. The exact release migration is:

ALTER TABLE `sky_fire_oil_spills`
    MODIFY COLUMN `source_plate` VARCHAR(64) NULL;

UPDATE `sky_jobs_configurator_settings`
SET `settings` = JSON_REMOVE(
        JSON_SET(
            `settings`,
            '$.hoseVehiclePumpHydraulicsHydrantSupplyLitersPerSecond',
            CAST(JSON_UNQUOTE(JSON_EXTRACT(
                `settings`,
                '$.hoseVehiclePumpHydraulicsHydrantSupplyGpm'
            )) AS DECIMAL(20, 6)) * 0.0630902
        ),
        '$.hoseVehiclePumpHydraulicsHydrantSupplyGpm'
    ),
    `revision` = `revision` + 1
WHERE `config_key` = 'sky_firejob'
    AND JSON_VALID(`settings`)
    AND JSON_CONTAINS_PATH(`settings`, 'one', '$.hoseVehiclePumpHydraulicsHydrantSupplyGpm')
    AND NOT JSON_CONTAINS_PATH(`settings`, 'one', '$.hoseVehiclePumpHydraulicsHydrantSupplyLitersPerSecond')
    AND JSON_UNQUOTE(JSON_EXTRACT(
        `settings`,
        '$.hoseVehiclePumpHydraulicsHydrantSupplyGpm'
    )) REGEXP '^-?[0-9]+([.][0-9]+)?$';

UPDATE `sky_jobs_configurator_settings`
SET `settings` = JSON_REMOVE(`settings`, '$.hoseVehiclePumpHydraulicsHydrantSupplyGpm'),
    `revision` = `revision` + 1
WHERE `config_key` = 'sky_firejob'
    AND JSON_VALID(`settings`)
    AND JSON_CONTAINS_PATH(`settings`, 'one', '$.hoseVehiclePumpHydraulicsHydrantSupplyGpm')
    AND JSON_CONTAINS_PATH(`settings`, 'one', '$.hoseVehiclePumpHydraulicsHydrantSupplyLitersPerSecond');

Automatic migration errors are intentionally visible and stop an unsafe silent reset. Manual SQL leaves an invalid old-only numeric value in place for explicit repair. The schema keeps ENGINE=InnoDB where required and inherits database charset/collation. There are no new tables or item definitions.

• Base 1.35.0, Jobs Base 1.38.0, and Fire 1.6.0 start in that order without migration errors.
• Group-only and exact job-based /skyfiremenu access match the new permission table, and unauthorized creator callbacks fail.
• Scenario create/copy/update accepts a current response plan, rejects a removed/stale pair, and automatic missions honor its minimum crew; a scenario without a plan still uses minOnDuty.
• Existing hydrant and portable-pump connections still work, enhanced pump valves start closed, controls stay locked while off, and an open connected intake changes supply, HUD, tank fill, or external vehicle transfer.
• Configured Fire job/duty rules apply to hose, pump, extinguisher removal, tablet, carry, and cross-resource Fire actions.
• The old saved GPM key is gone, its old-only value was converted by 0.0630902, and an existing new L/s value was preserved.
• sky_fire_oil_spills.source_plate is VARCHAR(64).

Stop the server after both dependencies are current. Back up the complete Fire resource, custom clothing values, shops, hose vehicle entries, cleanup access, reward settings, and saved /jobconfig overrides.

Install one complete 1.5.0 package. The mask item, clothing checks, HUD, locale, generated settings, server validation, hose runtime, manifest, and image must match.

Replace fxmanifest.lua, source, the complete built UI, and config/locales. Copy config/inventory/fire_protective_mask.png. Merge the public values below into the new config/config.lua or configure their saved equivalents after startup.

Add the mask to each intended Config.Jobs[*].shop; this row was absent in 1.4.0:

{ name = "fire_protective_mask", label = "Wildfire Protective Mask", price = 175 },

Add the complete shipped protective-mask block at Config.FireSystem.protectiveGear.breathing.protectiveMask:

protectiveMask = {
    enabled = true,
    smokeExposureMultiplier = 0.15,
    toxicSmokeExposureMultiplier = 0.85,
    maskOverlay = {
        enabled = false,
        forceFirstPerson = false
    },
    item = {
        enabled = true,
        name = "fire_protective_mask"
    },
    requiredComponents = {
        {
            component = 1,
            gearKey = "mask",
            label = "wildfire protective mask",
            drawable = 46,
            texture = 0
        }
    },
    femaleRequiredComponents = {
        {
            component = 1,
            gearKey = "mask",
            label = "wildfire protective mask",
            drawable = 46,
            texture = 0
        }
    }
},

This entire shipped table is Absent -> New. requiredProps and femaleRequiredProps are supported optional fields and exact /jobconfig keys, but they are not shipped config rows. Omit them when no prop is required, or add the following explicit empty defaults with identical behavior:

Config.FireSystem.protectiveGear.breathing.protectiveMask.requiredProps = {}
Config.FireSystem.protectiveGear.breathing.protectiveMask.femaleRequiredProps = {}

A multiplier of 0.15 leaves 15% of normal smoke exposure. The 0.85 toxic multiplier deliberately leaves 85% of toxic exposure; SCBA remains required. The mask does not change heat exposure.

Apply the remaining public config changes:

Config.OilSpills.cleanup.allowedJobs only adds non-Fire jobs. An empty {} means no additional jobs, while every configured Fire job remains authorized. Existing Config.OilSpills.cleanup.requireOnDuty = true applies to both configured Fire jobs and extra whitelist entries.

Replace the complete reward block so the four new switches stay beside their existing neighbors:

Config.SocietyRewards = {
    fire = {
        enabled = true,
        scenarioEnabled = true,
        jobs = {}
    },
    oil = {
        enabled = true,
        scenarioEnabled = true,
        jobs = {}
    },
    tree = {
        enabled = true,
        scenarioEnabled = true,
        jobs = {}
    },
    rescue = {
        enabled = true,
        scenarioEnabled = true,
        jobs = {}
    }
}

Each scenarioEnabled field is Absent -> New: true. enabled controls all payments; scenarioEnabled separately gates Mission Creator objective payments. Empty jobs first uses the applicable incident recipients and then all configured Fire jobs: mission objectives use Config.FireScenarioCreator.dispatch.jobs, ordinary tree incidents use Config.TreeIncident.dispatch.jobs, and ordinary fire, oil, and rescue completions use Config.FireSystem.dispatch.jobs. Default amounts remain fire 250, oil 150, tree 500, and rescue 750 unless saved job rows override them.

For hose vehicles, pumpPanelConfigured is an editor-managed hidden flag. A legacy entry with no flag is inferred as configured only when pumpPanelX, pumpPanelY, and pumpPanelZ all exist and at least one coordinate or pumpPanelSize differs from the default offset/size. Every other absent flag, and every explicit false, validly falls back to the vehicle area. For a precise target, open the vehicle card's Hose Control access action (pumpPanelAccess) on that actual model; saving writes pumpPanelX, pumpPanelY, pumpPanelZ, pumpPanelSize, and explicit pumpPanelConfigured = true.

Set pumpDischargeCount (1-4) and pumpIntakeCount (1-2), then use the actions pumpOutlet1Connection through pumpOutlet4Connection and pumpIntake1Connection through pumpIntake2Connection. Each active action saves its Label, X, Y, Z, Rx, Ry, and Rz values under the matching pumpOutletN* or pumpIntakeN* prefix. Never copy the packaged model's panel, intake, outlet, or rotation values to another model; edit and save the actual vehicle.

With /jobconfig, review these exact saved keys:

• Mask: fireProtectiveMaskEnabled, fireProtectiveMaskSmokeMultiplier, fireProtectiveMaskToxicMultiplier, fireProtectiveMaskOverlayEnabled, fireProtectiveMaskForceFirstPerson, fireProtectiveMaskItemEnabled, fireProtectiveMaskItemName, fireProtectiveMaskComponents, fireProtectiveMaskProps, fireFemaleProtectiveMaskComponents, and fireFemaleProtectiveMaskProps.
• Cleanup: oilCleanupAllowedJobs.
• Fire reward: societyRewardFireEnabled, societyRewardFireScenarioEnabled, and societyRewardFireJobs.
• Oil reward: societyRewardOilEnabled, societyRewardOilScenarioEnabled, and societyRewardOilJobs.
• Tree reward: societyRewardTreeEnabled, societyRewardTreeScenarioEnabled, and societyRewardTreeJobs.
• Rescue reward: societyRewardRescueEnabled, societyRewardRescueScenarioEnabled, and societyRewardRescueJobs.

Saved values override Lua defaults. Review both shipped mask component lists; the two prop keys may remain absent or empty unless prop variants are required. Save each affected vehicle card after using its panel/intake/outlet actions.

No SQL migration is required. Register the non-consumable fire_protective_mask item according to the active inventory and install config/inventory/fire_protective_mask.png. Keep the item name identical in the inventory, Fire shop, and protective-mask config. This release adds no other inventory item or image.

Scenario Hub deployment credentials remain server-only. Preserve the packaged runtime and configure credentials only through the protected deployment path; never paste a secret into config, logs, support messages, or public documentation. Restart sky_base, sky_jobs_base, and sky_firejob in that order.

• Base 1.34.0, Jobs Base 1.37.0, and Fire 1.5.0 start in order.
• The protective mask can be bought/used, validates the intended clothing, updates the HUD, reduces normal smoke, and does not replace SCBA or heat gear.
• Authorized extra jobs see only cleanup actions and lose access when job/duty requirements fail.
• Fire, oil, tree, and rescue society rewards follow their individual scenarioEnabled and enabled values.
• A legacy non-default pump panel is inferred without the new flag, an editor-saved panel uses explicit true, and every unconfigured or explicit-false model remains accessible through the vehicle-area fallback.
• Held and laid hoses remain responsive, grounded, smooth, and synchronized over long routes.
• Scenario vehicles retain saved positions and aircraft effects remain at a plausible height.
• Scenario publishing and thumbnail uploads succeed without exposing credentials.
• Equipment and placement feedback follows the selected locale.

Back up the complete Fire resource and intentional configuration. Install cleanly so runtime, UI, job configuration, HMAC support, manifest, and streamed hose model are from the same package.

Replace fxmanifest.lua, source, built UI, locales, README, tests, and stream/sky_hose_segment.ydr. Keep source/server/vendor/sha2.lua in the package.

Without /jobconfig, apply all of these public changes:

For every entry in Config.Hose.vehicles, keep the current editor-saved pump panel X/Y/Z/size, each active pumpOutletN position and rotation (X/Y/Z/Rx/Ry/Rz), and each active pumpIntakeN position and rotation. The shipped example now uses three discharges rather than four. Do not copy the example coordinates to a different vehicle model; position them through /jobconfig or the vehicle editor.

With /jobconfig, review and save Hose nozzle placement/animation, deployment and maximum length, target size/distance, per-vehicle panel/intake/outlet geometry, Carry vehicle behavior, entrapment detection, incident dispatch, extinguisher maintenance, and reward recipients. The empty job lists intentionally select the current configured Fire jobs.

No SQL migration, inventory item, or image registration is required. Replace stream/sky_hose_segment.ydr; mixed clients can otherwise render a different hose material than 1.4.0 clients.

Scenario Hub signing requires the deployment secret and key version to match the Public API. Never place the secret in public config, changelog, support messages, or AI knowledge.

• Base 1.33.0, Jobs Base 1.36.0, and Fire 1.4.0 are running.
• Every configured Fire job receives intended radial actions, dispatches, rewards, maintenance, and creator access.
• Pump targets appear at editor-defined points on each configured vehicle model.
• Monitor and transfer hoses reserve and render the intended nearest ports.
• A routed hose remains grounded and connected across slopes, MLO floors, and long paths up to 100 meters.
• The enhanced pump shuts down at zero fuel.
• Damage-based entrapment, Fire dispatch, Scenario Hub availability, carry, and image fallbacks work correctly.
• The updated streamed hose has the intended matte cloth appearance.

Stop the server after updating both base resources. Create these backups:

Do not overlay 1.3.1 on 1.3.0. The pump runtime and interface were expanded substantially.

Install the complete package:

Start with the new config/config.lua. The complete public 1.3.0 → 1.3.1 config migration is listed below.

Config.Hose.pump.waterSourceAreas = {
    {
        coords = vector3(1300.0, 4100.0, 30.0),
        radius = 850.0,
        zTolerance = 4.0
    }
}

If you use /jobconfig, open the Fire job and review Pump Panel:

• panel mode and pressure/RPM limits
• engine retention, fuel, heat, damage, and hydraulics
• every pump vehicle's intake/outlet counts, labels, and attachment positions

Save the job after reviewing it. Still edit the three portable-drafting values from section 1 manually.

No old public block was removed. Config.Hose.vehiclePumpBehavior.updateMs is the only existing shipped value changed by this patch.

No SQL migration and no new inventory item or inventory image are required for 1.3.1.

Keep the dependency order:

ensure sky_base
ensure sky_jobs_base
ensure sky_firejob

Test on a staging server:

• The console reports Base 1.32.1, Jobs Base 1.35.1, and Fire 1.3.1.
• Simple mode exposes one intake and one discharge; enhanced mode exposes the configured ports.
• Tank feed/fill, hydrant intake, portable pump intake, hose outlets, water monitor, and deck gun respect live valve and pressure state.
• Fuel use, temperature, cavitation, overload warnings, and damage respond to pump load.
• Natural drafting works inside every configured waterSourceAreas entry and is rejected outside them.
• A firefighter can lay down and retrieve an attack hose, including inside an MLO.
• Missing vehicle doors allow the intended rescue flow.
• Incident Reports fill the shared tablet and air-bottle storage closes with Escape.
• The protective-gear HUD shows helmet, mask, jacket, trousers, and boots correctly.

Update sky_base to 1.32.0 and sky_jobs_base to 1.35.0, then stop the server.

Do not overlay this release. The resource now includes a rebuilt interface and new streamed extinguisher-mount assets.

Install the complete package:

Confirm that stream contains sky_fire_exting_mount.ydr, .ytd, .ytyp, and _col.ybn.

Start with the new config/config.lua; it already contains every required block. Transfer your old server values into it instead of replacing the file. The complete 1.2.0 → 1.3.0 public config migration is grouped below.

{ name = "fire_extinguisher_mount_kit", label = "Fire Extinguisher Mount Kit", price = 250 }

Choose exactly one database path:

The migration keeps existing sky_fire_extinguishers rows and adds rx, ry, rz, fill_level, item_metadata, condition_status, is_taken, is_custom, last_inspected_by, last_inspected_at, and idx_inspection_due (is_taken, last_inspected_at). Do not drop the table.

Register fire_extinguisher_mount_kit in your active inventory unless the item already exists. The resource does not create the inventory item definition automatically. Copy config/inventory/fire_extinguisher_mount_kit.png into the inventory image folder.

Keep the dependency order:

ensure sky_base
ensure sky_jobs_base
ensure sky_firejob

Test on a staging server:

• The console reports Fire 1.3.0 without SQL, dependency, or missing-stream errors.
• A mount can be placed on a wall and ground, removed, and returned as an item.
• Extinguisher take/restock, fill, condition, and restart persistence work.
• Stock-based restocking uses the configured station, job, grade, item, and amount.
• Player carry synchronizes and releases correctly.
• Hose/nozzle props are visible to a second client.
• Hard braking alone does not trap players; real collisions and unordered multi-patient rescue work.
• Fire, oil, tree, and rescue objectives complete; oil-spill edits persist.
• Male and female protective gear rules and the trapped-player door overview display correctly.