Skip to main content

v3.3.3

Fixed

  • QBCore and Qbox: your staff could not open the admin dashboard, even though the permissions in your server.cfg were correct. The frameworks do not agree on how a group principal is named. ESX and Qbox use group.admin, QBCore uses qbcore.admin, and that is not something you can configure away: /addpermission and QBCore.Functions.AddPermission write exactly that. QBCore also only ever links qbcore.god to group.admin, so anyone below god level was a member of no group.* principal at all and the check came back empty for them. On ESX this stayed invisible, because there the group from the users table caught it, and that fallback does not exist on QBCore. The script now registers its own ace object per group and points both spellings at it, so add_principal identifier.license:xxx group.mod and /addpermission 1 mod both get you in.

  • /adlock was dead on QBCore for the same reason. The command was only granted to group.<name>, which a QBCore admin never holds. Both spellings are granted now.

  • Access denied for command add_ace spam on every server start. FiveM checks add_ace against the resource that runs it, and no resource holds that right by default. The ace objects were therefore never actually created, every attempt was refused and only printed an error. On ESX this went unnoticed because the framework group caught it. The aces are registered through msk_core now, which is the one resource your server.cfg already grants that right, and the script checks up front whether it is allowed instead of spamming the console.

Requires msk_core 3.3.0

This release uses MSK.AddRawAce and MSK.CanAddAce, both added in msk_core 3.3.0. Update msk_core along with this script, and make sure your server.cfg has the msk_core ace lines (they are the ones the msk_core documentation has always listed and they cover every MSK script at once):

add_ace resource.msk_core command.add_ace allow
add_ace resource.msk_core command.remove_ace allow
add_ace resource.msk_core command.add_principal allow
add_ace resource.msk_core command.remove_principal allow

If they are missing nothing breaks, the script says so on start and group access falls back to your framework group.

Nothing changes for ESX servers. There is nothing to rebuild and no database change. Replace the resource files and restart it.

Group names on QBCore

QBCore's staff levels are god, admin and mod. Put the ones that should reach the dashboard into Config.dashboardGroups, admin is always allowed and user is always denied. On ESX and Qbox the names are whatever you use in your add_principal lines.

Debugging access problems

With Config.Debug = true the server prints why a player was denied and what each check answered, per group: the script's own ace, the plain group.<name> ace, the qbcore.<name> ace, the framework group and QBCore's permission list.

Changed files​

fxmanifest.lua
server/admin/permissions.lua
server/main.lua
server/admin/boot.lua
server/admin/command.lua
config/settings.lua
web/src/admin/devMock.ts