Assign Sirens
How to assign sirens to vehicles using SIREN_ASSIGNMENTS table in SIRENS.lua,
SIREN_ASSIGNEMENTS Table
SIREN_ASSIGNMENTS = {
--['<gameName>'] = { <airhorn tone>, <siren tone-1>, <siren tone-2>, ... <siren tone-n> },
['DEFAULT'] = { 1, 2, 3, 4, 5, 6, 7, 8, 9, 10 },
['FIRETRUK'] = { 12, 13, 14, 11 },
['AMBULAN'] = { 1, 2, 3, 4, 11 },
['LGUARD'] = { 1, 2, 3, 4, 11 },
}
In this table you can add additional vehicles for assignment using the vehicles <gameName>
exactly as found in vehicles.meta
. It is case sensitive.
Both R* and LVC:v3 truncate down to 11 characters. It is important that the first 11 characters are unique.
Example: If my addon vehicles
<gameName>
is "2008 Ford CVPI CHP" and I have another vehicle "2008 Ford CVPI LSPD" both of these after truncate equate to "2008 Ford C" therefor LVC:v3 will not be able to differentiate these.
The default or fallback key ['DEFAULT']
should always be present and never removed. Doing so will result in issues.
Wildcards
Supported Wildcards:
#
represents 1 or more digits.
How it works:
LVC:v3 checks for vehicle profile matching game name. e.g.
['2008fpiu1']
If not found, attempts wildcard search, meaning wildcards will be used secondary to custom profiles. e.g.
['2008fpiu#']
If not found, attempts a less specific wildcard search, leading and trailing numbers. e.g.
['#fpiu#']
(v3.2.7)If not found, use default profile. e.g.
['DEFAULT']
Example:
* ['veh#'] = { ... }
will be used for vehicles with game names veh1
, veh2
, ..., veh9999
, etc. where exact profile not found.
Last updated
Was this helpful?