ESX • QBCore • Qbox compatible

Instant download

Updates included

Discord support

Secure checkout

Deployable Emergency Vehicle Light

Q: Do I need separate items for red, blue, and orange lights?

One generic deployable_light item is typical. Color is set per vehicle in Config.VehicleData through LightSetting ('red', 'blue', 'orange', 'white'). A default entry applies to all vehicles unless overridden. Separate color items exist but vehicle LightSetting still controls the emitted light.

Q: The light is in the wrong place on my vehicle

Position = vector3(0.0, 0.0, 0.0) lets the script auto-find the roof from vehicle collision. Non-zero values are offsets from the vehicle center (X left/right, Y front/back, Z up). Addon vehicles with bad collision may need manual coordinates or debug mode placement.

Q: Nothing happens when I use the command or item

Try this order: Disable item requirement (Config.RequiredItem.Enabled = false) and enable /light to isolate script vs inventory issues. Check F8 and server console for errors. Confirm the item exists in your inventory system (giveitem errors usually mean a missing items.lua entry). Use the exact ox_inventory snippet from the script readme or docs. Do not replace Config.AllowedModels; the script uses Config.VehicleData only.

Q: ox_inventory says "No such export deployable_light"

The item name in items.lua must match config. Use the exact snippet from the Gamzky docs. Re-download the resource if the export is missing from an old build.

Q: I changed the config and colors or behavior broke

Start from a fresh config.lua. Set LightSetting inside Config.VehicleData entries. Do not invent custom variables like AllowedModels. Keep vehicle hashes in backticks, not quotes. Avoid AI-generated config edits.

Resource folder: gs_deployablelight

View product

Installation Instructions for Deployable Emergency Vehicle Light

Follow these steps to install and configure gs_deployablelight on your FiveM server.

Download the Resource
- Go to portal.cfx.re
- Navigate to Assets > Granted Assets > gs_deployablelight
- Download the resource
Extract the Files
- Open the downloaded .zip file
- Inside, you'll find a folder named gs_deployablelight
- Move the entire gs_deployablelight folder into your desired server resources folder (e.g., /resources/[scripts])
Add to Server Configuration
- Open your server.cfg
- Add the following line:
```
ensure gs_deployablelight
```
Restart the Server
- Restart your FiveM server (Important!)
Configure the Script (Optional)
- Navigate to gs_deployablelight/config.lua
- Edit the configuration options to fit your server's needs

Included images

Installation Instructions

Add the following items to your ox_inventory/data/items.lua file:

['deployable_light'] = {
    label = 'Deployable Light',
    weight = 250,
    server = {
        export = 'gs_deployablelight.deployable_light',
    },
},
['deployable_light_blue'] = {
    label = 'Blue Deployable Light',
    weight = 250,
    server = {
        export = 'gs_deployablelight.deployable_light_blue',
    },
},
['deployable_light_red'] = {
    label = 'Red Deployable Light',
    weight = 250,
    server = {
        export = 'gs_deployablelight.deployable_light_red',
    },
},
['deployable_light_orange'] = {
    label = 'Orange Deployable Light',
    weight = 250,
    server = {
        export = 'gs_deployablelight.deployable_light_orange',
    },
},

Execute the following SQL query to add the items to the database:

INSERT INTO
	`items` (`name`, `label`, `weight`, `rare`, `can_remove`)
VALUES
	('deployable_light', 'Deployable Light', 0, 0, 1);

INSERT INTO
	`items` (`name`, `label`, `weight`, `rare`, `can_remove`)
VALUES
	('deployable_light_blue', 'Blue Deployable Light', 0, 0, 1);

INSERT INTO
	`items` (`name`, `label`, `weight`, `rare`, `can_remove`)
VALUES
	('deployable_light_red', 'Red Deployable Light', 0, 0, 1);

INSERT INTO
	`items` (`name`, `label`, `weight`, `rare`, `can_remove`)
VALUES
	('deployable_light_orange', 'Orange Deployable Light', 0, 0, 1);

Add the following items to your qb-core/shared/items.lua file:

['deployable_light'] = {
    ['name'] = 'deployable_light',
    ['label'] = 'Deployable Light',
    ['weight'] = 250,
    ['type'] = 'item',
    ['image'] = 'deployable_light.png',
    ['unique'] = false,
    ['useable'] = true,
    ['shouldClose'] = true,
    ['combinable'] = nil,
},
['deployable_light_blue'] = {
    ['name'] = 'deployable_light_blue',
    ['label'] = 'Blue Deployable Light',
    ['weight'] = 250,
    ['type'] = 'item',
    ['image'] = 'deployable_light_blue.png',
    ['unique'] = false,
    ['useable'] = true,
    ['shouldClose'] = true,
    ['combinable'] = nil,
},
['deployable_light_red'] = {
    ['name'] = 'deployable_light_red',
    ['label'] = 'Red Deployable Light',
    ['weight'] = 250,
    ['type'] = 'item',
    ['image'] = 'deployable_light_red.png',
    ['unique'] = false,
    ['useable'] = true,
    ['shouldClose'] = true,
    ['combinable'] = nil,
},
['deployable_light_orange'] = {
    ['name'] = 'deployable_light_orange',
    ['label'] = 'Orange Deployable Light',
    ['weight'] = 250,
    ['type'] = 'item',
    ['image'] = 'deployable_light_orange.png',
    ['unique'] = false,
    ['useable'] = true,
    ['shouldClose'] = true,
    ['combinable'] = nil,
},

What does this script actually do?

It deploys a rotating emergency beacon (and optional siren) on vehicles through target interaction. It has its own light and siren system and runs alongside ELS, Luxart, and similar resources without replacing them. It is not a lightbar menu script; separate blinking LED lightbars are not supported.

Default controls:

Target the vehicle to deploy or remove the light
L-SHIFT toggles siren (only when the light is deployed)
L-CTRL removes the deployed light
/light works when Config.EnableLightCommand = true

What are the requirements?

You need a target system (ox_target, qb-target, or similar). ox_lib is not required. Luxart is optional and does not control deployed lights.

I get "You lack the required entitlement to use gs_deployablelight"

Restart the server after purchasing so Keymaster entitlement loads. Confirm the correct licenseKey is set on the server.

Do I need separate items for red, blue, and orange lights?

One generic deployable_light item is typical. Color is set per vehicle in Config.VehicleData through LightSetting ('red', 'blue', 'orange', 'white'). A default entry applies to all vehicles unless overridden. Separate color items exist but vehicle LightSetting still controls the emitted light.

The light is in the wrong place on my vehicle

Position = vector3(0.0, 0.0, 0.0) lets the script auto-find the roof from vehicle collision. Non-zero values are offsets from the vehicle center (X left/right, Y front/back, Z up). Addon vehicles with bad collision may need manual coordinates or debug mode placement.

Nothing happens when I use the command or item

Try this order:

Disable item requirement (Config.RequiredItem.Enabled = false) and enable /light to isolate script vs inventory issues.
Check F8 and server console for errors.
Confirm the item exists in your inventory system (giveitem errors usually mean a missing items.lua entry).
Use the exact ox_inventory snippet from the script readme or docs.
Do not replace Config.AllowedModels; the script uses Config.VehicleData only.

The light deploys then instantly disappears

Common causes:

Item requirement is enabled but the item is not removed server-side, so the script removes the light again. Debug Functions.RemoveLightItem in bridge/sv_bridge.lua or disable item requirement to test.
Anticheat despawning unauthorized props.
Wrong ESX item name or a failing getInventoryItem call.

ox_inventory says "No such export deployable_light"

The item name in items.lua must match config. Use the exact snippet from the Gamzky docs. Re-download the resource if the export is missing from an old build.

All color items deploy a red light

Read the readme for color item setup. Color items need matching Config.LightSettings and correct per-vehicle LightSetting. Vehicle config controls the actual emitted color.

I changed the config and colors or behavior broke

Start from a fresh config.lua. Set LightSetting inside Config.VehicleData entries. Do not invent custom variables like AllowedModels. Keep vehicle hashes in backticks, not quotes. Avoid AI-generated config edits.

The light does nothing on certain vehicles

Some vehicles are blacklisted by default (for example adder). Remove them from the blacklist or add an explicit entry in Config.VehicleData.

Can the light blink instead of rotate?

Yes. Set LightBehaviour to 'blinking' instead of 'rotating' per vehicle in Config.VehicleData.

The light is hard to see during daytime

Day visibility is limited by the GTA engine and visual packs. Night visibility is stronger. Some servers raise Brightness in Config.LightSettings (for example 30.0) as a workaround.

Custom sirens (WM Server Sirens and similar) do not play

Install and stream the siren pack, add AudioBanks in Config.Siren, and set both SirenName and AudioRef per vehicle in Config.VehicleData. AudioRef is not the same as AudioBank. Built-in GTA sirens use default SirenName strings.

The siren does not work at all

The light must be deployed first. Press L-SHIFT (default Config.Siren.Key). Custom sirens need correct AudioBanks loaded.

Does this conflict with ELS or Luxart?

No. Scripts run independently. You can disable deployable sirens and use ELS for audio, or configure custom sirens in deployable config. Luxart's menu does not control deployed lights.

How do I restrict deployment to police, EMS, or mechanics?

Edit Functions.CanPlayerDeployLight in bridge/cl_bridge.lua for your framework and job list.

Light props are left on the ground when a vehicle is despawned

Recent versions clean this up automatically. Remove old manual workarounds such as gs_advancedtrunk:ResetTrunk snippets. Also check for a Config.RequiredItem.DefaultName typo (not Name) in config.

Does it work on addon vehicles?

Yes, if the model has reasonable collision for roof detection. Add a manual Config.VehicleData entry per model when auto placement fails.

Can I run this standalone without a framework?

Yes. Disable item requirement and use command mode. Set bridge permission checks to always allow deployment if needed.

Players joining late sometimes see the light as off

The script uses state bags and should sync when the vehicle loads. This is hard to reproduce. If it persists, note exact steps and report to support.

The game crashes when deploying a light

Test with default config and item requirement disabled. Crashes on live servers are often config corruption or a conflict with another script that does not appear on localhost.