Troubleshooting
Symptom-based fixes — lights not responding, editor access, silent sirens, state not syncing, install errors.
If none of these match, Still stuck? says what to send support.
Pressing Q does nothing
The vehicle has no LEDs, and every keybind needs at least one. The Lights tab says so outright:
- Get in and run
/telsedit - Lights tab → Create from siren bones
- Add a pattern on the Patterns tab
- Press Enter
- With no
sirenbones, place LEDs by hand in the Editor - If Q does nothing on a vehicle that does have LEDs, check No User Controls for that model on the editor's Vehicle behavior tab — it disables every tELS keybind
The lights work for me but nobody else sees them
State replicates through OneSync entity state bags.
Fix — enable OneSync (Infinity or Legacy) and restart the whole server, not just the resource. If OneSync is already on, confirm you own the vehicle — see ownership.
One player sees no tELS lights on any vehicle
That client never received the vehicle configs.
Fix — wait a minute; the client retries and the server pushes unprompted within 45 seconds of joining. After that, reconnect and check the server console — an oversized config is refused and named there.
/telsedit says "Permission denied"
You do not have tLib's admin ACE. Add it to server.cfg and reconnect:
add_ace group.admin tlib.admin allowIt also enables Set as Server Defaults and the editor button inside /tels.
/telsedit says "Must be in a vehicle"
The editor edits the vehicle you are sitting in. Any seat works, including a passenger's.
Editor changes aren't syncing to other players
The editor does not auto-save, and leaving discards the draft.
Fix — press Enter, or click Save, before you exit. Undo history clears on save. Sound overrides, on the Vehicle behavior tab, are the exception: server configuration, written immediately, not undone by Escape.
My pattern doesn't appear in the 9/0 cycle
Two settings take a pattern out of the cycle while leaving it playable by a rule.
| Cause | Fix |
|---|---|
| Flagged Trigger Only | Uncheck it, or drive the pattern from a rule |
| Restricted to a livery index | Set Livery to Any, or put the vehicle on that livery |
Server-sided sirens aren't playing
A server-sided tone needs four things. Missing any one falls back to the vanilla sound silently.
| # | Requirement |
|---|---|
| 1 | The tone has both a Server Sound and a Server Sound Ref |
| 2 | The audio bank ships with a resource that is started |
| 3 | Server-sided Sirens is enabled in /tels |
| 4 | tELS knows which audio bank that SoundSet belongs to |
The fourth catches people. tELS maps its own pack, WM-ServerSirens and OISS; every other
needs one, declared by the pack or written by you in siren_packs.json. See
Configuration → Custom siren packs.
Diagnose — press F8. A SoundSet with no bank prints:
SoundSet 'X' is used by a siren config but maps to no audio bank
- If the mapping exists but the bank never loads, the warning names the bank instead — usually a pack resource that is not started, or a wrong path
- A pack that works until the next restart is the classic no-mapping symptom
A player can't control the lights on a vehicle someone else drove
Ownership is per vehicle and held until released.
Fix — the owner releases it from /tels → Release Vehicle Ownership, or the new
player drives the vehicle to claim it.
I can't turn the car radio off
Q cycles the light stages, so GTA's radio wheel is suppressed.
Fix — press Radio Off/On on the Quick tab of /tels, or bind ELS: Radio
Off/On in Keybinds → FiveM. Station ◀ / Station ▶ step through stations.
My custom settings disappeared after a server restart
data.json was removed or replaced, and a missing file is rewritten empty on the next boot.
- Extracting a new release over the folder cannot replace it
- A folder deleted and re-extracted, a deploy step that mirrors the resource directory, or a restore from an older backup all will
- Per-player client settings are stored on the client and survive reconnects
Diagnose — check the server console on startup:
| Line | Means |
|---|---|
First boot: created data.json | tELS found no file. On anything but a new install, that is the cause |
data.json could not be created | The resource directory is not writable. Nothing survives a restart until that is fixed |
Fix — restore from a backup, then exclude whichever deploy step replaces the resource directory. Back it up before any update: it is the one file you cannot re-download.
SCRIPT ERROR: @tELS/... on startup
tLib is missing or started too late. "No such export" is the same problem.
Fix — in server.cfg, ensure tLib above tELS:
ensure tLib
ensure tELSA tLib version warning in the console
Your tLib is older than the version in tELS's manifest, and tELS refuses to start against it.
Fix — update tLib, not tELS: releases. See version compatibility.
references data file 'audio/data/tels.dat' ... that does not exist
A false positive. Do not fix it. It appears on every start:
Resource 'tELS' references data file 'audio/data/tels.dat'
of type 'AUDIO_SOUNDDATA' that does not exist.
The resource won't start at all
The folder is not named tELS.
Fix — rename it to exactly tELS: no spaces, no -main suffix from a zip extract.
Still stuck?
Run tels_diag in the F8 console for one paste-safe line, then contact support on
Discord with:
- The
tels_diagline - The full console error block, not a paraphrase
- Your
server.cfgload order aroundtELS - F8 client console output captured while the problem happens
- Which vehicle model, and whether it reproduces on a stock vehicle such as
police4
tELS
Still stuck? Support can answer it directly.
Was this page helpful?
TIMMYG Studios