Frameworks
How the suite behaves on Qbox, QBCore, ESX and standalone servers.
The released scripts don't depend on a framework. They look for one when they start and use it when it's there.
| Server | What happens |
|---|---|
| Standalone | Everything works. There are no framework-specific features to lose in Universal UI or Universal Targeting. |
| Qbox | A fresh Qbox ships with ox_lib and ox_target, and needs ox_lib for callbacks, zones and locales. Leave it installed. The bridge makes its UI calls render through the suite, and exports.qbx_core:Notify from the server is redirected too. |
| QBCore | Universal UI takes over QBCore.Functions.Notify, so every QBCore notification renders in the suite's style with no double pop-ups. |
| ESX | Universal UI takes over ESX's notifications the same way. Target options that use groups or items check them against es_extended. |
Target options with jobs and items
Universal Targeting understands ox_target's groups and items fields. It wires the checks to qbx_core, es_extended and ox_inventory automatically when they're running. For anything else, hand it your own checks with setRestrictionHandlers.
To keep your framework's own notifications instead, add setr universal_ui:adapters 0 to server.cfg.