Emergency lighting in FiveM has always meant patterns compiled into a vehicle resource. Every flash-rate change, every LED nudge, every siren swap means editing a file, reuploading, and restarting.

tELS throws that pipeline out. Sit in the vehicle, run /telsedit, place LEDs on the 3D model with a gizmo, paint patterns on a grid, and wire up the rules that fire them. Save, and every connected client has it — no restart, no reupload, no per-vehicle files.

vehicle-state conditions you can combine

74

siren tone slots, on two channels

8

files to edit — it's all built in game

0

dependency — tLib, and it's free

1

Will it run on your server?

What you get

Build the lightbar from the driver's seat

/telsedit opens a 3D editor over the vehicle you are sitting in. Drag LEDs into place with a gizmo, rotate and scale them, attach them to bones so they follow a door or the hood, and group them by location.

Starting from nothing? Create from siren bones reads the model's own siren1…sirenN bones and drops a grouped, sided starter bar in one click. Multi-select, duplicate, mirror across the centreline, or batch-edit a whole group.

Already have a lightbar? Paste its carcols

Copy a vehicle's carcols.meta, paste it into the importer, pick a siren set, and tELS converts its sequences, flash rate, phase offsets, and per-head colours into a real tELS pattern you can then edit like any other.

It is the difference between rebuilding a fleet and importing one.

Patterns painted on a grid

LEDs run across the top, frames down the side. Click a cell to colour it. Each pattern carries its own palette, its own frame rate, and per-frame durations — and cells marked dimmable fade into the next frame instead of snapping.

It previews on the real vehicle while you edit, so what you see in the editor is what the street sees.

74 conditions, combined how you like

Not a preset dropdown. Speed bands, individual gears, steering angle, brake, handbrake, each door, lock state, body damage, seat occupancy, the in-game clock, someone approaching the car — joined with AND/OR and negated per condition, driving 18 kinds of action.

Speed > 30 AND Lights Active AND NOT Custom Pattern → Set Stage 2

Audio that matches the lights

Eight tone slots per vehicle across a main and an auxiliary channel, plus a separate airhorn chain and a rumbler variant per tone. Every slot holds a vanilla game sound and, optionally, a server-side one — players pick which they hear.

Twelve custom tones ship. Horn gestures — tap, hold, double-tap — are conditions in their own right, so the horn can drive the lights.

Configure one car, deploy it to twenty

{ "$ref": "police4", "$all": true }

Point one vehicle at another instead of copying it. Edit the source and every vehicle referencing it updates. Orphans clean themselves up, and a vehicle resource can ship its own tels.json as a starting point — your edits always win over the pack's.

Built for a scene, not a screenshot

Ten units on one traffic stop is the case that matters. Vehicles beyond 500 m are skipped entirely, ones behind the camera are culled, lighting quality steps down with distance, and the expensive door/lock/occupancy checks only run for vehicles whose own rules ask for them.

Set environmental lighting to Smart and it watches frame time, easing quality up at 90 fps and back down at 75 so it settles instead of flickering between the two.

Also included

Specifications

Questions people actually ask