Common Errors
No such export Notification in resource vms_notify
Open config file of the script.
Search for
Config.Notification
.Remove
exports['vms_notify']:Notification(...)
.Add trigger/export from your notification system. (If you are using a custom notification system, go to the documentation of the creator of these notifications and implement the appropriate event or export)
Config.Notification = function(message, time, type)
if type == "success" then
-- exports['vms_notify']:Notification("MARKETPLACE", message, time, "#36f230", "fa-solid fa-store")
-- DEFAULT ESX Notification:
TriggerEvent('esx:showNotification', message)
-- DEFAULT QB-Core Notification:
TriggerEvent('QBCore:Notify', message, "success", time)
elseif type == "error" then
-- exports['vms_notify']:Notification("MARKETPLACE", message, time, "#f23030", "fa-solid fa-store")
-- DEFAULT ESX Notification:
TriggerEvent('esx:showNotification', message)
-- DEFAULT QB-Core Notification:
TriggerEvent('QBCore:Notify', message, "error", time)
elseif type == "info" then
-- exports['vms_notify']:Notification("MARKETPLACE", message, time, "#4287f5", "fa-solid fa-store")
-- DEFAULT ESX Notification:
TriggerEvent('esx:showNotification', message)
-- DEFAULT QB-Core Notification:
TriggerEvent('QBCore:Notify', message, "primary", time)
end
end
You lack the required entitlement
If you are displaying this error, it means that you do not have access to the script, if freshly after purchase you added the script to the server without restarting the server, you need to restart it because your server license key must refresh the scripts available to the server.
If the error still occurs, verify that your license key from the server matches the one on which you have purchased the scripts.
Make sure you haven't deleted the .fxap file - if there is one, download it again from keymaster and update this file
syntax error near '<\1>'
Check if your artifacts are not too old, to find out type
version
in the server console you will receive feedback with the version number, what you need to know is that artifacts for servers are created by the community, so some versions may turn out to be faulty, we recommend using LATEST RECOMMENDED artifacts which you can easily download using the blue button at the top of the page. FiveM artifacts: Linux, Windows
Changed key does not change
We use RegisterKeyMapping for performance purposes to dispense with the 0 tick loop so when you entered the server with the previous key, when you change the key it will not change automatically because it has already been saved to your client files, for new players it will be the key you set as the latest one.
To change the key at your game to the newly set one, you can do it in two ways:
Changing the key in the game settings
Go to game settings (ESC)
Then enter the Key Bindings section and the FiveM
Find the key by resource name and change it.
Remove the key in the game files
Exit FiveM
Navigate to the fivem.cfg file on the path
C:\Users\vames\AppData\Roaming\CitizenFX\fivem.cfg
Find the lines relevant to the resource name and delete them.
Last updated