sc_textUI is a framework-independent FiveM NUI resource that displays an interaction key and message through client exports or server events. FiveMX inspected the public ScubeScripts/sc_textUI repository on 23 July 2026 at commit e97687f41b97.
Verified interface
The manifest identifies version 1.0.0, declares ui/textui.html as its NUI page and exports showUI plus hideUI. The README documents the client calls exports.sc_textUI:showUI(key, message) and exports.sc_textUI:hideUI(). Server code can trigger the corresponding client events with a player ID, key and message.
The package does not require ESX or QBCore in its manifest. Its README includes a separate example for replacing ESX TextUI functions so messages such as Press [E] to use are split into a key and label before calling the sc_textUI export.
Installation and integration
- Clone or download the creator repository and pin the reviewed commit.
- Place
sc_textUIin the resources directory and addensure sc_textUIbefore resources that call its exports. - Replace one interaction at a time and keep the original UI call available for rollback.
- Always hide the UI when the player leaves the interaction range, the resource stops or the relevant state changes.
- Test both client exports and any server-triggered messages with normal player permissions.
UX and performance checks
Inspect the prompt at 16:9, ultrawide and smaller laptop resolutions, with long translated text and different UI scaling. Confirm that prompts do not stack when two resources call the UI and that a stale prompt disappears after death, teleport, reconnect or resource restart.
The README example loops every frame while a marker is nearby. That is example integration code, not a requirement of the UI itself. Profile the resource that owns the proximity loop and avoid duplicate loops from several interaction systems.
Licence and source status
The repository includes the GPL-3.0 licence. Preserve its notices and review the obligations before distributing a modified version. FiveMX did not reproduce a formal performance benchmark; the source review confirms the interface and files, not compatibility with every UI or framework version.