💻Advanced Configuration
Debugging and advanced configuration functionality.
Debug Mode
To temporarily toggle debug mode use chat command /lvcdebug
this resets on resource restart. For persistent debug mode use convar below.
Resource Convars (fxmanifest.lua)
beta_checking
enables beta version notifications to server console.experimental
will mute experimental messages for server console.debug_mode
increases console logging for client, prints <gameName> of vehicle if no profile was found.
Toggling these require the refresh
command to be ran first, then restart the resource for changes to take effect.
Custom HUD
Custom Graphics
The in game siren controller display or heads-up-display UI can be modified to your liking, you will need an understanding of HTML, Javascript, and NUI.
Support is limited in this area.
Move Default HUD location
All HUD related functions/code is located in the UI folder. The default position of the HUD is set in UI/html/style.css
.
The relevant attributes are: left, top, and transform-origin.
left determines how far in percentage of the screen resolution should the HUD be placed from the left edge. If you wanted to right align the HUD you could change this to
right: XX%
, 0% being against the right edge of the display.top determines how far down from the top the HUD should be placed.
transform-origin attribute determines which way the HUD should expand on size adjustment. For a bottom right aligned HUD you would want the transform-origin to be
right bottom
. This ensures that the HUD does not expand outside of the screen space.
Custom Audio Schemes
Custom front end sound effects can be added. Create a new folder in /UI/sounds
with the desired name of your scheme.
Sound scheme names cannot have any spaces in them.
Add scheme name to <SCHEMES>
object in VCF.
Ace Menu Permissions
Set up VCF for Permission
To do this add an attribute to the associated menu item you would like to limit a profile's VCF.
In the example above, we've added Permissions="true"
after the enable attribute. It is important to note that the Enabled
attribute must be true, it acts as an end-all-be-all switch. Permissions can be added to any of the <MENU>
elements, and are optional so you only need to add this attribute to the menu items you wish to limit access to.
Add Ace Config / Permissions Lines
Change the builtin.everyone
to the ace group you'd like to authorize, just like any other resource.
Menu_Access
in both VCF and ace permissions controls the menu as a whole, so you don't need to add every menu item if you intend on disabling the menu entirely.
Last updated