Editor

Watch video · starts muted

/telsedit opens the editor while you are in a vehicle, any seat. It needs the tlib.admin ACE and writes to data.json.

Enter saves every tab at once. Escape cancels. Alt+1…Alt+6 jump to a tab — Alt, not Ctrl, which is a camera view. ? opens the shortcut sheet.

Camera controls

Left mouse stays free for the gizmo.

Numpad camera

Blender's convention, on the Lights tab.

Fly camera

The camera button at the bottom of the left toolbar toggles fly camera: WASD moves, right-drag looks. W, A, S, D, Q and E then belong to the camera, suspending the gizmo and LED shortcuts.

Lights tab

To bone only some LEDs, select them and use Auto-detect on the properties panel's Bone row instead of the wand.

Click an LED in the viewport or the list to select it. Shift+click range-selects, Ctrl+click toggles one.

• A vehicle with embedded tELS LED markers fills this tab on its own
• Any saved layout wins over the model's, including one saved empty
• To restore one model LED, delete it and re-import

LED properties

What the vehicle costs to light

Two choices on this tab decide what every player pays for your vehicle. What is drawn scales with the LEDs lit on the current frame, not the LEDs configured.

An Arges spotlight head costs one extra LED. The two render-quality tiers a player picks are in Usage → Render quality; the cap itself is TELS_MAX_LEDS.

Surface textures

Row defaults to 1 when Col is 4 or fewer, 2 above that.

Custom LED textures

A vehicle resource supplies its own LED sprite from its fxmanifest.lua. Select it per LED with Surface → Res; the list reads No resources with tels_led_png declared when none has.

tels_led_png 'textures/my_led.png'
files { 'textures/my_led.png' }

Identity

Editor-created LEDs carry a generated UUID; model-defined LEDs keep their tels_led_NNN marker identity. Pattern cells map to those IDs and exported patterns may use LED names, so keep both stable across revisions.

Multi-select

Move, rotate and scale together, or batch-edit any shared property.

W, Q and E are suspended under fly camera.

Global, all tabs:

• Ctrl+Z undo · Ctrl+Y or Ctrl+Shift+Z redo
• Alt+1…Alt+7 switch tab · ? shortcut sheet
• Enter save and exit · Escape cancel and exit
• None fire while the caret is in a text field

Arges tab

Patterns tab

A grid sequencer — columns are frames, rows are LEDs — previewed live on the vehicle. Space plays and pauses.

The pattern list on the left takes the keyboard as well as the mouse: Tab into it, then ↑/↓ (and Home/End) to choose a pattern and F2 to rename the one selected. Double-clicking a row renames it too.

Import from carcols.meta

carcols… in the toolbar opens an importer.

• Paste a vehicle's carcols.meta and pick one of the siren sets it declares
• tELS converts that set's sequences, flash rate, phase offsets and per-head colours into an editable pattern, clamped to 1–30 FPS. It is a conversion, not a link

Pattern options

Under Advanced behavior in the pattern sidebar.

Show unfitted LEDs, above the disclosure, is an unsaved view toggle: off, the preview hides LEDs whose extra or modkit is not fitted; on, every LED draws.

Rules tab

Each rule is IF a compound of conditions is true, THEN run actions, in list order. Join conditions with AND or OR, and toggle NOT on any one of them.

Where two rules overlay a pattern onto the same LED, the one further down the Patterns list paints on top. Dragging triggers changes nothing; reorder the patterns.

HOLD: engage and release delays

Stops a rule flickering on a threshold — 15 mph exactly, a barely-touched brake, a bouncing door.

Both default to 0 and are set independently.

• engage 2000 / release 0 — flash only once a door has been open two seconds, and stop the moment it shuts
• engage 0 / release 3000 — flash instantly, and keep going three seconds after the condition clears
• A delay restarts from zero if the conditions flip back

Condition reference

Lights and stages

Audio

Modes

blackout is a suppressor, not a switch:

• lights_on stays true under it, so a rule that should fire only when the vehicle is visible needs lights_on and a negated blackout
• An LED overlay driven by a blackout rule is never seen. Use it for siren tone, rumbler, chirp or a HUD state

Vehicle state

Controls

Doors

Steering and transmission

Health and occupancy

Action types

Rising edge vs held.

• pattern_set, stage_set, park_chirp and ers_pullover fire once, as the rule becomes true, and what they set stays set
• pattern_overlay, siren_overlay and horn_play_airhorn run while it is true and stop on false

ERS pullover support (night_ers)

night_ers detects a pullover from GTA's native emergency-lights flag. tELS renders its own lighting and never sets that flag, so add an ers_pullover action, which blips it on the rising edge of whatever conditions you attach — typically stage_2, siren, or both.

Add Trigger, set those conditions, then Add Action → ers_pullover, then Enter. In data.json that is one triggers[] entry:

{
  "id": "a1b2c3d4e5f6a7b8",
  "conditions": ["stage_2"],
  "negated": [false],
  "operator": "and",
  "enabled": true,
  "actions": [{ "type": "ers_pullover" }]
}

The blip window defaults to 500 ms. Override it only for a detector that needs longer:

{ "type": "ers_pullover", "durationMs": 800 }

durationMs is floored at 300 ms — a smaller number is raised, not used. A shorter blip is missed outright.

Across a fleet, configure the trigger once on your primary model and reference it from the others, in each one's triggers[]:

{ "$ref": "police4", "triggerId": "a1b2c3d4e5f6a7b8" }

Sirens tab

Tone slots

Up to 8.

Airhorn, horn and chirp

Separate vanilla, server and rumbler-server fields for the airhorn, falling back to SIRENS_AIRHORN.

Livery sound profiles

Sound profile → Default / Any livery holds the normal sounds. Enter a zero-based livery index and click Add livery to override its sounds. Unmatched liveries use the default; a new profile inherits until edited.

Selecting a profile edits configuration; it does not change the vehicle's livery.

Custom siren packs

Server Sound Ref takes any SoundSet name, but tELS only plays one whose audio bank it knows — its own pack, WM-ServerSirens and OISS. Every other pack needs its own mapping, or its sirens are silent.

Vehicle behavior tab

Flags for the vehicle you are editing. The three horn flags live on Sirens.

Sound overrides

Which installed file plays for each tELS event on this model — Lights On, Lights Off, Tone Change, Airhorn, Chirp. Each row shows the server-wide mapping it inherits; choose a file to override it, or Inherit to drop back.

Set the server-wide mappings in /tels → Sounds, which needs the tlib.admin ACE.

Marketplace tab

The public catalogue of LED configs, patterns and whole vehicle setups, with a filter chip per kind, a search box and four sort orders.

• Browsing and previewing are rate limited per player, so several previews in one breath can return "too many requests"
• An import lands in the open vehicle as a draft edit: Enter saves it, Escape throws it away

LED configs

• Pick the LED configs chip, or the button in the Light placement header, which opens this tab already filtered
• Publish one from that header button with Share LED layout. No name is asked for — the listing is keyed to this vehicle's fingerprint and labelled with the model, so it finds the same car on another server
• Once it is published, the button becomes Update and Un-share. Update replaces the listing in place, so it keeps its id and its import count; Un-share takes it out of the catalogue and cannot be undone — publishing again starts a new listing
• Older listings, published before in-game editing existed, can only be re-shared as a new listing. The panel says so when that is the case

Sharing one pattern

Select the pattern, then press Share "<name>" at the top of the Patterns tab. One click, and it publishes under the pattern's own name — there is no form.

• It becomes Update shared plus Un-share once published, exactly like an LED layout
• Only patterns this vehicle owns can be shared. A pattern linked from another model has no frames of its own, so the button says to share it from there instead
• Renaming a shared pattern loses the handle to its listing: the name is what it was published and filed under. Rename first, share after

Sharing the full vehicle setup

The Marketplace toolbar's Share full setup publishes the whole vehicle you have open — LEDs, patterns, triggers, siren and Arges together.

• This is the one share that asks you to name it, because a whole vehicle has no name of its own. One line, not a title and a description
• The dialog lists every section that will travel, with counts, plus the sound packs the share declares when the siren uses server-sided audio
• The audio itself does not travel, so anyone without those packs gets silent tones
• Patterns and triggers borrowed from another vehicle are left out
• Published already? The button says Update and the dialog offers Un-share, the same three states as everywhere else
• HUD skins and sound packs install from the HUD layouts side

Un-share before you delete a vehicle

Un-share first, then delete the config. Permission to edit or withdraw a listing is held against the vehicle it was shared from. Delete that vehicle's configuration — or remove the vehicle resource — and the editor has nothing left to attach the listing to, so Un-share disappears and the listing stays in the catalogue. Sharing again publishes a second one rather than replacing it.

Nothing on your server can take down a listing in that state. Ask us at timmygstudios.com/help, or through the ticket panel in 🆘︱support on Discord, and we will remove it.

Cross-vehicle references

Open the reference menu on any pattern, trigger, siren or settings block to import it from another model instead of duplicating.

• Imported items show a link icon; items others reference show a share icon
• Editing a referenced item edits the source
• $all imports every non-referenced pattern or trigger at once
• Data format: Configuration → Cross-vehicle references

Saving

Save writes all tabs to data.json and broadcasts to every client. Undo history clears.

Two ceilings, both reported in the server console naming the vehicle: