General settings

Debug Mode

Controls the level of detail logged to the console.

Turn this on if something isn't working. It will print extra messages to the console to help you or the support team see exactly what the script is doing.

• true: Enables debug prints (Recommended during setup or troubleshooting).

• false: Disables debug prints (Recommended for the live server).

Default: false

Config.InfoPrints = false

Payment Source

Determines which currency type is used for transactions within the script.

• Choose where the money gets taken from: the player's pocket (Cash) or their account (Bank).

• true: Transactions use Bank Balance.

• false: Transactions use Cash.

Default: true

Config.UseBank = false

UI Exit Key & Visual Prompts

These settings control the key used to close the menu (NUI) and the visual hint displayed to the player.

• Important: You must ensure the Key Code and the Key Label match.

• Example: If you change the key to M, you must also change the Label to a control that represents M, otherwise the game will tell the player "Press X" but the button won't work.

NUI Key Code

Defines the specific keyboard button that triggers the exit action while the menu is open.

• How to find your key: Use Keycode.info to press your desired key and get its numerical value.

Default: 88 (Represents the X key in JavaScript)

Config.KeyToExitJS = 88

Control Label

Defines the text string or icon shown in the on-screen help notification (e.g., "Press [X] to exit").

• How it works: This does not control the actual key press; it only changes the icon displayed.

• Reference: Copy the "Control Name" (e.g., INPUT_VEH_DUCK) from the FiveM Controls List.

Default: 'INPUT_VEH_DUCK' (Displays the X icon/prompt)

Config.KeyLabel = 'INPUT_VEH_DUCK'

Ready Key Configuration

Defines the key used to toggle the player's status to "Ready."

• Synchronization: Just like the Exit keys, you must update three values to change this control: the Game Key (Lua), the UI Key (JS), and the Visual Label.

• Requirement: All three must correspond to the same physical button (e.g., Spacebar).

Default: Spacebar (Lua: 22, JS: 32, Label: INPUT_JUMP)

-- Game Engine Key (Lua)
Config.ReadyKey = 22

-- User Interface Key (JavaScript)
Config.ReadyKeyJS = 32

-- Visual Helper Text
Config.ReadyKeyLabel = 'INPUT_JUMP'

Transport Mode Selector

Defines the key used to cycle through available transport types or vehicles.

• Configuration Pattern: This setting follows the same structure as the Exit and Ready keys above. You must align the Game Key (Lua), UI Key (JS), and Visual Label to the same physical button.

Default Key: TAB

The default configuration uses the TAB key for all three values.

• A. Game Key (Lua): 37 (Matches INPUT_SELECT_WEAPON / Tab)

• B. UI Key (JS): 9 (Matches JavaScript Tab keycode)

• C. Visual Label: 'INPUT_SELECT_WEAPON' (Displays the Tab icon)

-- Reference: https://docs.fivem.net/docs/game-references/controls/
Config.TransportTypeKey = 37

-- Reference: https://www.toptal.com/developers/keycode
Config.TransportTypeKeyJS = 9

-- Visual Helper Text (Icon shown on screen)
Config.TransportTypeKeyLabel = 'INPUT_SELECT_WEAPON'

Close UI key

Defines the "master" key used to close any open UI windows or menus created by the script.

• Function: This listens for the key press inside the web interface (JavaScript). It acts as a fallback to ensure the player can always close the menu if they get stuck.

• Recommendation: It is highly recommended to leave this set to 27 (The ESC key), as this is the universal standard for closing menus in PC gaming.

Default: 27 (Represents the ESC key)

-- Reference: https://www.toptal.com/developers/keycode
Config.KeyEscJS = 27