Settings

Every setting in config.lua, taken from the file itself. The comments in the file and this page always say the same thing.

`Config.Framework`

Your framework: "esx", "qb-core", "qbox", "ox" or "custom". With "custom" the resource loads public/framework.lua instead.

Setting	Default	What it does
`name`	`"esx"`
`esxMode`	`"legacy"`	Only when name is "esx": "legacy" uses the export, "old" waits for the shared object event that older forks still use.
`esxSharedObjectEvent`	`"esx:getSharedObject"`

`Config.UI`

Notifications: "ox_lib" or "custom" (loads public/ui.lua).

Setting	Default	What it does
`name`	`"ox_lib"`

`Config.Language`

Any file in languages/, without the extension.

Config.Language = "english"

`Config.Debug`

Prints what the resource is doing to the console.

Config.Debug = false

`Config.Command`

The command that opens the interface. restricted turns it into an ACE restricted command; left false the job decides who gets the list.

Setting	Default	What it does
`enabled`	`true`
`name`	`"dispatch"`
`restricted`	`false`

`Config.Dispatch`

All of these are enforced on the server. The interface only displays what it is told.

Key	What it does
`callCooldownSeconds`	how long a player waits between two own calls
`resolvedVisibleSeconds`	how long a resolved call stays in the list
`notifyOnNewCall`	notify players with the job and no interface open
`notifyCaller`	tell the caller when their call is taken and done

Setting	Default	What it does
`callCooldownSeconds`	`300`
`resolvedVisibleSeconds`	`180`
`notifyOnNewCall`	`true`
`notifyCaller`	`true`

`Config.Priorities`

Low to high, in this order. The list is the ramp, so there is nothing to sort and nothing to switch off: a dispatch without a top level is not a dispatch.

Maps a job to a service, in the order they appear in the create call form. job may be one name or a list of names if several jobs share a dispatch, for example sheriff. The other way round a job belongs to one service: named under two, the first enabled one takes it.

enabled decides whether the service exists at all: not every server runs a fire department. A player without a matching job can still create calls, they just do not get the dispatch list.

`Config.Database`

Every call is written here: who called, what for, where, who took it, and when it was accepted and resolved. Created on first start.

Setting	Default	What it does
`enabled`	`true`
`table`	`"ktx_dispatch_history"`