General information

Most errors come from a bad update or hand-edited code. If you hit an error that isn’t covered below, test with the default resource first.

Which frameworks are supported?

ESX (es_extended), QBCore (qb-core) and Qbox (qbx_core). The framework is detected automatically at startup — whichever one is running is used, and Qbox is detected natively (not through its qb-core compatibility layer). Make sure the framework starts before bablo-bossmenu.

Which dependencies are required?

ox_lib and oxmysql are required. A target resource (ox_target or qb-target) is needed for target, ped and prop interactions — TextUI zones work with ox_lib alone.

Which inventories are supported?

tgiann-inventory, qb-inventory, qs-inventory, ps-inventory, ox_inventory, origen_inventory, core_inventory and codem-inventory. Auto-detected in that priority order, or force one with Settings.Inventory in shared/settings.lua. The inventory powers job stashes and store deliveries.

Where is the society money stored?

In one of: bablo-banking, qb-management, or esx_addonaccount — auto-detected in that priority order (force one with Settings.Society). With bablo-banking, a society account is created automatically on the job’s first deposit. With esx_addonaccount you must add a society_<job> row to the addon_account table yourself.

Which clothing resources work with outfits?

illenium-appearance, fivem-appearance, bl_appearance, crm-appearance, rcore_clothing, codem-appearance, tgiann-clothing, qb-clothing, esx_skin and skinchanger — auto-detected in that priority order, or force one with Settings.Appearance.

Do I need to import any SQL?

No. All tables are created automatically on first start. On ESX, jobs created in the Boss Creator are also written to the standard jobs / job_grades tables so they persist like any other ESX job.

Can I run boss menus for multiple jobs?

Yes — every job gets its own independent boss menu, locations, grades, store and statistics. Create as many as you want in the Boss Creator. Players interact with the menus of their currently active job.

Who can open the Boss Creator?

Players in the admin or superadmin group by default — configurable via Creator.Permissions in shared/creator.lua. On QBCore and Qbox, ace permissions (god / admin / command) are also accepted. See Boss Creator.

Only through locations placed in the Boss Creator — a target zone, a TextUI zone, a ped, or a prop. There is no command or keybind for players. It opens for the grades selected in the creator, any grade holding at least one permission, and always the highest grade.

Can I change what the “hours” statistic counts?

Worked hours count the time an employee is online while holding the job (flushed to the database every 5 minutes). Duty status doesn’t affect it — only the salary system checks duty.

How do I translate the resource?

Copy locales/en.json to your language code (e.g. locales/de.json), translate it, and set the ox_lib locale convar in your server.cfg: setr ox:locale de. The file covers the interaction labels (target), every notification (notify) and the full boss menu interface (ui). Untranslated keys automatically fall back to English. The Boss Creator (admin tool) is not translated.

Yes — see Events for the client events you can trigger to open the boss menu or the creator programmatically.