Bablo ResourcesDocs

Configuration

All configuration lives in two editable files: shared/settings.lua and shared/creator.lua. Everything else (jobs, grades, permissions, locations, store items, outfits) is configured in-game through the Boss Creator and saved to the database.

Changes to these files require a resource restart to take effect (restart bablo-bossmenu in the console).

Bridges

Every bridge auto-detects the first supported resource that is running, in the priority order shown — or can be forced to a specific resource name.

LUA
Settings.Appearance = 'auto'  -- clothing/appearance resource used for outfits
-- auto priority: illenium-appearance > fivem-appearance > bl_appearance
--   > crm-appearance > rcore_clothing > codem-appearance > tgiann-clothing
--   > qb-clothing > esx_skin > skinchanger
 
Settings.Inventory = 'auto'   -- inventory used for stashes, store items, deliveries
-- auto priority: tgiann-inventory > qb-inventory > qs-inventory > ps-inventory
--   > ox_inventory > origen_inventory > core_inventory > codem-inventory
 
Settings.Society = 'auto'     -- where the society/job money lives
-- auto priority: bablo-banking > qb-management > esx_addonaccount

If you force a resource by name, make sure it actually starts — a forced bridge waits for that exact resource and never falls back to another one.

Salary system

The resource can take over salary payouts from the framework, so bosses can set per-grade salaries in the boss menu and creator.

LUA
Settings.SalarySystem = {
    enabled = true,        -- master switch for the custom salary payout system
    intervalMinutes = 10,  -- how often salaries are paid out
    societyFunded = false, -- true = paychecks come out of the job's society money (skipped when it cannot afford)
    offDutyPay = false     -- true = also pay employees who are off duty (QBCore/Qbox duty system)
}
 
Settings.SalaryLimit = 25000 -- highest salary a grade can be given from the boss menu / creator

enabled = true — the resource pays every online employee on its own timer. A grade uses the custom salary set for it in the boss menu / creator; grades with no custom salary fall back to the job’s default framework payment, and jobs without a boss menu are paid their normal framework salary.

With the salary system enabled, turn the framework’s own paycheck off so nobody is paid twice — see Installation.

enabled = false — nothing here pays out and the “Set Salary” action is hidden in the boss menu. The framework handles salaries exactly as it did before (grade salaries set in the creator are still written into the job data, so the framework’s own paycheck keeps using them).

Store deliveries

LUA
Settings.OrderCheckMinutes = 10 -- how often the server checks for due store orders

Orders are stored with a delivery time; this only controls how often that list is polled. An order can therefore land up to this long after its delivery time (a 2-minute item on a 10-minute check arrives in 2–12 minutes). Lower it for punctual deliveries, raise it to do fewer database queries.

History retention

Old statistics rows are deleted automatically on startup:

LUA
Settings.RevenueHistoryDays = 30      -- how long to keep revenue data (in days)
Settings.AttendanceHistoryDays = 14   -- how many days of attendance history to keep
Settings.TransactionHistoryDays = 30  -- how many days of transaction history to keep

Debug

LUA
Settings.Debug = true -- verbose console logging

Set Settings.Debug = false on production servers to keep the console clean.

Boss Creator command

Configured in shared/creator.lua:

LUA
Creator.Command = "bosscreator"    -- the command that opens the Boss Creator
 
Creator.UsePermissions = true      -- false = everyone can use the command
Creator.Permissions = {
    "admin",
    "superadmin"
}

On QBCore and Qbox, the listed groups are checked against framework permissions and ace permissions (god, admin and command are always accepted as well). On ESX, the player’s group must exactly match one of the listed groups.