Skip to main content
ESX v2 is not supported by this submodule and will not function. Only ESX v1 is supported.

Activation Guide

  1. Download and Install the Resource

This submodule is already enabled by default when installing the Sonoran CAD FiveM resource.

  1. Adjust the Configuration

The CAD display settings are stored inside of the /configuration/frameworksupport_config.lua file.

  1. Ensure Players are Linked

Ensure the players have already linked their CAD for this integration to work.

Configuration

Review the frameworksupport_config.lua file to configure the submodule to behave how you like. The file is well documented. Please review all the settings!

Auto-Fines

Civilians in-game can be automatically fined for the crimes they commit based on fineable forms submitted. To do so, simply enable issueFines in the config and add a list of custom record types to the fineableForms array. Ex: fineableForms = {"Arrest Report", "Speeding Citation"} The fines are pulled from your custom records:
  • Charges section -> Fine field
  • Speed section -> Fine field

Usage

This submodule can be used to issue fines to players when reports/records are entered into the CAD that include fines. You can configure the reports/records that are finable in the configuration. This submodule also adds support for ESX that other submodules can take advantage of. Currently, the following submodules are supported:
  • dispatchnotify
    • Adds the ability to show character names in dispatch responses (officer names)
    • Adds the ability to restrict functionality to certain jobs (like police). See the dispatchnotify documentation for how to do this.
  • callcommands
    • Adds the ability to show character names for the caller when they use /911. This is automatic when the submodule is installed.
  • livemap
    • Adds the ability to show character names on the map.

Legacy ESX Support

Legacy ESX Support utilizes MySQL-Async in order to get character information from your database directly. ESX requires this in older versions so this shouldn’t be an issue.
This is mainly for ESX v1 releases that were made before the character system implementation using only the users database table. These versions of ESX used the users table only for player information of active characters and a characters table that held all character information (active and secondary characters of your players). Due to different handling of character information such as first name and last names, this option allows you to use esxsupport submodule with older “Legacy” ESX v1 releases. Simply set legacyESX to true in your config_esxsupport.lua