Getting help

Most problems are fixed by the checks below. If yours is not, open a ticket in our Discord and we will help you.

#First checks

#Start order

A script starts only after everything it depends on. In server.cfg, oxmysql, ox_lib, your framework, inventory and target come first, then gg_lib if the script uses it, then the script. See Start order.

#Renamed folders

Keep every folder name exactly as it comes in the download: gg_boosting, not gg_boosting (1) or gg_boosting_new. The same goes for dependencies, for example bl_ui, not bl_ui-2.1.0. Scripts find each other by name.

#Missing dependency

Look in the server console for a red line naming a resource. Older scripts print [ RESOURCE NOT FOUND ] with the missing category. Scripts on gg_lib say when gg_lib is too old. Install what is missing and start it above the script.

#Items not added

If an item does nothing or shows without an image, it is not in your inventory yet. Add the script's items from its Items page, then restart the server.

#Two copies of a script

A backup or old copy anywhere inside resources breaks the script. Keep one copy and move backups out of resources.

#Cache

After an update, stop the server, delete the cache folder in your server data folder (next to resources) and start again. If the game still shows the old version, close FiveM and delete server-cache and server-cache-priv in %localappdata%\FiveM\FiveM.app\data.

#Anticheat

Stop your anticheat fully to test: comment it out in server.cfg and restart. An exception list is not enough. If the script works without it, allow the script in your anticheat's settings.

#Escrow errors

"You lack the required entitlement" and "Failed to verify protected resource" have their own fixes on Downloads and updates.

#Read the consoles

• Server console: in txAdmin open Live Console. Run the action that fails, then copy the red lines and any line with the script's name.
• F8 console: in game, press F8. Errors on the player's side show here.

Send the text, not a photo of the screen, and include the lines from the moment it went wrong.

#Find the version

Every script has a version line at the top of its fxmanifest.lua, for example version '2.0.14'.

For scripts on gg_lib, Script Studio shows the version at the bottom of the menu's sidebar and on the script's Update Log page. The gg_lib version is on Home.

#Copy a support bundle

Scripts on gg_lib can collect everything we need in one click. In /ggsettings, open Help → Still stuck? → Copy support bundle, or press the clipboard button beside refresh at the top of any page. Paste it into your ticket. Discord sends a long paste as a message.txt file, which is what we want.

The bundle holds your versions, what gg_lib connected to, the recent server console and what GG scripts printed on your screen. The server console part is included only if your role has the Logs tool.

#Open a ticket

Join the Discord and open a support ticket. Have these ready:

• Your Tebex transaction ID (tbx-...) from the receipt email.
• Your framework: QBCore, Qbox or ESX.
• Whether you run an anticheat.
• What you expected, what happens instead and when it started.
• The script version and the console errors, or the support bundle.
• A screenshot or short clip, if you can.

Ideas for new features are welcome in the suggestions channel.