❓Frequent Questions

¿Why the alert is not being triggered with my robbery script?

If the alert is not running when a theft is executed, it is very possible that it is because you do not have the export/event added within that script, here is the list of exports to be able to add alerts.

¿Why I can't see buttons to add data in the criminal code?

QBCore

In qbcore you can define which ranks are bosses, if you do not have a rank that is considered a boss you will not be able to see the criminal code buttons.

Here we show an example where rank 4 is considered a boss and therefore will be able to see the buttons to add criminal code.

qb-core/shared/jobs.lua

police = {
	label = 'Law Enforcement',
	type = 'leo',
	defaultDuty = true,
	offDutyPay = false,
	grades = {
		['0'] = { name = 'Recruit', payment = 50 },
		['1'] = { name = 'Officer', payment = 75 },
		['2'] = { name = 'Sergeant', payment = 100 },
		['3'] = { name = 'Lieutenant', payment = 125 },
		['4'] = { name = 'Chief', isboss = true, payment = 150 }, -- BOSS
	},
},

ESX

¿How to change department/jurisdiction of a job?

QBCore

By default all ranges will have LSPD as department, you can change it by adding a field type in each range.

Example making rank 0, 1, 2, 3 be from department LSSD and rank 4 be from department BCSO

police = {
	label = 'Law Enforcement',
	type = 'leo',
	defaultDuty = true,
	offDutyPay = false,
	grades = {
		['0'] = { name = 'Recruit', payment = 50, type = "LSSD" },
		['1'] = { name = 'Officer', payment = 75, type = "LSSD" },
		['2'] = { name = 'Sergeant', payment = 100, type = "LSSD" },
		['3'] = { name = 'Lieutenant', payment = 125, type = "LSSD" },
		['4'] = { name = 'Chief', payment = 150, type = "BCSO", isboss = true, },
	},
},

ESX

SQL Error illegal mix of collations

This error occurs when a JOIN is performed between columns that use different collations. In our case, this happens when querying debtors by joining the origen_police_bills table with players or users.

To resolve this issue, make sure all text columns involved in the join use the same collation (e.g. utf8mb4_general_ci or utf8mb4_unicode_ci).

⚠️ Important: Make a backup before applying any collation changes—especially if your database contains Chinese, Japanese, or other non-UTF8MB4 characters.

QBCore

ALTER TABLE origen_police_bills CONVERT TO CHARACTER SET utf8mb4;
ALTER TABLE players CONVERT TO CHARACTER SET utf8mb4;

ESX