Bridge Files

For the developer on your team: the files you may edit, and what each bridge file has to provide so the panel keeps working. Everything else in the resource is protected by asset escrow.

#The open files

#Rules

• Keep every function name and its arguments. The protected code calls them by name.
• Return what the tables below say.
• Places made for your own script are marked [[ ADD YOUR … HERE ]].
• Restart 5code-adminpanel after an edit.
• Keep a copy of your edits before you update: see Updating.

#Exports and events

5code-adminpanel has no exports and no events meant for other scripts in this version. The bridge files are the only place to connect your own scripts.

#bridge/framework_server.lua

What the tables hold (the same on every framework):

-- Bridge.GetLiveProfile(src)
{ citizenid, charName,
  job = { name, label, grade, gradeLabel, onDuty },
  money = { cash = 0, bank = 0 },      -- one entry per account
  callsign, dead, cuffed }

-- Bridge.SearchOffline(query, limit): a list of
{ identifier = 'license:…', citizenid, name, account, job, lastSeen }   -- lastSeen in unix seconds

-- Bridge.GetOfflineProfile(identifier, citizenid)
{ citizenid, name, account, job = { name, label, grade, gradeLabel }, money = { … }, callsign, lastSeen }

Bridge.Framework holds 'qb', 'qbx' or 'esx'. Bridge.CreateCallback and Bridge.RegisterCommand belong to the panel itself: leave them as they are. Bridge.GetPlayerByCitizenId is in the file, but the panel does not call it in this version.

More on the frameworks: Frameworks & Inventories.

#bridge/framework_client.lua

The panel uses the first two for the player's ticket window: it comes back after a login and closes on a logout. Bridge.GetPlayerData and Bridge.OnJobUpdate are in the file, but the panel does not call them in this version. Bridge.TriggerCallback belongs to the panel itself: leave it as it is.

#bridge/notify.lua

How to add a notify script: Notifications, Chat & Weather.

#bridge/ambulance.lua

Used by Revive on a player and by Revive me. The panel brings the character back to life and fills the health itself. This file only tells your ambulance script, which keeps its own "this player is dead" state.

Some ambulance scripts are told on the server, others in the player's game. So the file runs on both sides and has one function for each:

Out of the box:

Nothing to choose: a script that does not run on your server is skipped.

Another ambulance script goes at one of the two marked places [[ ADD YOUR AMBULANCE SCRIPT HERE ]]. Its own docs tell you which side it is told on.

Told in the player's game:

function Ambulance.Revive()
    TriggerEvent('hospital:client:Revive')   -- qb-ambulancejob
    TriggerEvent('esx_ambulancejob:revive')  -- esx_ambulancejob (ESX up to 1.13)

    if GetResourceState('my-ambulance') == 'started' then   -- your ambulance script
        TriggerEvent('my-ambulance:revive')                 -- use the event from its own docs
    end
end

Told on the server:

function Ambulance.ReviveServer(target)
    -- ... the lines for qbx_medical and esx_death stay as they are ...

    if GetResourceState('my-ambulance') == 'started' then   -- your ambulance script
        exports['my-ambulance']:Revive(target)              -- use the export from its own docs
    end
end

my-ambulance, its event and its export are placeholders.

#bridge/appearance.lua

Used by Reset look, the way back from Set Model. The panel stores no looks. It asks your clothing script to load the player's own saved character: model, face, hair and clothes.

Out of the box, in this order: illenium-appearance, qb-clothing, then ESX skinchanger with esx_skin. Another clothing script goes at the marked place [[ ADD YOUR CLOTHING SCRIPT HERE ]], just before the last return false:

    if running('my-clothing') then
        exports['my-clothing']:reloadSkin()   -- the call that loads the player's saved character
        return true
    end

    return false

my-clothing and its export are placeholders. running(name) is a helper in the file: it is true when that resource is started.

#bridge/inventory.lua

The panel calls Inventory.AddItem for Give Item and Inventory.System for the Inventory button. The other three are in the file, but the panel does not call them in this version.

How to add an inventory: Frameworks & Inventories.

#bridge/jail.lua

How to add a prison script: Prison Scripts.

#bridge/world.lua

Keep the World.own table. The panel stores in it what it set last, and uses it for players who join later.

How to add a sync script: Notifications, Chat & Weather.