Core concepts

qb-core initializes the framework object, shared definitions, client/server functions, player state, commands, events, and its built-in DrawText NUI. Treat each API as commit-specific.

Start here

• Core object — request the whole object or selected sections
• Player data — character state exposed by the framework
• Functions — client and server helper map
• Events — lifecycle and update signals
• Shared data — items, jobs, gangs, vehicles, weapons, and locations
• Shared mutation exports — server-side runtime additions and updates
• DrawText helpers — core NUI text exports and events

Integration boundary

Acquire the object through the qb-core export and request only the sections your resource uses:

local QBCore = exports['qb-core']:GetCoreObject({ 'Functions', 'Shared' })

Verify function and event behavior in the current qb-core source . A client event is a request, not an authorization boundary; validate identity, permission, state, proximity, and values on the server.