Installation guide

Welcome to the Brutal Executions installation guide, here you can learn how to completely install our asset.

If you don't have any experience in development we are highly recommend to follow each step in this documentation, and if you have a developer ask them to install the script for you as they have more experience.

---

Asset download

Once the purchase is made on our official website, you will receive your asset directly in your Keymaster, in the Granted Assets panel you will see the asset, download it and do the following steps to install it correctly.

• Put the script folder to your server.

• Start the script in the server.cfg. (ensure brutal_executions)

• Restart your server! (And you get permission to use the script)

Click here if you haven't installed any script ever

---

Upload the SQL

Do not rename your previous SQL or columns to adapt them to this system, use the complete database without making use of edits in your old databases.

ESX

ALTER TABLE `users` ADD COLUMN `brutal_executions` longtext NULL DEFAULT NULL;

QBCORE

Click here if you don't know how to upload the sql, here is a quick guide

---

Upload the items

If you don't have the items integrated correctly, you will receive random errors.

Check that you don't have duplicate items in your inventory or database before integrating them, otherwise you might have some errors.

This asset depends on certain items for its operation, so don't forget to integrate all items correctly into your database or inventory system, depending on how you use your server.

If your inventory is not among the following, you can create the file yourself using the examples of each item by displaying any of the following tabs.

Items for esx_inventory

INSERT INTO `items` (`name`, `label`, `weight`, `rare`, `can_remove`) VALUES
('pliers ', 'Pliers ', 1, 0, 1),

Items for qb_inventory

['pliers'] 			 		 = {['name'] = 'pliers', 						['label'] = 'Pliers', 						['weight'] = 1, 		['type'] = 'item', 		['image'] = 'pliers.png', 				['unique'] = false, 	['useable'] = false, 	['shouldClose'] = true,	   ['combinable'] = nil,   ['description'] = ''},

Items for qs_inventory

["pliers"] = {
    ["name"] = "pliers",
    ["label"] = "Pliers",
    ["weight"] = 10,
    ["type"] = "item",
    ["image"] = "pliers.png",
    ["unique"] = false,
    ["useable"] = false,
    ["shouldClose"] = true,
    ["combinable"] = nil,
    ["description"] = "Not have"
},

Items for ox_inventory

["pliers"] = {
    label = "Pliers",
    weight = 1,
    stack = true,
    close = false,
},

51KB

pliers.png

image

Open

---

Lockpicking Minigame

6KB

lockpick-main.zip

archive

Open

---

Asset positioning

Correctly position the assets in the server.cfg by following this step, if something goes wrong you will probably get errors about exports not found, do not skip this step!

-- First we will start the cores, never below
ensure es_extended or qb-core

-- The Notify / TextUI or target system / Progressbar / Inventory / Billing have to be above our asset
ensure [notify]
ensure [inventory]
ensure [billing]
ensure [textui] -- or target system 

-- Start the Brutal Executions at the end
ensure brutal_executions

---

Setting the loaded event

If you are using a multicharacter system then this step is really important to make our script working propetly! If you don't use any or the loaded event is the same as the basic core one then you are done with this step.

In the client-core.lua file go to the LoadedEvent variable and if you are using a different event then paste there your event which is used on your server.

client-core.lua

---

Checking the Config file

Please make sure that you go through the whole file during the installation and check everything. It is one of the most important things as if you miss this step the script might won't work propetly.

Most important steps

The most important things always at the top of the config so pay the most attencion to these elements.

Setting the Core

Set your server's core wether it's using es_extended or qb-core, other cores aren't supported .

Setting the Notify

If you are using the Brutal Notify then it is good news, you don't have to do anything. If you aren't then set the BrutalNotify value to false in the config and set up your own notify in the cl-utils.lua

---

If you got any error

If you followed the installation guide and the script still don't work or you get any errors the please check the common errors, here in the docs and in our discord server, for more informations.