FiveM UI Pack | Complete Interface Framework | Nexus Studios

[Nexus-Studio]

Nexus - UI Pack

A modern UI framework designed for seamless interactions, premium visuals, and complete customization.

Links

Youtube : Teaser
Purchase: Tebex [19.99$]
Docs: Here!
Questions?: Discord

---

OVERVIEW

NXS UI Pack is a modern UI framework built for immersion, performance, and complete customization. Designed as a powerful standalone solution with optional ox_lib compatibility, NXS UI Pack delivers refined design, smooth animations, and a consistent user experience across every interface.

NXS UI Pack can be used as a standalone resource or alongside ox_lib, ESX, QBCore, QBox, and custom frameworks. Any references to ox_lib are intended solely to describe compatibility and replacement of the visual interface

BUILT FOR IMMERSION

Created with attention to detail and user experience in mind, NXS UI Pack transforms everyday gameplay interactions into something modern, responsive, and enjoyable. Every component is designed to feel polished, lightweight, and seamlessly integrated into your server.

EXTENSIVE CUSTOMIZATION

NXS UI Pack is built with flexibility at its core. Adjust layouts, animations, colors, typography, positioning, and component behavior through simple configuration files to create a completely unique interface experience.

OPTIMIZED & FRAMEWORK FRIENDLY

• Modern and responsive UI design
• Smooth animations and transitions
• Lightweight and highly optimized
• Fully configurable system
• Supports ESX, QBCore, QBox, and custom frameworks
• Works standalone or alongside ox_lib
• Developer-friendly and easy to extend

A COMPLETE UI ECOSYSTEM

NXS UI Pack is a complete interface framework designed to provide players and developers with a cohesive, modern, and highly customizable experience across every aspect of gameplay. With optional ox_lib compatibility and standalone support, it delivers a consistent and polished user experience across your entire server.

Features

• Complete UI Framework - Modern implementations of commonly used interface components with a fresh design, improved usability, and extensive customization options.
• Standalone Framework - Functions independently or alongside ox_lib without conflicts.
• Progress Bars - Multiple animated progress bar styles with extensive customization options.
• Interactive Minigames - Redesigned minigames with responsive feedback and smooth visual effects.
• Radial Menu - Modern radial menu system with fluid transitions, category support, and intuitive navigation.
• Notifications & Alerts - Elegant notifications, confirmations, and alert dialogs with polished animations.
• Context Menus - Clean and responsive context menus designed for clarity and accessibility.
• Input Dialogs - Fully redesigned input menus with modern styling and enhanced user experience.
• Fully Themeable - Customize colors, layouts, spacing, animations, and visual styling to match your server branding.
• Localization Ready - Multi-language support powered by configurable locale files.

GALLERY

Code is accessible	Yes ( except UI )
Subscription-based	No
Lines (approximately)	2000+
Requirements	nil
Support	Yes

[Somewhereover]

@Nexus-Studio

Code is accessible Yes ( except UI )

You must give full source code, reported post

[Nexus-Studio]

The resource does not include any modified or redistributed ox_lib source code. The UI was built from scratch and only accepts ox_lib props for compatibility.

The Lua/source code for my resource is fully accessible as stated. The UI assets are proprietary and are not derived from or copied from ox_lib. Therefore, this does not fall under redistribution of ox_lib code or require releasing unrelated proprietary UI files under the ox_lib license.

[TheMaximusPrime]

Before playing on words, please understand what the license actually implies.

Your calling it an ox_lib redesign which inherently means it’s considered deritative work, hence falls under GPL v3 license. Even if you don’t call it a redesign it stays as such because it’s a modification to the original project meaning it’s still deritative work.

@Nexus-Studio

NXS UI Pack is more than just an ox_lib redesign

Under GPLv3, if you’re redistributing the software or a modified version of it, you’re required to provide recipients with the corresponding source code under the same license terms. The license is specifically designed to ensure that recipients have the same freedoms to study, modify, and redistribute the software that you received from the original project.

Work that merely uses the public API of the resource (for example, through exports or an npm package) does not, by itself, constitute derivative work.

Here’s the license text so you can do some reading, licenses are not just there to be pretty.

ox_lib/LICENSE at main · overextended/ox_lib · GitHub

[Somewhereover]

How can you build something from scratch and it still handles all the functions from lua to frontend? Hmm I think you’re a bit bsing us right now no? You’re trying to make money out of a free release for the community. Shame yourself.

[omexstudio]

The layout looks clean and easy to navigate

[Nexus-Studio]

I think there may be a misunderstanding regarding what NXS UI Pack actually is.

NXS UI Pack is not a modified distribution of ox_lib, nor does it contain or redistribute any ox_lib source code. The UI and supporting code were created from scratch. The resource simply supports integration with ox_lib and can optionally replace the visual interface while continuing to use ox_lib’s public functionality.

When I referred to it as an “ox_lib redesign”, the intention was to communicate compatibility and the ability to replace the default ox_lib visual experience, not to imply that it is a modified version of ox_lib itself.

If that wording is misleading or suggests that the project is derived from ox_lib, I’m happy to update the post and clarify the description to avoid any confusion.

[Somewhereover]

The issue is that your original post explicitly marketed the resource as an “ox_lib redesign”. If the UI, frontend structure, components, styling, Lua implementation, or other parts were derived from ox_lib and then modified, that is derivative work under GPLv3 regardless of how much was changed.

GPLv3 does not only apply when you redistribute a 1:1 copy. It also applies to modified and derivative versions. In that case, recipients must receive the corresponding source code under GPLv3 terms.

If NXS UI Pack was genuinely built entirely from scratch and only interacts with ox_lib through its public exports/events without containing any ox_lib code, then GPLv3 likely does not apply to your resource itself. However, because you advertised it as an “ox_lib redesign”, people naturally assume it is based on ox_lib. The easiest way to clear this up would be to show that no ox_lib source code, frontend code, or Lua implementation was reused and update the wording of the release post accordingly.

[Nexus-Studio]

Handling the same functionality doesn’t mean the code was copied.

The resource communicates with Lua through exports, events, callbacks, and NUI messages, which are public interfaces intended for other resources to interact with. That’s how compatibility is achieved.

ox_lib is an open-source project, which makes it possible to understand how its public interfaces work and build compatible resources around them without copying or redistributing its source code. Compatibility and code reuse are two very different things.

NXS UI Pack was built from scratch and does not redistribute or modify ox_lib source code. Its purpose is to provide an alternative UI experience while remaining compatible with existing ox_lib functionality.

If the wording in the post gave the impression that this is a modified version of ox_lib, I’ll gladly update it to make that distinction clearer.

[Somewhereover]

I think that’s where the confusion comes from.

ox_lib doesn’t just expose exports. A large part of its functionality is tightly coupled between the Lua side and the React/NUI frontend. Things like context menus, notifications, input dialogs, alerts, progress bars and other UI elements rely on specific communication between Lua and the frontend.

So the question isn’t whether compatibility can be achieved through exports alone. The question is how NXS UI Pack reproduces the same functionality without reusing any part of the original frontend implementation.

If everything was genuinely rewritten from scratch, that’s fine. But given how closely ox_lib’s UI systems are integrated with its frontend, people will naturally ask for clarification on what was actually replaced and what remains from the original implementation.

At the moment we’re basically being asked to take “built from scratch” at face value without any technical explanation of how the compatibility layer works.

[TheMaximusPrime]

It could be that we all went down different interpretations, your wording does lead us (with @wheeriam) to believe that this is “just an ox_lib” redesign. Coupled with the lack of docs and the fact that it looks like simply like a styling reskin makes us believe that it is just another redesign distributed which infringes the original works license.

If factually this is an entirely separate resource, built without any reusing LGPL v3 code then I don’t see an issue. So rewording the post would help if it is.

[Nexus-Studio]

@Somewhereover @TheMaximusPrime

I’ve updated the post to make the wording clearer and avoid any confusion regarding the scope of the resource.

I understand why the original wording led some people to interpret it as a modified ox_lib release, which wasn’t my intention. The references to ox_lib were meant to describe compatibility and the ability to replace the visual experience, not that the project was derived from or redistributing ox_lib itself.

I appreciate the feedback and have updated the post accordingly so that it more accurately reflects what the resource is

[Nexus-Studio]

Thank you for the feedback

[Ashrigs]

Clean UI

[Nexus-Studio]

Thank you for the feedback