Permissions

How Sky checks command permissions

Every administrator command or protected feature is gated by Config.CommandPermissions in sky_mechanicjob/config/adv_config.lua. At server start, sky_base reads that table and emits one add_ace per command × group:

Config.CommandPermissions = {
    admintuning      = { "god", "superadmin", "admin" },
    adminrepair      = { "god", "superadmin", "admin" },
    debugadminrepair = { "god", "superadmin", "admin" },
    debugstancerdefault = { "god", "superadmin", "admin" },
    migrate          = { "god", "superadmin", "admin" },
    workshopcreator  = { "god", "superadmin", "admin" },
    debugwearzero    = { "god", "superadmin", "admin" },
    debugwearzeroall = { "god", "superadmin", "admin" },
}

For the snippet above, sky_base runs at boot:

add_ace group.god         sky_mechanicjob.admintuning allow
add_ace group.superadmin  sky_mechanicjob.admintuning allow
add_ace group.admin       sky_mechanicjob.admintuning allow
… one block per command

On QBCore, sky_base additionally wires the qbcore.<group> principal for resilience. At runtime each command resolves with a single IsPlayerAceAllowed(src, "sky_mechanicjob.<command>").

If a command is not listed in Config.CommandPermissions, only the server console can use it.

Framework setup

QBox (principal prefix: group.)

Add your admin player to group.admin:

add_principal identifier.license:<license> group.admin

Reference: Qbox txAdmin permissions recipe.

QBCore (principal prefix: qbcore. or group.)

sky_base wires both group.<g> and qbcore.<g> on QBCore, so either prefix works:

add_principal identifier.license:<license> qbcore.admin

Or, if an existing admin is already online:

/addpermission 1 god

ESX Legacy (users.group)

ESX's setGroup automatically calls add_principal identifier.<license> group.<g> via es_extended, so ESX players get the same ACE principal as QBox/QBCore. Grant the group in-game:

/setgroup 1 admin

References: ESX /setgroup, ESX principals.

vRP

Set the player's group via your vRP admin tooling, then ensure the group.<g> principal is registered (vRP setups commonly add this to server.cfg).

Custom groups

To allow another group (for example supporter) to use a single command, just add it to the relevant entry:

Config.CommandPermissions = {
    admintuning = { "god", "superadmin", "admin", "supporter" },
    …
}

Then grant the player the principal the same way as above (e.g. add_principal identifier.license:<license> group.supporter), and restart sky_mechanicjob so the new wiring runs.

Activating the boss menu with /setboss

Once your admin group is set, run /setboss to grant every permission to a specific job grade:

/setboss mechanic 4

See the Commands page for the full admin command list.

Troubleshooting

Support

Need help? Our support team is always ready to assist