Storm Surge

Resource: `qbx-stormsurge` — version 1.5.9. Storm Surge is a cargo-ship raid launched through the Operations Tablet. Local storm weather surrounds Daisy Lee, with ship guards, a civilian captain and four NPC-only perimet

US$17.99 before tax/VAT

Resource: `qbx-stormsurge` — version 1.5.9. Storm Surge is a cargo-ship raid launched through the Operations Tablet. Local storm weather surrounds Daisy Lee, with ship guards, a civilian captain and four NPC-only perimeter patrol boats: two Patrol Boats and two armed Dinghies. Boat targeting and ship tactics are configurable. The first crane movement triggers the configured on-ship reinforcement teams. The current configuration uses two teams of three soldiers; helicopter insertions are not part of the configured encounter. The four upper containers shuffle as complete groups each shared mission run. Their props, doors, safe and placed loot move together, while saved editor positions remain intact. Lower cargo is excluded. Loot points owned by `qbx-stormsurge` use their saved reward pools: each active participant receives a separate roll, and a location opens once per mission. Full-inventory rewards are queued by Elite Admin. Use A/D to rotate, E for the cable action, Left Alt for precision, and Backspace/Escape to leave the controls. The forward crane uses the real upper assembly and native hoist ropes. Deck opening bays remain available; ocean dumping is supported without requiring containers to have been opened first. Loot prompts are unavailable while their container is suspended or dumped. `crane/controls.json` stores the assigned crane console. `crane/bow_client.lua` is the active crane controller; the unloaded predecessor has been removed. Player boarding boats use the native anchor without freezing the entity, allowing buoyancy and wave motion. Mission patrol boats remain restricted to NPC crews. After visiting the ship, participants can leave at any objective stage. Completion and world cleanup wait until encounter positions are outside every connected player/camera safety envelope for ten seconds. Visitors and spectators count; stale visibility reports delay cleanup. `Config.Cleanup` controls the distances and grace period. Storm rain respects Add Mission Item's shelter detection. Physical collision, shadow coverage, wave response and NPC navigation should be checked in game after changes to ship assets. Rain suppression inside shelter can also hide rain visible through open doorways; it is not a replacement for correctly authored interior assets. Start these dependencies before the mission: `security_protection`, `universal_adapter`, `blips`, `ox_lib`, `activity_minigames`, `ox_target`, `ox_inventory`, `add_mission_item`, `mission_item_assets`, `rfs_thermal_lance`, and `job_tablet`. Install the resource as `qbx-stormsurge`, configure it, then start it through the server's normal resource controls. The live adapter is `@universal_adapter/runtime/runtime_adapter.lua`; no embedded adapter copy is needed. Master job ID: `stormsurge`. - `config.lua`: mission stages, equipment, weather, patrols, ship guards, reinforcement teams and cleanup. The reinforcement configuration retains the legacy name `HeliBoarding`. - `routes/guard_reinforcements.lua`: ship guard routes and captain positions. - `crane/cargo_layout.lua`: upper cargo grouping and runtime layout transforms. - `crane/controls.json`: saved crane console registration. - Elite Admin's placed loot editor: item pools, quantities, selection weights and access requirements. Select owning script `qbx-stormsurge`. The server exposes `GetLootRun` and `GetLootParticipants` for mission loot integration, and cargo transform exports for placed props and loot. Preserve these integrations when packaging the resource. Removed the obsolete Hydraulic Cutter (`hydrocutter`) and Waterproof Cargo Bag (`waterprooflootbag`) inventory definitions and the cutter's vendor listing. The Thermal Lance and Cargo Vault Keycard remain. Bank Teller's equipment is unaffected. Archived the unloaded old crane controller, embedded adapter reference snapshot and old Lua backup files outside the resource. Updated the manifest version and replaced contradictory historical setup notes with the current configured behaviour. No live resources were restarted by this cleanup. Support: [RealFiveMScripts.com](https://www.realfivemscripts.com). Protection packaging updated. See the package RELEASE-NOTES.md for activation requirements and validation status. Live development settings are not modified.