Configuration

Vehicles are configured in game, in the Editor — LEDs, patterns, rules and sirens are all set there, and Save writes them to one data.json at the resource root, keyed by model name.

This page is the rest: the settings an operator sets once for the whole server, and what a vehicle developer needs to ship a car that arrives already configured.

Server defaults

An admin with tlib.admin saves their display settings as the server-wide fallback through /tels → Set as Server Defaults. They become top-level keys in data.json, and a player's own setting always wins.

Custom siren packs

tELS must know which audio bank each SoundSet belongs to before it can play it. It already knows its own pack, WM-ServerSirens and OISS. Every other pack needs a mapping. Without one the sirens are silent, or audible only while another resource happens to have that bank loaded — which reads as a pack that works sometimes.

Packs that ship a manifest

tels_siren_pack 'tels_sirens.json'
files { 'tels_sirens.json' }

{
  "soundsets": {
    "MYPACK_SOUNDSET": "DLC_MYPACK\\SIRENS",
    "MYPACK_SOUNDSET_TWO": "DLC_MYPACK\\SIRENS_TWO"
  }
}

Start order does not matter, and a pack started mid-session needs no restart.

Packs that ship no manifest

Most existing packs, LG Mods included, carry no tels_siren_pack metadata. Map their SoundSets yourself rather than editing someone else's resource.

tELS/siren_packs.json

{
  "soundsets": {
    "LGMODS_MEGASIREN_SOUNDSET": "DLC_LGMODS\\MEGASIREN"
  }
}

Same shape, same escaping leniency, optional. An entry here overrides the pack's own; built-in SoundSets cannot be overridden from either source. Then, in the server console:

tels_reload_siren_packs

Rules and limits

A pack that loads prints Siren pack '<resource>': registered N SoundSets.

Cross-vehicle references

Reference patterns, triggers and sirens across similar vehicles instead of duplicating them. Set them up from the editor's reference menu; this is the shape they take on disk. Pattern and trigger refs live inline in the patterns / triggers arrays.

Render and bloom constants

The same on every vehicle and client, in config/render_config.lua — plain Lua, outside escrow, editable. A bad value is named in the server console at startup, with the fix.

Vehicle-developer export

Bundle a config inside the vehicle resource and it loads on server start, with nothing for the owner to copy. tELS scans every running resource for the tels_config key and merges the file it names. Server-owner edits in data.json take priority.

tels_config 'data/tels.json'

{
  "police4": {
    "leds": [],
    "patterns": [],
    "triggers": [],
    "siren": {}
  }
}

Discovery parameters

The strings to look for in the server console and your own listeners.

Schema reference

One entry per model name, in these five sections.

Vehicles authored with model LED markers can omit leds. An explicit leds array, including [], always overrides model discovery.

LED entry

{
  "id": "a3f1b2c4d5e6f7a8",
  "name": "LBF1",
  "x": 0.1, "y": 0.5, "z": 0.7,
  "yaw": 0, "pitch": 0, "roll": 0,
  "sw": 0.044, "sh": 0.02,
  "side": 1,
  "bone": "siren1",
  "groups": ["Right", "Front"]
}

Pattern entry

{
  "name": "Code 3",
  "fps": 10,
  "colors": [
    { "r": 255, "g": 0, "b": 0, "a": 1.0, "name": "Red" },
    { "r": 0, "g": 120, "b": 255, "a": 1.0, "name": "Blue" }
  ],
  "frames": [
    {
      "cells": { "a3f1b2c4d5e6f7a8": 1, "b4e2c3d5f6a7b8c9": 2 },
      "dimCells": { "a3f1b2c4d5e6f7a8": true },
      "duration": 1
    }
  ],
  "triggerOnly": false,
  "syncNear": false,
  "useEmergencyLights": false,
  "useHighBeams": false,
  "livery": 0,
  "modkit": 1,
  "extras": [{ "id": 3, "enable": true }],
  "mods": [{ "modType": 49, "modIndex": 0 }]
}

modkit, extras and mods are restored when the pattern stops, by the owning client only.

Trigger entry

{
  "id": "c5d6e7f8a9b0c1d2",
  "conditions": ["brake", "speed_30"],
  "negated": [false, false],
  "operator": "and",
  "enabled": true,
  "actions": [{ "type": "pattern_overlay", "patternName": "Brake Warning" }]
}

Legacy triggers shaped { trigger: "brake", patternName: "..." } auto-migrate on load.

Siren config

{
  "tones": [
    {
      "name": "Wail",
      "sound": "VEHICLES_HORNS_SIREN_1",
      "serverSound": "", "serverSoundRef": "",
      "rumblerSound": "", "rumblerServerSound": "", "rumblerServerSoundRef": "",
      "enabled": true,
      "triggerOnly": false
    }
  ],
  "airhorn": "SIRENS_AIRHORN",
  "serverAirhorn": "", "serverAirhornRef": "",
  "serverAirhornRumbler": "", "serverAirhornRumblerRef": "",
  "hornInterrupt": true,
  "parkKill": true,
  "useNormalHorn": true,
  "hornProgrammable": false,
  "lightsSuspendTA": true,
  "lightsSuspendTakedown": true,
  "chirpTone": 1,
  "chirpByCode": false,
  "noUserControls": false,
  "disabledExtras": []
}

Up to 8 entries in tones[], one slot each on R and keys 1–8.

Airhorn, horn and vehicle behaviour:

Server-sided sounds play when configured and the player has Server-sided Sirens on; otherwise the vanilla sound does. Third-party SoundSets also need an audio bank mapping.

Per-livery siren sounds

"liveryProfiles": [
  {
    "livery": 0,
    "tones": [
      { "serverSound": "police_wail", "serverSoundRef": "POLICE_SOUNDSET" },
      { "serverSound": "police_yelp", "serverSoundRef": "POLICE_SOUNDSET" }
    ],
    "serverAirhorn": "police_horn",
    "serverAirhornRef": "POLICE_SOUNDSET"
  }
]

One entry per zero-based native livery index. Tone entries line up with the existing default slots, and an empty object inherits one. A profile cannot add, reorder or rename slots, or change eligibility or vehicle behaviour.

Size limits

Enforced on every config the server accepts, and on the catalogue.