Changelog

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.