ox_lib

It depends on the resource. Cube Multicharacter ships its own NUI and does not depend on the ox_lib menus.

Own interface versus borrowed menus

ox_lib is the de facto library for menus, notifications and utilities in the FiveM ecosystem, and plenty of resources simply assume it. We treat it as a per-product decision rather than a dogma.

Cube Multicharacter is the clearest case: the NUI is its own, so it depends on neither esx_context nor the ox_lib menus. The identity form lives inside the resource, which also means you do not need esx_identity or qb-identity to have the full character creation flow.

Cube Garage follows the same line with its Preact and Tailwind interface on top of our own design system, and Cube Scammer builds its NUI on Vite and Preact.

Why this matters to you

Because a UI library dependency is the most common source of breakage when an update you do not control lands. A resource with its own NUI breaks when we break it, and then we are the ones who fix it.

That does not mean ox_lib is a problem or that we avoid it on principle. It means every product page lists its exact dependencies and minimum versions, so you know up front what your server needs.

Frequently asked questions

Do I need ox_lib to use Cube Multicharacter?

Not for the interface: the NUI is its own and uses neither the ox_lib menus nor esx_context. The exact dependencies of each resource are on its product page.

Do your resources break if I update ox_lib?

The ones with their own interface do not depend on that update. Either way, updates are free for life: if something breaks with a new version, we publish the fix.