Configuration

Advanced Electrician Job is set up in its config files. It is not in the in-game /ggsettings menu. Edit the files, then restart gg_electricianjob.

#Where the settings are

#Lock the job to a job name

By default anyone can work the job. To make it a company job, set job in config/shared/general.lua:

cfg.targetSettings = {
    ["electrical"] = {
        icon = "fas fa-recycle",
        distance = 2.5,
        job = "electrician", -- your job name; nil lets everyone in
    },
}

Only players with that job can then use the worker at the Electrical Center, so hiring and firing through your framework or business script controls who can work. The job must exist in your framework.

#Jobs, levels and group size

Each job in cfg.jobTypes in general.lua has a level and a group size:

#Pay

Each job file starts with its rewards:

cfg.installationCrew.rewards = {
    money = 250,
    experience = 300,
    item_discovery_chance = 25, -- % chance to find an item on each repair
    items = {
        { item = "plastic", probability_weight = 50, min = 1, max = 3 },
        { item = "copper",  probability_weight = 25, min = 1, max = 3 },
    },
}

Pay is cash and goes up with the player's level bonus. In a group, the money is split between members when defaults.split_pay is on, and every member gets the full XP.

#Reward items

The jobs give plastic and copper, and the daily challenge in general.lua gives Plastic, Glass or Copper, with capital letters. Item names are case sensitive in most inventories. Change each item to the exact name your inventory uses, or remove the line.

#Blackouts

cfg.settings.blackout in settings.lua:

During a blackout the artificial lights go out for every player on the server.

#Use ox_lib skill checks instead of bl_ui

Installation Crew and Field Repair Technician call bl_ui minigames. To run them on ox_lib instead, open config/shared/job_InstallationCrew.lua and config/shared/job_RepairTech.lua and, in every custom = function() that uses bl_ui, replace the bl_ui line with:

local success = lib.skillCheck({{ areaSize = 70, speedMultiplier = 0.6 }}, {'w', 'a', 's', 'd'})

For example, in job_InstallationCrew.lua:

custom = function() -- Custom Skill Checks
    local success = lib.skillCheck({{ areaSize = 70, speedMultiplier = 0.6 }}, {'w', 'a', 's', 'd'})
    return success
end,

Installation Crew has this line commented out above each bl_ui call already. Field Repair Technician has three bl_ui calls (bl_ui:Progress twice and bl_ui:KeySpam). Once no bl_ui line is left, you can remove bl_ui from your server.

#Settings owners change

#utility.lua

#Vehicle keys and fuel

The job gives keys and sets fuel through core/lib/miniBridge/client.lua. It uses the first key script it finds started, in this order: bhd_garage, brutal_keys, cd_garage, F_RealCarKeysSystem, mk_vehiclekeys, mono_carkeys, MrNewbVehicleKeys, 0r-vehiclekeys, p_carkeys, Renewed-Vehiclekeys, qb-vehiclekeys, qbx_vehiclekeys, qs-vehiclekeys, tgiann-hotwire, vehicles_keys, wasabi_carlock.

Fuel works with bigDaddy-Fuel, cdn-fuel, esx-sna-fuel, frkn-fuelstationv4, lc_fuel, LegacyFuel, okokGasStation, ox_fuel, ps-fuel, qb-fuel, qs-fuelstations, rcore_fuel, Renewed-Fuel, ti_fuel and x-fuel. With any other fuel script, the job sets the game's own fuel level.