FAQ

Can I use it as a complete replacement for ox_lib UI?

Yes. nxs_ui includes overrides for standard ox_lib UI modules (Notifications, Context Menus, Input Dialogs, Progress indicators, Menus, Radial Menus, Skill Checks, and Text UI). By adding @nxs_ui/init.lua to your script manifests, your scripts will automatically use the Nexus UI layout instead of the default ox_lib UI, without needing any code refactoring.

How do I disable a specific component?

You can disable specific UI component overrides by declaring the nexus:disabledComponents convar in your server.cfg before the resource starts. For example, to keep the default ox_lib radial menu, add:

setr nexus:disabledComponents '{"radial": true}'

Refer to the Installation page for the full list of component keys.

Can I rename the resource folder?

Yes. You can rename the resource folder to whatever you prefer. However, keep in mind:

• If you use direct exports (e.g., exports.nxs_ui:notify), you will need to change the resource name in the export calls to match your new folder name.
• If you use the ox_lib wrapper overrides (@nxs_ui/init.lua), it automatically resolves the new resource name internally, so no changes are needed.

Does it support markdown?

Yes. Text rendering across notifications, context menus, list menus, alert dialogs, and progress labels supports standard markdown tags (such as **bold**, *italics*, and `code snippets`).

Is the source code open?

The UI bundle (under the web/ directory) and client-side modules are escrow protected by Cfx.re. However, configuration files like config.lua and initialization scripts like init.lua are completely escrow-ignored and open-source, allowing you to tweak colors, options, and setup behaviors.

Need help with something else?

If you are experiencing issues or have ideas for new features, join our Discord  and open a support ticket.