Download the latest script on & unzip yeva_distresscall
Drag script into your resources folder, for example on [qb] or [esx_addons] folder.
Don't forget to start the script in the config.lua if you put the script outside of that folder.
Import sql.sql to your database server.
SQL File
CREATE TABLE `distress_calls` (
`id` INT(11) NOT NULL AUTO_INCREMENT,
`identifier` VARCHAR(255) NOT NULL,
`flag` INT(11) NOT NULL DEFAULT '0',
`victim` VARCHAR(255) NOT NULL,
`message` VARCHAR(255) NOT NULL,
`location` VARCHAR(255) NOT NULL,
`distance` VARCHAR(255) NOT NULL DEFAULT '0',
`time` TIMESTAMP NOT NULL DEFAULT CURRENT_TIMESTAMP(),
PRIMARY KEY (`id`)
);
Configuration
config.lua
config = {}
config.debug = false
config.framework = 'esx' -- esx or qb
config.distress = {
job = 'ambulance', -- Job allowed to access distress calls (ambulance)
spam = true, -- Prevents spamming distress calls (false = no spam allowed)
alertlimit = 10, -- Maximum number of alerts that can be sent
signallimit = 10, -- Maximum number of signals that can be sent
cooldown = 20000, -- Cooldown time in milliseconds before sending another signal/alert
autodelete = false, -- Automatically delete calls after processing (false = no auto-delete)
notifyaction = true -- Enables notification for actions taken (true = enabled)
}
config.trigger = {
command = true, -- Allows command usage to open distress menu
commandtext = 'distressmenu', -- Command text to trigger the distress menu
usekey = true, -- Allows using a key to trigger distress actions
buttonkey = 'M', -- The key used for triggering distress actions
signalform = true, -- Enables the use of a command to trigger a distress signal form
signalcommand = '900', -- Command to trigger the distress signal form
testalert = true, -- Enables test alert functionality
cmdtestalert = 'testalert', -- Command text to test sending an alert
testsignal = true, -- Enables test signal functionality
cmdtestsignal = 'testsignal' -- Command text to test sending a signal
}