Links
Comment on page
⚙

Configure Base Settings

Set a Community

This unique set of characters for your community will be used for profile saving.
  • The ID should be 4-6 alphanumerical characters.
  • Spaces are not allowed and will not work, dashes can be used instead.
  • Some examples may be your servers abbreviation, name, etc.
    • Examples: 'LCPS', 'LCPSR', 'SARP', 'LSDOJ', 'JakesRP', etc.
The purpose of this string is to differentiate the client side saves between servers. Since it is possible (and likely) that servers may use the same profile names, but different profile siren assignments.
This string should be set once, and never changed as it will result in loss of LVC saves for all players. It is not public facing so even if the server name changes it does not need to change.

Configure Controls

Register Key Maps

Users may change these in their GTA V > Settings > Hotkeys > FiveM settings. More info: CFX Cookbook - How RegisterKeyMappings Work List of Keys: RegisterKeyMap Supported Keys​
open_menu_key: sets default key for opening LVC:Fleet Menu. lockout_default_key: sets default key for toggling LVC:Fleet control lock, which disabled all controls.
​
Indicator Controls
These static keys cannot be changed by the end user and support controller keys as well. List of Keys: CFX Game Reference - Controls​
hazard_key: when held for hazard_hold_duration toggle 4-way flashers. left_signal_key: toggle left turn signal. right_signal_key: toggle right turn signal.

Assign Profiles

SETTINGS.lua
---------------------VCF FILES---------------------
VCF_Files = {
'DEFAULT.xml', --1
'WHELEN-295.xml', --2
'WHELEN-CENCOM-G.xml', --3
'MASTERCOM-B.xml', --4
'FS2000.xml', --5
'TMD.xml', --6
}
​
VCF_Assignments = {
['DEFAULT'] = { 1 },
['LAPD'] = { 1, 3 }
['<gameName>'] = { 1, 2, 3, 4, 5 }
}

VCF_Files

Table of VCF file names to be loaded on resource start. These should be locate in /VCF/ directory. VCF Files represent profiles and contain all of LVC:Fleet's settings for that profile.
To load newly installed VCF files, run refresh then restart lvc_fleet.

VCF_Assignements

In this table you can add additional vehicles for assignment using the vehicles <gameName> exactly as found in vehicles.meta. It is case sensitive.
vehicles.meta example:
...
<modelName>so2</modelName> <!-- SPAWN NAME -->
<handlingId>so2</handlingId>
<gameName>so2</gameName> <!-- GAME NAME (WHAT LVC:F USES) -->
<vehicleMakeName />
<expressionDictName>null</expressionDictName>
...
On the right side of the key, { 1, 2, 3 }, for example, are the index's of the profiles you would like assigned to this vehicle. In the above example, that would equate to DEFAULT, WHELEN-295, WHELEN-CENCOM-G. Moreover, changing the order of the VCF_Files, you would change which profiles are assigned.
Both R* and LVC truncate down to 11 characters. It is important that the first 11 characters of the vehicle game name 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:Fleet will not be able to differentiate these.
The default or fallback key ['DEFAULT'] in the VCF_Assignements table should always be present and never removed. Doing so will result in issues.

Wildcards

Supported Wildcards:
  • # represents 1 or more digits.
How it works:
  1. 1.
    LVC checks for vehicle profile matching game name. e.g. ['2008fpiu1']
  2. 2.
    If not found, attempts wildcard search, meaning wildcards will be used secondary to custom profiles. e.g. ['2008fpiu#']
  3. 3.
    If not found, attempts a less specific wildcard search, leading and trailing numbers. e.g. ['#fpiu#']
  4. 4.
    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.