QBCORE

Here you will find a basic errors in Inventory guide to know how to respond to your tickets.

1. COULDN'T START RESOURCE

This is one of the most common mistakes, but customers often do not review their console.
This is one of the most basic protocols that must be followed, seeing an error of (Field 'QS'), we must always ask for a screenshot of the start of qs-script in the Customer console.
Visual example of an error due to lack of start of a core or base.
If the customer with this problem teaches you your console and you see that the script is not started with a message similar to this, then you must review what is the missing dependence, you can give you access to this dependence on the customer, but it is recommended to make them come back To read the documentations and guide, since it possibly led some step.
The script is not executed because I miss the screenshot-Bbasic dependence on this example,.
The dependence must always have the name that asks in the error log. In this example, it should be screenshot-basic, never screenshot-basic-main for example.

2. OKOKNOTIFY SNIPPET

Format to change the Notifications from QS scripts to okokNotify. The Notifications Functions should be in QS config.lua file.
function SendTextMessage(msg, type) --You can add your notification system here for simple messages.
if type == 'inform' then
exports['okokNotify']:Alert('info', msg, 10000, 'info')
end
if type == 'error' then
exports['okokNotify']:Alert('error', msg, 10000, 'error')
end
if type == 'success' then
exports['okokNotify']:Alert('success', msg, 10000, 'success')
end
end
Last modified 1mo ago