QBCore Frameworkqbcore.netCommunity docs
On this page

2 min read

QBCore commands

This page is pinned to server/commands.lua.

Server command ACE permission and handler checks

Conceptual diagram; verify the behavior against your installed resource version.

Register a command

QBCore.Commands.Add(name, help, arguments, argsrequired, callback, permission, ...)

Additional accepted permissions are extra arguments, for example ..., 'admin', 'god').

ParameterTypeMeaning
namestringCommand name, stored lowercased
helpstringDescription shown in the command list
argumentstableArray of { name = ..., help = ... } entries
argsrequiredbooleanWhen true, refuses with a chat error if fewer args than #arguments are supplied
callbackfunctionCalled as callback(source, args, rawCommand)
permissionstringDefaults to 'user'
...stringsAdditional permission levels that may also run it

This is a server-side wrapper around RegisterCommand. What it adds at the pinned commit:

  • Ace permissions. For any permission other than user or god, it runs add_ace qbcore.<permission> command.<name> allow and registers the command as restricted. god is skipped because it is allowed everything, and user is skipped because it maps to builtin.everyone.
  • A cancellable pre-execution event. It fires QBCore:Server:PreCommandExecution with the source, name, args, and raw command, and aborts if a handler cancels it. That is the hook for audit logging or a per-command lockout.
  • An argument count check driven by argsrequired.
  • A registry at QBCore.Commands.List, keyed by the lowercased name.

Because permission defaults to 'user', omitting it produces an unrestricted command.

QBCore.Commands.Add('routecount', 'Show active delivery routes', {}, false, function(source)
    QBCore.Functions.Notify(source, ('Active routes: %d'):format(countRoutes()), 'primary')
end, 'admin', 'god')

Argument definitions contain name and help. Use optional = true only when the callback handles the missing value. Parse numbers and validate player IDs inside the callback.

Refresh suggestions

QBCore.Commands.Refresh(source) rebuilds chat suggestions for one connected player. It requires a real player source; it is not a broadcast API. The current core has no QBCore.Commands.Remove.

Permissions

Current permission names are configured in QBCore.Config.Server.Permissions in the root config.lua and backed by ACE/principal rules in server.cfg. Check permissions again inside any command that changes privileged state.

Current core commands include tp, tpm, togglepvp, addpermission, removepermission, openserver, closeserver, car, dv, dvall, dvp, dvo, givemoney, setmoney, job, setjob, gang, setgang, ooc, and me. Inventory resources and admin resources can register additional commands; do not assume /giveitem or /ban comes from current qb-core.

Found an issue in this guide?

Send the page URL, the affected example, and a source or reproduction to the site maintainer. For a server or resource problem, use the support guide.

On this page

Leonida RP server website built with RPWebsite
RPWebsite

Advertisement · RPWebsite

Want a website for your server?

Launch a site with live player status, rules, and a join button in minutes.

Build your website