The server key belongs to a different CFX account than the one that bought Text UI, or the protected files were modified or re-uploaded through FTP in text mode. Download it again from Granted Assets with the purchasing account, upload it in binary mode, and use a server key generated by that same account.

The script calling the export started before Text UI, or Text UI is not running. Move ensure qs-textui above every script that uses it, check the folder is named exactly qs-textui, and look further up the server console for the reason it did not start.

Only the update check failed — the server could not reach GitHub. Text UI itself works normally, and the message can be ignored.

A prompt has a job other than 'all', but no framework was detected. Either your framework starts after Text UI — move it above ensure qs-textui — or the server is standalone, and the prompt needs job = 'all'. A framework under another resource name can be added as shown in Integrations.

Go through these in order:

• It has no displayDist. Without it the prompt is skipped — with debug on, the console prints No displayDist.

• Its job is not your character's job, or its canInteract returns false.

• The id was already used. A second create3DTextUI with the same id is ignored, so the first one's coordinates and settings stay.

• The coordinate is under the floor or inside a wall, so it is never on screen. Raise z by half a metre.

• Another script has the mouse cursor open — an inventory or a menu. Prompts hide until it closes, by design.

• The prompt has a key but no keyNum. key is only the label; keyNum is the control that is listened to.

• Another option is selected. With several prompts in reach only the highlighted one responds — use the arrow keys.

• On a prompt on a player, enableKeyClick is missing. It must be true there.

• The event name in triggerData is wrong, or the event is server-side and isServer is not true.

• On-screen prompts from displayTextUI never handle a key — your script checks the key itself.

A 3D prompt was created without a key. Every prompt needs a key label — also a display-only one — so pass key = 'E' or any label, then restart qs-textui. If it comes from an old script through DrawText3D, use the wrapper, which fills in a key.

Prompts created through exports live in Text UI's memory, and a restart clears them. Restart the scripts that create them too, or have them recreate their prompts when Text UI starts — see When qs-textui Restarts.

Correct behaviour. Whenever another script has the mouse cursor, Text UI hides itself so it never covers that window, and comes back when it closes. The same happens in the pause menu and during screen fades.

The script calls drawText3D directly and never deletes the label. Use the full wrapper, which removes the label a few frames after the script stops drawing it, or call DeleteDrawText3D yourself.

They share an id. Every prompt needs its own — add the door number, the shop name or the entity to it: 'door_' .. doorId.

GTA colour codes are supported from version 1.2.27. Check the version in fxmanifest.lua and download the latest one from the CFX Portal.

A position that is not one of the nine names falls back to Config.DefaultAlign — left or right from QBCore, for example. Use the names listed in Screen Position, or the mapping in Integrations. In the Cyberpunk style, the dialogue sits at Config.CyberpunkTextUI.align unless the script chooses.

shared/config.lua is read when qs-textui starts. Restart it after every edit — and then restart the scripts that create prompts through exports, because the restart clears them.

The server key belongs to a different CFX account than the one that bought Text UI, or the protected files were modified or re-uploaded through FTP in text mode. Download it again from Granted Assets with the purchasing account, upload it in binary mode, and use a server key generated by that same account.

The script calling the export started before Text UI, or Text UI is not running. Move ensure qs-textui above every script that uses it, check the folder is named exactly qs-textui, and look further up the server console for the reason it did not start.

Only the update check failed — the server could not reach GitHub. Text UI itself works normally, and the message can be ignored.

A prompt has a job other than 'all', but no framework was detected. Either your framework starts after Text UI — move it above ensure qs-textui — or the server is standalone, and the prompt needs job = 'all'. A framework under another resource name can be added as shown in Integrations.

Go through these in order:

• It has no displayDist. Without it the prompt is skipped — with debug on, the console prints No displayDist.

• Its job is not your character's job, or its canInteract returns false.

• The id was already used. A second create3DTextUI with the same id is ignored, so the first one's coordinates and settings stay.

• The coordinate is under the floor or inside a wall, so it is never on screen. Raise z by half a metre.

• Another script has the mouse cursor open — an inventory or a menu. Prompts hide until it closes, by design.

• The prompt has a key but no keyNum. key is only the label; keyNum is the control that is listened to.

• Another option is selected. With several prompts in reach only the highlighted one responds — use the arrow keys.

• On a prompt on a player, enableKeyClick is missing. It must be true there.

• The event name in triggerData is wrong, or the event is server-side and isServer is not true.

• On-screen prompts from displayTextUI never handle a key — your script checks the key itself.

A 3D prompt was created without a key. Every prompt needs a key label — also a display-only one — so pass key = 'E' or any label, then restart qs-textui. If it comes from an old script through DrawText3D, use the wrapper, which fills in a key.

Prompts created through exports live in Text UI's memory, and a restart clears them. Restart the scripts that create them too, or have them recreate their prompts when Text UI starts — see When qs-textui Restarts.

Correct behaviour. Whenever another script has the mouse cursor, Text UI hides itself so it never covers that window, and comes back when it closes. The same happens in the pause menu and during screen fades.

The script calls drawText3D directly and never deletes the label. Use the full wrapper, which removes the label a few frames after the script stops drawing it, or call DeleteDrawText3D yourself.

They share an id. Every prompt needs its own — add the door number, the shop name or the entity to it: 'door_' .. doorId.

GTA colour codes are supported from version 1.2.27. Check the version in fxmanifest.lua and download the latest one from the CFX Portal.

A position that is not one of the nine names falls back to Config.DefaultAlign — left or right from QBCore, for example. Use the names listed in Screen Position, or the mapping in Integrations. In the Cyberpunk style, the dialogue sits at Config.CyberpunkTextUI.align unless the script chooses.

shared/config.lua is read when qs-textui starts. Restart it after every edit — and then restart the scripts that create prompts through exports, because the restart clears them.